- From: Jonathan Borden <jborden@mediaone.net>
- Date: Wed, 31 Jan 2001 18:27:23 -0500
- To: "Dan Brickley" <danbri@w3.org>
- Cc: <www-rdf-interest@w3.org>
Dan Brickley wrote: > > > I'm looking for people who are tracking the details of both XML TopicMaps > and the W3C XML Protocols work. > It has been suggested that XML TopicMap > syntax might provide a basis for a hypothetical "RDF 2.0" XML Syntax. > Similarly it has been suggested that the SOAP XML graph serialization > syntax might also provide such a syntax. XTM uses a simplified XLink syntax. --conversely there are people who are hoping that XTM '2.0' will be seen as an application of RDF (model and syntax). SOAP, I think, is simply akin to a very simplified RDF syntax in which the attribute abbreviated RDF form is disallowed. > > So I'm hearing from different directions that XTM may be a good fit for > RDF "2.0", and that XP Serialization may equally be an option for RDF > serialization. What I've heard suprisingly little about is the notion of > using XTM in an XP context. Hence this three-way crosspost. If anyone is > working in this area, I'd be very interested in your perspective... A primary reason why XTM and SOAP/XP are not a good fit as they are today is that XTM uses a simplified XLink which is attribute based and SOAP is element based (though one can encode anything in 'SOAP' via an extension syntax but doing this solves no problem. My personal view of RDF 2.0: 1) Keep the model 2) Fix the RDF syntax 3) Define mappings of XLink, TM, SOAP etc -- and arbitrary XML -- allowing parsing of such various syntaxes as RDF model triples -- of course by assuming rdf:parseType='Resource' and implementing XLink2RDF and fixing qname<->URI this is pretty much what you get. -Jonathan
Received on Wednesday, 31 January 2001 18:41:10 UTC