14:51:00 RRSAgent has joined #rdfa 14:51:00 logging to http://www.w3.org/2009/04/02-rdfa-irc 14:51:07 Meeting: RDF-in-XHTML Task Force 14:51:15 agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Apr/0018.html 14:51:45 -> http://www.w3.org/2009/03/19-rdfa-minutes.html previous 2009-03-19 14:52:15 regrets+ Michael 14:52:34 regrets+ Ben_Adida 14:52:38 regrets+ Michael_Hausenblas 14:52:49 regrets- Michael 14:53:06 rrsagent, please make record public 15:01:19 SW_SWD(RDFa)11:00AM has now started 15:01:26 +Ralph 15:01:46 markbirbeck has joined #rdfa 15:02:14 +??P27 15:02:25 zakim, I am ??P27 15:02:36 +msporny; got it 15:04:32 ShaneM has joined #rdfa 15:04:43 laptop has gone deeply insane - wokring on it 15:05:49 +ShaneM 15:06:31 chair: Manu 15:06:34 http://www.w3.org/2009/03/19-rdfa-minutes.html 15:06:51 [PENDING] ACTION: Ben to put up information on "how to write RDFa" with screencast possibly and instructions on bookmarklet. [recorded in http://www.w3.org/2008/11/06-rdfa-minutes.html#action12] 15:06:57 [PENDING] ACTION: Jeremy to demonstrate GRDDL with XHTML/RDFa once the NS URI is set up. [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action03] 15:07:46 ACTION: Manu to look at http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Dec/0037.html about resolving relative URIs [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action15] 15:07:54 Manu: I've replied and asked twice for a response 15:08:11 ... I think they're accepting the response 15:08:16 ... so I think we can consider this done 15:08:20 --done 15:08:26 [PENDING] ACTION: Manu to write summary for Semantic Web Use Cases for Ivan. [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action09] 15:08:39 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] 15:08:53 Mark, are you going to dial in soon? We're at your action items... 15:09:13 i|http://www.w3.org/2009/03/19-rdfa-minutes.html|Topic: Action Review 15:09:21 I'm about to dial in. 15:09:29 However, I have no updates on my actions. 15:09:31 I have made the request to generate http://www.w3.org/2009/04/02-rdfa-minutes.html Ralph 15:09:32 -- continues 15:09:44 [DONE] ACTION: Mark to review reasoning on setting explicit about="" on HEAD and BODY [recorded in http://www.w3.org/2008/12/18-rdfa-irc] 15:09:54 Oh...other than that one. :) 15:10:15 -> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Apr/0000.html The implied @about="": Explanation and some problems [Mark Birbeck 2009-04-01] 15:10:22 [PENDING] ACTION: Mark to send Ben ubiquity related wizard stuff [recorded in http://www.w3.org/2008/11/20-rdfa-minutes.html#action11] 15:10:25 zakim, code? 15:10:25 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 15:10:26 [PENDING] ACTION: Mark write foaf examples for wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action13] 15:10:32 [PENDING] ACTION: Michael to create 'RDFa for uF users' on RDFa Wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action14] 15:10:43 ACTION: Ralph or Steven fix the .htaccess for the XHTML namespace [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action01] 15:11:02 +??P4 15:11:04 Ralph: I know Steven poked someone about this 15:11:08 zakim, i am ? 15:11:08 +markbirbeck; got it 15:11:09 -- continues 15:11:13 [PENDING] ACTION: Ralph think about RSS+RDFa [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action15] 15:12:36 Topic: Report on AC Meeting 15:12:54 Manu: anyone there for the HTML discussions than Ben and Steven? 15:13:04 Shane: unfortunately Ben couldn't stay for the breakout session 15:13:18 Mark: the minutes suggest the discussion was quite positive 15:14:02 Ralph: I needed to participate in a different breakout 15:14:14 Mark: I'm looking at the minutes of the Backplane XG 15:15:39 Shane: there appears to be substantial support from the Membership for the extensibility model that XHTML has always had 15:16:45 Topic: @prefix syntax discussion 15:17:10 Manu: at our last discussion, Shane and Ralph were favoring the '=' syntax and Mark and I were favoring the JSON-esque syntax 15:17:29 ... any new thoughts in the subsequent 2 weeks? 15:18:16 Mark: I'm involved in a couple of projects where folk are producing what they think is RDFa 15:19:09 ... it's interesting; I see a growing need for tools to check the work 15:19:18 -ShaneM 15:20:28 ... simply typos like mismatch between namespace declaration and usage 15:20:48 +??P0 15:20:50 ShaneM has joined #rdfa 15:21:51 Ralph: no real additional thoughts but I did make note of Mark's concerns about the pattern @attr="prefix=value" 15:22:03 ... but if tools are generating this anyway, how much does it matter? 15:22:16 Mark: I'm thinking of checking tools more than generation tools 15:22:39 Manu: definitely think embedded '=' will cause confusion 15:22:55 ... and people will put whitespace around the '=' 15:23:05 ... so we need resilient syntaxes and parsers 15:23:36 Shane: I don't think it's terribly important to have delimiters other than whitespace between the items 15:23:45 ... but I won't fight on that 15:23:56 ... I understand the sensitivity to the repeated '=' issue 15:24:00 ... do you prefer ':'? 15:24:01 Manu: yes 15:24:17 Shane: that's probably fine, but then you end up with repeated ':' 15:24:26 perfix="xhv:http:..." 15:25:03 Shane: I leaned toward repeated '=' in the first place because that made it clear which was the prefix and which was the rest 15:25:07 prefix="xhv:xyz dc:xyz" 15:25:13 prefix="xhv=xyz dc=xyz" 15:25:25 Mark: we're tending to discuss as if ^ were the patterns 15:25:43 ... this is how @xml:schemalocation works 15:25:44 prefix=" 15:25:45 xhv: xyz, 15:25:45 dc: xyz 15:25:45 " 15:26:02 Mark: I'm thinking we should really be looking at layout such as ^ 15:26:16 ... in this case, additional delimiters are useful; we don't need to be compact 15:26:37 ... we should consider not just a syntax but also examples that people will cut & paste 15:27:15 ... if I were to copy one of Manu's audio prefix examples I could select a single line (of many declarations) and insert it into my list without introducing error 15:27:26 ... once you spread things out like this, why not allow further flexibility 15:27:27 prefix=" 15:27:27 "xhv": 'xy z', 15:27:27 dc: xyz 15:27:28 " 15:27:42 prefix=" 15:27:43 'xhv': 'xy z', 15:27:43 dc: xyz 15:27:43 " 15:28:12 Shane: my concern is that URIs allow these characters, so the syntax rules and the parsing are both more challenging 15:28:24 Mark: yes, but there are extra options for delimiting 15:28:49 ... if we say we're allowing quotes _as well_ this gives additional flexibility 15:28:50 prefix=" 15:28:50 'xhv': 'xy z,', 15:28:51 dc: xyz 15:28:51 " 15:29:17 Mark: if you did have a URI that ends in ',' then quoting allows an easy way to include it 15:29:45 ... ':' in @xmlns was really an effort to find one thing that would work 15:30:00 ... but we have greater flexibility 15:30:24 Manu: when people mint prefix mapping URIs I find it highly unlikely that they'll use a ',' in such a URI 15:30:57 ... yes, it _could_ happen but if it's a well-known design consideration that such characters cause trouble then vocabulary developers can avoid them 15:30:57 q+ to talk about embedding commas 15:31:05 Mark: what is the added complexity? 15:31:21 Manu: it's additional complexity in the parser. I'm questioning whether we really need it. 15:31:28 Mark: it's one regular expression 15:31:51 ... a way of trying to introduce resilience and something that [humans] can grok easily 15:32:09 ... we come back to this problem of recognizing what is a URI 15:32:36 ... I'm just thinking of ways to provide resilience when needed without mandating it all the time 15:32:44 prefix=" 15:32:45 xhv: {xy z,}, 15:32:45 dc: xyz 15:32:45 " 15:33:04 Manu: I'd like to see the regex 15:33:32 ... my C+sax-based parser doesn't have to use regex's anywhere right now 15:33:46 Mark: a space-separated list needs to be cracked into a list 15:33:54 ... even '=' can appear in a URI 15:33:55 index 15:34:06 index() 15:34:07 :) 15:34:28 Manu: I don't think we can count on authors writing examples consistently 15:34:39 ... and a mixture of styles will cause confusion 15:35:00 Mark: I'm proposing the _possibility_ of permitting this richer format, not _requiring_ it 15:35:46 Manu: I was only questioning whether example authors will really write the examples with multi-line declarations 15:35:52 prefix="xhv: xy, dc: xyz" 15:36:08 ... when the examples are written on a single line the richer syntax becomes confusing 15:36:29 Mark: consider space-separated lists 15:36:30 prefix="xhv:xy dc:xyz" 15:36:41 ... then you can't have space around ':' 15:36:53 ... the options for authors laying out the markup are limited 15:37:31 ... no flexibility for aligning things [in columns] 15:38:12 ... whereas the XML attribute syntax has a lot of flexibility, for example; can use whitespace to nudge things [into columns] 15:38:40 ... in terms of consistency, generally in XML spaces are ignored 15:39:03 ... other than the use in XML Schema to create lists, whitespace is not significant 15:39:20 Shane: whitespace is collapsed, not ignored 15:39:25 ... this includes newlines 15:39:37 ... collapsing inside attributes values 15:39:49 ... however, this is bad; in the HTML DOM whitespace is not collapsed 15:40:12 ... this means a parser that has to work with both XML and HTML has to be written to expect multiple whitespace 15:40:34 Mark; but the presence of whitespace is geenerally not significant 15:40:39 s/;/: 15:40:53 ... as long as there is whitespace in key places, such as between attributes 15:41:13 ... '=' vs. ':' is a separate discussion from whether whitespace is a delimiter 15:41:28 Manu: I agree; we shouldn't decide solely on whitespace 15:41:41 prefix="xhv:xy, dc:xyz" prefix="xhv:xy; dc:xyz" 15:41:55 ... for delimiters between mappings, we're considering something like ^ 15:42:17 Shane: a lot of our canonical examples are ones that contain ','; e.g. Wikipedia or Amazon 15:42:29 ... places where, for example, an ISBN might be interpolated 15:42:45 prefix="media: http://purl.org/media#, audio: http://purl.org/media/audio#" 15:42:53 Mark: yeah, can't quickly come up with an example 15:43:02 mapping, mapping, mapping 15:43:12 Mark: should treat as ^ 15:43:22 ... then decide what goes inside 'mapping' 15:43:32 prefix="media: http://purl.org/media# ; audio : http://purl.org/media/audio#" 15:43:41 Shane: can't just be 'ends in ,' -- must be 'includes ,' 15:44:18 Manu: are Shane and Ralph ok with using ',' between mappings? 15:44:30 Shane: if we're going to use ',' or ';' we need to define the escaping mechanism 15:44:41 ... maybe there's already a mechanism defined somewhere 15:45:01 ... my preferred syntax is identical to schemalocation but Ralph says that's a non-starter 15:45:15 Manu: ok to pick a character that must be URI-encoded in URIs? 15:45:37 http://en.wikipedia.org/wiki/Percent-encoding 15:45:42 Mark: every time I look at the URI spec I find it allows more characters than I expected 15:46:08 ... this discussion is pretty much the same discussion the @xmlns folk had to go through 15:47:07 Manu: we could require that reserved characters must be %-encoded 15:47:18 ... but that makes everything harder 15:47:27 Mark: and we'd have to avoid a requirement to double-encode 15:47:36 ... we need a non-reserved character 15:47:39 Shane: good luck with that! 15:47:48 ... remember that in the case of CURIE it's a IRI 15:47:57 ... so even a bigger set of non-reserved character 15:48:14 ... the only reserved character is space 15:48:37 ... even schemalocation cheated by not using '=' or ':'; they just use alternation 15:48:56 ... the problem with alternation is that we can't do anything clever with default or absent prefixes 15:49:12 ... but maybe we don't need such rules 15:49:29 prefix="a=b x=y" 15:50:39 wow.... we already have this problem! 15:50:42 Mark: if we needed @prefix on every element then perhaps we might go with [the '=' syntax] 15:50:52 xmlns:foo="URI" what happens if URI contains a quotation mark? 15:50:53 ... but perhaps we don't need that flexibility; be more restrictive 15:51:16 ... put everything in the head or having a predicate indicating a prefix mapping 15:51:31 Ralhp: predicate as in RDF predicate? 15:51:33 Mark: yes 15:51:41 15:51:57 ... however I didn't like that syntax as it puts meta information in the same graph as 'ordinary' information, which feels wrong 15:52:22 ... I'm looking for something that is "cut-and-paste reliable" 15:53:05 Ralph: Creative Commons would not accept restrictions on where mappings can be declared 15:53:57 Shane: separate two issues; 1. can we provide an alternative to @xmlns that would be acceptable beyond the XML community and 2. how do we make it easier for our constituents to use RDFa in ways @@ 15:54:36 s/ways @@/easier ways 15:54:49 ... we've talked about having external documents that declare prefixes 15:55:13 ... perhaps even with some well-known prefix declarations 15:55:34 ... maybe we'll make more progress by not trying to find a single solution to these two objectives 15:55:44 Mark: so do we need a lot of flexibility? 15:55:55 ... find just enough flexibility for the goals at hand 15:56:12 We should try hard to NOT over-engineer this solution without having the requirements in mind! 15:56:17 Manu: the second idea is that there's an @profile value that pulls in external mapping declarations 15:56:48 Mark: 1 is the namespace thing and 2 is ease of authoring 15:57:35 Shane: consider CSS syntax as an example of going too far; e.g. borders on table cells -- totally different behavior depending on how many values are supplied 15:57:45 dc: url(xyz) 15:57:49 Mark: I've just thought of another syntax! 15:58:43 Ralph: and it may be that the @xmlns problem will go away 15:58:55 Continuing Shane's point, why not 'solve' this: 15:58:57 http://wiki.creativecommons.org/CcREL 16:00:19 Mark: pick an example of something people will frequently want to copy and paste; e.g. ccRel 16:00:30 ... the simple example [in ccRel] is interesting 16:00:51 ... it just says some other mechanism has defined the token 16:01:41 ... consider the lengthier scenarios; what other ways are there to address these? 16:01:57 Manu: any of our proposed syntaxes would handle these examples fairly cleanly 16:02:22 prefix="a = b x = y" 16:02:24 Ralph: yeah, it's the ugly corner cases like ',' in URIs that are a problem 16:02:29 prefix="a=b x=y" 16:02:35 Shane: even quote is already an issue 16:02:55 Manu: a simple state machine will handle the '=' syntax 16:03:22 prefix=" 16:03:22 a = b 16:03:22 x = y 16:03:22 " 16:03:23 ... I see the argument for an extensible syntax that could support every use case but I wonder if [that flexiblity] will ever be used 16:03:38 ... we're trying to solve a very simple problem 16:04:01 Shane: Mark's desire to make this legible can easily be written using the '=' syntax 16:04:07 Shane don't we do this: xmlns:a=""b"" 16:04:08 ... we can easily deal with extra whitespace 16:04:28 a = http://example.org?a=b 16:04:46 (.*")\s*=\s*(.*?)\s+ 16:05:05 prefix="a = http://example.org?a=b&c=d" 16:07:11 Manu: I'm leaning toward preferring this solution 16:07:17 ... straightforward and easy to implement 16:07:25 actually - can't use \s... need [\s\r\n] 16:07:32 ... don't think there's much danger of authors confusing the syntax in the markup 16:08:05 -msporny 16:08:06 -markbirbeck 16:08:09 next meeting: 2 weeks (April 16) 16:08:11 [adjourned] 16:08:21 (.*)[\s\r\n]*=[\s\r\n]*(.*?)[\s\r\n]+ 16:08:25 rrsagent, please draft minutes 16:08:25 I have made the request to generate http://www.w3.org/2009/04/02-rdfa-minutes.html Ralph 16:10:08 -Ralph 16:10:10 -??P0 16:10:11 SW_SWD(RDFa)11:00AM has ended 16:10:13 Attendees were Ralph, msporny, ShaneM, markbirbeck 16:10:26 rrsagent, please draft minutes 16:10:26 I have made the request to generate http://www.w3.org/2009/04/02-rdfa-minutes.html Ralph 16:14:21 zakim, bye 16:14:21 Zakim has left #rdfa 16:14:23 rrsagent, bye 16:14:23 I see 3 open action items saved in http://www.w3.org/2009/04/02-rdfa-actions.rdf : 16:14:23 ACTION: Manu to look at http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Dec/0037.html about resolving relative URIs [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action15] [1] 16:14:23 recorded in http://www.w3.org/2009/04/02-rdfa-irc#T15-07-46 16:14:23 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] [2] 16:14:23 recorded in http://www.w3.org/2009/04/02-rdfa-irc#T15-08-39 16:14:23 ACTION: Ralph or Steven fix the .htaccess for the XHTML namespace [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action01] [3] 16:14:23 recorded in http://www.w3.org/2009/04/02-rdfa-irc#T15-10-43