W3C home > Mailing lists > Public > public-linked-json@w3.org > March 2016

Re: Using rdf:type instead of @type for node types

From: Adrian Pohl <pohl@hbz-nrw.de>
Date: Wed, 2 Mar 2016 08:28:07 +0100
To: public-linked-json@w3.org
Message-ID: <56D69607.5030100@hbz-nrw.de>
Thanks for your feedback, Dave and Markus. We recently decided how to 
proceed, refraining from mapping "type" to rdf:type  (see [1]):

- We will map "type" to "@type" as it is regarded to be "emerging best 
practice"[2] and people will be able to use framing on top of the data.
- As values of "type" in the actual data, we will use short names that 
are mapped to URIs in the context, e.g.: "type": [ "Book", "Thesis" ]
- All other URIs as values we will wrap inside a JSON object and add a 
label as side car, e.g.:

"subject":[
       {
          "@id":"http://d-nb.info/gnd/4181628-6",
          "label":"Skateboardfahren"
       },
...

All the best
Adrian

[1] https://github.com/hbz/lobid-resources/issues/31#issuecomment-188802597

[2] https://github.com/schemaorg/schemaorg/issues/854

Am 01.03.2016 um 21:51 schrieb Markus Lanthaler:
> On 22 Feb 2016 at 14:25, Adrian Pohl wrote:
>> Thus, the proposed solution is out of question for our use case. Do you
>> see a problem with using "type" mapped to rdf:type? Do others have an
>> opinion on this?
>
> I don't see any problem with that. Please note that framing isn't standardized yet so things may change there anyway.
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
>

-- 
Adrian Pohl
hbz - Hochschulbibliothekszentrum des Landes NRW
Jülicher Straße 6
50674 Köln
Telefon +49-221-40075-235
http://www.hbz-nrw.de
Received on Wednesday, 2 March 2016 07:28:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:47 UTC