- From: Charles McCathieNevile <charles@w3.org>
- Date: Tue, 19 Nov 2002 12:58:17 -0500 (EST)
- To: Jeremy Carroll <jjc@hplb.hpl.hp.com>
- cc: Jon Hanna <jon@spin.ie>, RDF-Interest <www-rdf-interest@w3.org>
My personally preferred approach tends to be using linked metadata, and even metadata that isn't explicitly linked. This is because I would prefer to make metadata for information where I am not the author or someone with write access anyway. Equally, I want access to metadata provided by people other than the original authors. Cheers Chaals Jon Hanna asked: The recommendation of WG to eschew embedding in XHTML and link in the RDF instead To what extent is that long-term advice, and to what extent merely a method that allows you to deal with there not currently being any way to put RDF in an XHTML document and remain valid XHTML? so On Tue, 19 Nov 2002, Jeremy Carroll wrote in response: >We've done some work looking at this problem from an XLink perspective. > >Abstract of http://weblabsrv.cnuce.cnr.it/www2003/36.pdf >Linking is a core common technology shared between the hypertext web and the >semantic web. Extended XLinks can encode RDF graphs in the head of XHTML >documents. These XLinks carry the semantic markup related to the document, >typically using elements from Dublin Core. XLinks from the head into the >body permit the use of the document's own displayed metadata. The use of >XLink permits the use of RDF without the dreadful RDF/XML syntax. RDF/XML >does not conform to XML Schema or DTD, and hence does not embed into >validated XHTML. The XLinks are 'harvested' as RDF Statements following the >method of Daniel. RDF/XML is not fit for the purpose of layering RDF over >XML in the semantic web architecture; this need can be addressed in part by >using XLink as an XML serialization for the RDF graph.
Received on Tuesday, 19 November 2002 12:59:21 UTC