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.

Sign up for GitHub

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

Jump to bottom

Services reference date should not be called "dataset reference date" #118

Open
archaeogeek opened this issue Oct 10, 2023 · 2 comments
Open

Services reference date should not be called "dataset reference date" #118

archaeogeek opened this issue Oct 10, 2023 · 2 comments
Labels
Guidance Issues that primarily affect the general or element guidance, not the "normative" parts

Comments

@archaeogeek
Copy link
Member

Is element name incorrect? This is for service metadata, not datasets.
Corresponding element in other standards - references ISO 19115:2003 MD_Identification.citation
Encloding guidelines note 1 needs to refere to service reference date (probably - if we decide element name needs to change)
@archaeogeek archaeogeek added the Guidance Issues that primarily affect the general or element guidance, not the "normative" parts label Oct 10, 2023
@nmtoken
Copy link
Contributor

nmtoken commented Oct 10, 2023

Posting here as general comment, but applies to all issues discussing relevance of data set metadata in service metadata records...

EN ISO 19119:2006

The structure of service metadata includes three major classes: a section of basic service metadata (SV_ServiceIdentification class) that provides a general description of the service and two sections that describe the operations (SV_OperationsMetadata) and data (MD_DataIdentification) available from a particular service.

So service metadata is expected to have some data set metadata elements

@archaeogeek
Copy link
Member Author

Should this be closed, based on @nmtoken's comment above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Guidance Issues that primarily affect the general or element guidance, not the "normative" parts
Projects
GEMINI issue handling
Status: To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@archaeogeek @nmtoken