290 likes | 699 Views
Drawing a line in the sand The role of ISO, CEN, OGC and legal processes in the building of SDIs Olaf Østensen Chair ISO/TC 211 Norwegian repr . to INSPIRE Committee Member of IOC TF Member of INSPIRE DT Network services Content
E N D
Drawing a line in the sandThe roleof ISO, CEN, OGC and legalprocesses in thebuildingofSDIs Olaf Østensen Chair ISO/TC 211 Norwegianrepr. to INSPIRE Committee Memberof IOC TF Memberof INSPIRE DT Network services
Content How can standards developing organisations serve European SDI needs – nationally and for Europe itself? Is there any natural distribution of roles – ISO, CEN and OGC? … some thoughts around theses subjects…
(28) In order to benefit from the state of the art and actual experience of information infrastructures, it is appropriate that the measures necessary for the implementation of this Directive should be supported by international standards and standards adopted by European standardisation bodies in accordance with the procedure laid down in Directive 98/34/EC of the European Parliament and of the Council of 22 June 1998 laying down a procedure for the provision of information in the field of technical standards and regulations (1). The role of Standards
(16) …Implementing rules should be based, where possible, on international standards and should not result in excessive costs for Member States. The role of Standards
Modernising ICT Standardisation in the EU Attributes of ICT standards associated with EU legislation and policies (1) Openness: The standardisation development process occurs within a non-profit making organisation on the basis of open decision making accessible to all interested parties. The open standardisation process is driven by the relevant stakeholder categories and reflects user requirements. (2) Consensus: The standardisation process is collaborative and consensus based. The process does not favour any particular stakeholder. (3) Balance: The standardisation process is accessible at any stage of development and decision making to relevant stakeholders. Participation of all interested categories of stakeholders is sought with a view to achieving balance. (4) Transparency: The standardisation process is accessible to all interested parties and all information concerning technical discussions and decision making is archived andidentified. Information on (new) standardisation activities is widely announced through suitable and accessible means. Consideration and response is given to comments by interested parties. … also relevant for INSPIRE technical guidelines?
MS apply Proto-types test Pilotsvalidate Public reviews Projectscontribute Experts are proposed CEN, ISO, OGC contribute Relevant international initiatives Commission Services co-ordinate The Process EC adopts INSPIRE Expert Groupadvises INSPIRECommitteevotes Review Formal Internet Consultation Draft Implementing Rules Implementing Rules Existing Reference Material Call for Interest Consolidation Team Drafting Teams LMOsre-view Spatial Data Interest Communities participate Association phase Drafting phase Review phase
Concernswereraisedearly… Issues were expected and tried to be addressed many years ago, cfr. Letter from February 2006 Later followed by a similar letter by CEN/TC 287 chair
CEN Start (incl. revision of existing IRs) INSPIRE informs CEN about draft IR May concern standard, TS, TR, workshop or agreement INSPIRE NIWP may concern standard or amendment to existing standard CEN as SDIC comments draft INSPIRE drafts IR ISO CEN/TC 287 ISO/TC 211; creates NWIP if required; common decision on lead ISO/TC 211 prepares NWIP INSPIRE submits IR to CEN/TC 287 ISO lead CEN lead parallel voting if work Item in CEN and ISO CEN/TC 287 WG drafts WD, CD for enquiry and preEN for formal vote ISO/TC 211 PT: WD, DIS, FDIS INSPIRE comments draft as liaison ISO criteria met CEN criteria met CEN publishes EN or EN-ISO (by successful parallel vote) ISO publishes IS [CEN criteria met] INSPIRE considers standard in future revisions of IR end
The components § Directive Implementingrules § ISO ISO ISO Technicalguidelines Otherdocuments
SDI requirements and standards Applications and Geoportals Access to data Service Bus Rights Management Layer Registry Service Discovery Service RMServices Transf. Service ViewService DownloadService InvokeSDService EN ISO 19128 EN ISO 19142 ISO 19143 Reg. data Service Metadata Data Set Metadata RM Data Spatial Data Set Spatial data See next slide! Metadata Thematic DS Framework for describing data EN ISO 19115 EN ISO 19119 Framework for harmonized DS
Data specifications in INSPIRE A long range of ISO 19100-series standards normative
CEN Start (incl. revision of existing IRs) INSPIRE informs CEN about draft IR May concern standard, TS, TR, workshop or agreement INSPIRE NIWP may concern standard or amendment to existing standard … failed so far ? … CEN as SDIC comments draft INSPIRE drafts IR ISO CEN/TC 287 ISO/TC 211; creates NWIP if required; common decision on lead ISO/TC 211 prepares NWIP INSPIRE submits IR to CEN/TC 287 ISO lead CEN lead parallel voting if work Item in CEN and ISO CEN/TC 287 WG drafts WD, CD for enquiry and preEN for formal vote ISO/TC 211 PT: WD, DIS, FDIS INSPIRE comments draft as liaison ISO criteria met CEN criteria met CEN publishes EN or EN-ISO (by successful parallel vote) ISO publishes IS [CEN criteria met] INSPIRE considers standard in future revisions of IR end
Manyissues to be resolved INSPIRE should be based on existing standards. No existing standard satisfies all the INSPIRE requirements. Implementing rules are not ensuring interoperability – they are at a too high level of abstraction Technical guidelines are not mandatory – can be ignored (?) Even the technical guidelines do not ensure interoperability
Technical guidelines INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119 Draft Technical Guidance Download Services Draft Technical Guidance for INSPIRE Coordinate Transformation Services INSPIRE View Service Technical Guidance Technical Guidance Discovery Services INSPIRE Data Specification on Protected Sites - Guidelines INSPIRE Data Specification on Transport Networks - Guidelines INSPIRE Data Specification on Cadastral Parcels - Guidelines INSPIRE Data Specification on Geographical Names - Guidelines INSPIRE Specification on Geographical Grid Systems - Guidelines INSPIRE Specification on Coordinate Reference Systems - Guidelines INSPIRE Data Specification on Administrative Units - Guidelines INSPIRE Data Specifications on Addresses - Guidelines INSPIRE Data Specification on Hydrography – Guidelines + Annex II and III to come ….
Example, Someissues in brief … • View services refer to ISO 19128 Web map server (= OGC WMS 1.3) • Issues, language parameter missing, SOAP binding missing, smaller other differences, (tiling not treated), etc. • Discovery services refer to OGC CSW 2.0.2 ISO AP 1.0.0 • Despite its name, not an ISO standard, language parameter missing, SOAP binding exists, but requirements not ideal, has been extended to cover INSPIRE metadata (but within capability of the specification)
Example, Someissues in brief … • Download services refer to ISO/DIS 19142 Web feature service (= OGC WFS 2.0?) and ISO/DIS 19143 Filter encoding (= OGC FE 2.0?) • These are still under development (FE soon publication, WFS at FDIS) • Issues, language parameter missing, SOAP binding compliant with the others?, etc. • Transformation services refer to OGC WPS • Not an ISO standard • The concrete services will have to be defined by INSPIRE • Other issues similar with the previous ones
A general problem OWS Common, which is a basis for all newer OGC services, has not been submitted to ISO
Standards bodiesfail to respond • Practical alignment of processes and rules • Who takes a lead or responsibility? • Who resource the tasks?
What to do In any case, a Standards Task Force should probably be set up by the CT to detail the issues and liaise with ISO/TC 211, OGC and CEN/TC 287 to define the best available approach and initiate the processes. Then, EC and MS should devote sufficient resources and egagement to enable the necessary processes!
Someprinciples • Standards should be developed at as general level as possible • E.g. general foundation standards should be global • Regional requirements that cannot be lifted to global, should be addressed at regional level • De jure standards bodies should liaise with consortia and other organisations to complement own processes • A standards body should ensure that user rquirements are met by appropriate standards – not necessarily develop everything themselves • E.g.ISO using the relationships with OGC, UN (FAO), IHO, DGIWG, ….
Strengths and weaknesses • ISO/TC 211 • CEN/TC 287 • OGC • INSPIRE legal and technical processes Do they meet the requirements of openness, consensus, balance, and transparency?
So, what now • INSPIRE has a liaison with ISO/TC 211 through JRC • ISO/TC 211 has a cooperativeagreementwith OGC, and a Joint Advisory Group to handle thecooperation • All have a closerelationshipwith CEN/TC 287 There is not a lackof arenas for cooperation and harmonisation
No conclusionshere Let us come back to these topics in the round table discussion at the end today!