14:21:19 RRSAgent has joined #rdf-wg 14:21:19 logging to http://www.w3.org/2011/06/01-rdf-wg-irc 14:21:21 RRSAgent, make logs world 14:21:21 Zakim has joined #rdf-wg 14:21:23 Zakim, this will be 73394 14:21:23 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 39 minutes 14:21:24 Meeting: RDF Working Group Teleconference 14:21:24 Date: 01 June 2011 14:27:12 Scott has joined #rdf-wg 14:30:55 cygri has joined #rdf-wg 14:51:14 Scott_Bauer has joined #rdf-wg 14:52:16 Guus has joined #rdf-wg 14:53:25 SW_RDFWG()11:00AM has now started 14:53:32 +hsbauer 14:53:42 +Guus 14:53:57 zakim, hsbauer is me 14:53:57 +Scott_Bauer; got it 14:55:07 mbrunati has joined #rdf-wg 14:55:40 +davidwood 14:56:12 zakim, who is here? 14:56:12 On the phone I see Scott_Bauer, Guus, davidwood 14:56:59 zakim, dial ivan-voip 14:56:59 ok, ivan; the call is being made 14:57:01 +Ivan 14:57:28 SteveH_ has joined #rdf-wg 14:57:30 Zakim, please dial ericP-office 14:57:30 ok, ericP; the call is being made 14:57:32 +EricP 14:57:45 +??P25 14:58:06 AZ has joined #rdf-wg 14:58:21 AndyS has joined #rdf-wg 14:58:40 Olivier has joined #rdf-wg 14:58:40 +??P22 14:58:45 pchampin has joined #rdf-wg 14:58:47 +??P26 14:58:53 zakim, ??P22 is me 14:58:53 +mbrunati; got it 14:58:56 Zakim, ??P26 is me 14:58:56 +SteveH_; got it 14:59:12 cmatheus has joined #rdf-wg 14:59:19 +AlexHall 14:59:24 AlexHall has joined #rdf-wg 14:59:47 zakim, who is here? 14:59:47 On the phone I see Scott_Bauer, Guus, davidwood, Ivan, EricP, ??P25 (muted), mbrunati, SteveH_, AlexHall 15:00:05 +FabGandon 15:00:15 zakim, ??P25 is me 15:00:15 +pchampin; got it 15:00:22 +??P30 15:00:42 +??P3 15:00:42 zakim, ??P30 is me 15:00:44 +AndyS; got it 15:00:50 +pfps 15:01:03 zakim, ??P30 is me 15:01:03 I already had ??P30 as AndyS, cmatheus 15:01:07 +wcandillon 15:01:19 pfps has joined #rdf-wg 15:01:20 zakim, wcandillon is me 15:01:20 +AZ; got it 15:01:22 +LeeF 15:01:35 zakim, who is on the phone? 15:01:35 On the phone I see Scott_Bauer, Guus, davidwood, Ivan, EricP, pchampin (muted), mbrunati, SteveH_, AlexHall, FabGandon, AndyS, ??P3, pfps, AZ, LeeF 15:01:42 +mhausenblas 15:01:42 Yes 15:01:46 zakim, ??P30 is really me. Really! Please let me have it. 15:01:49 I don't understand you, davidwood1 15:01:56 Zakim, I know :) 15:01:57 I'm glad that smiley is there, davidwood1 15:02:01 zakim, ??P3 is me 15:02:05 +cmatheus; got it 15:02:48 Chair: David Wood 15:02:51 zakim, who is on the phone? 15:02:51 On the phone I see Scott_Bauer, Guus, davidwood, Ivan, EricP, pchampin, mbrunati, SteveH_, AlexHall, FabGandon, AndyS, cmatheus, pfps, AZ, LeeF, mhausenblas 15:02:52 Zakim, who is here? 15:02:53 zakim, mhausenblas is temporarily me 15:02:54 On the phone I see Scott_Bauer, Guus, davidwood, Ivan, EricP, pchampin, mbrunati, SteveH_, AlexHall, FabGandon, AndyS, cmatheus, pfps, AZ, LeeF, mhausenblas 15:02:54 zakim, mute me 15:02:56 +cygri; got it 15:02:56 pchampin should now be muted 15:03:03 +??P36 15:03:10 Scribe: Alex Hall 15:03:21 Zakim, ??P36 is BBC 15:03:21 +BBC; got it 15:03:23 Scribenick: AlexHall 15:03:30 +JeremyCarroll 15:03:49 +Souri 15:04:22 regrets: axel, pat, mischat, souri 15:04:25 topic: Admin 15:04:53 zwu2 has joined #rdf-wg 15:04:55 davidwood: there were several resolutions from last meeting, please review the minutes. 15:05:02 zakim, code? 15:05:02 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), zwu2 15:05:13 RESOLVED: minutes from last meeting accepted 15:05:22 pfps has joined #rdf-wg 15:05:29 zakim, who is noisy? 15:05:30 minutes look OK to me 15:05:32 +zwu2 15:05:38 sorry I am late 15:05:39 ivan, listening for 10 seconds I heard sound from the following: AZ (16%), Guus (5%), davidwood (59%), Ivan (25%) 15:05:50 zakim, mute me 15:05:50 Ivan should now be muted 15:06:19 Zakim, BBC also has NickH 15:06:19 +NickH; got it 15:06:24 Zakim, BBC also has yvesr 15:06:24 +yvesr; got it 15:06:30 cygri: still working on writing up named graph proposals for action-25 15:06:46 ... happy to keep action open or accept help from others 15:07:01 JeremyCarroll has joined #rdf-wg 15:07:08 ACTION-25? 15:07:08 ACTION-25 -- Richard Cyganiak to write up the different options re ISSUE-15 -- due 2011-04-13 -- OPEN 15:07:08 http://www.w3.org/2011/rdf-wg/track/actions/25 15:07:39 +sandro 15:07:55 cygri: action-51 text is implemented in local copy and waiting for hg repository 15:08:11 +OpenLink_Software 15:08:18 Zakim, OpenLink_Software is temporarily me 15:08:18 +MacTed; got it 15:08:20 Zakim, mute me 15:08:20 MacTed should now be muted 15:08:45 trackbot, close ACTION-51 15:08:45 ACTION-51 Implement ISSUE-40 resolution in RDF Concepts Editor's draft; see http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0238.html and replies for text closed 15:08:55 guus: still trying to figure out what purpose of action-51 was 15:09:04 s/action-51/action-47 15:09:26 topic: Language tags 15:09:26 ISSUE-64: RFC 3066 or RFC 5646 for language tags? 15:09:26 Richard's proposal to resolve: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0441.html 15:09:26 ISSUE-64 RFC 3066 or RFC 5646 for language tags? notes added 15:09:44 davidwood: Richard has proposal to resolve language tag issue 15:09:52 AZ has joined #rdf-wg 15:10:05 q+ to express surprise at the current text 15:10:14 cygri: spec currently refers to obsoleted rfc 3066 for language tags 15:10:31 ... proposal is to use latest rfc 5646 15:10:38 Pat's reformulation/explanation: http://lists.w3.org/Archives/Public/public-rdf-wg/2011Jun/0010.html 15:10:56 Lee F also expressed support: http://lists.w3.org/Archives/Public/public-rdf-wg/2011Jun/0011.html 15:11:10 ... the new RFC has two notions of validity: well-formedness (grammar only) and validity (lang tag actually exists) 15:11:52 ... add a note that the previous RFC allowed lang tags that are no longer allowed under the latest version 15:12:01 +1 ref'ing 5646, +1 to holding at well-formedness, +1 to explanatory note 15:12:06 +1 15:12:07 ... adopt the loosest notion of well-formedness 15:12:36 davidwood: do you agree with pat's latest note on the mailing list? 15:12:49 cygri: seems to be about a different issue 15:13:13 davidwood: apologies, it was a different issue 15:14:23 ???: when i read this note, it prompted me to drill down into original text around lang tags in the spec 15:14:57 s/???/JeremyCarroll 15:15:03 ... at some point there was a phrase to reference RFC 3066 or its successors 15:15:20 ... not sure what that phrase was dropped, would like to find out why 15:15:39 FabGandon has joined #rdf-wg 15:15:43 s/what/why/ 15:16:07 refs to unicode serve as a precedent for "or it's successors", but there are contracts which allow forward-thinking parsers to know what could be valid in the next decade or so 15:16:25 ... richard's point about validity vs. well-formedness was well taken and i support the proposal. 15:16:51 http://www.w3.org/2011/rdf-wg/track/issues/64 15:17:03 OK by me 15:17:25 ... not that I care .... Issue 12, on the other hand ... 15:17:29 +1 15:17:31 PROPOSAL: Resolve ISSUE-64 by updating RDF concepts as per Richard's proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0441.html 15:17:31 +1 15:17:34 OK if syntax restriction - not depending on registry state 15:17:35 +0 15:17:36 +1 15:17:36 +1 15:17:36 +1 15:17:38 +1 15:17:41 +1 15:17:43 +1 15:17:55 +1 15:17:59 +1 15:18:03 +1 15:18:04 +1 15:18:07 Souri has joined #rdf-wg 15:18:39 -Scott_Bauer 15:19:07 +Scott_Bauer 15:19:12 RESOLVED: Resolve ISSUE-64 by updating RDF concepts per Richard's proposal 15:19:23 q+ 15:19:26 ack ivan 15:19:31 ACTION: cygri to implement ISSUE-64 resolution 15:19:31 Created ACTION-54 - Implement ISSUE-64 resolution [on Richard Cyganiak - due 2011-06-08]. 15:19:37 Proposed text on replacing URIref with IRI 15:19:37 http://www.w3.org/2011/rdf-wg/wiki/IRIs/RDFConceptsProposal 15:19:37 Related email: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0413.html 15:19:47 ack JeremyCarroll 15:19:47 JeremyCarroll, you wanted to express surprise at the current text 15:19:47 ack 15:19:56 +[Sophia] 15:20:04 https://dvcs.w3.org/hg/rdf/ 15:20:14 zakim, Sophia is me 15:20:14 +FabGandon; got it 15:20:30 ivan: before we move on to other major issues, I have the hg repository set up and link is posted in IRC 15:21:10 q? 15:21:39 topic: Replacing URIref with IRI 15:21:47 davidwood: This is Richard's text 15:22:24 cygri: link is posted in minutes. issue is that we need to replace references to URI Reference in Concepts with references to IRI 15:22:48 ... fortunately this simplifies things because IRI defines things which were previously defined in RDF 15:23:00 ... main issue is what to do with the left-over notes in Concepts 15:23:29 ... there are characters which were allowed in URIrefs which are no longer allowed in IRIs 15:23:37 q+ to discuss IPv6 in ihost: http://tools.ietf.org/html/rfc3987#page-7 15:23:47 ... add note to indicate that these are no longer allowed except in %-encoded form 15:24:21 ... also a note to discourage %-encoded characters in old text, not sure this is a good idea 15:24:34 q+ to discuss percent-encoding 15:24:51 ack davidwood 15:24:51 davidwood, you wanted to discuss IPv6 in ihost: http://tools.ietf.org/html/rfc3987#page-7 15:24:59 ... would like feedback from others who have looked into it 15:25:29 There is %-enc text in RFC => (summary) use % only as necessary and not wildly. 15:25:36 q+ to suggest editors' draft should be updated with new text and public review sought 15:25:47 q? 15:25:52 IPv6 are legal using [] 15:25:56 davidwood: occurred to me since i'm dealing with IPv6 issues... IRI grammar seems to allow host names and IPv4 addresses but not IPv6 15:26:12 ... anybody know why this is? 15:26:23 AZ has joined #rdf-wg 15:26:26 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 15:26:31 right 15:26:34 ???: IRI allows IPv6 addresses in square brackets 15:26:36 I've actually used them :) 15:26:46 ack AlexHall 15:26:46 AlexHall, you wanted to discuss percent-encoding 15:26:50 RFC2732 adds them 15:27:04 s/???/SteveH/ 15:27:38 RFC 3986 page 19 15:28:16 section 3.2.2. Host 15:28:22 q+ to say last note is too long! 15:30:23 is there any reference that we could refer to regarding this notion of "canonical IRI"? 15:30:27 ack JeremyCarroll 15:30:27 JeremyCarroll, you wanted to suggest editors' draft should be updated with new text and public review sought and to say last note is too long! 15:30:50 q+ 15:30:56 +1 to Jeremy - it is better to defer than to copy 15:31:34 q- 15:31:36 AlexHall: Intent of the original text with %-encoding seemed to be to avoid interoperability issues, so I agree with the new proposal in this regard. 15:31:48 -1 to David - informative lists tend to become too normative 15:32:07 q+ to ask jeremy how much is too long 15:32:14 JeremyCarroll: Would like to simply defer to IRI section 5 for normalization 15:32:31 ... giving a long list here runs the risk of people thinking this is exhaustive or normative 15:33:06 davidwood: having the list there is nice as a summary so people don't have to hunt down the list themselves 15:33:26 cygri: the intent here is that they are informative, not normative, and this will be explicitly noted in the document. 15:34:09 q+ to propose adding "While RDF does not require normalization or IRIs, using only normalized IRI forms will improve the chances that non-RDF tools will consume and produce the same IRIs and that other parties will reproduce the exact spelling of these IRIs." 15:34:18 q? 15:34:22 q- 15:34:36 JeremyCarroll: Historically this section has been note-heavy, would prefer to see this stuff moved into a new section 3.7 15:34:53 -AZ 15:34:54 AZ has joined #rdf-wg 15:35:05 moving to an informative section would help a lot! 15:35:25 ack ericP 15:35:25 ericP, you wanted to propose adding "While RDF does not require normalization or IRIs, using only normalized IRI forms will improve the chances that non-RDF tools will consume and 15:35:29 ... produce the same IRIs and that other parties will reproduce the exact spelling of these IRIs." 15:35:38 +AZ 15:35:58 ericP: seems the root issue is that producing non-normalized IRIs decreases the chance that other tools will produce the same form 15:36:12 q+ 15:36:15 And other RDF apps. 15:36:20 with that text we are well on the way to section 3.7 15:36:23 ack cygri 15:36:36 ... propose to add some text (quoted in IRC) to explain the motivations for this note. 15:37:08 cygri: prefer to avoid motivations and give just a concise summary 15:37:34 davidwood: would like to cater to people who don't want to read through all the specs to get a good understanding 15:38:02 ... most conerns at this point seem to be editorial in nature 15:38:29 cygri: as soon as the working draft goes live this content will be added and i encourage further comments 15:38:48 ... don't think we need a resolution now but want interested people to keep any eye on it. 15:39:03 Topic: Revisit RDF Postponed Issues 15:39:19 davidwood: This always seems to get pushed down to the bottom of the agenda 15:39:36 ... let's take a few minutes to knock some of these down now 15:39:39 http://www.w3.org/2011/rdf-wg/track/issues/55 15:40:01 Issue-55 - not only no, but xxxx NO! the request is incorrect, anyway 15:40:22 s/xxxx/hell/ 15:40:24 seconded 15:40:34 yeah, lets not do that :) 15:40:39 PROPOSED: To close ISSUE-55 as this is not considered the duty of this group 15:40:39 +1 close it 15:40:41 agreed with closing 15:40:41 +1 15:40:42 +1 15:40:43 +1 15:40:44 +1 15:40:53 +1 15:40:57 +1 15:40:58 +1 15:40:59 +1 15:41:02 ISSUE-55? 15:41:02 ISSUE-55 -- Revisit "Request for a richer vocabulary for languages" -- raised 15:41:02 http://www.w3.org/2011/rdf-wg/track/issues/55 15:41:03 +1 15:41:59 2) With respect to the rules for comparing literals: http://www.w3.org/TR/rdf-concepts/#section-Literal-Equality For reasons of standardization and ease of use, there should exist a higher level matching rule that allows one to search for (lang="en", str) and to get matches to more detailed tags (lang="en-gb", str). This higher level rule should be defined 15:42:19 JeremyCarroll: we should close saying lang-matches from SPARQL addresses this issue 15:43:05 issue-56? 15:43:06 ISSUE-56 -- Revisit "A request for a semantics free predicate for comments" -- raised 15:43:06 http://www.w3.org/2011/rdf-wg/track/issues/56 15:43:06 http://www.w3.org/2011/rdf-wg/track/issues/56 15:43:07 RESOLVED01: To close ISSUE-55 as this is not considered the duty of this group 15:43:20 ISSUE-56: Revisit "A request for a semantics free predicate for comments" 15:43:20 ISSUE-56 Revisit "A request for a semantics free predicate for comments" notes added 15:43:21 +q 15:43:25 -Scott_Bauer 15:43:51 +Scott_Bauer 15:43:52 ack pfps 15:43:53 rdfs:comment? 15:44:02 no - not rdfs:comment 15:44:17 rdf:universal 15:44:19 ok, then / # 15:44:27 pfps: this is from Ian, there was annoyance in the OWL wg that rdfs:comment has semantics 15:44:44 ... that ship has sailed, rdfs:comment is there and has semantics 15:45:05 ... no third party is allowed to add new predicates to the RDF namespace 15:45:13 ... we should close it 15:45:32 +1 to closing 15:45:33 +1 15:45:35 +0 15:45:36 +1 15:45:37 +1 15:45:37 +1 15:45:37 +1 15:45:39 +0 15:45:39 +1 to closing 15:45:40 +1 15:45:42 +0 15:45:44 +1 15:45:45 PROPOSED: Resolve ISSUE-56 by closing it. 15:46:15 +0 15:46:21 RESOLVED: Resolve ISSUE-56 by closing it. 15:47:23 http://www.w3.org/2011/rdf-wg/track/issues/57 15:47:29 q+ for issue-57 15:47:41 ISSUE-57: Revisit "A request to define subset of RDFS with a more conventional layered architecture" 15:47:41 ISSUE-57 Revisit "A request to define subset of RDFS with a more conventional layered architecture" notes added 15:48:06 is anybody speaking right now? 15:49:28 q+ 15:49:40 +1 to peter 15:49:50 close it, reject 15:49:54 davidwood: instead of continuing, we should open it and revisit when we finish the specs 15:50:20 What would a more layered architecture look like? It's not just change of exposition. 15:50:33 q+ to ask about RDFS-DL ? 15:50:49 ack pfps 15:50:49 pfps, you wanted to discuss issue-57 and to 15:50:51 pfps: we won't be addressing this in this WG 15:51:15 ... there was a request for some defined fragment of RDFS that fits nicely into OWL 15:52:13 davidwood: sounds like yet another proposal for yet another subset of logical formalism 15:52:13 q- 15:52:14 q+ 15:52:29 propose to close by doing nothing, no strong expressed need 15:52:31 ack JeremyCarroll 15:53:23 I don't think we need to spend telecon time on this, we are all in violent agreement :-) 15:54:00 +1 15:54:03 +0 15:54:04 +1 15:54:05 PROPOSED: to close ISSUE-57 by stating that it's not in our charter and we have no intention of doing it. 15:54:05 +1 15:54:07 +1 15:54:08 +1 to crush the can 15:54:09 +1 15:54:10 +0 15:54:10 +1 15:54:14 +1 15:54:21 1 15:54:23 +0 15:54:24 +1 15:54:28 RESOLVED01: to close ISSUE-57 by stating that it's not in our charter and we have no intention of doing it. 15:54:33 +1 15:54:47 ]/me Guus 15:54:56 ISSUE-12: Reconcile various forms of string literals 15:54:56 ISSUE-12 Reconcile various forms of string literals (time permitting) notes added 15:54:56 http://www.w3.org/2011/rdf-wg/track/issues/12 15:55:16 Topic: ISSUE-12 (string literals) 15:55:17 ISSUE-12: Reconcile various forms of string literals (time permitting) 15:55:17 ISSUE-12 Reconcile various forms of string literals (time permitting) notes added 15:55:47 davidwood: I note that this item is marked as "time-permitting" in the charter 15:55:59 q+ 15:56:05 +1 to keeping Pat simple :-) 15:56:17 "simple" != about 2k of text 15:56:25 ... who would like to speak for pat and his request to keep it simple? 15:56:27 ack cygri 15:56:28 http://www.w3.org/mid/C2088CAC-65A4-4B20-B657-C48A0440DE69@ihmc.us is pat's mail 15:56:48 Ivan, that URI gives me a 404 15:56:52 http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0430.html 15:56:58 Pat's email just re-expresses Richard's proposal, as far as i can tell. 15:57:02 http://www.w3.org/2011/rdf-wg/wiki/StringLiterals/AbolishUntaggedPlain 15:57:03 cygri: would not like to speak to what pat said, seems to just point out that the last proposal wasn't that complicated 15:57:21 sorry 15:57:29 http://lists.w3.org/Archives/Public/public-rdf-wg/2011Jun/0010.html is pat's mail 15:57:31 +1 to http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0430.html 15:57:36 Remaining issue is class vs datatype because DATATYPE("foo"@en) =? rdf:TaggedThing 15:57:37 ... would like to talk about another proposal that addresses only strings without language tag 15:57:50 ... seems to be agreement on this aspect of it 15:58:28 q+ 15:58:58 ... the proposal is to unify un-tagged string literals is to abolish the untagged plain literal in the abstract syntax and consider "foo" to be syntactic sugar for "foo"^^xsd:string in the concrete syntax 15:59:29 s/is to abolish/by abolishing/ 15:59:31 To Pat's email - if only class, then DATATYPE() => error still?? Seems unhelpful. 15:59:54 pfps: like this proposal better than previous ones 16:00:46 -FabGandon 16:01:00 -FabGandon.a 16:01:02 ... have some compliant about the use of rdf:LangTaggedString, not sure it is needed and will require changes to RDF semantics, OWL, and SPARQL 16:01:22 AZ has joined #rdf-wg 16:01:42 FabGandon has left #rdf-wg 16:01:56 rdf:LangTaggedString = rdfs:Literal - union of all typed literals 16:02:01 ... thinks it's OK to handle rdf:LTS in OWL but need to verify 16:02:17 ack SteveH 16:02:32 ... would like to send a note to the OWL WG 16:02:54 Question: Will "abc" still be a valid RDF literal? For example, would it be ok for me present the following triple for insertion: rdfs:label "John" , OR am I obliged to present: rdfs:label "John"^^xsd:string ? Also, can SPARQL query return "John" as a value for a variable? 16:03:02 q+ 16:03:11 SteveH: my concern is that we previously resolved to do just the opposite, to turn xsd:string into plain literals 16:03:26 q- 16:03:43 (was going to ask where this is visible, but then Steve answered it) 16:03:47 I agree with Steve's concern 16:03:48 ... this seems to match what users expect, since most string data in the wild is not typed as xsd:string 16:03:59 ... there is also concern about how this plays with SPARQL 16:04:38 +1 - SPARQL results must return non-DT string for xsd:string for this else massive surprises (= lots of support costs). 16:05:00 q? 16:05:15 s/agree with/share/ 16:05:18 ... SPARQL results will return lots of unexpected xsd:string datatypes 16:05:33 q+ 16:05:45 q+ 16:05:51 ack cygri 16:06:03 ... seems odd to go to all this trouble to remove plain literals from the abstract syntax and turn around and strip out xsd:string types on the way out of the system. 16:06:05 q+ to say we can have both : syntax vs semantics 16:06:12 making a difference btw 2 kinds of strings is even more perverse 16:07:01 cygri: the only syntax that really needs changing is N-Triples... 16:07:15 q+ to suggest predictability also hel[ful for XML 16:07:40 ... syntactic sugar in most concrete syntaxes is bad because it reduces predictability 16:08:23 ... forbidding one datatype in the abstract syntax is even more perverse than forbidding plain literals in one of the concrete syntaxes 16:09:02 SteveH, I liked deprecating xs:string until it looked like we could get rid of Plain Literals entirely (via using language-tags-as-datatypes). 16:09:25 Sandro, right. Me, too. 16:09:31 q- 16:09:32 ack ivan 16:09:35 We could have both "abc" and "abc"^^xsd:string as equivalent (identical when compared), but treat the simple literal form "abc" to be the canonical one. 16:09:35 davidwood: none of the proposals seems to play nicely with all the various levels (semantics, concepts, RDF document set, implementations) 16:09:37 I hope people wont be expected to emit the long form. 16:09:40 ack AndyS 16:09:40 AndyS, you wanted to say we can have both : syntax vs semantics 16:09:50 sandro, I like lang tag -> datatype 16:10:16 AndyS: agree with Steve's concerns re. xsd:string in concrete syntaxes, think this could be abolished if we're careful 16:10:17 ... 16:10:22 +1 to andy / split surface syntax from abstract syntax 16:10:29 +1 to short-forms only in the serializations 16:10:39 ack JeremyCarroll 16:10:39 JeremyCarroll, you wanted to suggest predictability also hel[ful for XML 16:10:43 +1 to AndyS 16:10:51 ... but we can split the abstract and sufrace syntaxes and use different approaches in each 16:11:00 AZ has joined #rdf-wg 16:11:18 Jeremy: If we're making N-Triples, Turtle more predictable then we should also make RDF/XML more predictable. 16:11:57 davidwood: If we ingest RDF literals, turn them into xsd:string internally, and emit them back as plain literals, is this consistent with what you said: 16:12:13 AndyS: yes it is, and I can't think of a format where you wouldn't want to do that. 16:12:30 NO! 16:12:53 davidwood: are we re-defining xsd:string? 16:12:57 everybody: NO! 16:13:39 q+ 16:13:41 ???: we're retroactively declaring that all plain literals without language tags are actually xsd:strings 16:13:47 At the RDF APIs will be much simpler, Andy. 16:13:55 At LEAST, the APIs.... 16:14:48 sandro - not so simple?? - are serializers inside or outside such API? 16:14:48 davidwood: Volunteers to start a wiki page to collect all the places that are affected by Richard & Pat's ISSUE-12 proposal? 16:15:22 Request for a consolidate text for R+P proposal. 16:15:26 http://www.w3.org/2011/rdf-wg/wiki/StringLiterals/AbolishUntaggedPlain 16:16:53 Please rename - if we keep untagged-in-surface syntax, it's a bad name. 16:17:08 cygri: it's been my understanding that this conversation has been only about string literals without language tags 16:17:34 AZ has joined #rdf-wg 16:17:39 davidwood: can you combine this with the language-tag proposal? 16:18:06 cygri: point was to keep them separate because there is still disagreement about language tags 16:18:45 q? 16:18:51 davidwood: request for somebody to add to the wiki page for this proposal a section that collects all documents which will need to change as a result of it. 16:19:39 ack Souri 16:19:59 SPARQL query is doable / SPARQL XML results is not being opened this time => trickier 16:20:20 souri: looking at this proposal, intent seems to be that these two forms are declared equivalent 16:20:45 ... we should define a canonical form for the surface syntax so we know how to output the value in query results 16:20:59 davidwood: we are over time 16:21:11 bye 16:21:12 regrets next week for semtech 16:21:12 ... think we've made progress 16:21:13 bye 16:21:13 bye 16:21:13 regrets for next week - semtech 16:21:15 ... adjourned. 16:21:16 -LeeF 16:21:17 -davidwood 16:21:17 -sandro 16:21:18 bye 16:21:19 -MacTed 16:21:20 -Ivan 16:21:20 -zwu2 16:21:21 -SteveH_ 16:21:21 -EricP 16:21:23 -pchampin 16:21:23 bye 16:21:25 -cmatheus 16:21:27 -JeremyCarroll 16:21:29 -mbrunati 16:21:31 -pfps 16:21:33 -Scott_Bauer 16:21:35 -AlexHall 16:21:37 -BBC 16:21:39 -AndyS 16:21:41 -Souri 16:21:43 -cygri 16:21:46 -AZ 16:21:47 -Guus 16:21:49 SW_RDFWG()11:00AM has ended 16:21:51 Attendees were Guus, Scott_Bauer, davidwood, Ivan, EricP, mbrunati, SteveH_, AlexHall, FabGandon, pchampin, AndyS, pfps, AZ, LeeF, cmatheus, cygri, BBC, JeremyCarroll, Souri, zwu2, 16:21:54 ... NickH, yvesr, sandro, MacTed 16:22:06 AndyS has left #rdf-wg 16:24:28 SteveH has joined #rdf-wg 17:02:09 SteveH_ has joined #rdf-wg 17:25:11 AlexHall has left #rdf-wg 18:36:10 Zakim has left #rdf-wg 18:38:38 mischat has joined #rdf-wg 19:08:05 SteveH has joined #rdf-wg 20:06:51 SteveH has joined #rdf-wg 20:09:37 davidwood has joined #rdf-wg