- From: Kuno Woudt <kuno@frob.nl>
- Date: Tue, 10 Jul 2012 23:18:29 +0200
- To: public-linked-json@w3.org
Hello,
On 07/10/2012 08:54 PM, Markus Lanthaler wrote:
>> There is lots of existing software out there which expects just the
>> bare
>> identifiers (our customers and other users of either the database or
>> the
>> existing xml webservice).
>>
>> [...]
>>
>> So, in general there are many websites, services and applications which
>> use just these bare identifiers. Because of this, users of our
>> webservice want to get just the identifier, so they can construct all
>> these urls.
>
> In that case I would suggest to just include both, the bare identifier and a
> link identifying the track/album within your webservice. Using your previous
> example something like:
>
> {
> "@context": { ... },
> "@id":
> "http://musicbrainz.org/ws/2/recording/fcbcdc39-8851-4efc-a02a-ab0e13be224f#
> _",
> "id": "fcbcdc39-8851-4efc-a02a-ab0e13be224f",
> "title": "LAST ANGEL",
> "length": 228106,
> "releases": [
> {
> "@id":
> "http://musicbrainz.org/release/abcd76db-7d5f-3eb7-b386-051c97bfe2e4#_",
> "id": "abcd76db-7d5f-3eb7-b386-051c97bfe2e4",
> "title": "Kingdom"
> }
> ]
> }
Yes, something like that is probably best.
Though I will probably keep the json as is (for clients with Accept:
application/json), but add the @context and @id for clients which
request with Accept: application/ld+json.
-- kuno / warp.
Received on Tuesday, 10 July 2012 21:18:54 UTC