RE: ACTION-78 & ACTION-58 json-ld and multilingual language tags

Hi Antonio,

My intentions behind adding that image was to give reader an perspective about where does JSON-LD fit in the overall RDF family

There was a discussion in the conference call about JSON-LD being an alternative of RDF. This image and 1st paragraph in the JSON-LD section strive to explain that JSON-LD is /ONE OF/  many RDF syntax that supports multiple graphs.

And i agree with Mark's comment about usefulness of version information.


Thanks
Sumit Purohit

________________________________________
From: Mark Harrison [mark.harrison@gs1.org]
Sent: Monday, September 15, 2014 2:55 AM
To: Antoine Isaac
Cc: Data on the Web Best Practices Working Group; Purohit, Sumit
Subject: Re: ACTION-78 & ACTION-58 json-ld and multilingual language tags

Hi Antoine,

I'm happy to include the example in that wiki page and have just done so.

The diagram was authored by Sumit - not me.  I think he was intending to show the additional features and representations introduced with RDF 1.1 - and I think we all hope that these will continue to be available in future versions of RDF.

Regarding version numbers of standards, I think the main reason why people sometimes have to be bothered with version history is that the deployed implementations do not always keep pace with the latest versions of the standards.  For example, you can still find a number of public SPARQL endpoints that are not yet fully supporting features introduced in SPARQL 1.1, such as predicate paths / property chains.
For example, the public SPARQL endpoint for WordNet at http://wordnet.rkbexplorer.com/sparql/ appears to be still only implementing SPARQL 1.0.  If I want to make a WordNet query that depends on SPARQL 1.1 features, I either have to rewrite my query as a slightly more verbose SPARQL 1.0 query or download the dump of the RDF triples, install them in my own triplestore (e.g. Jena Fuseki, which supports SPARQL 1.1) and then run the SPARQL 1.1 query against my local replica of WordNet.

Best wishes,

- Mark


On 15 Sep 2014, at 08:34, Antoine Isaac <aisaac@few.vu.nl> wrote:

> Hi Mark,
>
> OK, well then it's probably better that you did it yourself, because I have not much background on that wiki page, where it's integrated.
> Anyway, my notes overlap with yours. Perhaps the example would help, if just to give one example of JSON-LD in the page... But as said I don't know the full background.
>
> Perhaps just one remark on the rest though: I would not put the left column of the figure RDF vs RDF1.1. Why bother people with history? That's not the aim of the document I believe.
> In fact it's probably better to avoid version number as much as possible. The language tag will hopefully be still available in future versions of RDFa, not only 1.1.
>
> Kind regards,
>
> Antoine
>
> On 9/15/14 12:14 AM, Mark Harrison wrote:
>> Hi Antoine,
>>
>> No shame on you.  It's just that I was on the call on Friday and you weren't.  When your action was mentioned, I volunteered to write something about the @language tag in JSON-LD (because I've recently re-read the JSON-LD spec for our GS1 work ( we're thinking of preparing some JSON-LD templates with properties for various product categories to make it much easier for manufacturers and retailers to add structured data to their existing web pages about products).  I have now added the summary about multilingual support in JSON-LD here:
>>
>> https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases#Support_for_internationalisation_and_multi-lingual_strings
>>
>> Feel free to edit this, merge in your notes below or move to wherever else it belongs.
>>
>> Best wishes,
>>
>> - Mark
>>
>>
>>
>>
>> On 14 Sep 2014, at 22:38, Antoine Isaac <aisaac@few.vu.nl> wrote:
>>
>>> Hi,
>>>
>>> I see that Mark is now being assigned actions to chase me. Shame on me.
>>>
>>> Trying to prevent him from wasting too much time... When I accepted action 58 it was about the tricial issue of handling multilingual labels in JSON LD, especially when a same property would have values in different languages.
>>>
>>> The patterns to be used are explained at http://www.w3.org/TR/json-ld/#string-internationalization
>>> Look especially at example 34: Language map expressing a property in three language
>>> {
>>>  "@context":
>>>  {
>>>    ...
>>>    "occupation": { "@id": "ex:occupation", "@container": "@language" }
>>>  },
>>>  "name": "Yagyū Muneyoshi",
>>>  "occupation":
>>>  {
>>>    "ja": "忍者",
>>>    "en": "Ninja",
>>>    "cs": "Nindža"
>>>  }
>>>  ...
>>> }
>>>
>>> I guess this closes the two actions. As long as we remember to use these patterns when we start creating JSON-LD data of course.
>>>
>>> Best,
>>>
>>> Antoine
>>>
>>> On 9/12/14 3:49 PM, Data on the Web Best Practices Working Group Issue Tracker wrote:
>>>> dwbp-ACTION-78: Work on action 58 re summary of json-ld and multilingual language tags
>>>>
>>>> http://www.w3.org/2013/dwbp/track/actions/78
>>>>
>>>> Assigned to: Mark Harrison
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. GS1 may monitor communications. Third party rights acknowledged. (c) 2012.
>>> </a>
>>>
>>
>> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
>> If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
>> GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
>> GS1 may monitor communications.
>> Third party rights acknowledged.
>> (c) 2012.
>> </a>
>>
>
> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. GS1 may monitor communications. Third party rights acknowledged. (c) 2012.
> </a>
>

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
GS1 may monitor communications.
Third party rights acknowledged.
(c) 2012.
</a>

Received on Monday, 15 September 2014 17:50:46 UTC