Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Adding the CF Attributes to the NVS #217

Closed
feggleton opened this issue Mar 13, 2023 · 6 comments
Closed

Adding the CF Attributes to the NVS #217

feggleton opened this issue Mar 13, 2023 · 6 comments

Comments

@feggleton
Copy link
Collaborator

Hi everyone, I spoke to a couple of people at the last CF annual workshop about adding the CF Attribute Names to the NERC Vocab Server and I had good support to do so.

A new NVS collection has been created here: http://vocab.nerc.ac.uk/collection/P31/current/

I will initially be adding the 52 attribute terms from the CF Conventions document, Appendix A, table of Attributes. This controlled vocabulary is set up very similar to the standard names collection. I will maintain this collection should new attributes be added. Any comments or questions, please add below.

Thanks, Fran

@larsbarring
Copy link

Would it be relevant to provide this link in Appendix A.

@feggleton
Copy link
Collaborator Author

Possibly.. do we link to the NERC Vocab Server when we discuss Standard Names in the conventions document?

@larsbarring
Copy link

I had the same thought as you; if we add this link to Appendix A, we should do the same for standard names which would be http://vocab.nerc.ac.uk/collection/P07/current/. And I think the right place to do this would be in the standard name table (which is what actually is in NVS) as well as in Section 3.3.

Or, we do not add links in the Conventions document, but in the web site Vocabularies page, where a new section would then be needed for the Attributes.

@larsbarring
Copy link

.... or maybe we should not given the discussion in cf-convention/vocabularies#11 (which I just rigth now came across) ....

@davidhassell
Copy link
Collaborator

Hi, I think that making these connections on the website is better, and a good connection to make. The fact that these attributes are duplicated elsewhere doesn't really feel like part of the actual conventions themselves.

@rob-metalinkage
Copy link

Any progress on a resolution to this? There is a STAC JSON schema - https://github.com/stac-extensions/cf

We can connect this to an ontology using JSON-LD - if we had one :-)

This is part of a GeoDCAT requirements and development process where we can build profiles to match community standards:

https://ogcincubator.github.io/geodcat-ogcapi-records/

early days - but open to collaboration. Communities can engage to test, refine and promote these resources into formal standards as part of the OGC and ISO processes if appropriate.

@cf-convention cf-convention locked and limited conversation to collaborators Aug 21, 2024
@feggleton feggleton converted this issue into discussion #347 Aug 21, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants