What I'm saying is that if the XML-RDF file used as the data source contains only the element <dwc:recordedBy rdf:resource="http://people.vanderbilt.edu/~steve.baskauf/foaf.rdf#me%22/%3E there is no way for AJAX, XSLT, or anything else to know that the string for my name is "Steve Baskauf" without dereferencing the foaf.rdf file and interpreting it. Thus the rendered HTML can't display the text "Steve Baskauf" for a human user as the value of recordedBy. However, including the element rdfs:labelSteve Baskauf</rdfs:label> somewhere in the RDF+XML file makes it possible for any of the rendering methods you mentioned to get that information without dereferencing another URI and without "understanding" RDF.
This was the issue which I think this got lost somewhere earlier in the thread. Steve
Hilmar Lapp wrote:
Hi Steve:
On May 21, 2010, at 9:28 AM, Steve Baskauf wrote:
AJAX is "stupid" in the sense that it doesn't "understand" RDF. It just uses an XML file as a source of data. So an HTML file using the RDF+XML file as an AJAX data source would need to get the label information from within the particular RDF+XML file containing the representation of the GUID and not get it by dereferencing a link to another file, like the FOAF file that's the object of the dwc:recordedBy triple.
I'm not really following your argument here - maybe I'm missing some detail. RDF can be serialized to XML (and in fact your example is precisely such a serialization), so if your AJAX code needs XML as source, there is one. There are also JavaScript libraries that can invoke XSLTs on an XML source and render the resulting HTML (if that's what you need), and finally, there are also RDF->JSON converters. So I'm not sure where you see the bottleneck or hurdle.
-hilmar
=========================================================== : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : ===========================================================