Develop schematron rule-sets
(WIS-182)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | WMO CBS Demonstration |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Jeremy Tandy | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
See notes from ad-hoc ipet-mdi meeting (Toulouse 2010) for context
--- ACTION MDI-1-x (WIS-181: https://vets.development.ucar.edu/jira/browse/WIS-181) ... and ... ACTION MDI-1-xi (WIS-182: https://vets.development.ucar.edu/jira/browse/WIS-182) [JPA][TH] Conformance tests and ordering ... and the associated schematron rulesets A brief discussion suggested we should check (at least) the following: ○ Schema validation ○ Schematron validation ○ Code-lists ○ [external controlled vocabularies?] For more information on NGDC's conformance tests see their wiki (category = ISO19115: https://www.nosc.noaa.gov/dmc/swg/wiki/index.php?title=Category:ISO_19115) ... although I can't seem to find exactly the right resource just now! ACTION 4: TH to send link to schematron validation rules used at NGDC to JT & JPA ... and add a link on the WIS wiki --- Send information to Jeremy and Jean-Pierre ,,, and link to the WIS wiki! |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | WMO CBS Demonstration |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Jeremy Tandy | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
see notes from ad-hoc IPET-MDI meeting in Toulouse (sept 2010) for context:
--- ACTION MDI-1-v (WIS-176: https://vets.development.ucar.edu/jira/browse/WIS-176) JPA has begun to catalogue the geographic extents for sea regions described for SHIPS & BOUYS; he notes that the TTAAii for these entities only describes the sea region as described in the Code-table TH indicated that NGDC distribute a 'Global Maritime Boundaries database (GMBdb) on behalf of NASA ACTION 3: TH to send link to GMBdb resources to JPA & JT ... and add a link on the WIS wiki --- Send information to Jean-Pierre and Jeremy & post a link on the wis wiki! |
| Comments |
| Comment by Ted Habermann [ 25/Sep/10 4:19 AM ] |
| I have requested that Barry Eakins send a copy of a shape file with this information to JT and JPA. Will follow up next week... |
Develop candidate static metadata components
(WIS-174)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | WMO CBS Demonstration |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Jeremy Tandy | Assignee: | Jean-Pierre |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Use of recurring time definitions may make it easier to identify 'static' meetadata components that can be 'normalised' out ...
See context from notes of ad-hoc IPET-MDI meeting in Toulouse, 2010 Please pass information to Jeremy Tandy and Ted Habermann, and add the examples to the WIS wiki [http://www.wmo.int/pages/prog/www/WIS/wiswiki/tiki-index.php?page=IPET-MDI] |
Develop candidate static metadata components
(WIS-174)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | WMO CBS Demonstration |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Jeremy Tandy | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Taken from notes of ad-hoc IPET-MDI meeting in Toulouse, Sept 2010:
--- Action MDI-1-ii (WIS -174: https://vets.development.ucar.edu/jira/browse/WIS-174) ... and ... Action MDI-1-xxiii ( Concerning development of static metadata components ○ TH discussed mechanism used in NGDC: using xlink to refer to metadata component 'tagged' with UUID; access is via a restful interface; codebase is Java with Oracle XMLdb; the tool handles 'any' blob of XML and autogenerates the UUID for the component ○ Tool is able to 'merge' non-default values into the 'template' xml-component We agreed that the NGDC instance of this tool would be used to host the WMO metadata fragments for the interim period - we would look to create an alternate instance at a later stage (or formalize NGDC's commitment to host on behalf of WMO) JPA will modify his Metadata-Generator tool to exploit the NGDC metadata component server. Description of tools developed at NGDC can be found here: https://www.nosc.noaa.gov/dmc/swg/wiki/index.php?title=ISO_Components Also note the (very useful) 'landing page' for the Metadata Tools category of the NGDC wiki: https://www.nosc.noaa.gov/dmc/swg/wiki/index.php?title=Category:Metadata_Tools JT noted that he was vaguely aware of a W3C initiative to specify xlinks - this is rumoured to be different to OGC's usage ... a quick Google finds this page [http://www.w3.org/XML/2008/05/xlinklc/] which I have not assessed yet, but see Simon Cox (OGC-superhero!) has been involved & commented JPA has some suggestions already for 'candidate' components that can normalized from the metadata records ... ○ CI_ResponsibleParty ... § JPA's excel list of NMHS's [http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/documents/IR3.JPA.v0.1.xls]* has been sent to TH § TH has converted this into a first pass XML doc that can be used for components ... looks quite sparse to me on a first glance though! ACTION 1: TH agreed to list the entities within ISO records that he sees routinely factored out within metadata at NGDC |
| Comments |
| Comment by Ted Habermann [ 25/Sep/10 3:58 AM ] |
|
JT - I believe that the translation captured all of the content that was in JPA spreadsheet. I will try to batchload the contents this week so you guys can take a look...
P.S. One of the nice features is that you can open and edit components using the "Open URL" option in Oxygen. I believe that this also works in XMLSpy, but I may need to test that w/ JPA... Ted |
[WIS-206] Build dataset examples for TIGGE Created: 13/Jul/10 Updated: 24/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Manuel Fuentes |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Action: MDI-1-iii Build dataset examples for TIGGE Document Section: 2.1.2.19 Document: Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_iii |
[WIS-205] Cross reference IPET-MDI meeting actions to JIRA milestones/versions, in collaboration with IPET-MDI members Created: 29/Jun/10 Updated: 13/Jul/10 Resolved: 13/Jul/10 |
|
| Status: | Closed |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Michael Burek [ 13/Jul/10 12:39 PM ] |
| WIKI Cross reference has been updated to use WMO HTML meeting report, JIRA updated to add links to the HTML report |
[WIS-204] Collaborate with Matteo to provide example metadata records for testing Created: 16/Jun/10 Updated: 16/Jun/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Action MDI-1-xxxii Michael, Eiji and the whole metadata team Most of the team were asked to contribute to developing example metadata records ... we can use Matteo's requirement to drive this action. From Matteo: In order for us to have reproducible tests we would need some sample of data and metadata, ideally sample that are not by default in the catalogue of the GISCs (i.e metadata from non essential data or products) test case 1: We need there valid and an invalid metadata records. We also need couples of metadata record with the same unique identifier test case 2 : idem as 1: sample of metadata record test case 3: sample of data with associated metadata test case 4: sample of metadata with associated data from different WMO program. |
[WIS-203] Transfer any pertinent information that is currently on the NCAR wiki to the WIS wiki Created: 16/Jun/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Action MDI-1-xxxii
Document: n/a Michael & Timo 'Mine' the now defunct IPET-MI wiki hosted by NCAR for useful information and transfer to WIS WIKI (if any) |
[WIS-202] Liaise with JCOMM/IOC Created: 16/Jun/10 Updated: 31/Aug/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | G. Reed |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Laise with JCOMM/IOC to facilitate the provision of oceanographic thematic vocabularies
|
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Action MDI-1-xxx Document: n/a Convert meeting recommendations into online user documentation |
Update UML diagrams of WMO Core Profile
(WIS-199)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Action MDI-1-xxix Document: n/a Validate UML diagrams of WMO Core Profile provided from Action MDI-1-xxviii |
[WIS-199] Update UML diagrams of WMO Core Profile Created: 16/Jun/10 Updated: 02/Sep/10 |
|
| Status: | In Progress |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||
| Sub-Tasks: |
|
||||||||||
| Description |
|
Action MDI-1-xxviii Document: n/a Update UML diagrams of WMO Core Profile to reflect changes agreed; this will mostly be in the form of additional constraints |
| Comments |
| Comment by Jeremy Tandy [ 27/Aug/10 7:16 AM ] |
|
I'm about to incorporate the new constraints for the WMO core profile of ISO19115 (type-1 profile; restriction only) that we discussed at our meeting [http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm]. I am wondering what the current recommended best practice is for creating these constraints in the UML model is.
I've asked Rob Atkinson (CSIRO ... & general expert in this stuff) to confirm that this page [https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/MetadataProfiles] from the SEEGrid twiki is still valid. Please add any up to date guidance here if you are aware. |
| Comment by Jeremy Tandy [ 27/Aug/10 7:17 AM ] |
|
I'm about to incorporate the new constraints for the WMO core profile of ISO19115 (type-1 profile; restriction only) that we discussed at our meeting [http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm]. I am wondering what the current recommended best practice is for creating these constraints in the UML model is.
I've asked Rob Atkinson (CSIRO ... & general expert in this stuff) to confirm that this page [https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/MetadataProfiles] from the SEEGrid twiki is still valid. Please add any up to date guidance here if you are aware. |
[WIS-198] WIS Sub-version repository Created: 09/Jun/10 Updated: 13/Jul/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 4.2.4 Action MDI-1-xxvii Michael Assess whether NCAR could host a WIS subversion repository Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxvii |
[WIS-197] Discuss choice of wiki software Created: 09/Jun/10 Updated: 25/Sep/10 Resolved: 25/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 4.2.3 Action MDI-1-xxvi Ted, Dave & Timo Discuss choice of wiki software for future robustness & capability Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxvi |
| Comments |
| Comment by Ted Habermann [ 23/Sep/10 6:19 AM ] |
| Talked about the wiki choice with Dave and Timo. They pointed out that Tiki-Wiki is well supported at this point and that it is satisfying their needs. This seems like a reasonable choice for the WMO wiki at this point. Thanks to them for the information! |
| Comment by Jeremy Tandy [ 25/Sep/10 4:19 AM ] |
|
Resolved - Ted has completed this action and use of Twiki WIKI remains OK.
|
[WIS-196] Migrate useful content from IPET-MDI Huddle site Created: 09/Jun/10 Updated: 14/Jul/10 Resolved: 14/Jul/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Complete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 4.2.1 Action MDI-1-xxv Jeremy (Timo to assist?) Migrate useful content from IPET-MDI Huddle site to WIS WIKI & retire Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxv |
| Comments |
| Comment by Jeremy Tandy [ 14/Jul/10 11:09 AM ] |
|
Done. Various files and discussion threads have been moved across to the WIS wiki (http://www.wmo.int/pages/prog/www/WIS/wiswiki/tiki-index.php?page_ref_id=50) and associated discussion thread topics (http://www.wmo.int/pages/prog/www/WIS/wiswiki/tiki-view_forum.php?forumId=5) Jeremy |
[WIS-195] Transition from Volume C1 to the WIS DAR catalogue Created: 09/Jun/10 Updated: 02/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Guofu Wanggf |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||
| Description |
|
Document Section 2.1.2.53 Action MDI-1-xxiv Guofu + Eiji, Ashok, Siegfried / Jürgen & Jean Pierre Establish & lead a sub-group to assist the WMO Secretariat [Pierre] specify how the transition from Volume C1 to the WIS DAR catalogue will be achieved. Of particular interest will be the recommendation of operational practices whilst Volume C1 is being maintained in parallel with the new DAR catalogue while the WIS infrastructure matures. Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxiv |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Ted Habermann |
| Resolution: | Complete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section: 2.1.2.49 Action MDI-1-xxiii Ted, Michael & Jean Pierre Define best practices relating to resolving metadata components - especially with reference to the implications of updating metadata components & needing to propagate changes to impacted metadata records. Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxiii |
| Comments |
| Comment by Ted Habermann [ 23/Sep/10 6:12 AM ] |
| See https://www.nosc.noaa.gov/dmc/swg/wiki/index.php?title=ISO_Components for information on components, referencing components, default values and substitutions. |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Document Section: 2.1.2.43 Action MDI-1-xxii Michael Add examples with agreed upon reference URLs for schemas so that members can validate from the same sources Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxii |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | WMO CBS Demonstration |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section: 2.1.2.39 Action MDI-1-xxi Ted Recommend best practice to enable transition from MD_Metadata to MI_Metadata - including reference 'official' schema location Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xxi |
| Comments |
| Comment by Ted Habermann [ 13/Jul/10 1:41 PM ] |
|
The transition from ISO 19115 with MD_Metadata as the root element to ISO 19115-2 with MI_Metadata as the root involves two steps: 1. Add the gmi namespace definition (xmlns:gmi="http://www.isotc211.org/2005/gmi") to the root element and 2. Change the root element from gmd:MD_Metadata to gmi:MI_Metadata. The root element then looks like: <gmi:MI_Metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://www.ngdc.noaa.gov/metadata/published/xsd/schema.xsd" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gml="http://www.opengis.net/gml" xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gts="http://www.isotc211.org/2005/gts" > The schema location in this example (http://www.ngdc.noaa.gov/metadata/published/xsd/schema.xsd) works for either MD_Metadata or MI_Metadata, but is not a permanent location. The final location will be something like http://www.isotc211.org/2005/gmi, but it is not currently available. |
| Comment by Jeremy Tandy [ 24/Sep/10 3:00 AM ] |
|
Further discussion between Ted Habermann and Jeremy Tandy @ OGC TC meeting in Toulouse, Spet 2010:
--- TH indicated that due to ISO 'red-tape' the schemas and resources for ISO19115-2 are not yet hosted on the ISO TC/211 pages … but the next best thing can be found on the Eden wiki (hosted by IGN; the French national mapping agency: http://eden.ign.fr/xsd/isotc211/isofull/20090316/resources/view. These schemas could be view as 'almost' official - TH's view was that they are safe to reference. TH expects the ISO19115-2 (2009) schemas to be publically hosted on the ISO TC/211 website soon. --- |
| Comment by Jeremy Tandy [ 24/Sep/10 3:02 AM ] |
| The semi-official schemas hosted by IGN are adequately stable for the interim. |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Document Section: 2.1.2.35 Action MDI-1-xx Jeremy Add example of both specification & use of multi-language code-list Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xx |
[WIS-190] Assess current best-practices for tools for ontologies or taxonomies or skos Created: 09/Jun/10 Updated: 02/Sep/10 |
|
| Status: | In Progress |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Document Section 2.1.2.32 Action MDI-1-xix Jeremy Assess current best-practices for providing simple tools to help metadata authors browse ontologies or taxonomies or skos Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xix |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 5:22 AM ] |
|
Having had some discussions with 'industry experts' in this space, I discovered that this subject is still in a rapid state of flux.
I'm currently working my way through the W3C standards relating to RDF (RDF-A, RDF-S), SKOS, OWL etc. My gut feeling - it appears that ONTOLOGIES need only be used where you want to INFER meaning from a hierarchy of related vocabularies. I don't think we need to go this far ... 'Taxonomy' is still relevant even where you have complex M-to-N mappings of controlled vocabs. Here's some notes from some of my discussions: --- Ontology vs. taxonomy Ontology = OWL, SPARQL A-box inference data, T-box class data Notion of inheritance, i.e. you can infer the answer to which city am I in? based on a hierarchy of reference data RDF gives you a graph but no inference Taxonomy = structured lists of information --- Clearly I need to do some more research here ... but for now I'll be focusing on TAXONOMIES rather than ONTOLOGIES! |
[WIS-189] Investigate the use of Protegé tools to build hierarchical taxonomies Created: 09/Jun/10 Updated: 02/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Manuel Fuentes |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Document Section: 2.1.2.32 Action MDI-1-xviii Manuel + Michael + Jeremy Investigate the use of Protegé tools, RDF/OWL & SKOS Simple Knowledge Organization System [http://www.w3.org/2004/02/skos/] to build hierarchical taxonomies / simple ontologies from GCMD, CF standard names & WMO Common Codes table C13. Note that NCAR's portal codebase now includes these technologies Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xviii |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Manuel Fuentes |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 2.1.2.32
Action MDI -1-xvii Manuel + Jeremy + Ted Define (best) practices for referencing keywords from fixed vocabularies Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xvii |
| Comments |
| Comment by Jeremy Tandy [ 24/Sep/10 2:54 AM ] |
|
Discussion between Ted Habermann and Jeremy Tandy @ OGC TC meeting in Toulouse (Sept 2010):
--- JT indicated that SKOS [http://www.w3.org/2004/02/skos/] appears to be the preferred model / format for publishing web-accessible vocabularies. This offers a richer set of semantics than the 'blunt' ISO Code-List catalogue. TH provided examples where NGDC are using controlled vocabularies: GCMD [http://gcmd.nasa.gov/], CF-Standard Names [http://cf-pcmdi.llnl.gov/documents/cf-standard-names/] and UDUnits [http://www.unidata.ucar.edu/software/udunits/]. UDUnits and CF Standard Names appear to have created a custom xml structure ... The key requirement is that the (XML) structure employed must have ANCHORS allowing the xlink from the metadata instance to link directly to the appropriate part of the vocabulary ... e.g. myVocabFile.xml#myElement. The xml file in this example could easily be an ISO Code-List catalogue or a SKOS vocabulary. --- |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 2.1.2.28 Action MDI-1-xv Eiji + Michael + Ashok + Ted Develop a sophisticated stylesheet that provides guidance & in-line editing capabilities to support validation of baseline metadata developed by Meteo France (would this also provide a basic template for the minimum metadata footprint - i.e. be able to create a new metadata record from scratch?) Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xv |
| Comments |
| Comment by Jeremy Tandy [ 25/Sep/10 4:17 AM ] |
|
Ted - when we talked at OGC TC meeting we suggested that you take the initiative and contact Michael & Eiji to walk them through all the material you have developed for RUBRICs and NGDC ...
Thanks, Jeremy |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Eiji |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 2.1.2.28 Action MDI-1-xiv Eiji + Michael + Ashok + Ted Develop stylesheet to render human readable WMO Core Profile records, presented in response to browsing the GISC catalogue Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xiv |
| Comments |
| Comment by Ted Habermann [ 23/Sep/10 6:26 AM ] |
| There are many stylesheets available at http://www.ngdc.noaa.gov/metadata/published/xsl/. These are used to support the views at http://www.ngdc.noaa.gov/metadata/published/iso/ |
| Comment by Eiji [ 23/Sep/10 6:36 AM ] |
|
Thanks for reminder. I'll study those XSLs.
I wrote a minimalistic XSLT to do the GMD & SRU visualization, currently available at http://www.gisc.kishou.go.jp/toyoda/2010/0918-xsl-devel/gmd2html.xsl with examples http://www.gisc.kishou.go.jp/toyoda/2010/0918-xsl-devel/md1.html http://www.gisc.kishou.go.jp/toyoda/2010/0918-xsl-devel/sruout.xml Eizi |
| Comment by Jeremy Tandy [ 25/Sep/10 4:15 AM ] |
|
During ad-hoc meeting of ipet-mdi members at OGC TC meeting (Toulouse, 2010) we discussed this issue ...
--- TH indicates that NGDC have several style-sheets for rendering this content - but suggests we may need a more focused style-sheet specifically for the WMO / WIS community. He also notes that the 'hierarchy' best-practices are not yet rendered in this form ... TH suggests that the most productive route may be the conversion of the ISO19139 records in JSON [http://www.json.org/] (rather than HTML) to enable simple navigation of the record within a browser. By way of example, TH demonstrated the ncISO tool @ NGDC that crawls a THREDDS catalogue and builds a JSON document for browsing: http://www.ngdc.noaa.gov/eds/tds/. An example of the browsable hierarchy can be found here: http://www.ngdc.noaa.gov/eds/tds/oceanSITESMetadataAssessment.html --- |
[WIS-184] Human readable response to SRU query Created: 09/Jun/10 Updated: 31/Aug/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Eiji |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Document Section: 2.1.2.28 Action MDI-1-xiii Eiji + Michael + Ashok Develop a stylesheet to render human readable response to SRU query Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xiii |
[WIS-183] Review existing SRU response schema Created: 09/Jun/10 Updated: 31/Aug/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Eiji |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Document Section: 2.1.2.27 Action MDI-1-xii Eiji Review Timo's existing SRU response schema & develop to suit community needs Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xii |
[WIS-182] Develop schematron rule-sets Created: 09/Jun/10 Updated: 02/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jean-Pierre |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||
| Description |
|
Document Section 2.1.2.25 Action MDI-1-xi Jean Pierre with guidance from Greg & Ted Develop schematron rule-sets to implement the conformance tests, using the geonetwork & ANZLIC schematron rules as a baseline. The focus will be on validation against the WMO profile. Developing validation tests against other profiles by interpretting the ISO19115 extension record is a significantly lower priority. Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_xi |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jean-Pierre |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Document SECTION 2.1.2.25 Action MDI-1-x Jean Pierre & Jeremy Review candidate conformance tests & rank in order of validation Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_x |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document section 2.1.2.24 Action MDI-1-ix Jeremy - Define the full set of WMO Core Profile code-lists Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_ix |
[WIS-179] Define the WMO Core Profile extension object Created: 09/Jun/10 Updated: 13/Jul/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section 2.1.2.24 Action MDI-1-viii Ted - define the WMO Core Profile extension object Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_viii |
Machine readable gazetteers of geographic identifiers and of volume A MDI
(WIS-157)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | G. Reed |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Action MDI-1-vii: Greg Liaise with groups building gazetteer services and provide implementation experience and project updates to IPET-MDI Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_vii |
Machine readable gazetteers of geographic identifiers and of volume A MDI
(WIS-157)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Manuel Fuentes |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Document Section 2.1.2.21 Action: MDI-1-vi Manuel & Jeremy (& Alexander Besprozvannykh?) - develop simple Vol A gazetteer Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_vi |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jean-Pierre |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Document Section 2.1.2.21 Action MDI-1-v Jean Pierre & Simon - develop a first-cut set of metadata with appropriate bounding boxes, including SHP & AMDAR products Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_v |
[WIS-175] Create hierarchies of related datasets using ISO19115 Created: 09/Jun/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Document Section: 2.1.2.19 Action MDI-1-iv Ted & Michael develop best practices for building hierarchies of related datasets using the ISO19115 conceptual model subject to the constraints of implementation! Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_iv |
| Comments |
| Comment by Jeremy Tandy [ 23/Sep/10 2:12 AM ] |
| Ted has done some work in this area ... |
| Comment by Ted Habermann [ 23/Sep/10 6:21 AM ] |
| See https://www.nosc.noaa.gov/dmc/swg/wiki/index.php?title=Metadata_Hierarchies for a discussion of hierarchies for in-situ data. |
| Comment by Jeremy Tandy [ 25/Sep/10 4:07 AM ] |
|
Also Ted presented on this subject at the OGC TC meeting ... I've appended the presentations to the IPET-MDI twiki page 'resources' here: http://www.wmo.int/pages/prog/www/WIS/wiswiki/tiki-index.php?page=IPET-MDI]
|
| Comment by Jeremy Tandy [ 25/Sep/10 4:08 AM ] |
| Ted - are you satisfied that this issue can be resolved given the guidance information you have provided? |
| Comment by Ted Habermann [ 25/Sep/10 4:21 AM ] |
| I think it would be best to try a few examples... Can we think of one that is specific to WIS? |
[WIS-174] Develop candidate static metadata components Created: 07/Jun/10 Updated: 02/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Jean-Pierre |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Description |
|
MDI-1-ii Static metadata components will be identified by UUID and resolvable by URL. These metadata components will be hosted at wis.wmo.int/ Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_ii Document Section 2.1.2.19 |
Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12)
(WIS-127)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Ted Habermann |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Action: MDI-1-i Propose mechanism for unique identification of place names - e.g. urn:x-wmo:place:int.wmo.wis::AtlanticOcean Document: http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#MDI_1_i Document Section 2.1.2.9 |
[WIS-172] Complete IPET-MDI meeting report Created: 11/May/10 Updated: 29/Jun/10 Due: 12/May/10 Resolved: 29/Jun/10 |
|
| Status: | Closed |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Burek | Assignee: | Michael Burek |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Eiji [ 02/Jun/10 2:33 AM ] |
|
Nearly-closing draft is available at http://docs.google.com/Doc?docid=0AQcTAyotgnOvZGRtN3R6YnFfMTgxY2RnaGh3ZGc&hl=en |
| Comment by Jeremy Tandy [ 02/Jun/10 4:40 PM - Visible by: wis-users ] |
|
Hi Eiji. I have been monitoring the flurry of activity to finalize the report (lead primarily by yourself - thanks). Unfortunately I have let things run for a week or so longer than is healthy - my apologies. I have allocated all of tomorrow to review the closing drafts & comment on any outstanding issues. Michael Burek has offered to help complete this task. |
| Comment by Jeremy Tandy [ 03/Jun/10 6:53 PM - Visible by: wis-users ] |
|
The current status of the meeting report is: * the document can be accessed here: http://docs.google.com/Doc?docid=0AQcTAyotgnOvZGRtN3R6YnFfMTgxY2RnaGh3ZGc&hl=en * all changes proposed have been reviewed & incorporated as appropriate ... too many to list here. Within the google-docs, please use the revision history [File > See Revision History] to see the most recent changes I have incorporated - compare against version 2088. * I *think* I have removed all of the 'strike-through' text * I cannot vouch for the spellings or grammar (it's very late!) So what next? As I am headed out on vacation tomorrow for two-weeks, Michael Burek has offered to coordinate the finalization & release of the meeting report. He will: * co-ordinate a final review (please participate if you can - the doc will need a full end-to-end read through / sanity check) * work with Atsushi on formatting etc. & publish the report to the WIS Wiki * take ALL the actions listed in the meeting report & create JIRA tickets for each one so we can track progress - expect to see some coming your way :-) Michael will contact you all and outline the timescales for this last stage. Once the report is published, we can extract all the recommendations & create some useful online user documentation to publish on the WIS wiki. |
| Comment by Jeremy Tandy [ 03/Jun/10 6:55 PM - Visible by: wis-users ] |
| Mike - over to you for the last phase :-) |
[WIS-162] Data owners to be able to define recipients of data that is restricted in its distribution (Can we have an easier solution than current GTS practices?) Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 02/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
MDI to provide a standard way of describing data policy in metadata. MDI - vocab for data access control in discovery metadata WISC - method of defining and implementing rules for distribution of data concentrate on simple "licence" criteria that cover 80%+ of data transferred. - and implications for exchange of recipient information between GISCs"
|
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 3:59 AM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Definition of access control policy controlled vocabulary & implementation in metadata record 2.1.2.36 The subject here is the access constraints for the target dataset. Recommendation 31: candidate vocabulary terms for WIS access constraints include: - Unrestricted - Resolution 40 and Resolution 25 Essential Data - Resolution 40 and Resolution 25 Additional Data - Custom 2.1.2.37 Unrestricted is semantically equivalent to Resolution 40 and Resolution 25 Essential Data. Continuing current GTS practices where RTHs are responsible for enforcing access control policies on behalf of data-providers, GISCs will be responsible for enforcing the access control policies cited in the metadata record for each product. Recommendation 32: best practice suggests that the absence the useConstraints attribute: MD_Metadata/identificationInfo/MD_Identification/resourceConstraints/MD_LegalConstraints/useConstraints implies Unrestricted. However, the Resolution 40 and Resolution 25 Essential Data access control category should be used explicitly to indicate that data-providers are sharing this dataset under WMO Resolution 40 or Resolution 25. Recommendation 33: the Custom access control category is used to indicate access control that is defined by the data-provider. The details of the policy must be referenced by URL. Recommendation 34: the access control policy will be defined in the following elements: - MD_Metadata/identificationInfo/MD_Identification/resourceConstraints/MD_LegalConstraints/useLimitation/gco:CharacterString = "«category-code»" - MD_Metadata/identificationInfo/MD_Identification/resourceConstraints/MD_LegalConstraints/useConstraints/MD_RestrictionCode = "otherRestrictions" - MD_Metadata/identificationInfo/MD_Identification/resourceConstraints/MD_LegalConstraints/otherConstraints/gco:CharacterString = "«category-code»" - «category-code» will be a semi-controlled vocabulary for the WMO Core Profile and can be either: o "WMO Essential" o "WMO Additional" o «free-text» "otherRestrictions" is part of the codelist MD_RestrictionCode «free-text» is used to describe the custom access control policy and is recommended to include the URL of a resource describing the access control policy in detail. If the access is NOT controlled (i.e. unrestricted) the resourceConstraints element is omitted. 2.1.2.38 Example from NOAA Metadata constraints (WMO probably has their own language...) <gmd:metadataConstraints> <gmd:MD_LegalConstraints> <gmd:useLimitation> <gco:CharacterString>While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.</gco:CharacterString> </gmd:useLimitation> </gmd:MD_LegalConstraints> </gmd:metadataConstraints> Maintenance note <gmd:metadataMaintenance> <gmd:MD_MaintenanceInformation> <gmd:maintenanceAndUpdateFrequency gco:nilReason="Unknown"/> <gmd:maintenanceNote> <gco:CharacterString>This metadata was automatically generated from the FGDC Conten Standards for Digital Geospatial Metadatastandard version FGDC-STD-001-1998.</gco:CharacterString> </gmd:maintenanceNote> </gmd:MD_MaintenanceInformation> </gmd:metadataMaintenance> Note: ISO19115:2012 revision is likely to add a citation attribute that will enable the custom access control policy to reference the details. Resolution 40 and Resolution 25 may also be cited using this mechanism. --- |
[WIS-160] Vocabularies, multi-language and navigation hierarchies MDI - keywords in English required Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: Priority is thematic hierarchies. Other Commissions to provide their keyword proposals based on their vocabs and provide templates appropriate to commission's work.(need domain expertise beyond MDI participants) Product priority code list Mechanism for maintaining vocabularies WISC - define how data are to be navigated (themes, geography, others) |
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 12:08 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Recommendation 23: Where WMO Core Profile metadata records include multiple language definitions, validation will ensure that English definitions are present at a minimum. --- Recommendation 30: multi-language implementations of code-lists may be used. --- 2.1.2.54 Multi-language metadata Recommendation 51: the following policies will apply to multi-language metadata records: - At a minimum, metadata will be published in English - An abstract must primarily be in English; alternative language versions may be provided - GISC systems will always operate on the primary English metadata - Where a 3rd party wishes add translation to a metadata record, they must propose changes to the metadata custodian (data-owner) for the record. Only the metadata custodian (or their delegated agent) has the authority to update the metadata. Updates will be propagated via the WIS via the normal mechanism. The default language and character set of the metadata record is explicited in the MD_Metadata/language and MD_Metadata/characterSet elements: <gmd:language> <gmd:LanguageCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#LanguageCode" codeListValue="eng"/> </gmd:language> <gmd:characterSet> <gmd:MD_CharacterSetCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#MD_CharacterSetCode" codeListValue="utf8"/> </gmd:characterSet> Each alternate language for the metadata is defined via a MD_Metadata/locale element: <gmd:locale> <gmd:PT_Locale id="locale-fr"> <gmd:languageCode> <gmd:LanguageCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#LanguageCode" codeListValue="fra"/> </gmd:languageCode> <gmd:characterEncoding> <gmd:MD_CharacterSetCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#MD_CharacterSetCode" codeListValue="utf8"/> </gmd:characterEncoding> </gmd:PT_Locale> </gmd:locale> Each metadata element with a CharacterString type and free text domain can be instantiated with a gmd:PT_FreeText_PropertyType type: <gmd:abstract xsi:type="gmd:PT_FreeText_PropertyType"> <gco:CharacterString>Abstract in english</gco:CharacterString> <gmd:PT_FreeText> <gmd:textGroup> <gmd:LocalisedCharacterString locale="#locale-fr">Résumé en français</gmd:LocalisedCharacterString> </gmd:textGroup> <gmd:textGroup> <gmd:LocalisedCharacterString locale="#locale-sp">Resumen en espanol</gmd:LocalisedCharacterString> </gmd:textGroup> </gmd:PT_FreeText> </gmd:abstract> In the example above, two alternate languages are assumed to be defined. The abstract element is provided in the default language with a common gco:CharacterString element. An additional gmd:PT_FreeText element is present, containing possibly a gmd:textGroup element for every alternate translation. Translations may be defined in translation files instead of being embedded in the metadata record. In this case, it is simpler to group in a single file the definition of one alternate language and the associated translations, each translated string identified by a unique id attribute. Here is an example translation file: <gmd:PT_LocaleContainer xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://www.isotc211.org/2005/gmd/gmd.xsd"> <!-- gmd:description element not shown --> <gmd:locale> <gmd:PT_Locale id="locale-fr"> <gmd:languageCode> <gmd:LanguageCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#LanguageCode" codeListValue="fra"/> </gmd:languageCode> <gmd:characterEncoding> <gmd:MD_CharacterSetCode codeList="http://wis.wmo.int/2006/catalogues/gmxCodelists.xml#MD_CharacterSetCode" codeListValue="utf8"/> </gmd:characterEncoding> </gmd:PT_Locale> </gmd:locale> <!-- gmd:date element not shown --> <!-- gmd:responsibleParty element not shown --> <gmd:localisedString> <gmd:LocalisedCharacterString locale="#locale-fr" id="abstractfr">Résumé en français</gmd:LocalisedCharacterString> </gmd:localisedString> <!-- other gmd:localisedString elements not shown --> </gmd:PT_LocaleContainer> The translated values of textual metadata elements are then referenced in the multi-lingual metadata as in: <gmd:abstract xsi:type="gmd:PT_FreeText_PropertyType"> <gco:CharacterString>Abstract in english</gco:CharacterString> <gmd:PT_FreeText> <gmd:textGroup xlink:href="fr-fr.xml#abstractfr"/> </gmd:PT_FreeText> </gmd:abstract> Note: the object type MemberName is used within software systems like a foreign key. As such it is never translated in multi-lingual metadata. --- Issue WIS-191 requests provision of best practice information on use of multi-language codelists. |
[WIS-157] Machine readable gazetteers of geographic identifiers and of volume A MDI Created: 23/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 12:49 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Recommendation 16: place-names used as keywords and geographicIdentifiers will be defined in a register (or controlled vocabulary) based on the content of Vol A. Each entry must have a UUID (as primary key) in addition to the (mostly) unique WMO station-code identifier. The station-gazetteer register & each entry will be resolvable by URL (incorporating the UUID) and, as a minimum, validate the authenticity of a given station. The Volume A gazeteer implementation will be available in the form of a CT_CodelistCatalogue (e.g http://asdd.ga.gov.au/asdd/profileinfo/anzlic-allgens.xml) that can be referenced as: a keyword thesaurus MD_Metadata/identificationInfo/MD_DataIdentification/descriptiveKeywords/MD_Keywords/thesaurusName/CI_Citation or as an authority in the geographicIdentifier case: MD_Metadata/identificationInfo/MD_DataIdentification/gmd:extent/EX_Extent/geographicElement/EX_GeographicDescription/gmd:geographicIdentifier/MD_Identifier/authority/CI_Citation In the geographicIdentifier case, the code: MD_Metadata/identificationInfo/MD_DataIdentification/extent/gmd:EX_Extent/geographicElement/EX_GeographicDescription/geographicIdentifier/MD_Identifier/authority/CI_Citation/identifier/MD_Identifier/code/CharacterString shall have the form: http://wis.wmo.int/WMOVolumeAGazeteer.xml#WMOStationNumber. The CT_CodelistCatalogue includes a codeEntry element for each item in the catalog. The codelistItem/CodeListDictionary/codeEntry/description shall include the bounding box or location and elevation for the item in well-known text (http://en.wikipedia.org/wiki/Well-known_text). Note: If the WMO Station Index refers to separate locations for surface and upper air observations, the location shall be described as MULTIPOINTZ((LON1 LAT1 ELE1),(LON2 LAT2 ELE2)). --- Also see linked issue WIS-177 |
[WIS-156] XML schema to allow metadata validation against - and publish it officially MDI Created: 23/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 4:16 AM ] |
|
The issue of deciding what is 'officially' published for a metadata release was discussed at meeting IPET-MDI 1 in Geneva (April 2010). See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
Publication of the schemas remains an outstanding issue. Also note the comment: "GISCs are likely to keep a local copy of these entities in order to speed validation etc" An extract of the meeting report is included below ... --- 2.1.2.64 Candidate release process (until congress 2011): · OPAG-ISS / WISPO will establish a set of agreed release milestones for metadata guidelines. These will be organized to support the WIS project plan; e.g. guidelines released with sufficient lead-time ahead of major deliverables. The release schedule is critically important to maintain as this is the 'tempo' of change; implementers can plan to adapt at known dates and be assured that there will be no change until the next release milestone. Each release milestone must clearly define the reasons why it exists - what future project deliverable / outcome does it support? · JIRA release management software [web-based service, provided by NCAR (Don Middleton)] used to capture issues. · IPET-MDI chair will distribute 'problem tickets' to the team, whereupon they will be assessed each in turn against the growing historical knowledge base and 'inside' knowledge. · Where IPET-MDI deem it necessary to propose new metadata usage guidelines to clarify or resolve issues, such problem tickets will be allocated to the AGREED release milestones in consultation with ET-WISC. · Where metadata usage guidelines are considered to impact the GISC implementation community, then a future release milestone will be identified where the guideline becomes BINDING. Until that time, the guideline is not enforceable but will be marked as DEPRECATED in the automated validation. Any instances of deprecated practices will identify when they are due to become binding. · IPET-MDI will develop & publish the guidelines and associated collateral material (including updates to the automated validation scripts) in time to meet the release milestone. · Release package ‘manifest’ – host @ wis.wmo.int/2010/... o Schema(s) iso19139 o Schematron rules o Controlled vocabularies, code-list extensions (& gazetteers) o Guidance notes – wiki (& later PDF document compiled by WISPO-contractor) o Sample metadata o Static metadata components & component management tools o Conformance tests o Stylesheets + ‘rubric tests’ [prioritize ‘minimum metadata’ requirements] o Metadata editor stylesheets; template metadata o UML Recommendation 59: the candidate release process was approved. Recommendation 60: all material pertaining to a release of the WMO Core Profile standard will be published to: - http://wis.wmo.int/«YYYY» Note that GISCs are likely to keep a local copy of these entities in order to speed validation etc. The WMO Secretariat will support the release process. The IPET-MDI team will work closely with the WISPO and their nominated expert contractor to further develop the metadata guidelines into the Manual on WIS. --- |
[WIS-155] How mark metadata record as draft MDI Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 12:39 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- 2.1.2.53 Marking metadata as draft To support the initial implementation of WIS, Metéo France will create a complete set of metadata records for the GTS products intended for global exchange. These metadata records will form a baseline for the DAR catalogue until the data-owners (i.e. WMO member-states & organizations) are ready to begin maintenance of their metadata records. As these records are created by Metéo France rather than the official data-owner, these records will be marked as draft. Once the metadata has been validated by the appropriate member organization, ownership will be transferred and the 'DRAFT' status will be removed. In order to ensure that DRAFT status is amended during validation, the team recommend a scheme whereby the member organization will need to overwrite an element with their own information. The following schemes were reviewed but discarded: - MD_Metadata/metadataMaintenance/MD_MaintenanceInformation/maintenanceNote = "DRAFT" - MD_Metadata/metadataConstraints/MD_Constraints/useLimitation = "DRAFT" Recommendation 50: Météo France 'baseline' metadata will be marked as DRAFT using the following scheme: - gmd:MD_Metadata/gmd:metadataMaintenance/gmd:MD_MaintenanceInformation/gmd:contact/gmd:CI_ResponsibleParty/gmd:organisationName = "Meteo France (on behalf of «NC or DCPC» by interim agreement with ICG-WIS)" - gmd:MD_Metadata/gmd:metadataMaintenance/gmd:MD_MaintenanceInformation/gmd:contact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress = "quelqu-un@meteo.fr" --- |
[WIS-154] Guidance on metadata for authors (including samples and templates) - clear specification of minimum metadata requirements - and make it clear that metadata is for datasets and not instances MDI Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:41 AM ] |
| This is a highlevel description of the need for metadata guidance. I expect it will have many subtasks. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 7:37 AM ] |
|
The concerns raised in this issue were discussed at length during IPET-MDI 1 meeting in Geneva (April 2010). The meeting report (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm) provides guidance for metadata authors. The guidance generated at the meeting is incomplete; a list of outstanding issues (and links to the issues within JIRA) can be found here:
http://www.wmo.int/pages/prog/www/WIS/wiswiki/tiki-index.php?page=Meeting+Document+actions+to+JIRA+ticket+cross+reference |
[WIS-153] Us of bounding boxes and geographic records MDI Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:39 AM ] |
| Jeremy, some of these tasks could do with a little background added and purpose. Otherwise, is this a part of the user guidelines activities? Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:01 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See meeting report for more details (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Recommendation 13: boundingBox MD_Metadata/identificationInfo/MD_DataIdentification/extent/EX_Extent/geographicElement/EX_GeographicBoundingBox will be mandatory to ensure compliance with INSPIRE regulations. Where the sensor platform is mobile (e.g. AMDAR, ships or bouys) the bounding box will describe the maximum reasonable extent within which the platform may operate, potentially a global extent. However, it should be noted that GTS practices (tables C1, C2 & C3 of the Manual on GTS) keep the extent of the bulletin fixed and require that the data from mobile platforms is allocated to the appropriate bulletin based on the location of the platform. The team noted that specifying datasets that include the north or south poles may be difficult. Also, best practices on acceptable units for lat/lon must provided (e.g. -180 to +180, -90 to +90; 0 to 360; or East/West notation. --- Note the linked issue WIS-176:: Action MDI-1-v: Jean Pierre & Simon - develop a first-cut set of metadata with appropriate bounding boxes, including SHIP & AMDAR products |
[WIS-152] Confirm rules for versioning metadata MDI Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:36 AM ] |
| Jeremy, this task could be a sub task or super task for the role of the file identifer task. Hopefully we can combine some of these tasks or at least make them sub tasks of a particular activity. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:36 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- 2.1.2.15 The team was asked to verify the agreement made at the ICG-WIS 6 indicating that only the fileIdentifier element and metadata creation date-time stamps will be used to assess uniqueness / duplication of a given metadata record compared to other records.The sequence (time-order) of metadata files with the same fileIdentifier will be assessed according to the date-time stamp. Recommendation 7: WIS implementers will assess the uniqueness of a metadata record using only the fileIdentifier element and metadata creation date-time stamps: gmd:MD_Metadata/gmd:fileIdentifier gmd:MD_Metadata/gmd:dateStamp Version numbering or date-stamps are explicitly forbidden from the fileIdentifier element. The MD_Metadata/dateStamp is the correct place for this information. It may also optionally appear in the metadata filename (see below). Changing the fileIdentifier element in any way will appear to be a new product! Note to implementers: The gmd:dateStamp within the metadata record should be distinguished from the datestamp in OAI-PMH wrapper XML, which appears as oai:header/oai:datestamp. Note that the OAI-PMH Implementation Guideline mandates that the OAI-PMH Aggregators (i.e. a WIS Center that provides metadata harvested from somewhere else) must use local harvesting time as oai:datestamp. In other words, OAI-PMH providers of GISCs and RTH-type of DCPCs must not use gmd:dateStamp as oai:datestamp, because connected GISC cannot use incremental harvesting from such provider. In some implementations the timestamp of metadata files are given as oai:datestamp, and the operator can cause re-synchronization by changing metadata file time stamps (such as touch(1) command). This is intended behavior, and developers should follow this methodology so as not to disable this functionality. --- |
[WIS-151] Method of defining unique identifier MDI Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:33 AM ] |
| Jeremy, this was well covered in the IPET-MDI first session and I think is appropriate to assign to ipet-mdi chair. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:13 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
Separate guidance is provided on BOTH filenames and metadata identifiers --- Recommendation 1: when metadata file is transferred between WIS centres, the metadata filenames: - must comply with the WMO file-naming-convention; - should use T_ product identifiers in place of A_ product identifiers to aid simplicity - should truncate W_ product identifiers to form an invariant string; i.e. the date and amendment / correction code will be excluded - must ensure that Z_ product identifier are globally unique within the WIS - must use the «YYYYMMDDhhmmss» element from the top-level file-naming convention to express the metadata publication / update date-time (this must represent the same date-time as the MD_Metadata/dateStamp element); - Use an '.xml' extension: - Examples: - T_FCUK31_C_EGRR_20100310180000.xml - T_HHXA05_C_BABJ_20100427083000.xml - W_FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW_20100428115800.xml --- Recommendation 2: gmd:MD_Metadata/gmd:fileIdentifier is a URI (Universal Resource Identifier) structured as follows: - fixed string "urn:x-wmo:md:" - citation authority - Examples: § "int.wmo.wis" § "gov.noaa" § "edu.ucar.ncar" § "uk.gov.metoffice" - Citation authority "int.wmo.wis" is used for all datasets intended for global exchange - Citation authority for other datasets remains with the dataset provider, expressed using a reverse-DNS name - Register of citation authorities should be maintained by WMO secretariat - separator colon ':' - empty string, reserved for future extension - separator colon ':' - unique identifier: - if a GTS «TTAAii» and «CCCC» is allocated for the product use «TTAAii»«CCCC»; - else if a WMO Product Identifier is allocated for the product use a truncated WMO product identifier field of the associated data-files, excluding the date-stamp and any other varying elements as necessary; or - else use a locally-unique identifier for the citation authority (not recommended for data and products intended for global exchange) Examples: - urn:x-wmo:md:int.wmo.wis::FCUK31EGRR - urn:x-wmo:md:cn.gov.cma::NMC.NWP.HCXA05BABJ - urn:x-wmo:md:int.wmo.wis::FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW --- Recommendation 3: gmd:MD_Metadata/gmd:fileIdentifier elements are treated as CASE-INSENSITIVE when assessing metadata records for duplication. --- Recommendation 5: where possible, the metadata identifier should map onto the invariant elements of the data-filename to help a human reader infer the connection. An explicit machine-interpretable linkage to the associated data-files will be expressed within the metadata record itself using the MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName element with regular expression of filename as content. Additional mandatory elements are: fileDescription and fileType --- Recommendation 6: where the citation authority is int.wmo.wis (signifying a dataset intended for global exchange), a standardized regular expression syntax will be used to express the linkage between the metadata record and the associated data-files via the MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName element. Multiple linkages may be expressed using the OR syntax in regular expression '|'. Examples: - Data-filename instance: "A_SMCI01BABJ281200_C_BABJ_20100428120000.txt" - MD_Metadata/fileIdentifier="urn:x-wmo:md:int.wmo.wis::SMCI01BABJ" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName="/^A_ SMIC01BABJ[0-9]+_C_BABJ_[0-9]+\.txt$/" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileDescription="General description of the datafile" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileType="text/plain" - Data-filename instance: "W_FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW_ 20061001000000.bin" - MD_Metadata/fileIdentifier="urn:x-wmo:md:int.wmo.wis::FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N- 60W65E_C_LFPW" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName="/^W_FR- meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW_[0-9]{14}\.bin$/" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileDescription="General description of the datafile" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileType="application/ octet-stream" --- |
[WIS-149] Multi-language metadata - how create MDI document current agreement - Park Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:28 AM ] |
| Jeremy, this could be a sub task of user guidelines on creating and managing metadata. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:17 PM ] |
|
This issue is a duplicate - the guidance on use of multi-lingual metadata is provided in the linked issue |
[WIS-144] De-reference shared name space to local caches - further discussion needed to clarify required outcome WISC Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 3:17 AM ] |
| Jeremy, this is perhaps an ET-WISC task but I think your initial comments would be welcome. Alternatively, reassign to Heinrich. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:23 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Recommendation 45: when serving querying responses from the GISC search portal, GISCs will amend the information served to the user by inserting an additional MD_Distributor object that describes their local GISC-cache. This gives the recipient a choice of destinations: the original source or the local cache. Such amended metadata must not be re-distributed for other GISCs]. There is no restriction on the format or structure of onlineResource attributes describing the local GISC-cache. Also note that there is no restriction on the format or structure of onlineResource attributes describing products that are not globally exchanged: i.e. those served only from an NC or DCPC and do not form part of the GISC cache. --- The meeting report provides significantly more information. Please refer. |
[WIS-143] Namespace used for all WIS WISC Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 3:11 AM ] |
| Jeremy, this was discussed at ipet-mdi 1st session. You may wish to add the recommendations of the meeting and reassign to Steve or Heinrich. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 11:56 AM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. The meeting report (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm) states:
+++ Recommendation 60: all material pertaining to a release of the WMO Core Profile standard will be published to: http://wis.wmo.int/«YYYY» Note that GISCs are likely to keep a local copy of these entities in order to speed validation etc. +++ The current published version of the WMO Core Profile is published to wis.wmo.int/2006 Once formalized, recommendations from IPET-MDI 1 will be published to wis.wmo.int/2010 Further information is provided in the meeting report on the 'namespaces' used for metadata identifiers. Recommendation 2 refers. |
[WIS-139] Given data filenames have to be the same as metadata filename. How do we describe the rules (pattern) for linking metadata to a data filename to a set of files. Need users guidelines WISC escalated to IPET-MDI to review and to prepare guidelines Created: 23/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | ET-GDDP Validation |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Comments |
| Comment by Dave Thomas [ 04/May/10 2:53 AM ] |
| Based on IPET-MDI 1st session, the assumption in this record may no longer be true. Need to clarify meeting conclusion and pass back to ET-WISC chair. Dave |
| Comment by Jeremy Tandy [ 31/Aug/10 12:21 PM ] |
|
This issue was discussed at meeting IPET-MDI 1 in Geneva (April 2010). The actions from the meeting include resolution of this concern. See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
--- Recommendation 5: where possible, the metadata identifier should map onto the invariant elements of the data-filename to help a human reader infer the connection. An explicit machine-interpretable linkage to the associated data-files will be expressed within the metadata record itself using the MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName element with regular expression of filename as content. Additional mandatory elements are: fileDescription and fileType --- Recommendation 6: where the citation authority is int.wmo.wis (signifying a dataset intended for global exchange), a standardized regular expression syntax will be used to express the linkage between the metadata record and the associated data-files via the MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName element. Multiple linkages may be expressed using the OR syntax in regular expression '|'. Examples: - Data-filename instance: "A_SMCI01BABJ281200_C_BABJ_20100428120000.txt" - MD_Metadata/fileIdentifier="urn:x-wmo:md:int.wmo.wis::SMCI01BABJ" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName="/^A_ SMIC01BABJ[0-9]+_C_BABJ_[0-9]+\.txt$/" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileDescription="General description of the datafile" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileType="text/plain" - Data-filename instance: "W_FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW_ 20061001000000.bin" - MD_Metadata/fileIdentifier="urn:x-wmo:md:int.wmo.wis::FR-meteofrance-toulouse,GRIB,ARPEGE-75N10N- 60W65E_C_LFPW" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileName="/^W_FR- meteofrance-toulouse,GRIB,ARPEGE-75N10N-60W65E_C_LFPW_[0-9]{14}\.bin$/" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileDescription="General description of the datafile" - MD_Metadata/gmd:describes/gmx:MX_DataSet/gmx:dataFile/gmx:MX_DataFile/gmx:fileType="application/ octet-stream" No serious issues are likely to arise from use of regular expressions on GTS filenames as the character set is limited to International Alphabet 5. Further information on Regular Expressions can be found at http://docs.google.com/View?id=df4kmgqs_50ffmzmqgj. The summary is: - Metadata creator or manager should provide regular expression that is understandable for all GISCs. Recommended syntax is chosen from common subset of various implementations (cf. above reference for detail; syntax letters are ? * + {,} (|) ^ $ [] [^] [a-z] \d \w . \. \+). - GISC Cache should support at least recommended syntax. It may also support other metacharacter for further development, but it must not alter recommended syntax and its semantics. It is advised to check regular expression provided in metadata before matching. - Although WMO Filename Convention is case-insensitive, metadata creators should give regular expression in correct case of letters. For example, location identifier should be described as [A-Z]{4}, not [a-z]{4}. - GISC Cache should use "ignore-case" option of regular expression library in matching metadata and dataset fragment. Above recommendations should be reviewed when use of the regular expression is extended beyond current GTS files and bulletins, or WIS data or products intended for global exchange is extended beyond current GTS. --- |
Publish initial proposal for WMO Conceptual Data Model
(WIS-133)
|
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-b |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 4:23 AM ] |
| Awaiting delivery of candidate conceptual model ... see parent task. WIS-133 |
[WIS-135] Recommendation of metadata for delivery of high priority information to user communities to support hazard warnings Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-a |
[WIS-133] Publish initial proposal for WMO Conceptual Data Model Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | In Progress |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-b |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 4:21 AM ] |
| This activity is being progressed within the OGC Met-Ocean domain working group. The wiki provides up-to-date information (see the section 'Conceptual Modelling'): http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/WebHome |
[WIS-132] Engage with OGC Meteorology Domain Working Group to review proposed met-ocean profile for OGC Web Map Service specification Created: 14/Apr/10 Updated: 25/Sep/10 Resolved: 02/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Incomplete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-f |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 3:45 AM ] |
|
The OGC Met Ocean domain working group continues to create a met-ocean profile for WMS. More information can be found here: http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/WebHome
This work is ongoing & I will maintain visibility of the outcomes. I consider this a LOW priority activity as it does not contribute directly to the success of the WIS or help resolve data format issues within the aviation community. My proposal is to let this activity run at its own timescales. Participants from NMS's are involved so I do not anticipate that the result will be problematic for the WMO community |
[WIS-131] Publish review of existing metadata & environmental information standards landscape - including usage & adoption profiles and development roadmaps where known Created: 14/Apr/10 Updated: 25/Sep/10 Resolved: 02/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Incomplete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-c |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 6:14 AM ] |
|
Whilst not 'published' this activity was undertaken at the 2nd workshop for use of OGC standards in meteorology (Toulouse, 2009) and subsequently via the OGC Met Ocean domain working group 'conceptual modelling' group. The minutes of telecons (http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/ConceptualModellingMinutes) reveal insight into the discussions.
As we now have a strategy in place resulting from this community engagement, I think this ISSUE is time expired. |
[WIS-130] Publish results study to determine feasibility for WMO to host & maintain standard software libraries to encode / decode / transform binary data representations. (EC 3.5.1.12) Created: 14/Apr/10 Updated: 25/Sep/10 Resolved: 02/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Incomplete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-c |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 6:08 AM ] |
| This issue cannot be resolved until we have defined the conceptual data model and understand what tools are required to encode / decode / translate etc. |
[WIS-128] Send to ET-OI updated contributions to Manual on GTS updated to include interaction with WIS centres (EC 3.5.2.1, 3.5.2.2) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-e |
[WIS-127] Publish recommended best practice for metadata usage and adoption plan (EC 3.5.1.12) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | In Progress |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-e |
| Comments |
| Comment by Jeremy Tandy [ 02/Sep/10 5:28 AM ] |
|
Identifying best practice for metadata usage was the main topic discussed at meeting IPET-MDI 1 in Geneva (April 2010). See the meeting report for more information (http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm)
This is a 'place-holder' ISSUE, to which a number of SUB-ISSUES have been associated |
[WIS-126] Proposals to make WMO Core and Marine Metadata Profiles interoperable or better (EC 3.5.1.12) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-e |
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 11:08 AM ] |
| It is anticipated that improved interoperability with Marine metadata profiles will be delivered by close liason with JCOMM / IOC - namely with assistance of Greg Reed. The first step is to obtain thematic vocabularies for oceanography (issue WIS-202 refers). |
[WIS-125] Plan published for interoperability of BUFR, GRIB, CREX, NetCDF, HDF and XML Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-e |
[WIS-124] Publish Metadata governance procedures (including the mechanisms for all Programmes to propose changes and how these proposals will be managed) (EC 3.5.1.12) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-d |
[WIS-123] Ensure CCl and other Programmes are aware of consultation so they can include data rescue and IPY aspects (EC 3.5.3.4) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-d |
[WIS-122] Consultation on format for delivery of aviation information to end users Created: 14/Apr/10 Updated: 25/Sep/10 Resolved: 02/Sep/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Complete | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-d |
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 11:11 AM ] |
| Work in progress via OGC Met Ocean domain working group. See MO.dwg twiki for more information: http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/WebHome |
| Comment by Jeremy Tandy [ 02/Sep/10 6:17 AM ] |
| Consultation is on-going with representatives from NextGen (FAA) and SESAR (EuroControl). This ISSUE provides no further insight on what that consultation needs to achieve - so I am marking it as resolved. |
[WIS-121] Publish community engagement plan to identify existing data & metadata standards adoption profile / issues plus training requirements Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Reopened |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: MDI-0c |
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 7:57 AM ] |
|
Development of DATA standards is a collaborative exercise that exists under with the OGC Met-Ocean domain working group. Refer to their wiki for more information: http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/
The 'conceptual modelling' sub-group is co-chaired by Andrew Woolf (STFC) and Jeremy Tandy (Met Office). Part of the MO.dwg activity has been out-reach to communities of interest. This has enabled the identification of existing DATA standards (http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/MetWeatherExchangeModels). At present time, the strategy employed aligns with that recommended by INSPIRE (http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/DataSpecifications/D2.6_v3.0.pdf). ISO19156 'Observations and Measurements' (O&M) (http://www.opengeospatial.org/standards/om) has been identified as the 'target' conceptual model. The use-cases (defined here: http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/MetOceanUseCases) are being used to define the data objects used within this domain of interest. These data objects are then mapped onto the O&M conceptual model to assess whether it is fit for purpose. A PROFILE of O&M will be created for meteorology and climate; ideally this will be a 'type-1' profile (restriction only). If necessary, O&M will be extended to provide a richer conceptual model for this domain. Finally, the working group will examine how to encode the ADDITIONAL metadata afforded by O&M into the 'standard' encodings in use today. Guidance for metadata authors will be provided in response to issue WIS-201(https://vets.development.ucar.edu/jira/browse/WIS-201) Guidance on the transition from Vol C1 to WIS DAR catalogue will be provided in response to issue WIS-195 (https://vets.development.ucar.edu/jira/browse/WIS-195) - this transition plan will include training requirements for WIS participants. I note that the WIS Programme Office plan to fund a technical author (?) to develop the Manual on WIS, which I expect to draw together disparate sources of guidance. |
[WIS-120] Specify use cases that will be used to drive further development of data and metadata standards, including as minimum: GISC, GEOSS, INSPIRE and Emergency Management Created: 14/Apr/10 Updated: 25/Sep/10 Resolved: 31/Aug/10 |
|
| Status: | Resolved |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: DRC-c |
| Comments |
| Comment by Jeremy Tandy [ 31/Aug/10 7:31 AM ] |
|
This issue refers only to DATA standards.
Definition of the use-cases used to drive the development of data standards can be found at the OGC twiki for Met-Ocean domain working group (http://external.opengeospatial.org/twiki_public/bin/view/MetOceanDWG/MetOceanUseCases). These use cases have been developed with input from open & inclusive discussion stimulated by OGC. The main stakeholder groups include: WMO, Aviation and INSPIRE. |
[WIS-119] Confirmed with IOS that the discovery metadata required for lightning data is available. (EC 3.1.10) Created: 14/Apr/10 Updated: 25/Sep/10 |
|
| Status: | Open |
| Project: | WMO Information System |
| Component/s: | IPET-MDI |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Timo Proescholdt | Assignee: | Jeremy Tandy |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Working Group: IPET-MDI
Terms of Reference: DRC-c |
[WIS-210]