We need to go a bit further and describe (syntax) and spec (api) how to retrieve a context when dereferencing the resolved URL results in an HTML document. This might include either/or fragment identifiers and profile=http://www.w3.org/ns/json-ld#context.

Resolving a relative IRI reference to a context would be similar to resolving a relative IRI within embedded JavaScript, IMO, which would use the base URL of the script element.

One interesting use case might be the following:

<html>
  <head>
    <base href="http://example.org/" />
    <script type="application/ld+json;profile=http://www.w3.org/ns/json-ld#context">
      {
        "@context": {"@vocab": "http://schema.org/"}
      }
    </script>
    <script id="starthere" type="application/ld+json">
      {
        "@context": "",
        "@id": "",
        "@type": "Thing"
      }
    </script>
  </head>
</html>

If you expanded the document with target "starthere", it would load the context from itself, and use the first script, due to the type profile, setting @vocab to http://schema.org/. The result should be something like the following:

[{
  "@id": "http://example.org/",
  "@type": ["http://schema.org/Thing"]
}]

HTML baseURI and @context? #53

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions