Definition of temporal extent within WIS Discovery Metadata records

36 views
Skip to first unread message

Jeremy

unread,
Jun 14, 2012, 8:17:36 AM6/14/12
to wmo-i...@googlegroups.com

In IPET-MDI meeting 2 we proposed that:

The temporal extent within metadata for bulletins exchanged in real time currently reflects the date at which real time exchange started, rather than the current availability of the bulletins currently travelling within the WIS. A separate record is required for the real time bulletins and for an historical record of the data in the bulletins. The transient nature of the bulletins should be reflected by using a temporal extent in the metadata that indicates the rolling 24h cache of bulletins. A method of doing this is required. (Issue is expressing “now” in ISO 8601).

During the discussion on this point at the ICT-ISS meeting, we concluded that for ‘transient data products’ that are routinely exchanged in the WIS it does not make sense to define a temporal extent for those products; the metadata record is intended to describe a ‘template’ for a data product that is exchanged. Instances of that product may or may not be available from the GISC cache at any given time therefore we cannot authoritatively define a temporal extent for that ‘dataset’.

(As an aside, I wonder if we should invent a new term in MD_ScopeCode ‘template’ to describe this kind of metadata record?)

The recommendation of ICT-ISS is the following Guidance.

1)      Please can we update the WIS wiki with this additional Guidance

2)      Please can we create a Schematron test to validate this Guidance

 

 

Guidance:       A WIS Discovery Metadata record describing a transient data product published for global exchange via the WIS should NOT specify temporal extent.

Test method:   (i) Inspect the instance document under test to assess whether the metadata record describes a transient data product published for global exchange:

                        (i.a) Inspect the instance document under test to assess whether the WMO_DistributionScopeCode code list is specified as a keyword thesaurus within an instance of gmd:MD_Keywords using the following XPath:

/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title// = “WMO_DistributionScopeCode”

A gmx:Anchor element may be used to specify the location of the Code List; e.g.

/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/

↘gmx:Anchor/@xlink:href = “http://wis.wmo.int/2012/codelists/WMOCodeLists.xml#WMO_DistributionScopeCode

(i.b) Inspect the associated gmd:MD_Keywords element to ensure that the keyword type is specified as “dataCentre” from the (amended) MD_KeywordTypeCode code list; e.g.

/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:type/gmd:MD_KeywordTypeCode = “dataCentre”

(i.c) Inspect the associated gmd:MD_Keywords element to assess whether the keyword “GlobalExchange” from the WMO_DistributionScopeCode code list is present; e.g.

/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:keyword = “GlobalExchange”


(iii) Inspect the instance document under test to assess that NO instances of temporal extent element are specified; e.g.

/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ ↘gmd:extent/gmd:EX_Extent/gmd:temporalExtent

 

Message has been deleted

Jeremy

unread,
Jun 14, 2012, 10:15:55 AM6/14/12
to wmo-i...@googlegroups.com
This requirement should apply to GTS data for Global _AND_ Regional exchange ...

Propose to update the test as follows:

---

(i.c) Inspect the associated gmd:MD_Keywords element to assess whether the keyword “GlobalExchange” from the WMO_DistributionScopeCode code list is present; e.g.

(/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:keyword = “GlobalExchange”) OR (/gmd:MD_Metadata/gmd:identificationInfo//gmd:descriptiveKeywords/ ↘gmd:MD_Keywords/gmd:keyword = “RegionalExchange”)


TOYODA Eizi

unread,
Jun 14, 2012, 6:01:33 PM6/14/12
to wmo-i...@googlegroups.com
Jeremy,
 
It's no problem to remove temporal extent from metadata records for ordinary bulletins.  At least that means I don't have to write a specification and rationale for notation.
 
In the new rule, is it prohibited to notify the date of end of distribution for bulletins scheduled to terminate on some date?
 
Eizi
----- Original Message -----
From: Jeremy
Sent: Thursday, June 14, 2012 9:17 PM
Subject: Definition of temporal extent within WIS Discovery Metadata records

In IPET-MDI meeting 2 we proposed that:

The temporal extent within metadata for bulletins exchanged in real time currently reflects the date at which real time exchange started, rather than the current availability of the bulletins currently travelling within the WIS. A separate record is required for the real time bulletins and for an historical record of the data in the bulletins. The transient nature of the bulletins should be reflected by using a temporal extent in the metadata that indicates the rolling 24h cache of bulletins. A method of doing this is required. (Issue is expressing “now” in ISO 8601).

During the discussion on this point at the ICT-ISS meeting, we concluded that for ‘transient data products’ that are routinely exchanged in the WIS it does not make sense to define a temporal extent for those products; the metadata record is intended to describe a ‘template’ for a data product that is exchanged. Instances of that product may or may not be available from the GISC cache at any given time therefore we cannot authoritatively define a temporal extent for that ‘dataset’.

(As an aside, I wonder if we should invent a new term in MD_ScopeCode ‘template’ to describe this kind of metadata record?)

The recommendation of ICT-ISS is the following Guidance.

<!--[if !supportLists]-->1)      <!--[endif]-->Please can we update the WIS wiki with this additional Guidance

<!--[if !supportLists]-->2)      <!--[endif]-->Please can we create a Schematron test to validate this Guidance

Jeremy Tandy

unread,
Jun 15, 2012, 1:47:13 AM6/15/12
to wmo-i...@googlegroups.com
I think that the date of termination of when a bulletin is scheduled to be terminated might be best communicated using the resource maintenance information. There doesn't appear to be a formal way to specify "this resource will no longer be updated / available after YYYYMMDD", so the only option I can think of is the free-text maintenanceNote:

/gmd:MD_Metadata/gmd:identificationInfo//resourceMaintenance/maintenanceNote 

Ideas?

Jeremy

