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

Typo in JSON-LD schema retrieved from https://www.w3.org/ns/pub-context #11

Open
Addeventure opened this issue Oct 1, 2021 · 3 comments · May be fixed by #12
Open

Typo in JSON-LD schema retrieved from https://www.w3.org/ns/pub-context #11

Addeventure opened this issue Oct 1, 2021 · 3 comments · May be fixed by #12

Comments

@Addeventure
Copy link

Hi!

The schema returned from https://www.w3.org/ns/pub-context contains:

        "inLanguage": {
            "@language" : null,
            "@direction": null,
            "@container": "@list",
            "@id": "http://schema.org/inDirection"
        },

but I think that "@id" should be: "http://schema.org/inLanguage"

@mattgarrish
Copy link
Member

Yup, that's definitely a typo. There isn't even such a thing as inDirection in schema.org; that's a property we defined very early on in the process.

@iherman I assume we can make this change immediately since it's outside of the specification proper (factoring in you'll need to republish it to wherever that /ns links goes), but should we figure out what the plan is for addressing the other errata in the document?

@iherman
Copy link
Member

iherman commented Oct 6, 2021

@mattgarrish I would prefer to mark this is an accepted editorial erratum (as @wareid has done) and then discuss on how to move on with an editorial republication ("when", mostly).

@mattgarrish
Copy link
Member

We can't fix this issue here. I'm going to move this issue to the pub-vocab repository.

@mattgarrish mattgarrish transferred this issue from w3c/pub-manifest Aug 4, 2023
@mattgarrish mattgarrish linked a pull request Aug 4, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants