15:14:38 <trackbot> Sorry, Steven, I don't understand 'trackbot, comment issue-4 The references section in the XHTML+RDFa errata and the RDFa Core 1.1 document have been updated'. Please refer to http://www.w3.org/2005/06/tracker/irc for help

Trackbot IRC Bot: Sorry, Steven, I don't understand 'trackbot, comment ISSUE-4 The references section in the XHTML+RDFa errata and the RDFa Core 1.1 document have been updated'. Please refer to http://www.w3.org/2005/06/tracker/irc for help←

15:26:33 <ShaneM> ... @profile is not currently a part of HTML5. If HTML5 adopts @profile everywhere, then we could rely upon that. If it does not, we would need to use a different name.

... @profile is not currently a part of HTML5. If HTML5 adopts @profile everywhere, then we could rely upon that. If it does not, we would need to use a different name.←

15:28:38 <ShaneM> ... Other items that should be in: Default RDFa Vocabulary / Profile. Mark has indicate that the default should ONLY be used if a page does not specify a profile. If there is a profile specification, then it should be used instead of any default profile.

... Other items that should be in: Default RDFa Vocabulary / Profile. Mark has indicate that the default should ONLY be used if a page does not specify a profile. If there is a profile specification, then it should be used instead of any default profile.←

15:36:04 <ShaneM> ivan: agree that this is a hack. Also, xmlns defines prefixes for the file that is being processed. Having those declarations leak into another document is inconsistent.

Ivan Herman: agree that this is a hack. Also, xmlns defines prefixes for the file that is being processed. Having those declarations leak into another document is inconsistent.←

15:36:55 <ShaneM> ... if I have a vocabulary document and I want to document the document itself, then I might want to use RDFa to do that documentation and bring in other vocabularies. Those vocabularies should not leak into the document that is USING the vocabulary.

... if I have a vocabulary document and I want to document the document itself, then I might want to use RDFa to do that documentation and bring in other vocabularies. Those vocabularies should not leak into the document that is USING the vocabulary.←

15:41:25 <ShaneM> manu: Just to clarify: we don't want to overload xmlns to declare tokens and prefixes in vocabulary documents. Additionally, we WANT to use RDFa to declare terms and prefix mappings in the vocabulary documents.

Manu Sporny: Just to clarify: we don't want to overload xmlns to declare tokens and prefixes in vocabulary documents. Additionally, we WANT to use RDFa to declare terms and prefix mappings in the vocabulary documents.←

15:41:39 <ShaneM> ivan: Well, isn't that the next topic? We were going to discuss JSON

Ivan Herman: Well, isn't that the next topic? We were going to discuss JSON←

15:49:22 <ShaneM> manu: There is also the cost of maintaining the JSONp file and keeping it in sync. The alternative is that you enable CORS support. Supporting CORS is potentially easier than maintaining multiple documents.

Manu Sporny: There is also the cost of maintaining the JSONp file and keeping it in sync. The alternative is that you enable CORS support. Supporting CORS is potentially easier than maintaining multiple documents.←

15:51:33 <ShaneM> ... I was opposed to that because it means an RDFa parser needs to understand multiple formats. But if it enables the javascript implementation, then it might be okay to support JSON.

... I was opposed to that because it means an RDFa parser needs to understand multiple formats. But if it enables the javascript implementation, then it might be okay to support JSON.←

15:52:43 <ShaneM> manu: Feels that the server MUST support vocabularies in both formats. If what we are trying to do is make it easy for implementors, then we want to have an RDFa mechanism all the way through. The only reason is to have the JSON support is to help javascript implementations. However, that problem can also be solved via CORS. But CORS is not widely distributed yet.

Manu Sporny: Feels that the server MUST support vocabularies in both formats. If what we are trying to do is make it easy for implementors, then we want to have an RDFa mechanism all the way through. The only reason is to have the JSON support is to help javascript implementations. However, that problem can also be solved via CORS. But CORS is not widely distributed yet.←