Re: [whatwg] header for JSON-LD ???

On 07/24/2017 04:43 PM, Qebui Nehebkau wrote: On 24 July 2017 at 19:21, Michael A. Peters wrote: But if you define your structured data as attributes then information about the other 11 is not available to machines that fetch the page and want to know what the page

Re: [whatwg] header for JSON-LD ???

On 24 July 2017 at 19:21, Michael A. Peters wrote: > But if you define your structured data as attributes then information > about the other 11 is not available to machines that fetch the page and > want to know what the page offers. > It sounds like the machines

Re: [whatwg] header for JSON-LD ???

When too much is displayed, the website is too busy. If there are 12 audios in a group, the person can only listen to one at a time so it is pointless to have 12 audio nodes present. But you can display one and have the other 11 accessible via a select menu, so that if and when the user

Re: [whatwg] header for JSON-LD ???

On 21 July 2017 at 23:21, Michael A. Peters wrote: > I am (finally) starting to implement JSON-LD on a site, it generates a lot > of data that is useless to the non-bot typical user. > > I'd prefer to only stick it in the head when the client is a crawler that > wants it.

Re: [whatwg] header for JSON-LD ???

...pardon, I meant to reply to the group. Thank you for the notice. Reposting to group: Am 24.07.2017 5:41 nachm. schrieb "Jonathan Zuckerman" < j.zucker...@gmail.com>: How about a hyperlink to an artist page with complete info about the artist? This has been the established pattern since the

Re: [whatwg] header for JSON-LD ???

I think one of the best aspects of the web platform is that there can be a single node in the network that is accessible to *all*. The linked data approach hides the information from humans. The structured data alternative you suggest (div display none) still hides the information from humans.