Re: ACTION-64 Update

Hello, All,

As I remember, the first intention of talking about json-ld in the WG was
as a way of delivering our publications in a more "human readable" form,
using, for example, a dcat json-ld description, as raised in action-55.

I think it is very interesting and useful to have these use cases and the
discussion about the different ways of serializing rdf and embedding in
documents. I don't know if it is in the scope of the WG to define the way
these things will be done by the users.

Best Regards,
Laufer

2014-09-16 10:04 GMT-03:00 Mark Harrison <mark.harrison@gs1.org>:

> Hi Phil,
>
> To be honest, I'm not entirely sure where this document fits.  Sumit
> initiated the document and I saw some things I felt I could usefully add.
> The intention (from my side) is not really to compare RDF and JSON-LD -
> but to compare RDFa with JSON-LD.  Both can be viewed as serialisations of
> RDF, each with advantages and disadvantages.  My intention is not to say
> that one is conclusively better than the other or is the recommended best
> practice for structured data within web pages - it really depends on how
> that data is being consumed (e.g. faceted browsers vs smartphone apps vs
> search engines).
>
> I agree that it could be a candidate for merging with Jeni's document,
> though I don't think we've discussed that with her yet.
>
> I'm happy for you to invite Markus to a vocals call - certainly no
> objections to that.
>
> Best wishes,
>
> - Mark
>
>
> On 16 Sep 2014, at 11:47, Phil Archer <phila@w3.org>
>  wrote:
>
> > There's some terrific material here, thanks Sumit and Mark.
> >
> > I have some minor editorial concerns (the title suggests a greater
> division between RDF and JSON-LD than might be appropriate) but overall
> this is a very positive and potentially very useful document I think.
> >
> > Some questions:
> >
> > 1. Do you see this as a possible stand alone document or as part of the
> bigger best practices doc? (That's a WG decision I guess but how do you see
> it?)
> >
> > 2. Is it a use cases doc or guidance on when to use which? Jeni Tennison
> wrote a document (in her role on the TAG) that might be relevant here.
> >
> > http://www.w3.org/TR/html-data-guide/ talks about when to use
> microformats, microdata and RDFa. It *might* be appropriate to think in
> terms of updating that to include JSON-LD? (I'm not pushing for this, just
> raising it as an option - it talks about HTML pages which is not really our
> focus).
> >
> > 3. Do we still want to invite Markus along to a vocabs call? (mu
> Action-57).
> >
> > Cheers
> >
> > Phil.
> >
> > On 12/09/2014 13:05, Mark Harrison wrote:
> >> Hi,
> >>
> >> I like the summary that Sumit has written at
> >>
> https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases#More_Use_Cases
> >>
> >> I've also just added some further material to that page about what I
> think are the pros and cons of inline semantic markup (using RDFa or
> Microdata) versus single block semantic markup using JSON-LD.
> >>
> >> Feel free to edit this further - I'd be very interested to see
> additional edits comments on this.
> >>
> >> We have been considering these issues in the GS1 Digital / GTIN+ on the
> Web project and we are currently favouring JSON-LD as an easier way for
> companies to provide semantic structured markup in their pages
> (particularly for data-driven websites) in a way that is both easier for
> them to implement and less brittle than RDFa or Microdata.  We may even
> provide companies with some JSON-LD templates for various product
> categories, pre-configured with relevant terms from schema.org or the GS1
> Ontology (currently under development), so they can simply fill in the
> blanks with real data.
> >>
> >> Best wishes,
> >>
> >> - Mark
> >>
> >>
> >>
> >> On 12 Sep 2014, at 11:30, Ghislain Atemezing <
> auguste.atemezing@eurecom.fr> wrote:
> >>
> >>> On 12/09/2014 12:17, Eric Stephan wrote:
> >>>> I think you do a great job categorizing how each approach might be
> >>>> used.  I'm wondering if you would be interested in helping develop use
> >>>> cases that illustrate real world examples that we might be able to
> link
> >>>> to data usage.
> >>> Recently, Markus Lanthaler added support for JSON-LD context to
> prefix.cc [1]. It means there are more vocabularies added in the existing
> json-ld contexts [2], many are subpart of Linked Open Vocabularies.
> >>>
> >>>
> >>> HTH
> >>>
> >>> Ghislain
> >>>
> >>>
> >>> [1]http://prefix.cc/context.
> >>> [2] https://github.com/json-ld/json-ld.org/wiki/existing-contexts
> >>>
> >>> --
> >>> Ghislain Atemezing
> >>> EURECOM, Multimedia Communications Department
> >>> Campus SophiaTech
> >>> 450, route des Chappes, 06410 Biot, France.
> >>> e-mail: auguste.atemezing@eurecom.fr & ghislain.atemezing@gmail.com
> >>> Tel: +33 (0)4 - 9300 8178
> >>> Fax: +33 (0)4 - 9000 8200
> >>> Web: http://www.eurecom.fr/~atemezin
> >>> Google+:http://google.com/+GhislainATEMEZING
> >>> Twitter:@gatemezing
> >>>
> >>> 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>
> >>
> >>
> >>
> >
> > --
> >
> >
> > Phil Archer
> > W3C Data Activity Lead
> > http://www.w3.org/2013/data/
> >
> > http://philarcher.org
> > +44 (0)7887 767755
> > @philarcher1
> >
>
> 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>
>
>
>


-- 
.  .  .  .. .  .
.        .   . ..
.     ..       .