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

Update context file to contain updated ssn-ext to sosa namespace #99

Closed
bsimons14 opened this issue Feb 26, 2020 · 8 comments
Closed

Update context file to contain updated ssn-ext to sosa namespace #99

bsimons14 opened this issue Feb 26, 2020 · 8 comments
Assignees

Comments

@bsimons14
Copy link
Contributor

@dr-shorthair wrote #94:
"I just noticed that you are still using the old version of SSN-ext ... because the graph URI https://www.w3.org/ns/ssn/ext/ resolves to a stale version of the RDF :-( It was all updated when the new Working Draft of SSN-ext was published in January. I've logged this issue to get it fixed.

The main difference is for you guys is that the new classes and properties are now in the SOSA namespace and ssn-ext: is no longer used - see https://raw.githubusercontent.com/w3c/sdw/gh-pages/ssn-extensions/rdf/ssn-ext.ttl"

@bsimons14 bsimons14 changed the title Update context file to contain updated sosa ssn-ext namespace Update context file to contain updated ssn-ext to sosa namespace Feb 26, 2020
@dr-shorthair
Copy link

The online version of the ontology is now corrected
w3c/sdw#1169
see https://www.w3.org/ns/ssn/ext/

@dblodgett-usgs
Copy link
Contributor

Sorry to be naive here but are there changes this implies to this context?
https://opengeospatial.github.io/ELFIE/contexts/elfie-2/ssn-ext.jsonld

@dblodgett-usgs dblodgett-usgs self-assigned this Feb 28, 2020
@dr-shorthair
Copy link

dr-shorthair commented Feb 28, 2020

There is no https://www.w3.org/ns/ssn/ext/ namespace or ssn-ext: prefix.
There is a graph at https://www.w3.org/ns/ssn/ext/ which contains some new axioms and URIs in the https://www.w3.org/ns/sosa/ namespace, but I think that is a secondary concern. It would be required for processing and reasoning, but not to mention the new resources.

@dblodgett-usgs
Copy link
Contributor

Shoot -- didn't think this would close like that. @dr-shorthair I just removed the ssn-ext context and added the content from it to https://github.com/dblodgett-usgs/ELFIE/blob/master/docs/contexts/elfie-2/sosa.jsonld

That in line with what you would have expected?

@dr-shorthair
Copy link

This is the full set:
image
image

@dblodgett-usgs
Copy link
Contributor

The intention of the context was to strike a balance of completeness and approachability. If you feel we've left anything out that should really be in, can you PR against the context? Happy to add if needed.

@dr-shorthair
Copy link

Apologies @dblodgett-usgs - it was unclear to me whether you wanted your config to automatically accommodate all SOSA. If that is not the case then it is up to you guys to pick and choose. I was only providing this for x-reference.

(The issue closed automatically because you had the magic word 'fixes' in the PR.)

@dr-shorthair
Copy link

but to answer @dblodgett-usgs question more clearly - no, I don't expect you to declare classes and properties that you don't use. But it would be best to use the correct namespace for the ones that you do!

i.e. all the new classes and properties from https://www.w3.org/TR/vocab-ssn-ext/ are in the sosa: namespace.

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