W3C home > Mailing lists > Public > public-gld-comments@w3.org > July 2013

Re: Use of dcat:mediaType

From: John Erickson <olyerickson@gmail.com>
Date: Thu, 18 Jul 2013 11:41:20 -0400
Message-ID: <CAC1Gg8TCydz3sFXCUYOykPaQ-h-jYX1hQ0iAzaAAmXf-XQKT5A@mail.gmail.com>
To: Alasdair Gray <alasdair.gray@manchester.ac.uk>
Cc: public-gld-comments@w3.org
Hi Alasdair!

RE the dcat:mediaType issue, I think this applies to many properties
that typically will have literal values (e.g. "audio/BV16"), but in
some cases might have URI values (e.g.
http://purl.org/NET/mediatypes/audio/BV16 ). DCAT shares this with
esp. Dublin Core.

For a good discussion of how DC accommodates this see e.g.
"Representing DCAM constructs using the RDF Model"
<http://www.dublincore.org/documents/dc-rdf/#sect-4>

John

On Thu, Jul 18, 2013 at 10:54 AM, Alasdair Gray
<alasdair.gray@manchester.ac.uk> wrote:
> Hi,
>
> I am curious as to how dcat:mediaType should be used within a description.
>
> There is a single example in the DCAT document that has a literal as the
> value. Is there a list of all the valid values? WIll this be pointed to by
> the document?
>
> Have you thought about pointing to a URI instead of a literal? For example
> using something like
> http://purl.org/NET/mediatypes
>
> Also, what is considered good practice when the dataset files have been
> zipped? Should the content type be captured as something like
> 'Application/gzip' or should it still be the underlying data format, e.g.
> 'text/turtle'? How then should the fact that it is compressed be captured.
> In an http header this would be captured with a separate field
> Content-Encoding.
>
> Thanks,
>
> Alasdair



-- 
John S. Erickson, Ph.D.
Director, Web Science Operations
Tetherless World Constellation (RPI)
<http://tw.rpi.edu> <olyerickson@gmail.com>
Twitter & Skype: olyerickson
Received on Thursday, 18 July 2013 15:41:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 October 2018 10:43:23 UTC