CAUTION: NO WARRANTY AT ALL.
PART V. WIS DISCOVERY METADATA
5.1 All information to be exchanged through the WIS shall have a WIS Discovery Metadata record associated with it.5.2 WIS Discovery Metadata Records shall be provided by the data custodian to the principal GISC for the centre to which the data custodian is attached. No change should be made to a WIS Discovery Metadata record without the express approval of the data custodian other than in the case that the principal GISC for the data custodian may alter or withdraw the WIS Discovery Metadata record if it is found to interfere with the correct operation of the WIS, in which case an emergency change should be made and the data custodian shall be requested to provide an appropriate corrected Discovery Metadata record.
5.3 WIS Discovery Metadata records shall conform to the ISO 19115 standard and as a minimum contain the information specified as mandatory in the WMO Core Metadata Profile of that standard as defined in Appendix C to this Manual.
5.4 The Commission for Basic Systems shall maintain and develop the WMO Core Metadata Profile. Changes to the WMO Core Metadata Profile shall be governed using the procedures defined in Appendix C to this Manual.
APPENDIX C: THE WMO CORE METADATA PROFILE OF THE ISO 19115 METADATA STANDARD
C.1 Implementation of the WMO Core Metadata Profile
C.1.1 The WMO Core Metadata Profile of the ISO 19115 Metadata Standard places constraints on the contents of a discovery metadata record that are additional to those in the ISO standard. Authors of WIS Discovery metadata records shall apply these constraints.C.1.2 Specifications in this Manual shall take precedence over the specifications in ISO 19115.
C.1.3 The Secretariat shall publish guidance materials to assist authors of WIS Discovery Metadata maintain consistency between metadata records.
C.1.4 WIS Discovery Metadata records shall be provided to GISCs conformant with ISO 19136 and ISO 19139 expressed in Geographic Markup Language (GML).
C.2 Procedures for amending the WMO Core Metadata Profile
C.2.1 General validation and implementation procedures
C.2.1.1 Proposal of amendments
Amendments to the WMO Core Metadata Profile must be proposed in writing to the WMO Secretariat. The proposal shall specify the needs, purposes and requirements and include information on a contact point for technical matters.C.2.1.2 Drafting recommendation
The Inter-Programme Expert Team on Metadata and Data Representation Development (IPETMDRD1), supported by the Secretariat, shall validate the stated requirements (unless it is consequential to an amendment to the WMO Technical Regulations) and develop a draft recommendation to respond to the requirements, as appropriate.Footnote 1: The IPET-MDRD, the ICT-ISS and the OPAG-ISS are the current bodies dealing with the WMO Core Profile within the Commission for Basic Systems (CBS). If they were replaced by other bodies performing the same function, the same rules would apply, by replacing the names of the entities appropriately.
C.2.1.3 Date of implementation
The IPET-MDRD should define a date of implementation in order to give sufficient time to the WMO Members to implement the amendments after the date of notification; the IPET-MDRD should document the reasons to propose a time span of less than six months except for the fast track procedure.C.2.1.4 Procedures for approval
After a draft recommendation of the IPET-MDRD is validated in accordance with the procedure given in section C.6 below, depending on the type of amendments, the IPET-MDRD may selectone of the following procedures for the approval of the amendments:
- Fast-track procedure (see C.2.2);
- Procedure for the adoption of amendments between CBS sessions (see C.2.3);
- Procedure for the adoption of amendments during CBS sessions (see C.2.4).
C.2.1.5 Urgent introduction
Regardless of the above procedures, as an exceptional measure, the following procedure accommodates urgent user needs to introduce new entries in the Code Lists and XML schema that support the WMO Core Metadata Profile or to correct errors in the metadata validation criteria.(a) A draft recommendation developed by IPET-MDRD shall be validated according to C.2.6.1, C.2.6.2 and C.2.6.3;
(b) The draft recommendation for pre-operational use, which can be used in operational data and products, shall be approved by the chairpersons of IPET-MDRD and OPAGISS, and the president of CBS. The list of pre-operational entries is kept on-line on the WMO web server;
(c) Pre-operational entries need to be approved by one of the procedures in C.2.1.4 for operational use;
(d) The lowest level of the version number of the metadata standard will be incremented (see C.2.1.6).
C.2.1.6 Issuing updated version
Once amendments to the WMO Core Metadata Profile are adopted, an updated version of the relevant part of the Manual on WIS shall be issued in the four languages: English, French, Russian and Spanish. The Secretariat shall inform all WMO Members of the availability of a new updated version of that part at the date of notification mentioned in C.2.1.3.Version numbers of the WMO Core Metadata Profile have the form a.b.c where:
- a shall be incremented if the change requires modifications to software (for example moving to a new version of the ISO 19115 standard). This is the top level of the version number. Such changes should follow the Changes during Sessions procedure in C.2.4.
- b shall be incremented if changes to conformance checking rules or changes to Code Lists are introduced and are mandatory for compliant metadata records. This is the middle level of the version number. Such changes should follow the Changes Between Sessions procedure in C.2.3.
- c shall be incremented if the changes have no impact on existing metadata records (for example adding a new entry to a Code List, or introducing a conformance checking rule that results in a warning rather than causing a metadata record to be declared invalid). This is the lowest level of the version number. Such changes should use the Fast Track procedure in C.2.2.
Note: development versions of the WMO Core Metadata Profile, not intended for operational use, are denoted by the digit 0 in second part of the version number. For
example: 2.0.1. Development versions are intended to enable the development of a new version of the WMO Core Metadata Profile requiring changes to software systems.
C.2.2 Fast-track procedure
C.2.2.1 Scope
The fast-track procedure can be used for additions to Code Lists and validation rules that result only in warnings.C.2.2.2 Endorsement
Draft recommendations developed by the IPET-MDRD, including a date of implementation of the amendments, must be endorsed by the chairperson of OPAG-ISS.C.2.2.3 Approval
C.2.2.3.1 Minor adjustments
Correcting typographic errors in descriptive text in Code Lists is considered a minor adjustment, and will be done by the Secretariat in consultation with the president of CBS.Note: a Code List is a list of valid entries that are permitted in a metadata field.
C.2.2.3.2 Other types of amendments
For other types of amendments, the English version of the draft recommendation, including a date of implementation, should be distributed to the focal points for Discovery Metadata matters for comments, with a deadline of two months for the reply. It should then be submitted to the president of CBS for consultation with the presidents of technical commissions and adoption on behalf of the Executive Council (EC).C.2.2.4 Frequency
The implementation of amendments approved through the fast track procedure can be twice a year in May and November.
C.2.3 Procedure for the adoption of amendments between CBS sessions
C.2.3.1 Approval of draft recommendation
For the direct adoption of amendments between CBS sessions, the draft recommendation developed by the IPET-MDRD, including a date of implementation of the amendments, shall be submitted to the chairperson of OPAG-ISS and president and vice-president of CBS for approval. The president of CBS shall consult with the presidents of technical commissions.C.2.3.2 Circulation to Members
Upon approval of the president of CBS, the Secretariat sends the recommendation in the four languages (English, French, Russian and Spanish), including a date of implementation of the amendments, to all WMO Members for comments to be submitted within two months following the dispatch of the amendments.C.2.3.3 Agreement
Those WMO Members not having replied within the two months following the dispatch of the amendments are implicitly considered as having agreed with the amendments.C.2.3.4 Coordination
WMO Members are invited to designate a focal point responsible to discuss any comments/disagreements with the IPET-MDRD. If the discussion between the IPET-MDRD and the focal point cannot result in an agreement on a specific amendment by a WMO Member, this amendment will be reconsidered by the IPET-MDRD.C.2.3.5 Notification
Once amendments are agreed by WMO Members, and after consultation with the chairperson of the OPAG-ISS and the president and vice-president of CBS, the Secretariat notifies at the same time the WMO Members and the members of the Executive Council of the approved amendments and of the date of their implementation.
C.2.4 Procedure for the adoption of amendments during CBS sessions
For the adoption of amendments during CBS sessions, the IPET-MDRD submits its recommendation, including a date of implementation of the amendments, to the Implementation/Coordination Team on Information Systems and Services (ICT-ISS) of the Open Programme Area Group on Information Systems and Services (OPAG-ISS). The recommendation is then passed to the presidents of technical commissions for consultation, and to a CBS session that shall be invited to consider comments submitted by presidents of technical commissions. The recommendation shall then be submitted to an EC session for decision.
C.2.5 Procedure for the correction of existing entries in the Code Lists and validation rules
C.2.5.1 Correcting errors in the text describing a Code List entry
Where a minor error in the specification of a CodeList is found (e.g. typing error or incomplete definition) the CodeList entry shall be amended and re-published. The CodeList dictionary itself (the XML document) shall increment its version number. If, however, the error is in the meaning of the CodeList, then a new CodeList entry should be created and the existing (erroneous) entry marked as deprecated. Authors of metadata records should not use deprecated CodeList items. This situation is considered a minor adjustment according to C.2.3.1 above.C.2.5.2 Correcting an error in a conformance checking rule
If an erroneous specification of a conformance checking rule is found, a new descriptor should preferably be added to the appropriate table through the fast-track procedure or the procedure for adoption of amendments between CBS sessions. The new conformance checking rule should be used instead of the old. An appropriate explanation shall be added to the description in the description of the conformance checking rule to clarify the practice along with the date of the change.C.2.5.3 Submission of changes to Code List Entries or conformance checking rules as a result of correcting an error
Such changes shall be submitted through the fast-track procedure.C.2.6 Validation procedure
C.2.6.1 Documentation of need and purpose
The need for, and the purpose of, the proposal for changes should be documented.C.2.6.2 Documentation of result
This documentation shall include the results of validation testing of the proposal as described below.C.2.6.3 Testing with WIS metadata applications
For new or modified Code List entries and validation rules, proposed changes should be tested by the use of at least two independently developed metadata editors and two independently developed GISC catalogues which incorporated the proposed change. Results should be made available to the IPET-MDRD with a view to verifying the technical specifications.C.3 Contents of the WMO Core Metadata Profile
C.3.1 Each supported version of the WMO Core Metadata Profile is listed in C.4. Versions that are no longer supported by WIS are denoted as “obsolete” and their definitions should be retained on the WMO website. Definitions of the versions of the WMO Core Metadata Profile are in sub-appendices of this Appendix.C.4 WMO Core Profile Versions
Note: Versions of the WMO Core Profile before 1.2 did not provide all the functionality required by the WIS and are no longer supported.WMO Core Profile version 1.2. This is defined at http://wis.wmo.int/2010/metadata/version_1-2
Note: metadata created using profile version 1.2 is compatible with that created under version 1.3 other than that the records may have been completed inconsistently and therefore may fail the version 1.3 conformance checking rules.
WMO Core Profile Version 1.3. This is defined at http://wis.wmo.int/2012/metadata/version_1-3. This is described in Appendix C.1.3 to this Manual.
No comments :
Post a Comment