You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Corresponding elements in other standards - again a reference to ISO 19115:2003 MD_Identification
Encoding guidance - example 5. Should this be dropped as it is not to be used?
The text was updated successfully, but these errors were encountered:
archaeogeek
added
the
Guidance
Issues that primarily affect the general or element guidance, not the "normative" parts
label
Oct 10, 2023
Isn't the point of the guidance to say what not to use, just as much as what to use, as per the note:
The srv:SV_ServiceIdentification XML element has an optional property srv:keywords which exhibits the same behaviour as gmd:descriptiveKeywords. Consequently keywords for service metadata could be encoded in the way shown in Example Five. This approach shall not be followed in GEMINI2 metadata instances
Regarding 'corresponding element in other standards', again this is because 'descriptiveKeywords' is a property of MD_Metadata, inherited by both ISO 19115:2003 MD_DataIdentification and ISO 19119:2005 SV_ServiceIdentification
Regarding "example 5": this no longer seems to exist (in either datasets of services)
Example Five (services) - keywords in the srv namespace (this encoding is not to be used)
<gmd:MD_Metadata>
...
<gmd:identificationInfo>
<srv:SV_ServiceIdentification>
...
<srv:keywords>
<gmd:MD_Keywords>
<gmd:keyword>
<gco:CharacterString>humanCatalogueViewer</gco:CharacterString>
</gmd:keyword>
</gmd:MD_Keywords>
</srv:keywords>
...
</srv:SV_ServiceIdentification>
</gmd:identificationInfo>
...
</gmd:MD_Metadata>
Corresponding elements in other standards - again a reference to ISO 19115:2003 MD_Identification
Encoding guidance - example 5. Should this be dropped as it is not to be used?
The text was updated successfully, but these errors were encountered: