14:56:28 RRSAgent has joined #rdfa 14:56:28 logging to http://www.w3.org/2007/07/05-rdfa-irc 14:56:34 zakim, this will be rdfa 14:56:34 ok, Steven; I see SW_SWD(RDFa)11:00AM scheduled to start in 4 minutes 14:56:42 rrsagent, make log public 14:59:18 kwijibo has joined #rdfa 14:59:55 SW_SWD(RDFa)11:00AM has now started 15:00:04 +ShaneM 15:00:13 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0009 15:00:23 Steven has changed the topic to: Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0009 15:00:29 zakim, dial steven-work 15:00:29 ok, Steven; the call is being made 15:00:31 +Steven 15:04:01 +Ralph 15:04:29 Meeting: RDFa Task Force 15:05:27 -> http://www.w3.org/2007/06/28-rdfa-minutes.html previous 2007-06-28 15:06:15 +??P19 15:06:29 zakim, i am ? 15:06:29 +markbirbeck; got it 15:06:35 benadida has joined #rdfa 15:07:05 + +1.617.395.aaaa 15:07:11 zakim, aaaa is Ben 15:07:11 +Ben; got it 15:08:03 Chair: Ben 15:08:22 zakim, who's on the phone 15:08:22 I don't understand 'who's on the phone', benadida 15:08:24 zakim, who is here? 15:08:27 On the phone I see ShaneM, Steven, Ralph, markbirbeck, Ben 15:08:29 On IRC I see benadida, kwijibo, RRSAgent, Zakim, RalphS, ShaneM, Steven, markbirbeck 15:09:49 Topic: Action Summary 15:10:21 ACTION: Ben make a scribe schedule 15:10:32 scribe: Ralph 15:10:54 ACTION: Michael add a test case that test for omitted @about [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action04] 15:10:57 -- continues 15:11:04 ACTION: Michael correct TC15 title [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action05] 15:11:05 -- continues 15:11:12 ACTION: Michael create a .htaccess hack to make the test case identifiers resolve to something useful [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action01] 15:11:13 -- continues 15:11:19 ACTION: Shane investigate the @xml:base validation issue [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action02] 15:11:30 Shane: this appears to be harder than I thought 15:11:46 Ben: we expect xml:base to be used in HEAD ? 15:12:03 ... to set the CURIE base URI? 15:12:24 Mark: yes, it should work with HTML base 15:12:29 -- continues 15:12:38 [DONE] ACTION: Shane to correct DTD to permit RDFa attributes on the head element. [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action03] 15:12:50 [DONE] ACTION: Ben get further input from Creative Commons on @RESOURCE and @HREF [recorded in http://www.w3.org/2007/06/21-rdfa-minutes.html#action15] 15:13:07 Simone has joined #rdfa 15:13:46 -> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jun/0147.html the Creative Commons take on @href everywhere [Ben 2007-06-27] 15:13:56 zakim, q+ 15:13:56 I see markbirbeck on the speaker queue 15:14:02 ACTION: Ben to figure out the RDFa-GRDDL-profile URI (at w3.org) [recorded in http://www.w3.org/2007/06/14-rdfa-minutes.html#action15] 15:14:04 -- continues 15:14:14 Ralph: I'll take this one over from Ben 15:14:47 Mark: let's put @href everywhere on our syntax agenda; what does it mean for HTML ? 15:14:56 ... it's no longer XHTML2-ish 15:15:08 ... one possibility is to defer @href everywhere to a future version 15:15:25 Ben: I'll add this to issues list 15:15:31 s/@href/@xml:base/ 15:15:43 +??P24 15:15:56 s/put @href/put @xml:base/ 15:16:05 ACTION: Ben to look into Science Commons use case [recorded in http://www.w3.org/2006/12/11-htmltf-minutes.html#action04] 15:16:07 -- continues 15:16:07 Zakim, ??P24 is me 15:16:07 +Simone; got it 15:16:13 ACTION: Elias to send email to list with use case from IBM [recorded in http://www.w3.org/2006/12/04-htmltf-minutes.html#action10] 15:16:14 -- continues 15:16:24 ACTION: Mark get input from Joost on @HREF everywhere [recorded in http://www.w3.org/2007/06/21-rdfa-minutes.html#action14] 15:16:25 -- continues 15:16:34 Mark: I sent email to Joost today 15:16:46 ACTION: Mark produce more examples of applicability of n-ary relations from IPTC documents [recorded in http://www.w3.org/2006/10/23-htmltf-minutes.html#action08] 15:17:06 Mark: this is part of the reification discussion 15:17:20 ... let's defer it to the future 15:17:41 -- withdrawn 15:18:21 ACTION: MarkB to work rdf:label back into RDFa syntax when using @content [recorded in http://www.w3.org/2007/03/19-rdfa-minutes.html#action25] 15:18:44 -- continues 15:19:02 Mark: this is more problematic than I first though too 15:19:10 [DONE] ACTION: Steven to put together sample XHTML2 doc with all mime type, etc. [recorded in http://www.w3.org/2006/09/19-htmltf-minutes.html#action01] 15:19:43 Topic: METAs and LINKs in the body: should we get rid of them? 15:20:09 -> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0007.html [RDFa] ISSUE 9: META and LINK in the body 15:20:37 Ben: if we remove LINK in the body then it feels to me we may need to have @href and @resource everywhere 15:20:59 Steven: I think it's a bad idea to depend on META and LINK in the body 15:21:15 ... everything that depends on this behavior we should find a different way to do 15:22:02 Ben: if served as html+xml then FireFox no longer repositions these to HEAD 15:22:11 ... IE continues to do this, however 15:22:44 Ralph: this feels to me as something where we should not step on the base language 15:23:00 Shane: we have changed the content model of HEAD by saying META and LINK both accept content 15:23:04 no, simone, we don't hear you 15:23:07 Steven: yes, for XHTML2, and this is a good thing 15:23:25 Mark: IE does not move LINK and META in HTML mode 15:23:26 zakim, who is here? 15:23:26 On the phone I see ShaneM, Steven, Ralph, markbirbeck, Ben, Simone 15:23:27 On IRC I see Simone, benadida, kwijibo, RRSAgent, Zakim, RalphS, ShaneM, Steven, markbirbeck 15:23:45 ... what it does do is treat META as a straight element with open and close tags 15:24:04 ... text is treated as 3 sibling nodes by IE 15:24:18 ... so even if we do allow META in the body there is quirky parsing 15:24:32 ... I've made this work in my parser but it is quirky 15:25:11 -Simone 15:25:27 Shane: my change to HEAD content model is for XHTML1.1 -- let's not discuss XHTML2 here 15:25:55 Ben: should we change back to original content models for LINK and META and just add @property ? 15:26:34 Steven: I think it's good to permit LINK and META in body for XHTML2 but not for XHTML1.1 15:26:49 Ben: what about content of LINK and META? This doesn't seem very useful in this case 15:27:05 Shane: I don't understand what problem this was intended to solve, but LINK can contain LINK 15:27:40 Ben: since we're deferring reification, maybe we can undo our changes to LINK and META content model 15:27:54 ... we had a use case from Bob Ducharme with nested LINKs 15:28:05 ... we could say this feature will only be available in XHTML2 15:28:48 Steven: if you want to put something in the HEAD and have marked-up content in META you couldn't do this 15:29:16 Mark: Bob's example was the IPTC use case of wanting to say who made an assertion; this is reificiation 15:29:37 ... the other use case for content in META is XMLLiteral 15:29:51 ... since attribute content can't contain markup 15:31:51 PROPOSE: LINK and META appear only in HEAD with no changes to content model 15:31:55 [no objections] 15:32:04 action: Ben to send to mailing list PROPOSE: LINK and META appear only in HEAD with no changes to content model 15:32:34 Shane: I think this allows us to remove the whole "metainformation module" part of the spec 15:32:51 Topic: @about 15:33:05 Steven: we say 'use the closest @about when generating the subject' 15:33:14 ... with special rules for META and LINK 15:33:20 ... I guess those special rules now go away? 15:33:29 Ben: but we still want bnodes 15:33:41 ... so some of the use cases are replaced by @rel without @href 15:34:05 Steven: this takes care of object, but not subject 15:34:09 Ben: can do the same with SPAN 15:34:19
15:34:25 Ben 15:34:27
15:35:25 Ben: in this example, @rel sets the subject because there's no @href 15:35:36
15:35:40
15:35:45 Ben 15:35:47
15:35:48
15:35:59 <#bar> foaf:knows <#foo> 15:36:04 Ben: this example means ... 15:36:12 <#foo> foaf:name "Ben" 15:37:04 ... @rel without @href makes that node be the subject; it would be a bnode if it didn't have @id 15:37:30 ... later we can talk about what it means if the DIV had @href 15:37:41 Mark: agree with that interpretation 15:38:00 Ben: so this handles most of the cases where we used META in BODY 15:38:20 Simone has joined #rdfa 15:38:38 ... it becomes more important to relate the bnode to the document 15:38:48 ACTION: Ben summarize the state of @rel everywhere 15:40:17 simone, are you on the call? 15:40:29 zakim, who is here? 15:40:29 On the phone I see ShaneM, Steven, Ralph, markbirbeck, Ben 15:40:30 On IRC I see Simone, benadida, kwijibo, RRSAgent, Zakim, RalphS, ShaneM, Steven, markbirbeck 15:40:55 can you type out your comment? 15:41:26 simone, ok to put "I prefer to not use META and LINK an all, I like approach of iRDF (fromer eRDF), so META is an EMPTY element and may create problems" into the record? 15:41:36 oops 15:41:39 I guess I just did :) 15:41:53 Simone: I prefer to not use META and LINK an all, I like approach of iRDF (fromer eRDF), so META is an EMPTY element and may create problems 15:42:12 Topic: CURIEs vs. QNames: what to do for XHTML1.1+RDFa? 15:42:50 zakim, q+ 15:42:50 I see markbirbeck on the speaker queue 15:42:51 Ben: as Shane points out, since CURIE spec is not done it's dangerous for RDFa to have it as a dependency 15:43:22 Mark: the choices are not CURIE vs QName but CURIE vs. something unspecified 15:43:35 ... look at SPARQL and RULEML 15:43:58 ... there is a tendency towards using the [syntactic] concept of QName but without the restrictions 15:44:16 ... we either do the same thing; looks like a QName but new rules for how they're defined 15:44:29 ... I don't like to continue the misuse of QName 15:44:51 ... QName is for defining elements and attributes in XML markup 15:44:53 cc:attributionName 15:45:49 Ben: cc:attributionName can be expressed in RDF/XML 15:46:03 ... is this not really a QName, just looks like one? 15:46:26 Mark: it conforms to the syntax but out of context it can't be a QName, because the purpose of QName is to define an element 15:47:03 ... so when it's used as a predicate in RDF/XML it's fine because it _is_ defining an element 15:47:48 Ben: can we punt to SPARQL and N3 and simply say we're using the syntax the same way they are? And in XHTML2 clean it up by defining CURIE 15:48:08 ... we can say we'll use the same inconsistent view that others have 15:48:18 Mark: but SPARQL doesn't refer to QName 15:49:22 http://www.w3.org/TR/rdf-sparql-query/#QSynIRI 15:50:38 Steven: SPARQL calls these "prefixed names", not QNames 15:51:05 Mark: and there's a big red box noting that not all prefixed names are XML QNames 15:51:21 Ben: will we get into trouble by using @xmlns to define the prefixes? 15:51:33 Mark: this has been talked about a lot 15:51:49 ... one suggestion is to say that @xmlns is only one way to define prefixes 15:52:28 ... could use a triple to declare a prefix; then LINK suffices 15:52:49 (rel = curiePrefix) 15:52:50 ... alternative is to include @xmlns in our vocabulary 15:53:26 ... or, further, say 'given these attribute values, load these triples'; e.g. well-known prefixes 15:53:45 Ben: I don't like the third option as it doesn't allow people to include arbitrary RDF 15:53:59 s/RDF/RDF vocabularies/ 15:54:31 Steven: the triple relation would be between a string and a URI, right? so it would have to be done with META and not LINK 15:54:45 15:55:03 Mark: I agree with Steven 15:55:37 Ben: I'm concerned about using a triple for this because the declaration should only be local to the document 15:56:15 Simone has joined #rdfa 15:56:19 Mark: the point is that we can't simply refer to the SPARQL spec because they don't define their term 15:56:27 Ben: but we can use their wording 15:57:08 ... to avoid arguments from opponents of CURIEs 15:57:20 Mark: the SPARQL spec effectively defines CURIEs 15:57:39 Steven: so we could just say that we're using p-names from SPARQL 15:58:02 Mark: but SPARQL has only created its p-name for use within its own context 15:58:13 ... CURIE is meant to resolve this all over 15:58:21 While there is risk in depending upon another spec, the XHTML 2 working group can complete the CURIE spec now. 15:58:27 Ben: but we've gotten push-back on CURIEs, including from the Director 15:59:07 ... since SPARQL is nearly complete, it would be hard for people to fight us if we do the same as SPARQL 16:00:02 Mark: looking at the SPARQL spec, we're a lot closer to agreement on CURIE that we were at the time of the Edinburgh AC meeting 16:00:23 Ben: why should we take on this fight? 16:00:50 Mark: we can't refer normatively to [what SPARQL] does just as we can't currently refer normatively to a CURIE spec 16:01:21 Ben: we'll have a bigger fight on our hands if we cite CURIE 16:01:49 Mark: I suggest we take the text and BNF from the CURIE document and drop it in 16:02:10 -ShaneM 16:02:14 ... don't use the name CURIE 16:02:15 -markbirbeck 16:02:19 -Steven 16:02:19 [adjourned] 16:20:27 -Ralph 16:20:29 -Ben 16:20:31 SW_SWD(RDFa)11:00AM has ended 16:20:32 Attendees were ShaneM, Steven, Ralph, markbirbeck, +1.617.395.aaaa, Ben, Simone 16:20:38 rrsagent, draft minutes 16:20:38 I have made the request to generate http://www.w3.org/2007/07/05-rdfa-minutes.html RalphS 16:22:00 rrsagent, bye 16:22:00 I see 13 open action items saved in http://www.w3.org/2007/07/05-rdfa-actions.rdf : 16:22:00 ACTION: Ben make a scribe schedule [1] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-10-21 16:22:00 ACTION: Michael add a test case that test for omitted @about [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action04] [2] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-10-54 16:22:00 ACTION: Michael correct TC15 title [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action05] [3] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-11-04 16:22:00 ACTION: Michael create a .htaccess hack to make the test case identifiers resolve to something useful [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action01] [4] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-11-12 16:22:00 ACTION: Shane investigate the @xml:base validation issue [recorded in http://www.w3.org/2007/06/28-rdfa-minutes.html#action02] [5] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-11-19 16:22:00 ACTION: Ben to figure out the RDFa-GRDDL-profile URI (at w3.org) [recorded in http://www.w3.org/2007/06/14-rdfa-minutes.html#action15] [6] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-14-02 16:22:00 ACTION: Ben to look into Science Commons use case [recorded in http://www.w3.org/2006/12/11-htmltf-minutes.html#action04] [7] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-16-05 16:22:00 ACTION: Elias to send email to list with use case from IBM [recorded in http://www.w3.org/2006/12/04-htmltf-minutes.html#action10] [8] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-16-13 16:22:00 ACTION: Mark get input from Joost on @HREF everywhere [recorded in http://www.w3.org/2007/06/21-rdfa-minutes.html#action14] [9] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-16-24 16:22:00 ACTION: Mark produce more examples of applicability of n-ary relations from IPTC documents [recorded in http://www.w3.org/2006/10/23-htmltf-minutes.html#action08] [10] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-16-46 16:22:00 ACTION: MarkB to work rdf:label back into RDFa syntax when using @content [recorded in http://www.w3.org/2007/03/19-rdfa-minutes.html#action25] [11] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-18-21 16:22:00 ACTION: Ben to send to mailing list PROPOSE: LINK and META appear only in HEAD with no changes to content model [12] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-32-04 16:22:00 ACTION: Ben summarize the state of @rel everywhere [13] 16:22:00 recorded in http://www.w3.org/2007/07/05-rdfa-irc#T15-38-48 16:22:20 zakim, bye 16:22:20 Zakim has left #rdfa 16:22:22 kwijibo has joined #rdfa