|
Here are a few more links to weblog posts related to the current RDF/XML/RSS buzz.
DJ has a brief introduction to RDF and its place in RSS.
Leigh Dodds writes on the problem of mining existing knowledge represented in XML and how to mine it into RDF. He notes that people will not be rewriting their data (or applications) to fit RDF; rather, RDF needs as many import tools as it can get. See also his post at Eclectic.
Dorothea seems to think along the same lines as I do, very much so, in fact.
Last, but not least, my CSS example seems to have struck a cord with Joe Gregorio.
One thing that occurred to me while I was reading Dorothea's post was that we need a way for plain XML documents to explicitly declare links to "decorated" versions. There are two natural ways this could be done. (1) An XML file can have a processing instruction linking it to another web resource, just like a <LINK> element is used by HTML pages (for example, this weblog links to my subscription list in OPML, to the RSS feed, and to my blogroll, all using the <LINK> mechanism). (2) An XML file can have a processing instruction which links to an XSLT document that, when applied to the XML document, creates another resource. You could then have an RSS 2.0 feed, for example, that says "to transform me into an RSS 1.0 document, use this XSLT", or "to transform me into an RDF document, use this XSLT".
(It is not practical to use the XML's xml-stylesheet processing instruction here, because its semantics is that of a "to display this document, first pass it through the stylesheet", which is not what we're after.)
Strangely, although both (1) and (2) seem like natural things to want to do on XML files, I couldn't find any standard saying how to do them.
|
