Re: Namespace landing page

Ivan, some issues with the landing page.

Retrieving http://www.w3.org/ns/csvw.jsonld returns content as text/plain. Should be application/ld+json

Using content-negotiation returns the right file, but also as text/plain:

curl -I -H 'Accept: application/ld+json' http://www.w3.org/ns/csvw
HTTP/1.1 200 OK
Date: Wed, 31 Dec 2014 22:51:23 GMT
Server: Apache/2
Content-Location: csvw.jsonld
Vary: negotiate,accept
TCN: choice
Last-Modified: Mon, 29 Dec 2014 08:42:04 GMT
ETag: "6d19-50b56d947af00;9f-50ab8a8466840"
Accept-Ranges: bytes
Content-Length: 27929
Cache-Control: max-age=21600
Expires: Thu, 01 Jan 2015 04:51:23 GMT
P3P: policyref="http://www.w3.org/2014/08/p3p.xml"
Content-Type: text/plain

The inappropriate content-type messes up some tooling.

Gregg Kellogg
gregg@greggkellogg.net

P.S. Happy New Year!

> On Dec 22, 2014, at 1:14 AM, Ivan Herman <ivan@w3.org> wrote:
> 
> All updated. I have also updated the README file that was still referring to the old names for the .ttl and jsonld version...
> 
> Although I have ruby on my machine, I never used it (sorry:-). I may test this at some point, although I may not have the right libraries either...
> 
> Ivan
> 
>> On 21 Dec 2014, at 19:52 , Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> 
>> One more change to consider for the Namespace: It uses the same title as [tabluar-metadata], namely "Metadata Vocabulary for Tabular Data", which of course, it is. We could consider something like "Namespace for Tabular Data".
>> 
>> (I also made a small change to the term definitions for for dc:title and dc:description to say "object values are interpreted as language-specifc, indexed by language". Instead of "array values interpreted as @language", which is incorrect, but this isn't very critical right now.
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> 
>>> On Dec 21, 2014, at 10:40 AM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>>> 
>>>> On Dec 21, 2014, at 4:02 AM, Ivan Herman <ivan@w3.org> wrote:
>>>> 
>>>> Gregg,
>>>> 
>>>> I have installed the files under
>>>> 
>>>> http://www.w3.org/ns/csvw.*
>>>> 
>>>> I used the 'base' as the respec document type; although that adds some lines to the status section that we should probably remove for the final version.
>>> 
>>> We may want to create a new document type in ReSpec for such namespace documents. It might also leave out the Editor field, which is not typical for namespace documents; I can look into that.
>>> 
>>>> I have also changed the 'alternate format' URI-s to csvw.{ttl,jsonld}, because that is how it works in the /ns directory. It may be a good idea to change that on the repository, too, but that probably depends on the way you generate those files, so I did not want to touch that. I have pushed the small changes of the index.html file to the repo.
>>> 
>>> Noted; I changed the filenames for those files in the repo, as well as the README entries on generating those files. For reference, the README in that directory describes how to update the vocabulary definitions (in _vocab.xlsx) and regenerate index.html, csvw.ttl and csvw.jsonld. We may want to find some automated way of verifying that term definitions used in the metadata document, the namespace document, and other documents are consistent. Perhaps, with suitable markup, the metadata document could be used as the source for generating the namespace documents.
>>> 
>>> Gregg
>>> 
>>>> Thanks!
>>>> 
>>>> Ivan
>>>> 
>>>> 
>>>>> On 21 Dec 2014, at 01:39 , Gregg Kellogg <gregg@greggkellogg.net> wrote:
>>>>> 
>>>>> Okay, now uses ReSpec and indicates status.
>>>>> 
>>>>> Gregg Kellogg
>>>>> gregg@greggkellogg.net
>>>>> 
>>>>>> On Dec 20, 2014, at 12:13 PM, Dan Brickley <danbri@google.com> wrote:
>>>>>> 
>>>>>> On 20 December 2014 at 08:44, Ivan Herman <ivan@w3.org> wrote:
>>>>>>> I haven't reviewed all the details, but I am happy to install these if we all give a thumb up (you have mine). Even if the content is not final, hey, these are still drafts.
>>>>>> 
>>>>>> It looks good to me in terms of the basic structure / approach. It
>>>>>> needs a 'Status of This Document' warning that it is a
>>>>>> work-in-progress and in support of [list of docs] produced by the CSVW
>>>>>> WG [link]. We should also flag the possibility that it may not be
>>>>>> perfectly in sync with the latest Working Drafts from the WG, or for
>>>>>> that matter that the WDs might not all be 100% mutually consistent
>>>>>> (and on that point, I can't comment on the detail of how well it does
>>>>>> match materials from the WDs...)
>>>>>> 
>>>>>> Apart from that it looks good to go.
>>>>>> 
>>>>>> Thanks for putting this together, Gregg!
>>>>>> 
>>>>>> Dan
>>>>>> 
>>>>>>> Ivan
>>>>>>> 
>>>>>>>> On 19 Dec 2014, at 20:26 , Gregg Kellogg <gregg@greggkellogg.net> wrote:
>>>>>>>> 
>>>>>>>> I created an HTML+RDFa version of the CSVW vocabulary [1], built from the JSON-LD context document [2]. Note that the context was updated to use reverse properties to reference rdfs_classes, rdfs_properties, rdfs_datatypes, and rdfs_instances, making the body of the context a single object, rather than an array referenced by @graph.
>>>>>>>> 
>>>>>>>> The HTML includes RDFa equivalent to both the JSON-LD and Turtle [3] versions which are also referenced from the document as "alternate" references.
>>>>>>>> 
>>>>>>>> With group consensus, I believe that [1] can be placed at http://www.w3.org/ns/csvw/index.html along with context.jsonld and vocab.ttl, which should be served from http://www.w3.org/ns/csvw via appropriate content negotiation.
>>>>>>>> 
>>>>>>>> Gregg Kellogg
>>>>>>>> gregg@greggkellogg.net
>>>>>>>> 
>>>>>>>> [1] http://w3c.github.io/csvw/ns/
>>>>>>>> [2] http://w3c.github.io/csvw/ns/context.jsonls
>>>>>>>> [2] http://w3c.github.io/csvw/ns/vocab.ttl
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> ----
>>>>>>> Ivan Herman, W3C
>>>>>>> Digital Publishing Activity Lead
>>>>>>> Home: http://www.w3.org/People/Ivan/
>>>>>>> mobile: +31-641044153
>>>>>>> ORCID ID: http://orcid.org/0000-0003-0782-2704
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> ----
>>>> Ivan Herman, W3C
>>>> Digital Publishing Activity Lead
>>>> Home: http://www.w3.org/People/Ivan/
>>>> mobile: +31-641044153
>>>> ORCID ID: http://orcid.org/0000-0003-0782-2704
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
> 
> 
> ----
> Ivan Herman, W3C
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
> 
> 
> 
>

Received on Wednesday, 31 December 2014 22:53:44 UTC