- From: Ivan Herman <ivan@w3.org>
- Date: Fri, 21 Jan 2011 11:47:30 +0100
- To: Harry Halpin <hhalpin@w3.org>
- Cc: W3C RDFa WG <public-rdfa-wg@w3.org>
- Message-Id: <E9EA2680-28F6-4A27-9DE1-D1888CCC754D@w3.org>
Harry, this is a request for clarification. For ISSUE-77 I have added, as explanation, your text: [[[ Adding in extra blank node default subjects as a feature of RDF Profiles vocabularies, i.e. to make vocabularies like OGP produce valid triples. Note that in some instances of RDFa processing the profile is retrieved anyways, so might as well make it do very useful things. ]]] But I must admit I do not fully understand what you mean. Do you mean to define, say, for <head> an automatic default subject in the form of a new blank node? If this is what you mean... The problem is that, at this moment, there *is* a default subject, namely the document itself. The typical @rel relationships, that are used in the <head>, like 'stylesheet' or 'copyright', make sense only for that subject, and they obviously would not make any sense for a separate blank node. This also means that we would seriously break deployed RDFa code. Another way of interpreting what you say is that a profile would/could also define a default subject. While that might be clear when the profile is used on <html> or even on <head> or <body>, it becomes a bit difficult if the profile is used somewhere down the XML hierarchy. But I am also not sure this would solve the Facebook issue, unless Facebook is ready to deploy a separate facebook profile. Other than that, this should be part of the default profile of HTML, in which case we would fall back on the previous problem... I may misunderstood what you meant, though. Thanks Ivan ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 21 January 2011 10:47:47 UTC