In the proposed solution, the label required to be used for gmd:protocol element refers to the INSPIRE code list labels that use an expressive format for OGC services (e.g., "OGC Web Map Service"). The expressive labels do not match the OGC's preferred labels (e.g., "wms"). Additionally, the expressive labels for OGC services in the INSPIRE code list are linked to their associated OGC pages in which the OGC preferred label is clearly identified.
The likelihood is high that this will confuse end users as to which label to use. Additionally, requiring expressive labels precludes de facto standard web applications from populating this element value using the preferred label from an international standards organization. At worst, using the OGC preferred label will cause the INSPIRE metadata record to be rejected as invalid.
Suggestions to address this discrepancy, either:
- In the INSPIRE code list registry, change the labels for the INSPIRE protocol values to match the OGC preferred labels, e.g., http://www.opengis.net/def/serviceType/ogc/wms expressed with the label “wms”, or
- In the GP, for backwards/forwards compatibility of de facto standard web applications, allow the gmd:protocol element to use either the OGC preferred label or the INSPIRE code list label.
Finally, would there be any practical implications for future validation tests that are relaxed to be case-insensitive, e.g., WMS or wms?
thank you for your consideration
In the proposed solution, the label required to be used for gmd:protocol element refers to the INSPIRE code list labels that use an expressive format for OGC services (e.g., "OGC Web Map Service"). The expressive labels do not match the OGC's preferred labels (e.g., "wms"). Additionally, the expressive labels for OGC services in the INSPIRE code list are linked to their associated OGC pages in which the OGC preferred label is clearly identified.
The likelihood is high that this will confuse end users as to which label to use. Additionally, requiring expressive labels precludes de facto standard web applications from populating this element value using the preferred label from an international standards organization. At worst, using the OGC preferred label will cause the INSPIRE metadata record to be rejected as invalid.
Suggestions to address this discrepancy, either:
Finally, would there be any practical implications for future validation tests that are relaxed to be case-insensitive, e.g., WMS or wms?
thank you for your consideration