W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > October 2019

Re: [dxwg] Dedicated support for HTTP compliant datasets (#1086)

From: Claus Stadler via GitHub <sysbot+gh@w3.org>
Date: Fri, 11 Oct 2019 20:02:00 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-541204779-1570824119-sysbot+gh@w3.org>
A quick example to clarify what I mean by the HTTP content negotiation aspect:

Let's say there is a DCAT catalog on the Web with an n-triple and turtle distribution
        a cat:Dataset ;
        cat:distribution my:dist-as-ttl, my:dist-as-nt .

my:dist-as-ttl        a                cat:Distribution ;
        dc:format "application/turtle" ;
        cat:downloadURL  <https://gitlab.com/.../demo.ttl> .

my:dist-as-nt        a                cat:Distribution ;
        dc:format "application/n-triples" ;
        cat:downloadURL  <https://gitlab.com/.../demo.nt> .

Then I would assume that if anyone wrote a DCAT HTTP server that can serve datasets based on DCAT (I call that a data node), that a client could do:

`curl -X POST -H 'Accept: application/n-triples 'http://localhost/my-datanode?id=my:dataset`

And the data node would choose the appropriate distribution from it:

HTTP/1.1 200 OK
Date: Fri, 11 Oct 2019 19:49:09 GMT
Content-Type: application/n-triples; charset=utf-8
Content-Location: https://gitlab.com/.../demo.nt <--- ntriples served

Of course there are forseeable subtleties, which a data node has to handle, such as avoiding sending out content locations that cause a HTTP 506 Variant Also Negotiates.

GitHub Notification of comment by Aklakan
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1086#issuecomment-541204779 using your GitHub account
Received on Friday, 11 October 2019 20:02:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:21 UTC