TOYODA Eizi

unread,
Jun 15, 2012, 2:01:10 AM6/15/12
to wmo-i...@googlegroups.com
That's great.
 
In practical sense, I'm anticipating that data-originating centres would like to include many miscellaneous informations:
 
 - this bulletin is no longer delivered after YYYY-MM-DD
 - sorry about inconvenience, but that is conform WMO's TDCF migration plan
 - you can use BUFR message IXXX99 XXXX instead
 - ...
 
So free text is blessing rather than curse!
 
Cheers,

David Thomas

unread,
Jun 15, 2012, 2:42:54 AM6/15/12
to wmo-i...@googlegroups.com
hi Jeremy,
perhaps the starting date of the bulletin can also be recorded in the resource maintenance information too?
Dave




The information contained in this electronic message and any attachments are intended for specific individuals or entities, and may be confidential, proprietary or privileged. If you are not the intended recipient, please notify the sender immediately, delete this message and do not disclose,  distribute or copy it to any third party or otherwise use this message. The content of this message does not necessarily reflect the official position of the World Meteorological Organization (WMO) unless specifically stated. Electronic messages are not secure or error free and may contain viruses or may be delayed, and the sender is not liable for any of these occurrences.
SAVE PAPER - Please do not print this e-mail unless absolutely necessary



--
David Thomas
Chief, Information and Telecommunication System Division
Observing and Information Systems Department
World Meteorological Organization
Tel: +41 22 730 82 41
Fax: +41 22 730 80 21
Mobile:+41 79 425 59 60
e-mail: dth...@wmo.int


The information contained in this electronic message and any attachments are intended for specific individuals or entities, and may be confidential, proprietary or privileged. If you are not the intended recipient, please notify the sender immediately, delete this message and do not disclose,  distribute or copy it to any third party or otherwise use this message. The content of this message does not necessarily reflect the official position of the World Meteorological Organization (WMO) unless specifically stated. Electronic messages are not secure or error free and may contain viruses or may be delayed, and the sender is not liable for any of these occurrences.
SAVE PAPER - Please do not print this e-mail unless absolutely necessary

Jeremy Tandy

unread,
Jun 15, 2012, 2:46:16 AM6/15/12
to wmo-i...@googlegroups.com
Seems reasonable ...

Jeremy

On 15 June 2012 07:42, David Thomas wrote:
hi Jeremy,
perhaps the starting date of the bulletin can also be recorded in the resource maintenance information too?
Dave

Steve Foreman

unread,
Jun 20, 2012, 2:50:18 AM6/20/12
to wmo-i...@googlegroups.com
All,

to summarise:

1) we remove the temporal extent from the metadata
2) we include start date (and end date if known) into the resource maintenance as /gmd:MD_Metadata/gmd:identificationInfo//resourceMaintenance/maintenanceNote 

It would be useful to have "boilerplate text" for people to copy for this.

Jeremy has to get the text of the specification agreed very soon - so it would be good to close this issue before 21 June!

Steve
__________________________________________________
Dr Steve Foreman
Chief, Data Representation, Metadata and Monitoring
World Meteorological Organization
 

David Thomas

unread,
Jun 20, 2012, 3:05:09 AM6/20/12
to wmo-i...@googlegroups.com
Thanks Steve,
just to be sure, we are only referring to cases where the temporal extent conflicts with discovery, but in particular GTS traffic which uses a metadata record to describe a message or bullelletin. eg a bulletin used daily should not include a temporal extent field, but a data set with contents covering a period should still use the  field.
regards
Dave

Steve Foreman

unread,
Jun 20, 2012, 5:27:56 AM6/20/12
to wmo-i...@googlegroups.com
Yes, Dave, that is exactly what I meant - sorry for being too brief!

Steve

Jeremy

unread,
Jun 24, 2012, 6:03:40 AM6/24/12
to wmo-i...@googlegroups.com
Steve - the text of the specification does not include this Guidance ... we don't need to rush for its inclusion. However, it will be good to get this task completed. Jeremy


On Wednesday, June 20, 2012 7:50:18 AM UTC+1, Steve Foreman wrote:
All,

to summarise:

1) we remove the temporal extent from the metadata
2) we include start date (and end date if known) into the resource maintenance as /gmd:MD_Metadata/gmd:identificationInfo//resourceMaintenance/maintenanceNote 

It would be useful to have "boilerplate text" for people to copy for this.

Jeremy has to get the text of the specification agreed very soon - so it would be good to close this issue before 21 June!

Steve

Seems reasonable ...

Jeremy


The information contained in this electronic message and any attachments are intended for specific individuals or entities, and may be confidential, proprietary or privileged. If you are not the intended recipient, please notify the sender immediately, delete this message and do not disclose,  distribute or copy it to any third party or otherwise use this message. The content of this message does not necessarily reflect the official position of the World Meteorological Organization (WMO) unless specifically stated. Electronic messages are not secure or error free and may contain viruses or may be delayed, and the sender is not liable for any of these occurrences.
SAVE PAPER - Please do not print this e-mail unless absolutely necessary


The information contained in this electronic message and any attachments are intended for specific individuals or entities, and may be confidential, proprietary or privileged. If you are not the intended recipient, please notify the sender immediately, delete this message and do not disclose,  distribute or copy it to any third party or otherwise use this message. The content of this message does not necessarily reflect the official position of the World Meteorological Organization (WMO) unless specifically stated. Electronic messages are not secure or error free and may contain viruses or may be delayed, and the sender is not liable for any of these occurrences.
SAVE PAPER - Please do not print this e-mail unless absolutely necessary



--
__________________________________________________
Dr Steve Foreman
Chief, Data Representation, Metadata and Monitoring
World Meteorological Organization
 


Reply all
Reply to author
Forward
0 new messages