json-ld

It looks like we will require two different serializations of JSON-LD. The current proposal is to serve them with two different media types:

• application/ld+json
• application/vnd.drupal.ld+json

You can weigh in on the decision of how to negotiate between the two.

Why do we need two?

As Larry talked about in his WSCCI Web Services Format Sprint Report, we want Drupal 8 to be able to serialize data "for consumption by remote programs (either other Drupal sites as in the case of content staging, other non-Drupal sites, client-side applications, or mobile apps)".

There's been lots of discussions on various approaches for serializing entities in the WSCCI group and with Drupal 8 feature freeze only a few months away, it's time to start coding. JSON-LD was chosen as a potential good candidate for serializing Drupal entities. One of the key features of JSON-LD is the ability to include a @context along with your data. This context describes the data present in the JSON document and is useful for consumers to understand how to best make use of the data.

From what I've been able to gather, one of the two major use cases that WSCCI is targeting with its JSON-LD support is deployment.

I've been having a little trouble wrapping my head around how we want deployment to work. In this post, I lay out my understand of how it could work, some of which exploits the Linked Data part of JSON-LD. I'm hoping that those involved in developing deployment can help me understand if/where I've got it wrong.

I've drawn this up as a UML activity diagram, with different streams for the following actors (left to right):

<

ol>

We should review which features of JSON-LD we are likely to use in Drupal 8 and what their status is, as some are still under development.

Since many contributors do not have a grounding in linked data and haven't been involved in the JSON-LD selection process, I start with the basics, which are pretty stable. I then then move on to the parts of the spec that are fluctuating.