- Tom: > In my view, the achilles heel of XSLT and any similar *query* > tool is that these tools are not designed to handle the > dynamics of the information being modeled -- they have at > best a very limited execution or process model. This is not > to say that such tools are useless for us, it is instead to > observe that they belong in the quiver of arrows that we use > to analyze the > *results* of running a model generated in a "full blown > programming language" from an RDF/OWL representation. +1. The key word is the "dynamics". But don't confuse the dynamic value from dynamic structure. >From _:foo _:hasValue "2" to _:foo _:hasValue "3" is dynamic value. But >From _:foo _:hasValue "2" to _:foo _:hasAnotherValue "3" is dynamic structure. SW technologies is best suited for handling the later. For the former, RDF won't make it better than existing technology, if not making it worse (performance wise). > I don't see RDF as an *alternative* to a database. It might > be an alternative serialization of a database, but I'm not > sure about even that. +1. RDF is a representation technology, not necessarily storage. XiaoshuReceived on Wednesday, 1 March 2006 15:17:01 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:16:32 GMT