Didier PH Martin wrote:
> How would an RDF engine recognize that we are dealing with an RDF statement?
> Do we need to enclose this in an <rdf> element or is there any other rules
> an engine may use to recognize an RDF fragment.
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 .
you can do this because as Jonathan points out RDF/XML parsers will
make assumptions about the structure of XML elements being feed to
them, mapping them onto triples and reporting errors if the
structure (striping) isn't 'there'. IMO it makes for ugly markup,
but each to their own.
cheers
Bill
