13:27:33 RRSAgent has joined #rdfa 13:27:33 logging to http://www.w3.org/2011/10/06-rdfa-irc 13:27:35 RRSAgent, make logs world 13:27:35 Zakim has joined #rdfa 13:27:37 Zakim, this will be 7332 13:27:37 ok, trackbot; I see SW_RDFa()10:00AM scheduled to start in 33 minutes 13:27:38 Meeting: RDF Web Applications Working Group Teleconference 13:27:38 Date: 06 October 2011 13:27:47 Chair: Manu 13:56:18 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Oct/0000.html 13:57:32 gkellogg has joined #rdfa 13:58:34 niklasl has joined #rdfa 13:58:35 gkellogg has joined #rdfa 13:59:44 ShaneM has joined #rdfa 13:59:52 Steven has joined #rdfa 14:00:05 SW_RDFa()10:00AM has now started 14:00:13 +??P11 14:00:21 zakim, I am ??P11 14:00:31 +ShaneM; got it 14:00:31 zakim, dial ivan-voip 14:00:41 ok, ivan; the call is being made 14:00:43 +Ivan 14:00:45 +??P25 14:00:47 +??P20 14:00:50 zakim, I am ??P25 14:00:50 +manu1; got it 14:01:00 zakim, I am ??P20 14:01:01 +niklasl; got it 14:01:16 +scor 14:02:35 +??P41 14:02:59 + +1.415.686.aaaa 14:03:12 zakim, I am +1.415.686.aaaa 14:03:12 +gkellogg; got it 14:03:26 zakim, I am ??P41 14:03:26 +bergie; got it 14:04:08 +Steven 14:04:33 zakim, who is on the call? 14:04:34 On the phone I see ShaneM, Ivan, manu1, niklasl, scor, bergie, gkellogg, Steven 14:04:48 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Oct/0000.html 14:05:02 scor has joined #rdfa 14:05:39 q+ 14:05:48 I posted an announcement of ODF 1.2 to rdfa.info 14:06:07 ack niklasl 14:06:18 TOPIC: Rechartering 14:06:45 Topic: Pending technical issues 14:06:57 scribenick: ShaneM 14:07:30 +??P57 14:07:39 List of acceptable rel values. Manu has it on his list to send out an email about this. Need a volunteer to look at this. 14:07:54 inList and rev. 14:08:08 How to discuss profiles when we don't really have profiles any longer 14:08:11 also, multi-valued @about/@resource 14:09:29 MS: We should deal with these issues before we discuss the administrative issues 14:09:34 q+ to clarify what we're doing about LC 14:09:57 IH: We shouldn't put out a new last call before the task force has done anything. That wouldn't be very smart. 14:10:22 ... gkellogg's issue is something that is within the baliwick of that taskforce. 14:10:53 ... my proposal is that we get the draft done with everything sorted except the multi @about / @ resource and publish a working draft. 14:10:54 ack manu1 14:10:54 manu1, you wanted to clarify what we're doing about LC 14:11:33 MS: I agree. What I was trying to say is that we should start moving towards last call. We need to make it clear to everyone that we are planning on this. The technical issues are sorted modulo stuff on the call. 14:11:49 IH: Yes, but we should stil do a working draft so the task force has a solid thing to look at. 14:12:51 MS: I did talk with Jeni, and she thinks that we have addressed most issues already. multi about / resource has no use cases. img / src change might be requested, but we are already planning to do that. 14:13:00 +??P60 14:13:16 ... itemref-like support. We have pushed back on that. We might do something close to it with multi about / resource. 14:13:23 Zakim, +??P60 is me 14:13:23 sorry, bergie, I do not recognize a party named '+??P60' 14:13:54 Zakim, i am ??P60 14:13:54 +bergie; got it 14:14:01 MS: My concern is that we are pushing this out and creating more and more confusion in the market. 14:14:31 ... any additional changes we might make would be to address schema.org requirements. 14:15:48 MS: rough plan is have technical discussions, generate a working draft, let people know we need feedback if they have concerns before we go into third last call. 14:16:28 MacTed has joined #rdfa 14:17:07 MS: one more issue.... TimBL has some concerns about W3C specs that have no media type associated. RDFa Core 1.1 does not define a media type for XML+RDFa 14:17:14 q+ to discuss media type 14:17:37 ... The tag would like there to be some way to follow your nose from the wrapper of a document to the spec to realize what format the specification is in. 14:18:12 ... one option is to change text/html and application/xhtml+xml to say that there might be RDFa in such a document. 14:18:38 +??P63 14:18:44 IH: The HTML5 spec will eventually include RDFa. 14:18:48 MS: No, it will not. 14:18:49 Zakim, i am ??P63 14:18:49 +bergie; got it 14:19:24 ack shaneM 14:19:24 ShaneM, you wanted to discuss media type 14:19:53 ShaneM: Don't forget in Core 1.1, we also have XML+RDFa 1.1 and we don't have a media type for that... and we're not going to be able to change text/xml and application/xml 14:20:17 ShaneM: If this is a real concern, we might need to do a registration for text/rdfa+xml or application/rdfa+xml 14:20:51 Ivan: I thought registrations were pretty easy. 14:22:00 q+ 14:22:23 ShaneM: GRDDL announcement mechanism might be adequate. 14:22:29 ack gkellogg 14:23:17 GK: It seems like microdata and rdfa are at odds here. There is no way to know. Second the point of RDFa is that you can annotate any language. This puts the whole situation on its head. 14:23:50 MS: is there a way to handle this? 14:23:53 q+ 14:24:02 GK: We could parameterize them. It is supported. 14:24:12 ack niklasl 14:24:13 q+ to ask Steven about parameterization 14:24:33 NL: How is it with SVG 1.1 - does it link to RDFa 1.0? 14:24:36 Re media types, RDFa is not a set of elements, but a set of attributes. Other W3C specs that define sets of XML attributes (e.g. xml:base spec, xml:id spec, XML namespaces spec, XLink, etc) do not define media types. 14:24:55 IH: The SVG document says that there are ways to incorporate metadata via RDFa 1.0 14:25:10 q+ 14:25:39 ack shanem 14:25:39 ShaneM, you wanted to ask Steven about parameterization 14:25:58 q+ to kick back issue to HTML WG? 14:26:25 ShaneM: Steven, we talked a bit about parameterization of the media type in XHTML2... could we use that? 14:26:30 ack scor 14:26:31 SP: doesn't remember how we discussed using parameters in XHTML. 14:26:49 I remember the discussion, but not the conclusion 14:27:20 Certainly some XHTML's get announced with a parameter on the media type 14:27:23 Stephan: I dont think new media types are feasible. The browsers might take years to support it, and people wont know that they need to use it. It is also difficult to do on the server - especialy for static files. 14:28:04 ... in next drupal we need it to be as seamless as possible. It cannot be required to change based upon whether RDFa is being sent out or not. 14:28:27 ack manu1 14:28:27 manu1, you wanted to kick back issue to HTML WG? 14:28:28 MS: so we shouldn't depend upon the mime type at all? 14:28:31 Accept: application/xhtml+xml; 14:28:31 profile="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd" 14:28:32 Stephan: right. 14:28:57 MS: should we just put it back on HTML5 working group? 14:29:12 q+ 14:29:18 ack niklasl 14:29:45 ... if HTML5 references the spec then we are okay SVG already does, and other languages can do so as well. 14:30:48 Not just attributes, also elements 14:30:53 XForms has no mediatype 14:31:08 NL: Yes, I agree. Do we expect people to just use RDFa stand alone? No. 14:31:16 SM: no... but we permit it. 14:31:29 I agree, push back 14:31:32 SM: And remember there are lots of other specs that introduce attributes outside of the context of a markup language. 14:31:43 MS: So we should just push back to the TAG? 14:31:48 (general agreement) 14:32:35 PROPOSAL: RDFa is not a set of elements, but a set of attributes. Other W3C specs that define sets of XML attributes (e.g. xml:base, aria, spec, xml:id spec, XML namespaces spec, XLink, etc) do not define media types. RDFa falls into the same category as these specs, that is, it doesn't require a MIMEtype registration. 14:32:52 looks good 14:33:26 SP: Not just attributes - elements are relevant as well. It doesn't have a root element. So it shouldn't have its own media type. 14:33:27 what if several syntaxes are used in the same document (e.g. RDFa and microdata)? can a document define multiple MIME types? 14:33:40 No - only one. 14:34:02 so that's another argument against defining MIME types for each of them 14:34:15 since we can't combine them 14:35:51 SM: Dont forget that XHTML+RDFa IS a document type. it should not have its own media type. 14:36:32 +1 14:36:57 ... parameters on the media type are a reasonable way to do this. profile="someURI someotherURI" 14:37:04 q+ 14:37:17 ... profile should be able to take more than one value so a document can reference multiple sets of processing rules 14:37:38 ack Steven 14:38:02 SP: HTML5 and microdata is a great example. There shouldn't be two media types for HTML5 and HTML5+microdata. 14:38:14 ... so it isn't something that the working group needs to handle. 14:38:57 IH: No, the working group needs to update the media registration to allow for any additional parameters, not just microdata or RDFa. 14:39:32 MS: I think this is a non issue. No one is going to use this. It is overly pedantic. Processors will grab documents and try to extract triples. If they get some, great. If not, also great. 14:40:17 .. as long as official validators (will) accept the attributes, there is no technical issue. 14:41:20 IH: didn't the HTML5 working group remove @profile? 14:41:44 q+ 14:41:50 q- 14:42:00 http://dev.w3.org/html5/profiles/source/ 14:43:24 Look at http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview-src.html#major-differences-with-rdfa-syntax-1.0 14:43:33 MS: Push back on the tag first. 14:44:50 PROPOSAL: RDFa Core 1.1 is a set of attributes. There are other specs that are just sets of attributes like xml:base, aria, xml:id, XML namespaces, XLink) and those do not define media types. RDFa Core 1.1 falls into the same category as these specs, that is, it doesn't require a MIMEtype registration. 14:45:03 +1 14:45:06 +1 14:45:07 +1 14:45:07 +1 14:45:08 +1 14:45:08 +1 14:45:09 +1 14:45:11 +1 14:45:15 RESOLVED: RDFa Core 1.1 is a set of attributes. There are other specs that are just sets of attributes like xml:base, aria, xml:id, XML namespaces, XLink) and those do not define media types. RDFa Core 1.1 falls into the same category as these specs, that is, it doesn't require a MIMEtype registration. 14:46:46 PROPOSAL: The SVG 1.1 spec and the ODF spec already refers to the RDFa specification, therefore no action is necessary. 14:46:55 +1 14:46:56 +1 14:46:57 +1 14:46:58 +1 14:47:00 +1 14:47:06 +1 14:47:06 +1 14:47:12 RESOLVED: The SVG 1.1 spec and the ODF spec already refers to the RDFa specification, therefore no action is necessary. 14:48:34 (actually, it seems like it's SVG 1.2 Tiny which explicitly refers to RDFa) 14:49:15 with that, +1 14:49:27 PROPOSAL: The text/xml, application/xml, text/html and application/xhtml+xml MIMETypes are not under the purview of this Working Group and therefore this WG cannot refer to the RDFa Core 1.1 or XHTML+RDFa or HTML+RDFa or Microdata specifications. The WG associated with each of those MIMETypes will need to add them to the associated specification. 14:49:42 s/MIMETypes/Media Types/ 14:49:46 +1 14:49:46 +1 14:49:47 +1 14:49:47 +1 14:49:48 +1 14:49:48 +1 14:49:49 +1 14:49:50 +1 14:50:04 PROPOSAL: The text/xml, application/xml, text/html and application/xhtml+xml Media Types are not under the purview of this Working Group and therefore this WG cannot refer to the RDFa Core 1.1 or XHTML+RDFa or HTML+RDFa or Microdata specifications. The WG associated with each of those Media Types will need to add them to the associated specification. 14:50:10 RESOLVED: The text/xml, application/xml, text/html and application/xhtml+xml Media Types are not under the purview of this Working Group and therefore this WG cannot refer to the RDFa Core 1.1 or XHTML+RDFa or HTML+RDFa or Microdata specifications. The WG associated with each of those Media Types will need to add them to the associated specification. 14:50:47 TOPIC: rel / rev values 14:51:29 We need a volunteer. No one wants to do it. 14:51:59 We need to go through and remove things from default profile(s) that we don't want to handle any longer. Semantics have changed for some values. 14:52:54 ZAKIM, WHO IS NOISY? 14:53:10 Steven, listening for 10 seconds I heard sound from the following: gkellogg (35%) 14:53:13 ACTION: ShaneM to review rel / rev values and find items that should be removed 14:53:14 Created ACTION-97 - Review rel / rev values and find items that should be removed [on Shane McCarron - due 2011-10-13]. 14:53:57 Shane++ 14:53:57 [[[ 14:53:59 Backwards compatibility with RDFa 1.0 is of great importance. That means, in general, that all triples that are produced via the October 2008 version of RDFa, should still be generated in the new version. For each new feature, if there is doubt or a perceived problem with respect to this, the guideline should be not to include the feature in the set of modifications. The two minor features the Working Group has identified and which may constitute possible exceptions 14:53:59 this rule, is the default XML Literal generation (see the proposal and the corresponding thread for details), and the list of predefined @rel/@rev values that automatically generate triples (these predefined values are under re-evaluation by the HTML community, and inconsistencies may occur if all RDF triples are generated). 14:54:01 ]]] 14:54:53 default evaluation context? 14:55:03 s/default/initial/ 14:55:29 Use the term 'initial evaluation context'. 14:55:32 Topic: Default Profile language 14:56:42 use 'initial evaluation context' as the term. 14:57:08 SM: remove the section that describes how to specify default profiles. 14:57:51 didn't we want to be able to add terms in the future? 14:58:27 q+ 14:58:49 My implementation parses the profile docs to create constant definitions in the parser 14:58:56 MS: We can't just use the spec. We need an external document. 14:59:18 ... publishing cycle at the W3C is too long. External document is used to maintain the data. 14:59:44 ack ivan 14:59:59 IH: use the different name, but keep the current mechanism. 15:00:17 ... the mechanism provides the possibility to either hardcode or use caching and retrieve or whatever. 15:00:22 ... we don't want to impose that. 15:01:01 ... not in favor of hardcoding. 15:01:04 +1 to ivan 15:01:05 SM: okay 15:01:30 PROPOSAL: Use the terminology 'initial evaluation context' to specify the initial list of terms and prefixes that should be used by a processor. 15:01:46 IH: might need to change names of triple predicates. 15:01:47 +1 15:01:48 +1 15:01:48 +1 15:01:48 +1 15:01:57 +1 15:02:03 +1 15:02:31 RESOLVED: Use the terminology 'initial evaluation context' to specify the initial list of terms and prefixes that should be used by a processor. 15:03:27 rssagent, set minutes public 15:03:41 -bergie.aa 15:03:45 rrsagent, set minutes public 15:03:45 I'm logging. I don't understand 'set minutes public ', ivan. Try /msg RRSAgent help 15:03:58 rrsagent. make minutes public 15:04:05 rrsagent, make minutes public 15:04:05 I'm logging. I don't understand 'make minutes public', ivan. Try /msg RRSAgent help 15:04:12 ShaneM has left #rdfa 15:04:13 rrsagent, make logs public 15:04:44 ivan has left #rdfa 15:04:51 -ShaneM 15:04:55 -gkellogg 15:05:01 -scor 15:05:05 -Steven 15:05:20 niklasl has left #rdfa 15:05:47 -niklasl 15:05:54 -Ivan 15:05:55 -manu1 15:27:19 bergie has joined #rdfa 15:30:29 manu1: FYI, https://github.com/bergie/VIE/issues/42 15:31:41 ShaneM has joined #rdfa 15:33:06 ShaneM1 has joined #rdfa 15:36:38 ShaneM1 has left #rdfa 15:59:54 bergie: I see it - let me know if you have any questions. All the source for that site is available publicly. 16:00:43 MacTed has joined #rdfa 16:06:12 manu1: seems straightforward, I just need to tune the tests so we can run them in browser (no body/head elements, etc) 16:07:45 We've been needing to convert the test suite so that it works w/ JavaScript implementations... the other alternative is to use node.js to run the test suite. 16:27:20 MacTed has joined #rdfa 16:37:49 manu1: yeah, we have *also* tests for node 16:42:36 ShaneM has joined #rdfa 16:54:06 ShaneM has left #rdfa 17:33:25 tinkster has joined #rdfa 18:42:48 tinkster has joined #rdfa 19:17:22 bergie has joined #rdfa 21:31:31 gkellogg has joined #rdfa