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

Context URL and the links it contains are invalid #6

Open
WesIngwersen opened this issue Feb 24, 2022 · 5 comments
Open

Context URL and the links it contains are invalid #6

WesIngwersen opened this issue Feb 24, 2022 · 5 comments

Comments

@WesIngwersen
Copy link
Contributor

openLCA JSON_LD typically contains
@context":"http://greendelta.github.io/olca-schema/context.jsonld
which breaks

It refers to what appears to be this file


which itself contains URLs for the schema that break

@bkuczenski
Copy link

It just needs to be added to the "docs" folder so that it appears as a static resource

msrocka added a commit that referenced this issue Feb 24, 2022
@msrocka
Copy link
Member

msrocka commented Feb 24, 2022

copied it to the docs folder so that the URL http://greendelta.github.io/olca-schema/context.jsonld should work now.

which itself contains URLs for the schema that break

note that these are not URLs but namespace URIs

@bkuczenski
Copy link

thanks

@WesIngwersen
Copy link
Contributor Author

I remember when URIs came out with XML, but to this day I do not see the value in including namespace URIs that don't resolve as valid URLs. In this case, while the context.jsonld file might be valid under the JSON-LD spec, I don't see any value with it otherwise, either for machines or humans.

@msrocka
Copy link
Member

msrocka commented Feb 25, 2022

These URIs (or IRIs) are an essential part of the linked data specification and the semantic stack: they serve as identifiers of things (and do not have to resolve to something). With these URIs, the property unit in a JSON document would expand to http://openlca.org/schema/v1.0/unit. And in another document with another context unit could mean something different than in the openLCA schema (and would expand to another URI). True, that it is nice when such an URI resolves to the documentation of that thing that it describes, but the main purpose here is to get identifiers without clashes... That said, as data sets in the openLCA schema are not used as linked data, I agree that this is overhead without much value.

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