The underlying question seems to be about whether the surrounding HTML effects the contained JSON-LD (i.e. <base>, <srcipt lang>, etc).

Right now, it's my assumption that the markup does not need to be consulted when extracting or using the JSON-LD, but that the request URL and response headers used to convey the HTML (with the embedded JSON-LD) would retain their meaning to the JSON-LD.

For example (riffing off this example in the spec):

GET /markus
Host: http://example.com/
Accept: text/html

HTTP/1.1 200 OK
Content-Type: text/html
Link: <https://json-ld.org/contexts/person.jsonld>;
        rel="http://www.w3.org/ns/json-ld#context";
        type="application/ld+json"

<html>
<head>
  <script type="application/ld+json">
{
  "@id": "",
  "name": "Markus Lanthaler",
  "homepage": "http://www.markus-lanthaler.com/",
  "image": "http://twitter.com/account/profile_image/markuslanthaler"
}
  </script>
</head>
<body>
  <img src="http://twitter.com/account/profile_image/markuslanthaler" />
  <a href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>
</body>
</html>

Given that the document was requested from http://example.com/markus then the triples I'd expect would be:

<http://example.com/markus> <http://xmlns.com/foaf/0.1/homepage> <http://www.markus-lanthaler.com/> .
<http://example.com/markus> <http://xmlns.com/foaf/0.1/img> <http://twitter.com/account/profile_image/markuslanthaler> .
<http://example.com/markus> <http://xmlns.com/foaf/0.1/name> "Markus Lanthaler" .

Essentially...

the request URL becomes the Base URI (as described in that section)
the context is set (in this case) just as it would be for a "plain JSON" document (as current described in Interpreting JSON as JSON-LD).

This would avoid the complication(s) of consulting the surrounding formats many similar value expressions (lang, base, etc), while still benefiting from the HTTP message headers we're already leaning on for the "plain JSON" use case.

If this is on the right track, I'm happy to contribute text to make the Embedding JSON-LD in HTML Documents normative (following the pattern set in the "plain JSON" section).

Just let me know. 😃

What is 'base' for an embedded json-ld? #23

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions