[whatwg] header for JSON-LD ???
Michael A. Peters
mpeters at domblogger.net
Tue Jul 25 15:40:56 PDT 2017
On 07/25/2017 02:42 PM, Qebui Nehebkau wrote:
> On 25 July 2017 at 17:32, Michael A. Peters <mpeters at domblogger.net> wrote:
>> Nor does his assumption that I am "new" to the web somehow disqualify me
>> from making suggestions with current use cases that could reduce the bloat
>> of traffic.
> Oh, then I think you misunderstood his statement. As I read it, "spend more
> time working with the web you have before trying to change it" was a
> suggestion to look for a way to do what you want with current technology,
> not an argument that you don't have enough web experience. "Spend more
> time" on this particular project, not in general.
I have a way to do what I want with current technology.
I can detect bots based upon user agent and only send the JSON-LD when I
However there are some things that may be of use to a browser with
accessibility functions, such as declarations regarding whether or not a
page (or resource on a page) has flashing content or has simulated
motion. So there are legitimate reasons why an end user client may want
the JSON-LD data before rendering a page.
Just like the accept header for WebP, an accept header for JSON-LD could
solve this problem. Bots and non-bot users agents that want it send it.
Webmasters who understand people in undeveloped countries benefit from
non-bloated paged can then choose to only send the JSON-LD in their
pages when it is wanted.
Much better to implement this now when JSON-LD is still relatively young.
Whether JSON-LD is the best way to add structured data to a page
probably depends upon a lot of different factors, that's a different
discussion. But it is being used. That's the discussion, reducing the
drawbacks of bloated content for clients that ignore it anyway.
More information about the whatwg