Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

follow link relations: meta, alternate and describes #3

Open
elf-pavlik opened this issue Dec 6, 2015 · 4 comments
Open

follow link relations: meta, alternate and describes #3

elf-pavlik opened this issue Dec 6, 2015 · 4 comments

Comments

@elf-pavlik
Copy link

Some pages, instead of embedding structured data, only provide a reference to it for example with rel="meta" http://patterns.dataincubator.org/book/autodiscovery.html

Possibly also using rel="alternate"

`

`

or rel="describes"

<link rel="describes" href="https://data.alice.example/12312321441#this"/>

maybe sniffer could try following all such links using appropriate content negotiation?

@kidehen
Copy link

kidehen commented Dec 15, 2015

It will treat this as Plain Old Semantic HTML (POSH) and present the relations via POSH Tab. This is on our todo.

@tyrosinase
Copy link

What about when it's <script type="application/ld+json" src="(some json file")> ? I'm not even seeing that come up in the POSH tab.

@kidehen
Copy link

kidehen commented Sep 15, 2016

@tyrosinase -- JSON-LD is supported in the latest release. Islands take the form <script type="application/ld+json"> {json-ld} </script>.

I don't know about @source being an acceptable mechanism for achieving this goal .

@tyrosinase
Copy link

@source? Not sure what that means.

It's probably kind of a moot point for me, since Google doesn't seem to recognize non-embedded data (at least their Structured Data Testing Tool doesn't). Gonna hafta bloat up the pages with embedded data, apparently. Bah.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants