Open PeterParslow opened 3 years ago
INSPIRE expects (requires) two resourceConstraints/MD_LegalConstraint elements, one for element 25 Limitations on public access and one for element 26 Use constraints
The one for #25 shall contain a single accessConstraints/MD_RestrictionCode element, encoded exactly as specified.
It can then contain as many gmd:otherConstraints elements as required, as shown in Example three.
This allows you to have more than one Limitations on public access. The same pattern applies to #26, but using gmd:useConstraints
Documentation of this could be clearer.
Better examples of different otherconstraints elements are required! Everyone to add examples so we can discuss and pick the most representative
Example: OS NGD Sites record
OS considers this as two Limitations on Public Access, the first giving the "INSPIRE reason" and the second providing some detail.
@nmtoken , perhaps you have some example(s)?
The multiplicity at https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#25 states that multiple limitations on public access are allowed, but the encoding guidance states that all limitations have to be encoded within one instance of MD_LegalConstraints. This strikes me as a contradiction which could lead implementers to be confused. A similar situation exists for Use Constraints. Can this be discussed by the Group?