- From: Sandro Hawke <sandro@w3.org>
- Date: Wed, 30 May 2012 10:12:46 -0400
- To: David Wood <david@3roundstones.com>
- Cc: RDF WG <public-rdf-wg@w3.org>
On Mon, 2012-05-28 at 11:56 -0400, David Wood wrote: > Hi all, > > Thanks to all who reviewed. The presentation has been updated. Detailed comments below. And now some more comments. Overall, speaking as someone who's done lots of these, it looks good. A few little things: - I wouldn't say "consensus is fragile", because that suggests the process is unreliable. I'd say these are the decisions we've made based on the input we have so far, but we're still gathering input and if something unexpected comes in, at this stage we might still change the design because of the new data. - The list of current resolutions is nice; maybe also point to the list of closed issues: http://www.w3.org/2011/rdf-wg/track/issues/closed (it might be nice to view them side-by-side, some day. Many of them need the other. Want an RDF dump of the issues? :-) - On little turtle changes, I'd include issue 18. ("You no longer need to put a space before the period, but you do need to include a trailing digit after your decimal points.") -- Sandro > On May 28, 2012, at 04:35, Richard Cyganiak wrote: > > Slide 17 says: "The value space consists of is a set…" Remove the extra words > > Done. > > > > > 16+17 Value space and equality for rdf:XMLLiteral and rdf:HTML are in fact identical; the slides sort of re-state them in different ways, implying a significant difference > > Thanks, normalized. > > > > > 17 It's rdf:HTML, not rdf:HTMLLiteral > > OK. Changed. > > > Maybe worth noting that one can now escape characters in prefixed names using backslashes: ex:resource\/thing123, ex:thing123\#this. In general, there was an attempt to allow as many characters as possible unescaped in prefixed names (period, colon, digit at start), while allowing the rest in escaped form. > > Done. > > > On May 28, 2012, at 04:21, Andy Seaborne wrote: > > Slide 5: +1 to DanBri's point about N3 > > Looking back at the presentation and my notes, I have no idea why that is there. It has been removed. > > Thanks to Nathan, Dan and Andy for catching that error! > > > > > Was that supposed to be N-Quads and TriG? > > Hmm, no. I didn't want to say anything about anything that might not happen. > > > > > > Slide 18: > > > > Worth mentioning UTF-8 for N-triples? > > Done. > > > > > Slide 19: > > > > In Turtle, I thought "true" and "false" are case sensitive (they should have been in SPARQL because the lexcial forms in XSD are -- too late). > > Good catch! The January 2010 ED [1] says "case-independent constants for XSD booleans true and false", but the current Turtle editors' draft, section 3.2.3 [2] says: > [[ > Boolean values may be written as either true or false (case-sensitive) and represent RDF literals with the datatype xsd:boolean > ]] > > > > > ns:foo:bar is now legal. > > Thanks, added. > > On May 27, 2012, at 22:31, Nathan wrote: > > Slide 11 - "Graph Container ... like a set" - ensure they know you mean a mutable set, rather than a static mathematical set. > > Thanks. I added the word "mutable". > > > Regards, > Dave > > [1] http://www.w3.org/2010/01/Turtle/ > [2] http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#representing-booleans-in-turtle > > > > > Andy > > > > On 28/05/12 03:15, David Wood wrote: > >> Hi all, > >> > >> My slides for a talk on "Updating RDF" to be given at SemTechBiz [1] on Wed, 6 June in San Francisco are at [2]. Any comments appreciated. The speaker's notes are at the bottom of the slides. > >> > >> Regards, > >> Dave > >> > >> [1] http://semtechbizsf2012.semanticweb.com/ > >> [2] http://www.slideshare.net/3roundstones/rdf-wg-update-semtechbiz-2012 > >> > >> > >> > > > > >
Received on Wednesday, 30 May 2012 14:12:59 UTC