Hi Bill,
> With some editorial fixes, your XML produces these triples :
>
> _:j36 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
> <http://example.org/exobject> .
> _:j36 <http://example.org/ex1type> "extended" .
> _:j36 <http://example.org/exSSN> <uuid:ssn:1112223344> .
> _:j36 <http://example.org/exhasIncomeOf> "1000000" .
> _:j38 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
> <http://example.org/exHouse> .
> _:j38 <http://example.org/exhasAddress> "1234 West Ridge Road" .
> _:j36 <http://example.org/exownsHouse> _:jARP14838 .
> _:j39 <http://example.org/ex1type> "locator" .
> _:j39 <http://example.org/ex1href> "urn:csb:1263-27389" .
> _:j36 <http://example.org/exbank-transaction> _:jARP14839 .
> _:j40 <http://example.org/ex1type> "locator" .
> _:j40 <http://example.org/ex1href> "urn:csb:1263-38562" .
> _:j36 <http://example.org/exbank-transaction> _:jARP14840 .
>
>
Ok I get it. So, other XML documents may as well be processed by an RDF
parser and transformed into triples. Interesting, up to now I saw RDF in
more restrictive ways.
Cheers
Didier PH Martin
