search

ISO-TC211 / StandardsTracker

This GitHub repository lets you - our users - log and track issues that you find with our standards and other document. Tag the issue with the standard or standards effected; we will assign it to the relevant group(s) within TC 211.
11 stars 0 forks source link

Request to modify mcc:URI so that is might have content (a URI) #346

Open isotc211 opened 3 years ago

isotc211 commented 3 years ago

Justification: Issue using MD_KeywordClass/conceptIdentifier (ISO 19115-1:2014 line 75) as the class it calls (mcc:URI) has no content mcc:URI is defined in .../19115/-1/mcc//commonClasses.xsd it can have attributes id and uuid URI should be able to provide a link to and/or a URI (UML model is not informative on how) Proposal: Change type on mcc:URI to type="xs:anyURI"

isotc211 commented 3 years ago

It is possible that the URI class should be in ISO 19103 as it has been identified in Annex C.3.1 ALTERNATIVELY Change XSD (.../19115/-1/mcc//commonClasses.xsd):

TO:

The resultant output would change FROM: my.favourite.org/myFavouriteURInode This could be amended as part of the ISO 19115-3 Review with addition of gcx:URI of type="anyURI" OR the current gcx: could be expanded to include gcx:URI_PropertyType and gcx:URI of type="anyURI" Or perhaps 19115-1 should use the 19103 class URI (an HMMG call?) That class should then have an agreed XML encoding of xs:anyURI (an XMG call?) The open question of where to put the XML encoding of 19103 (effectively, a managed list of places where we use ISO 19139-1 clause 7.3.8, the /req/external/ group (Peter Parslow)
isotc211 commented 3 years ago

It is possible that the URI class should be in ISO 19103 as it has been identified in Annex C.3.1 ALTERNATIVELY Change XSD (.../19115/-1/mcc//commonClasses.xsd):

TO:

The resultant output would change FROM: my.favourite.org/myFavouriteURInode This could be amended as part of the ISO 19115-3 Review with addition of gcx:URI of type="anyURI" OR the current gcx: could be expanded to include gcx:URI_PropertyType and gcx:URI of type="anyURI" Or perhaps 19115-1 should use the 19103 class URI (an HMMG call?) That class should then have an agreed XML encoding of xs:anyURI (an XMG call?) The open question of where to put the XML encoding of 19103 (effectively, a managed list of places where we use ISO 19139-1 clause 7.3.8, the /req/external/ group (Peter Parslow)
ejbleys commented 1 year ago

In https://schemas.isotc211.org/19115/-1/mri/1.3/identification.xsd <element minOccurs="0" name="conceptIdentifier" type="gcx:URI_PropertyType" Should the 19115/-3/mri/1.0|2.0/identification.xsd be versioned and similarly re-typed? Noting that re-versioning is only likely to be picked up in a few implementations