Content Management using the ISO/TC 211 standards ESDI Workshop on CSL and Tools nicolas.lesage@ign.fr (on behalf of IGN

1. Content Management using the ISO/TC 211 standardsESDI Workshop on CSL and Toolsnicolas.lesage@ign.fr(on behalf of IGN France, DGIWGand Eurogeographics) • Throughexperiences • Translation of GI Data • 19139 PT • MGCP Modèle TN-02.019 –1.0 Standardization unit DT.TN/05.097

2. Experience in translation and interchange of GI dataContext • ContentManagement • Translation of GI Data • 19139 PT • MGCP • French NMA (IGN), early to mid 90’s • The base principles are still applicable!!! • Member of the IGN exchange format team • Specification of (generic) translator between: • GIS (Arc Info, Tigris, Geoconcept…) or external exchange format (EDIGéO, DXF, …) • the IGN internal exchange format for vector data • Configuration of the translators for different data product Standardization unit DT.TN/05.097

3. Experience in translation and interchange of GI dataGeneric translators • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Translation rules based at a high conceptual level • General Feature Model for the semantic aspects • Metadata/Quality schema • Geometry/Topology schema • Use of configuration files for a given data product Standardization unit DT.TN/05.097

4. Experience in translation and interchange of GI dataNeed for transformation tools • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Generic transformation tools to manage the major conceptual mismatches • « application schema » transformation • Geometry/Topology transformation • CRS transformation • Sometimes, need for pre/post processing using the GIS abilities Standardization unit DT.TN/05.097

5. Experience in translation and interchange of GI data“exchange convention” • ContentManagement • Translation of GI Data • 19139 PT • MGCP • An agreement between a data provider and a data customer on a full interchange process • pre processing • translator configuration • transformation tools and their configuration • controls • post processing • A principle to keep in mind for any kind of interchange • What about a “delivery specification” standard? Standardization unit DT.TN/05.097

6. Experience in translation and interchange of GI dataThe technological gaps - GFM • ContentManagement • Translation of GI Data • 19139 PT • MGCP • No more geometry-oriented feature types • multiple geometry • separation of geometry and topology • different management of topology • no or less layering constraints • Object-oriented approach • Inheritance/abstraction • Operation!? • Formalisation of constraints Standardization unit DT.TN/05.097

7. Experience in translation and interchange of GI dataTechnological opportunities • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Well formalised and standardised GI concepts • modular abstract schemas (ISO 19115, ISO 19107, ISO 19108, …) • Should ease the establishment of transformation rules (Divide to conquer) • a standardised GFM • a reference for establishing transformation rules • disconnection of the concepts and their encoding • Distributed environment • Emergence of Web Services • CRS transformation, data access and transformation • A Web service is a standard interface for transformation tools Standardization unit DT.TN/05.097

8. Experience in translation and interchange of GI dataSome technological opportunities, but … • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Technological gaps to be managed • the GI system / software are not yet fully ready to support the ISO/TC 211 standards (GFM and abstract schemas) • Need to move forward in a controlled manner • simple features, enhanced simple features, … • implies a high level (OGC, ISO/TC 211, …) scheduling • No miracle • The processing requirements are still the same • Web Services will not necessarily met all those processing requirements • but, we can take advantage of our experience • “High level transformation rules” still needed (at least as long as systems/softwares don’t handle the GFM) • Dangerous to rely the GI Technology on the XML Technique • Need for formalising some of the OGC Specification in a CSL (UML?) • e.g., FE, WFS-X • A consistent use of the ISO standards is a challenge Standardization unit DT.TN/05.097

9. ISO 19139 ExperienceAbout defining encoding rules • ContentManagement • Translation of GI Data • 19139 PT • MGCP • It’s a hard task because • it involves mapping at a high conceptual level • and so, a good understanding of CSL and XML concepts • it requires to consider the actual or short/mid term usage of the encoding (and CSL) • It’s consequently an area for standardisation • with possible difficulties to come up to an agreement • with a need for clear requirements • It’s possible • but, it requires the involvement of relevant experts • the higher is the representation of the domain actors, the better is the result Standardization unit DT.TN/05.097

10. ISO 19139 ExperienceEncoding rules and transformation tools • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Transformation tools are needed, but are accessory • Two pieces of software have been developed by ISO 19139 PT members and have produces compatible result • A clear understanding of the encoding rules is the challenge • The issue is a general standardisation issue • Generation of XML Schemas is not achieved so often • Encoding rules make the transformation tool easier to develop • The encoding rules and transformation tools are not dependant on the CSL Tool • the effective transformation can be processed outside of CSL Tool, using or not a “standard CSL exchange format” • Standardisation of XMI is a challenge in term of CSL Tool use, but is not a specific issue for transformation tools Standardization unit DT.TN/05.097

11. The MGCP ExperienceContext • ContentManagement • Translation of GI Data • 19139 PT • MGCP • A Military Co-production initiative for 1:50K equivalent scale vector database • Product content varies depending on the sources available • will to keep track of the content variation • General and common content requirements, • but, the content reqs may be specialised • Use of the DFDD data dictionary (FACC) as the reference for GI concept definitions • Data interchange by transfer: • ESRI SHAPE format used for the data, but GML may be used later Standardization unit DT.TN/05.097

12. The MGCP ExperienceApplication schema vs Feature catalogue (1/2) • ContentManagement • Translation of GI Data • 19139 PT • MGCP What are the respective roles of application schemaand feature catalogue? Standardization unit DT.TN/05.097

13. The MGCP ExperienceApplication schema vs Feature catalogue (2/2) • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Application schema • Expressed using a CSL • Managed using a CSL Tool => Can’t be easily queried • Provide a useful visual understanding of a product content • Depending on CSL, allow for user community extensions (tagged information) • Feature Catalogue • Abstract specification which can be implemented as a database or register and as an interchange format (e.g. XML) • Can be more easily queried, but is is not designed for display • Is considered limited to the semantic aspect of a product content (no geometry/topology, no metadata/quality, …) • Provide a mean to rely the Feature types, Attributes Types, Association types and roles to external concepts • e.g. a normal dictionary, a 19126 data dictionary or a more “abstract” FC Standardization unit DT.TN/05.097

14. The MGCP ExperienceMGCP assumption • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Limiting the use of ISO 19110 (FC) to the semantic aspects is like using UML for abstract classes!? • ISO 19110 abstract schemas can support any types of attributes, including metadata, geometry, topology, … • It is possible to establish abstract FC dealing only with the semantic aspect of data products • But, it is also possible to establish concrete FC handling the full data product content and referencing an abstract FC • FC can be used for managing product contents • An application schema can be derived from a concrete FC • the product content can be accessed, queried, modified and interchanged more conveniently Standardization unit DT.TN/05.097

15. 19110 Amndt 19110 MGCP Profile 19139 Encoding rules 19110 XSD 19139 XSD MGCP XSD DFDD Is compliant with References General FC RawXMLExport FC MGCP XML Excel Macro XSL Transf. References XSL view Raw XML Export Profiled FC MGCP XML Specialised FC The MGCP ExperienceImplementation of ISO 19110 ISO 19110 • ContentManagement • Translation of GI Data • 19139 PT • MGCP Standardization unit DT.TN/05.097

16. The MGCP ExperienceFrom the MGCP FC to an AS • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Generation of a UML AS from the XML FC • 1 hour to have an XSL generating a cat file • A very poor AS generated as expected • no Association, no inheritance, … • the initial FC was non as poor • Ad hoc meeting for establishing rules for enhancing the application schema • use of DFDD codes as stereotypes • rules for classification (inheritance) • rules for expressing topological constraints • Optimisation of the AS • FC can be viewed as expressing a profile of the new AS • An abstract FC could be generated from the new AS Standardization unit DT.TN/05.097

17. The MGCP ExperienceIssues • ContentManagement • Translation of GI Data • 19139 PT • MGCP • Generation of control tools from CSL constraints • Dream or reality? • Literal conformance requirements to be documented • Compatibility of AS related to a single abstract FC Standardization unit DT.TN/05.097

18. When? -19126 NWIP Later - ISO/DIS 19131 - ISO 19110 - but, experimental use Tomorrow Feature Catalogue Today - This workshop Application Schema - ISO/DIS 19136 - GML 3.0 - GML 2.x Yesterday GML Schema Standardisation Time axis The MGCP ExperienceThe GI standardisation paradox Data Dictionary • ContentManagement • Translation of GI Data • 19139 PT • MGCP Data product specification Standardization unit DT.TN/05.097

19. Conclusion • ContentManagement • Translation of GI Data • 19139 PT • MGCP • No need for Geo-specific UML softwares • but, use/enhance ISO/TC 211 profile of UML • Let’s use the available standard to manage the data product content independently of any CSL • ISO 19110, ISO 19131 • Contribute to ISO 19126 • Need for new standards • delivery specification • AS/FC transformation Standardization unit DT.TN/05.097