MIWP-8 virtual meeting 2015-10-20

Time 15:00-16:30 CET

Connection details

Agenda

 

Remaining issues for MIWP-8 members

Tasks for finalizing  draft

Description of transition phase when implementation changes from TG 1.3 and 2.0

 

Remaining issues for MIWP-8 members

  1. Analyze/rewrite requirements based on suggestions (Marc, Peter, Ine)
    This document at 
    https://docs.google.com/spreadsheets/d/1gbYcYTwmYYLK-_7YTNd10_VnTAaJmdG9lUF6ZStZ1M4/edit?usp=sharing

     Is updated by Ine, Marc and Peter.
    Do we need more details and concensus for an editor to continue ?

     

  2. On newly added theme specific elements extract theme specific recommendations to separate doc                remark by Peter: this has already been done!
    We need to discuss the prio for this.
    In Malmö we decided to keep technical implementation details in document but to extract theme specific recommendations
    in a separete document. Suggestions also exists to lift this out of the TG which I disagree on.
    My believe is that all elements we suggest for editing must have a defined technical implementation.

  3. Write introducing section on use of Anchor / xlink:href and for what use each of them is useful (Angelo, Martin)

  4. Go through all sections where Anchor/xlink:href is recommended and make sure correct implementation is selected based on the needs (Marie, Michael Ö)
    To-Do

  5. Add an Annex with defined ”codelists” we define in registry. Also codelists used but that does not exist in IR. (Antonio)

  6. Clarification of needs for documentation of OSDS in December 2015 (Ine -> Michael L)
    Ine

  7. i Clarification on what other documents are affected by changes in the TG  (update ticket https://ies-svn.jrc.ec.europa.eu/issues/2408) (Michael L)
    This is not part of TG but I think important? Shuold we just leave this for discussion in MIG-t ?

  8. Update Draft 0.5 with all changes done and comments.

  9. Propose options to the MIWP-8 sub-group for re-structuring the document (e.g. in different parts, with an overview table showing requirements for all major ”resource-types” the TG covers), taking into account

  • that the document should be based on ISO (rather than INSPIRE) metadata elements

  • readability for implementers

  • maintainability of the TGs for future updates

 

Tasks for finalizing  draft

1. consolidate the requirements needed to reflect IR requirements, i.e. add/remove requirements (based on the IR-to-TG analysis available in https://docs.google.com/spreadsheets/d/1gbYcYTwmYYLK-_7YTNd10_VnTAaJmdG9lUF6ZStZ1M4/edit?usp=sharing )Responsible: Contracted Editor

2. Edit the sections where technical changes have been agreed by the MIWP-8 sub-group (see attached draft with tracked changes - section 2.13 will probably be moved out of the document)
Responsible: Contracted Editor

 
3. Implement other cross-cutting changes throughout the document that have been agreed by the MIWP-8 sub-group, in particular
  • replace "services" with "Invocable spatial data services" or "Network services"

  • edit an introductory section on use of Anchor / xlink:href and for what use each of them is useful (based on a draft from the MIWP-8 group)

  • Review all sections where Anchor/xlink:href is recommended and make sure correct implementation is selected based on the needs

Responsible: Contracted Editor

 
 

4. Draft a section with detailed IR-to-TG mapping (to be included as an annex) 

Responsible: Contracted Editor

5. Propose options to the MIWP-8 sub-group for re-structuring the document (e.g. in different parts, with an overview table showing requirements for all major ”resource-types” the TG covers), taking into account
  • that the document should be based on ISO (rather than INSPIRE) metadata elements

  • readability for implementers

  • maintainability of the TGs for future updates

Responsible: MIWP-8


6. Restructure the document according to the option preferred by the MIWP-8 group

Responsible: Contracted Editor 

 
 

7. Re-word TG requirements (if necessary) to remove INSPIRE jargon. 

Responsible: MIWP-8 or JRC
 
8. Update the tests in the ATS reflecting the new list of requirements 

Responsible : MIWP-5 or JRC

 

Description of transition phase when implementation changes from TG 1.3 and 2.0