1 / 22

ISO/TC 211 WG4 Geospatial services

ISO/TC 211 WG4 Geospatial services. WG4-report to the ISO/TC 211 in Beijing Morten Borrebæk - Convenor WG4. Work items: Positioning services Portrayal of geographic information Encoding Services. ISO/TC 211 WG4 Portrayal. CD-date according to work-program 98-03.

ros
Télécharger la présentation

ISO/TC 211 WG4 Geospatial services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISO/TC 211 WG4Geospatial services WG4-report to the ISO/TC 211 in Beijing Morten Borrebæk - Convenor WG4 Work items: Positioning services Portrayal of geographic information Encoding Services

  2. ISO/TC 211 WG4Portrayal CD-date according to work-program 98-03 WD Date of deliverable WG4 doc-nr 0.1 1996-03-29 N029 1.0 1996-09-30 N038 1.1 1997-01-08 N052 1.2 1997-06-30 N073 2.0 1998-02-26 N082 CD 1998-05-29 N091

  3. ISO/TC 211 WG4editing committee meeting Portrayal • Based on documentsN 533, N 567 and N 571 • A total of 241 • plus annexesfrom France,Switzerlandand Norway

  4. ISO/TC 211 WG4editing committee meeting Portrayal • Type of comment • Duplicates • from 241to 112

  5. ISO/TC 211 WG4 Unresolved comments for editing management committee. • Metadata as placeholder for portrayal rules. • Character set (should be the same for the whole family of standards) • Diagram technique. UML is not suitable for all kind of figures, and the diagram techniques might be harmonized. • Functional languages. There is a need for standardizing a functional language (or to more precise an action language) for several standards, and avoid a mixed set of Gopher, SQL, ++,. OCL is not the correct choice for actions, but an extension of UML is under construction (UML-action language). • Terminology. All comments on terms not specific to Portrayal will be handled to the terminology team.

  6. ISO/TC 211 WG4editing committee Beijing 1998-09 Input from Switzerland and Canada on Annexes 1998-11-01 New version distributed to EC-members for comment 1998-11-08 Comments from members of EC 1998-11-20 Submitt revised CD to ISO/TC 211 secretariat Secretariat preparation 1 week CD - period 3 months for DIS-voting Preparation by secretariat 1 week 2’nd editing committee meeting on Portrayal in Wienna 1999-03 ? Result from unresolved issues reported to editing management committee

  7. WI19 Services CD-date according to work-program 98-10 WD Date of deliverable WG4 doc-nr 0.1 1996-05-20 N032 1.0 1996-10-09 N043 1.2 1998-02-25 N085 2.0 1998-09-17 N100

  8. WI19 Services Quality sub schema General Feature Model Rules for Application Schema Meta data Spatial sub schema Coord Ref. Sys 4) Portability/Interoperability interface possible 1. Conformance Abstract Service Spec (UML w/precision) (Common Imp.spec) Direct C++/Java Portability/Interop Interface Feature rel.ship OGC Spatial sub schema 2- Conformance Imp. Spec ODMG/ODL 3. Reverse mapping for Portability and Interoperability Imp. Spec COM/MIDL Imp. Spec CORBA/IIDL Imp. Spec ODBC/SQL SQL3/MM Imp. Spec SDAI/EXPRESS

  9. ISO/TC 211 and OpenGIS Reference Models Harmonized

  10. Harmonizing ISO/TC 211 and OpenGIS Service Architecture and identified services The Geospatial Domain Services describes the various services identified in the OpenGIS service architecture These services have been mapped into the ISO/TC211 service categories.

  11. WI19 Services • Identification of services: Completed (30 services) • Normative: How to write abstract service specifications and conforming implementation specifications (one-way and two-way) - by 98-11 • Apply service specification approach to Positioning service (from part X) and Feature access, query and update (from OGC + SQL-3/MM) - by 99-03 • Propose new work items: Catalogue Service, Coordinate Transformation Service, Imagery/Gridded Data/Coverage access, query and update • CD by 1999-03 (to incorporate work on Feature access, query and update)

  12. WI16 Positioning CD-date according to work-program 98-09 WD Date of deliverable WG4 doc-nr 0.1 1997-06-12 N071 1.0 1997-09-02 N075 1.1 1997-09-12 N079 1.6 1998-09-10 N097

  13. WI16 Positioning Joint sessions during the Beijing - meeting WI5 Conformance and testing. The work on conformance clause in WI16 aligns well with the principles in WI5, but needs further improvement. WI11 Spatial referencing by coordinates. Discussions on terminology and concepts like stability. The concepts on coordinate reference system in WI11 is changed, and WI16 must be restructured according to this. REM Later discussions with PT11 has clarified that this was resolved during the Victoria meeting. WI13 Quality principles. Should WI13 be the placeholder of a quality element on positional stability, or as an annex in WI16.

  14. WI16 Positioning Unresolved issues UML The UML description is started, but needs to be completed. Conformance clause The conformance clause needs to be verified in accordance with WI5 Terminology There were several comments on positioning services terms discussed in Beijing, half of them are still unresolved. Coordinate reference system The draft needs to be restructured according to the new structure in WI11 REM Later discussions with PT11 has clarified that there has been no restructuring since Victoria.

  15. WI16 Positioning Date for CD submission…. • One more meeting is needed to handle the unresolved issues. (Estimated to October) • UML modelling assistance is required. • The Services WD (WI19) will have a normative part on “How to write abstract service specifications and conforming implementation specifications (one-way and two-way)”. A proposal for this is estimated to be finalised by 98-11. To ensure that Positioning services is written according to this guidelines, a delay is required. • Proposal 1998-12.

  16. WI18 Encoding CD - date according to work-program 98-12 WD Date of deliverable WG4 doc-nr 0.1 1996-05-08 N030 1.0 1996-10-04 N040 2.0 1998-01-31 N078 3.0 1998-09-15 N099

  17. <<ApplicationSchema>> I WI18 Encoding Encoding Service DTD I UML model Declaration conversion rules Instance conversion rules data XML file

  18. WI18 Encoding Joint sessions during the Beijing - meeting • WG1 - CSL . • Editing committee on Portrayal. • WG2 on Spatial schema regarding modelling and encoding • WG3 assistance on modelling • WI5 conformance on encoding • WG5 joint meeting. Requirements from the joint sessions on Tuesday has been discussed with WG’s.

  19. WI18 Encoding Character set • This standard adopts the following international character set standards: • ISO/IEC 8859-1 • ISO/IEC 10646-1, UCS-2, UTF-8, UTF-16 • ISO/IEC 10646-2, UCS-4 • These standards define an international recognised repertoire of characters and their encoding. • Additional requirements • Composite characters deprecated • Language tags

  20. WI18 Encoding XML in Japanese ISO/IEC JTC1/SC2

  21. WI18 Encoding Unresolved issues in addition to character sets: Several issues remains unresolved. The most important are: • XML - 3 alternatives must be reduced to 1. Will be discussed with XML-experts. • UML. Modelling requirements must be inserted in modelling guidelines and used in WD/CD’s to enable encoding • Conformance clause / falsification clause • Encoding services Proposed date of CD 1998-12.

  22. THANK YOU

More Related