Open heidivanparys opened 6 years ago
I'm not sure why we have inspire_common:Keyword elements when all the OGC services have a place for service keywords?
I would agree that the ows:Keyword
element should be used.
I understand that a specific element was included in the INSPIRE extended capabilities to allow specifying the title and reference date of the originating controlled vocabulary (as required by the MD IR for keywords originating from a controlled vocabulary.
However, looking at its definition, maybe we could find a way to specify these using the type element:
<complexType name="KeywordsType">
<annotation>
<documentation>Unordered list of one or more commonly used or formalised
word(s) or phrase(s) used to describe the subject. When needed, the optional
"type" can name the type of the associated list of keywords that shall all have
the same type. Also when needed, the codeSpace attribute of that "type" can
reference the type name authority and/or thesaurus.
If the xml:lang attribute is not included in a Keyword element, then no language
is specified for that element unless specified by another means. All Keyword elements
in the same Keywords element that share the same xml:lang attribute value represent
different keywords in that language. </documentation>
<documentation>For OWS use, the optional thesaurusName element was omitted as
being complex information that could be referenced by the codeSpace attribute of
the Type element. </documentation>
</annotation>
<sequence>
<element name="Keyword" type="ows:LanguageStringType" maxOccurs="unbounded"/>
<element name="Type" type="ows:CodeType" minOccurs="0"/>
</sequence>
</complexType>
(...)
<complexType name="CodeType">
<annotation>
<documentation>Name or code with an (optional) authority. If the codeSpace attribute
is present, its value shall reference a dictionary, thesaurus, or authority for the name
or code, such as the organisation who assigned the value, or the dictionary from which
it is taken. </documentation>
<documentation>Type copied from basicTypes.xsd of GML 3 with documentation edited,
for possible use outside the ServiceIdentification section of a service metadata document.
</documentation>
</annotation>
<simpleContent>
<extension base="string">
<attribute name="codeSpace" type="anyURI" use="optional"/>
</extension>
</simpleContent>
</complexType>
The mapping of the Keyword metadata element is ambiguously defined in table 19 in the TG Download Services. ows:Keywords/ows:Keyword can refer to:
As table 19 describes the mapping of metadata elements for a download service, ows:ServiceIdentification/ows:Keywords/ows:Keyword would be the right place for the keywords.
Therefore, the following change to the TG Download Services is proposed:
This issue is derived from the discussion around issue #81 .