-
Notifications
You must be signed in to change notification settings - Fork 12
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
Be more specific in /req/pre-defined/collection-naming #51
Comments
Feature type is defined in the glossary, I am not sure how much more information we need? Perhaps the additional documentation should describe this (for the second target group, see #20 (comment) )? A link to a specific article would be good indeed. From https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02010R1089-20141231&from=EN#tocId7
Examples: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02010R1089-20141231&from=EN#tocId187
So the lowercase version would be https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02010R1089-20141231&from=EN#tocId460
Here the lowercase version would be |
Link / referance to specific article will help already a lot! And examples even more... But then there's still a question about Annex III? For example theme AC-MF says:
In practice there are very different kind of data under same feature types. Should all collections in that theme use the same name? |
Perhaps we could also refer to https://www.w3.org/TR/sdw-bp/#spatial-things-features-and-geometry |
I think it's best to refer to explisit requirements in INSPIRE context. If we want to give some more information, those examples are the best way to make text more clear. |
Resolved in #63 |
Current wording in req /req/pre-defined/collection-naming:
is unclear. What is feature type in this context? Some explanation would be beneficial and it would be better to refer to a specific article / page number.
How this should be interpreted in Annex III? Data related to the themes Atmospheric Conditions or Meteorological Geographical Features shall be made available using the types defined in Specialised Observations package in Annex I, the OM_Observation spatial object type or sub-types thereof. Should all collections in that theme use the same name?
The text was updated successfully, but these errors were encountered: