Hi Ben, happy new year... I have just read through the latest primer; can I have two minor comments? 1. I see that you have put in the role of the 'class' attribute leading to 'rdf:type'. If I look at chapters 2.5 and 2.6, in the example at the end of 2.5 you have two very similar constructions with class "val:Vevent" and class="contactinfo" but, according to the generated RDf tripls in 2.6, the first one leads to a <#xtech_conference_talk> rdf:type cal:Vevent whereas the second one does not yield any similar constraction. Is this a bug or a feature? If it is a feature, I would have hard time explaining it to an unitiated... 2. My comment on XMLLiteral is still pending[1]. I also see that there *is* a 'type' attribute that one can use to set the datatype (as an aside, I am not sure I like the word 'type' for this, it is misleading for an RDF person:-(. I did not realize that in my previous comment. In view of this and my arguments described in [1], let me rephrase my proposal: the default datatype should be 'xsd:string' (which would also mean stripping all the xml elements from the results if necessary); if one really wants xml, than setting the rdfs:XMLLiteral datatype explicitly is an option. Thanks Ivan [1] http://www.w3.org/mid/4549CAF0.8060506@w3.org -- Ivan Herman, W3C Semantic Web Activity Lead URL: http://www.w3.org/People/Ivan/ PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdfReceived on Monday, 8 January 2007 14:15:44 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:03 GMT