[go: nahoru, domu]

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

Document JSON-LD examples that do not require fetching of remote context URLs to extract RDF #3164

Open
danbri opened this issue Aug 18, 2022 · 6 comments
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:tricky problem Hard problems, including modeling / vocabulary and infrastructural aspects (eg fiction, probability)

Comments

@danbri
Copy link
Contributor
danbri commented Aug 18, 2022

Very rough notes here: https://docs.google.com/document/d/1Jo4-dTDo1osL3Mr9-THqwKywWu-NiFGagFTQV5mr-N8/edit#

@danbri danbri added status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:tricky problem Hard problems, including modeling / vocabulary and infrastructural aspects (eg fiction, probability) labels Aug 18, 2022
@danbri danbri self-assigned this Aug 18, 2022
@WeaverStever
Copy link
WeaverStever commented Aug 20, 2022

@danbri

I came across this example from Yoast, using the isPartOf property a month or so ago.
here
https://developer.yoast.com/features/schema/functional-specification/

and also here
https://yoast.com/open-schema-protocol/

Is this the same concept your document is about? I have not tested yet, but my inclination is to believe that the JSON-LD can be stitched together using component parts using the @id.

"@type": "Article",
              "@id": "https://www.example.com/#/schema/Article/abc123",
              "headline": "Example article headline",
              "description": "Example article description",
              "isPartOf": {
                  "@id": "https://www.example.com/blog/example-article/"
              },
   ...

@danbri
Copy link
Contributor Author
danbri commented Aug 23, 2022

Hi @WeaverStever

This is somewhat different, I believe. Because Schema.org has an underlying "graph" data model (triples of: some entity, some property, some value) it is possible to compose multiple schema.org descriptions together (even if written in different syntaxes, i.e. Microdata or JSON-LD or RDFa) into larger integrated graph structures. I think that's what they're doing - maybe @jdevalk or @jonoalderson might be able to confirm?

My document is on a more specific technicality relating only to W3C JSON-LD (1.0 and 1.1), around the use of URLs in the @context declaration. Documents that use this style cannot be parsed into structured data graphs without either fetching that document (and potentially others it references), or guesswork/hardcoding. I list in the doc some scenarios and motivations for wanting sometimes to avoid this. Hope this helps.

@Tiggerito
Copy link

In the past, you could not link between syntaxes. I believe that is still the case. So microdata is an island, and JSON-LD is an island, even if they use the same IDs. At least with Google.

@jonoalderson
Copy link
jonoalderson commented Aug 23, 2022

Yep, IDs between syntaxes don't connect/merge/etc.

However, you can cross-relate multiple graphs (even with different @contexts / @vocabs). E.g., https://gist.github.com/jonoalderson/386bc97420fa91e208fa380f58e743ad

@danbri
Copy link
Contributor Author
danbri commented Aug 23, 2022 via email

@github-actions
Copy link

This issue is being nudged due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:tricky problem Hard problems, including modeling / vocabulary and infrastructural aspects (eg fiction, probability)
Projects
None yet
Development

No branches or pull requests

4 participants