From: Dominique Martinet <asmadeus@codewreck.org>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] json what to do
Date: Sun, 6 May 2018 14:22:58 +0200 [thread overview]
Message-ID: <20180506122258.GA992@nautica> (raw)
In-Reply-To: <20180406074533.eklhad@comcast.net>
Karl Dahlke wrote on Sun, May 06, 2018:
> <script type="application/ld+json">
>
> What is that? I'm sure it's there for a reason. We need to know what to do with it.
I don't think we need to do anything with it, it apparently is for
search engines
Here's a link to what google has to say about such "structured data":
https://developers.google.com/search/docs/guides/intro-structured-data
Basically it tells them how the site is structured, for the ibm websites
it has a "SearchAction" that lets ibm pick how google should search
within the site, if I understand that correctly...
I don't know if actual scripts in the page should be able to access it
but that seems fairly useless for browsers, I think we're safe to ignore
it
--
Dominique
prev parent reply other threads:[~2018-05-06 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 11:45 Karl Dahlke
2018-05-06 12:22 ` Dominique Martinet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180506122258.GA992@nautica \
--to=asmadeus@codewreck.org \
--cc=edbrowse-dev@edbrowse.org \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).