- From: Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk>
- Date: Fri, 20 Jun 2014 15:07:50 +0000
- To: Ivan Herman <ivan@w3.org>
- CC: W3C CSV on the Web Working Group <public-csv-wg@w3.org>
Monday ... very fine! Have a nice weekend. Jeremy > -----Original Message----- > From: Ivan Herman [mailto:ivan@w3.org] > Sent: 20 June 2014 15:33 > To: Tandy, Jeremy > Cc: W3C CSV on the Web Working Group > Subject: Re: June 18 call summary: resolved to publish use-cases-and- > requirements > > Jeremy, > > I am happy to help but... not right now. I have just come back home, > sorting out my emails, but will not really touch things before Monday. > I hope that is fine. > > Some comments/answers below. > On 20 Jun 2014, at 11:33 , Tandy, Jeremy > <jeremy.tandy@metoffice.gov.uk> wrote: > > > Ivan - request for a little favour please :-) > > > > There are a small number of references in the [UCR doc][1] that point > to W3C specs using anchor elements <a> rather than the "proper" > [[{ref}]] method. > > Ah, yes. That should be fine. As long as the same specs also appear in > the references, ie, that at least at some page you use the [[...]] > jargon. > > > > > I'm stumped as to which reference should be used. > > > > Not sure I understand the quesiton. > > > There are also some relative (or explicit refs to w3c.github.io/csvw) > references to the CSV data model / syntax and metadata vocabulary > documents too. Should these also use the [[{ref}]] form? > > In those cases relative references are definitely not good, the > github.io should be used. I think it would be a good idea to use the > [[{ref}]] making it sure that these are the editor's copy, but also > refer to the /TR version as a reference (when applicable, that is) > > > > > > Finally, we make a few references to RDF, Turtle, JSON and XML. > Should these be explicitly linked to the appropriate W3C TRs? > > I think it would be better indeed. > > > > > If you feel that it is necessary, please could you amend the HTML and > commit the changes to gh-pages branch please? > > > > Intances: > > > > [lines 114 & 115] RDF, JSON and XML ... informative references; not > > currently linked """<li>Mapping mechanism to transforming CSV into > various Formats (e.g., RDF, JSON, or""" > > """XML)</li>""" > > > > ... there are a large number of references to RDF, JSON and XML in > the remainder of the document; hopefully if we provide the references > here at the beginning of the file, this will suffice? > > Yes. > > > > > [line 134] tabular data model > > """<a href="../syntax/index.html">Model for Tabular Data and Metadata > on the Web</a>:</p>""" > > > > [line 1916] tabular data model > > """<a href="http://w3c.github.io/csvw/syntax/#core-model">core > tabular data model</a>""" > > Use absolute URI, but I think it is better to add a reference to the > end. Eventually, when the document is final, it should refer to our own > documents in the references, so doing it now looks like a good idea. > > > > > [line 2804] RDF/OWL ... informative reference """(from 2012-2013) > > developed an <a > href="http://hxl.humanitarianresponse.info/ns/index.html">RDF/OWL > vocabulary</a>""" > > That should be fine. > > > > > [line 2944] SKOS ... informative reference """<p>Being familiar with > > <a href="http://www.w3.org/TR/skos-reference/">SKOS</a>, our user > decides""" > > > > That should be fine. We do not refer to SKOS as a fundamental > reference, it is only in the explanation > > > > [line 3119] Turtle syntax ... informative reference; not currently > > linked """<p>A snippet of the final SKOS concept scheme, expressed in > RDF using Turtle syntax, resulting""" > > > > I think having a reference to the formal Turtle syntax is better. But > it is borderline. But if you do not go through the [[...]] jargon, at > least an <a> element would be good. > > > [line 3183] tabular data model > > """<a href="http://w3c.github.io/csvw/syntax/">syntax for tabular > data</a>.</p>""" > > > > See above. > > > [line 3230] metadata vocabulary > > """the <a href="../metadata/index.html">Metadata Vocabulary for > Tabular Data</a>.</p>""" > > > > Again, use absolute URI, but I think it is better to add a reference to > the end. Eventually, when the document is final, it should refer to our > own documents in the references, so doing it now looks like a good > idea. > > > > [line 3338] tabular data model > > """<a href="http://w3c.github.io/csvw/syntax/#core-model">core > tabular data model</a>, yet lacking""" > > > > Same as above. > > > [line 3796] Turtle syntax ... informative reference; not currently > > linked """illustrates how a row of tabular data can be mapped to > equivalent content expressed in RDF (Turtle).</p>""" > > > > Ah, in line 3796 this seems like a borderline... > > > [line 3893] CURIE ... informative reference """permitted in URIs (as > > defined in [[RFC3986]]) or <a > href="http://www.w3.org/TR/curie/">CURIEs</a>.</p>""" > > > > I think a formal reference would be better. > > > [line 4155] tabular data model > > """<a href="http://w3c.github.io/csvw/syntax/index.html">model for > tabular data</a>, prior to applying""" > > > > [line 4164] tabular data model > > """<a href="http://w3c.github.io/csvw/syntax/index.html">model for > tabular data</a>.</p>""" > > > > See above. > > I hope this helps a little. More on Monday... > > Cheers > > Ivan > > > Thanks, Jeremy > > > > [1]: http://w3c.github.io/csvw/use-cases-and-requirements/ > > > >> -----Original Message----- > >> From: Dan Brickley [mailto:danbri@google.com] > >> Sent: 18 June 2014 14:33 > >> To: public-csv-wg@w3.org > >> Subject: June 18 call summary: resolved to publish use-cases-and- > >> requirements > >> > >> agenda: https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-06-18 > >> minutes: http://www.w3.org/2014/06/18-csvw-minutes.html > >> > >> highlights: > >> > >> Re http://w3c.github.io/csvw/use-cases-and-requirements/ > >> > >> On the basis of unanimous 'yes' responses by email and in the > >> meeting, > >> * RESOLVED: ok to publish at editor's + staff contact's discretion > >> > >> We also discussed republishing http://w3c.github.io/csvw/syntax/ > >> (which Jeni will propose on the list) and getting a 1st WD for the > >> Metadata spec. There are a few editorial tasks to address first, > >> again Jeni will propose something to the list. > >> > >> Next steps: UCR editors, can you wrap up any outstanding tweaks, and > >> liaise with Ivan to get a publication date scheduled? (please copy > >> the list on these details) > >> > >> chairs, > >> > >> Dan > > > > > ---- > Ivan Herman, W3C > Digital Publishing Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > GPG: 0x343F1A3D > WebID: http://www.ivan-herman.net/foaf#me > > > >
Received on Friday, 20 June 2014 15:08:20 UTC