Difference between revisions of "Meetings:Telecon2012.10.10"

From RDF Working Group Wiki
Jump to: navigation, search
(Turtle LC comments)
(Turtle LC comments)
Line 73: Line 73:
 
Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0013.html
 
Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0013.html
  
*
+
* ISSUE 189
 +
See thread starting with: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0043.html
 +
 
 +
* ISSUE-191: Various nits in Appendix B
 +
Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0017.html
 +
 
 +
 
 +
* Remaining i18n comments
 +
See summary: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0020.html
  
 
== Provenance Constraints Review ==
 
== Provenance Constraints Review ==

Revision as of 12:12, 9 October 2012

Wednesdays at 11am US Eastern time for 75 minutes
  17:00 Paris/Berlin/A'dam; 16:00 London)
Telephone US: +1.617.761.6200
  SIP: zakim@voip.w3.org
 Zakim code: 73394
IRC channel: #rdf-wg on irc.w3.org on port 6665
Zakim instructions:  http://www.w3.org/2001/12/zakim-irc-bot.html
RRSAgent instructions: http://www.w3.org/2002/03/RRSAgent
Scribe list: http://www.w3.org/2011/rdf-wg/wiki/Scribes


Admin

  • Chair: Guus Schreiber
  • Scribe: Mischa Tuffield
  • Alternate: Nicholas Humfrey


Minutes of last meeting

PROPOSED to accept the minutes of the 3 Oct:

   http://www.w3.org/2011/rdf-wg/meeting/2012-10-03


Review of action items

Next meeting

  • Next telecon: 17 October 2012


Next FTF

Mon-Tue 29-30 Oct, Lyon, France, co-located with TPAC.

Info and registration information:

 http://www.w3.org/2012/10/TPAC/

See also Sandro's recommendation for attending other meetings during TPAC:

 http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jul/0039.html

REMINDER: Please remember to register your intent on the F2F3 and, if attending in person, register and pay for TPAC.


Turtle LC comments

  • ISSUE-178: Reference IETF BCP 47 for language declaration label

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0008.html

  • ISSUE-179: Scope of document language label

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0001.html

  • ISSUE-180: Various random character references should be more explicit label

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0009.html

  • ISSUE-181: Non-ASCII IRI example

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0010.html

  • ISSUE-182: cultural relevance of examples

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0011.html

  • ISSUE-184: Malformed escapes examples

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0012.html

  • ISSUE-185: Line terminator assumptions

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0023.html

  • ISSUE-188: special handling of % in IRI

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0013.html

  • ISSUE 189

See thread starting with: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0043.html

  • ISSUE-191: Various nits in Appendix B

Proposal: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0017.html


  • Remaining i18n comments

See summary: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0020.html

Provenance Constraints Review

Progress on LC reviews (actions 184+185)

 http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jul/0043.html
 http://www.w3.org/blog/SW/2012/09/12/last-call-constraints-of-the-provenance-data-model/

Graphs

Given our timeline, can we be finished with Datasets in this telecon?

TriG Syntax

Discuss whether in our dataset syntax, triples of the dataset's default graph MUST or MAY be surrounded by curly braces.

Related question: How can a human tell a Turtle document from a TriG document?

PROPOSED: In TriG, triples of the dataset's default graph [MUST|MAY] be surrounded by curly braces.


PROPOSED: Implementations that parse and store information from TriG documents MAY turn the TriG default graph into a named graph with a name chosen in an implementation-dependent way.

PROPOSED: The WG suggests it's a good practice to put metadata about a TriG document in the document's default graph.

AOB