> We apparently have to live with the fact that some > RDF graphs can not > be serialized in XML (or at least not in RDF/XML). Ack! Would it really have killed anyone to have a fallback position added to rdf/xml? The only way that I can think of requires OWL Lite. That is [1]: <rdf:Description rdf:about="%base;#isDefinedBy"> <owl:equivalentProperty rdf:resource="&ex;is%20defined%20by" /> </rdf:Description> <rdf:Description rdf:about=""> <base:isDefinedBy rdf:resource="%ex;/definition%20of%20subject" /> </rdf:Description> For an issue of serialization, this is a really big goof! Reasoning shouldn't be needed for such issues. It requires more complicated processors and "pollutes" the graph. Why wasn't something like the following added to rdf/xml: <rdf:description rdf:about=""> <rdf:link rdf:name="&ex;is%20defined%20by" rdf:resource="%ex;/definition%20of%20subject" /> </rdf:description> RDF/XML 2.0 should definitely have something to correct this issue. -- Jimmy Cerra [1] Given: <!DOCTYPE rdf:RDF [ <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" > <!ENTITY owl "http://www.w3.org/2002/07/owl#" > <!ENTITY ex "http://example.com/schema-uri/" > <!ENTITY base "http://.example.com/base-uri/" ]> <rdf:RDF xml:base="%base;" xmlns:base="%base;" xmlns:ex="&ex;" xmlns:owl="&owl;" xmlns:rdf="&rdf;" > __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250Received on Monday, 20 December 2004 21:17:06 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:53 UTC