Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)

Thank you for that summary @hadleybeeman!

To be clear(er?), there are two warring scenarios:
1. embedding JSON-LD into HTML for *conveyance*
2. embedding JSON-LD into HTML for *enhancement*

Currently, JSON-LD in a [data block](https://www.w3.org/TR/html5/semantics-scripting.html#data-block) is (like anything in a data block) simply there for conveyance. JavaScript *may* use it to inform the current page's interactions or it may not. Typically, because Schema.org, it's primarily there for SEO reasons.

The more futuristic hope/dream is that JSON-LD would become as @hadleybeeman described a more valuable part of constructing meaningful documents and apps whereby JSON-LD content might become deliberately intertwined with other data within the page.

These two scenarios currently look identical:
```html
<script type="application/ld+json">{"@contenxt": "..."}</script>
```
But the desired level of integration with the surrounding markup depends on which one of those scenarios one is currently focused on--as well as if the JSON-LD is seen as primarily existing on its own and occasionally embedded (for conveyance) into HTML or if the JSON-LD's whole purpose is to influence the surrounding documents processing/handling/scripting.

Both usage scenarios are valid, but if they go in the same data block space, there's concern about breaking existing tooling--[not all of which uses the DOM](https://github.com/w3c/json-ld-syntax/issues/23#issuecomment-430791254).

Hope that helps a bit!
🎩 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/312#issuecomment-434728315