the model-driven approach to geographic information system … · 2013-01-30 · documentation...
TRANSCRIPT
1Arne J. Berre 1SINTEF
"The Model-driven Approach to Geographic Information System Standardisation
- Lessons Learned - "
"The Model-driven Approach to Geographic Information System Standardisation
- Lessons Learned - "
• Problem: Interoperability of GIS – through standards• Requirement: For data and services• ISO solution: ISO/TC211 modeling approach – ISO 191XX series
– ISO 19101, 19103, 19119, 19109, 19118• OGC solution – Open Geodata Consortium – standard approach
– GML 1.0, 2.0, 3.0, Abstract and Implementation specifications• Lessons learned: The conflict - Specification vs Implementation + tools • What should be done next: PIM-PSM mapping standards/tools, ’HUTN XMI’
Dr. Arne J. BerreSINTEF, Oslo, NorwayDistributed Information SystemsPhone: (+47) 22 06 74 52E.mail:[email protected]
www. isotc211.orgwww. isotc211.org www. www. opengisopengis.org.org
2Arne J. Berre 2SINTEF
AbstractAbstract
Since 1995 the two main standardisation organisations for Geographic Information, ISO/TC211 and OGC (Open GeodataConsortium) have worked on the specification of standards for geographic data and services. UML has been selected as the normative specification language within ISO/TC211 since 1998, while OGC is currently using UML in a non-normative way. ISO/TC211 focuses on platform independent models expressed in UML, and on a model-driven approach for mapping these to XML, while OGC is addressing implementation specifications for multiple technologies. Currently it has not been possible to fullyrealise the model-driven approach to standard specifications across ISO/TC211 and OGC. An analysis of the current situation, and requirements for what needs to be done to achieve this, willbe presented.
3Arne J. Berre 3SINTEF
Problem Goal: Transparent Access to Heterogeneous Geodata and Geoprocessing Services
Non-traditional
DBMS
File FormatFile FormatFile Format
File Format
Real-TimeData Feed
File FormatTraditional
DBMS
File Format File Format
NETWORKS AND CLIENT/SERVER TECHNOLOGY
File FormatFileFormat
File Format
File Format
4Arne J. Berre 4SINTEF
ISO/TC211 & OGC “Roadmap”ISO/TC211 & OGC “Roadmap”
19921993199419951996
1997
1998
1999
2000
2001
2002CEN/TC287
(Europe)ISO/TC211established ISO 19103
ISO 19118
ISO 19109 ISO 19119 ISO 19135ISO 191XXUMLAdopted
SimpleFeaturesAdopted
GridCoveragesAdopted
CatalogServicesAdopted
Web MapServer
Adopted
CoordinateTransformation
Adopted
GML Recommendation
Paper Adopted
GFSGazetteerWFS, WCSGeoLink, LOFGeoparse, GeocodeGML XML SchemaThesaurusType Dictionary
WMS-2Legend,Style Sheet &S.S.CatalogSLD, Symbol LibraryGML Extensions:IML, Coverage,
Basic Service ModelFilter
ISO/TC211 Stds
OGC Specifications
5Arne J. Berre 5SINTEF
!! ISO 19101 ISO 19101 -- Reference modelReference model!! ISO 19102 ISO 19102 -- OverviewOverview!! ISO 19103 ISO 19103 -- Conceptual schema languageConceptual schema language!! ISO 19104 ISO 19104 -- TerminologyTerminology!! ISO 19105 ISO 19105 -- Conformance and testingConformance and testing!! ISO 19106 ISO 19106 -- ProfilesProfiles!! ISO 19107 ISO 19107 -- Spatial schemaSpatial schema!! ISO 19108 ISO 19108 -- Temporal schemaTemporal schema!! ISO 19109 ISO 19109 -- Rules for application schemaRules for application schema!! ISO 19110 ISO 19110 -- Feature cataloguing methodologyFeature cataloguing methodology!! ISO 19111 ISO 19111 -- Spatial referencing by coordinatesSpatial referencing by coordinates!! ISO 19112 ISO 19112 -- Spatial referencing by geographic Spatial referencing by geographic
identifiersidentifiers!! ISO 19113 ISO 19113 -- Quality principlesQuality principles!! ISO 19114 ISO 19114 -- Quality evaluation proceduresQuality evaluation procedures!! ISO 19115 ISO 19115 -- MetadataMetadata!! ISO 19116 ISO 19116 -- Positioning servicesPositioning services!! ISO 19117 ISO 19117 -- PortrayalPortrayal
!! ISO 19118 ISO 19118 -- EncodingEncoding!! ISO 19119 ISO 19119 -- ServicesServices!! ISO/TR 19120 ISO/TR 19120 -- Functional standardsFunctional standards + new rev+ new rev!! ISO/TR 19121 Imagery and ISO/TR 19121 Imagery and griddedgridded datadata!! ISO/TR 19122 ISO/TR 19122 -- Qualifications and certification Qualifications and certification
of personnelof personnel!! ISO 19123 ISO 19123 -- Schema for coverage geometry and Schema for coverage geometry and
functionsfunctions!! ISO 19124 ISO 19124 -- Imagery and Imagery and griddedgridded data data
componentscomponents!! ISO 19125 ISO 19125 -- Simple feature access Simple feature access –– Part 1Part 1--33!! ISO 19126 ISO 19126 -- Profile Profile -- FACC Data DictionaryFACC Data Dictionary!! ISO 19127 ISO 19127 -- Geodetic codes and parametersGeodetic codes and parameters!! ISO 19128 ISO 19128 -- Web Map Server InterfaceWeb Map Server Interface!! ISO 19129 ISO 19129 -- Imagery,Imagery, griddedgridded and coverage dataand coverage data
frameworkframework!! ISO 19130 ISO 19130 -- Sensor and data model for imagerySensor and data model for imagery
andand griddedgridded datadata!! ISO 19131 ISO 19131 -- Data product specificationData product specification!! ISO 19132 ISO 19132 -- Location based services possibleLocation based services possible
standardsstandards!! ISO 19133 ISO 19133 -- Location based services trackingLocation based services tracking
and navigationand navigation!! ISO 19134 ISO 19134 -- MultimodalMultimodal location based serviceslocation based services
for routing and navigationfor routing and navigation!! ISO 19135 ISO 19135 -- Procedures for registration ofProcedures for registration of
geographic information itemsgeographic information items
ISO/TC211Overview
6Arne J. Berre 6SINTEF
ISO 19103 – Conceptual Schema Language (UML)ISO 19103 – Conceptual Schema Language (UML)
• Basic data types• Stereotypes• Naming• Documentation of models• Implementation neutral vs implementation specific
models• Information modeling guidelines
7Arne J. Berre 7SINTEF
General Feature meta modelGeneral Feature meta model
8Arne J. Berre 8SINTEF
ISO 19103 Base TypesISO 19103 Base Types
Date and Time<<Leaf>>
(from Primit ive)+ Date
+ DatePrecision+ DateTime
Records <<Leaf>>
(from Implementation)+ Any
+ Record+ RecordContainer+ RecordSchema
+ RecordType
Numerics<<Leaf>>
(from Primitive)+ Decimal+ Integer+ Number
+ Real+ UnlimitedInteger
+ Vector
Enumerations<<Leaf>>
(from Primitive)+ Sign
Collections<<Leaf>>
(from Implementation)+ Bag
+ CircularSequence+ CodeList
+ Dictionary+ KeyValuePair
+ Reference+ Sequence
+ Set+ TransfiniteSet
Text<<Leaf>>
(from Primitive)+ Character
+ CharacterSetCode+ CharacterString
+ Sequence<Character>
Units of Measure<<Leaf>>
(from Derived)+ Angle+ Area
+ Distance+ ISOStandardUnits
+ Length+ Measure
+ Scale+ Time
+ UnitOfMeasure+ UomAngle+ UomArea
+ UomLength+ UomScale+ UomTime
+ UomVelocity+ UomVolume
+ Velocity+ Volume
Derived Implementation Primitive
9Arne J. Berre 9SINTEF
ISO PackagesISO PackagesISO 19112 Location
by Identifier
ISO 19107 Spatial Schema
ISO 19108 Temporal
ISO 19109 Rules for App Schema
ISO 19103 Conceptual Schema Language
ISO 19116 Positioning Services
ISO 00639 Human Language
ISO 19123 Coverages
ISO 19115 Metadata
PBLSchema<<Leaf>>
ISO 19117 Portrayal
ISO 19110 Feature Cataloging
ISO 19111 Spatial Ref By Coordinates
ISO 19118 Encoding
Norwegian Land Information
10Arne J. Berre 10SINTEF
UML as a basis for multiple representations
Parts of ISO 191XX
Application Schema
Data Interchange
Service Implementations
EXPR
ESS
UML - Graphical and lexical (Normative)
EXPR
ESS-
base
d
MID
L/C
OM
EXPR
ESS/
SDA
I
IIDL/
CO
RBA
SQL/
SQL/
MM
OD
L/O
DM
G
….UM
L
INTE
RLI
S
Gen
eric
….
XML
...
E U I I I S E O
Usage
(UML mappings can be semi-automatic)
11Arne J. Berre 11SINTEF
ISO/TC211-19119 and OpenGIS – ”vision”ISO/TC211-19119 and OpenGIS – ”vision”
Imp. SpecCOM/MIDL
Imp. SpecCORBA/IIDL
Imp. SpecODBC/SQLSQL3/MM
Imp. SpecSDAI/EXPRESS
Imp. SpecODMG/ODL
Abstract Service Spec(UML w/precision)
(Common Imp.spec)
Direct C++/JavaPortability/Interop Interface
Spatialsub schema
OGC
ISO
Metadata
CoordRef. Sys
Qualitysub schema
Spatialsub schema
Featurerel.ship
2- Conformance
4) Portability/Interoperability interface possible
3. Reverse mapping for Portability and Interoperability
1. Conformance
GeneralFeatureModel
Rules forApplication
Schema
12Arne J. Berre 12SINTEF
The OpenGIS Abstract Specificationinformal text and diagrams (Syntropy/UML)
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Feat
ure
Geo
met
rySp
atia
l Ref
. Sys
.Lo
catio
nal G
eom
.St
ored
Fcn
s & In
t’p.
Feat
ure
& C
olle
ct’n
s
Cov
erag
eTy
pe
Earth
Imag
ery
Rel
atio
ns b
tw F
eaQ
ualit
yFe
atur
e C
olle
ctio
nsM
etad
ata
Serv
ice
Arc
hite
ctur
eC
atal
og S
ervi
ces
Sem
antic
s & In
fo.C
mty
s.5a aFe
atur
e &
Col
lect
’ns
5 bFe
atur
e &
Col
lect
’ns
5cFe
atur
e &
Col
lect
’ns
0O
verv
iew
15Im
age
Expl
oita
tion
Svcs
16Im
age
Coo
rd x
-for
m17
Loca
tion
Serv
ices
13Arne J. Berre 13SINTEF
Achievements: Implementation SpecificationsAchievements: Implementation Specifications
1. OpenGIS® Simple Feature Access Interfaces1. SQL2. COM/OLE3. CORBA
2. OpenGIS® Catalog Service Interfaces3. OpenGIS® Coordinate Transformation Services4. OpenGIS® Grid Coverage Service Interfaces5. OpenGIS® Web Map Server Interfaces 6. OpenGIS® Geography Markup Language (GML)
14Arne J. Berre 14SINTEF
Implementation Specifications Expected SoonImplementation Specifications Expected Soon
7. Location Client8. Data/Service Registry9. Gazetteer Server10. Yellow Page Server11. Web Feature Server12. Web Coverage Server13. Data/Service Registries/Repositories14. Gateway Services 15. Route Servers16. Geocoder17. Geoparser 18. Style Layer Descriptor/Legends19. Search and Mining
15Arne J. Berre 15SINTEF
OGC TrendsOGC Trends
OLD
• GIS . . . . . . . . . . . . .• Government Led . . . . . . . .• Stand-Alone Spatial Services . . .
• Focus on Portrayal & Analysis . . .• De Jure Standards . . . . . . .• Abstract Specifications . . . . . .• Custom/ Proprietary Identifiers . . .• Expert Driven . . . . . . . . .• Isolated GIS Services . . . . . .
NEW
• Location-Based Services• Industry Led• Spatial Services Integrated into
Business Objects• Focus on Position & Navigation• Industry Consensus Standards• Implementation Details• XML and GML• Market Driven• In Command and Control Loop
16Arne J. Berre 16SINTEF
Example UML modelExample UML model
Roadclassification : CharacterStringnumber : CharacterStringlinearGeometry : GM_Curve
RivercenterLineOf : GM_Curve Mountain
elevation : Integer
CityMemberCityModel
dateCreated : Date0..*
+cityMember
0..*
17Arne J. Berre 17SINTEF
simpleXMI - reducing the complexity of XMIsimpleXMI - reducing the complexity of XMI
<class name="Road" superClass="CityFeature" abstract="false"><attribute name="classification" type="CharacterString"/><attribute name="number" type="CharacterString"/><attribute name="linearGeometry" type="GM_Curve"/>
</class><class name="River" superClass="CityFeature" abstract="false">
<attribute name="centerLineOf" type="GM_Curve"/></class><class name="CityModel" abstract="false">
<attribute name="dateCreated" type="Date"/><relationship name="cityMember" otherClass="CityFeature"
cardinality="0..*" collectionType="set"aggregationType="composite"/>
</class>
18Arne J. Berre 18SINTEF
ISO 19118 encoding –based on the simple XMI approach
ISO 19118 encoding –based on the simple XMI approach
<complexType name="Road"><sequence>
<element name="classification"type="CharacterString"/>
<element name="number" type="CharacterString"/><element name="linearGeometry"
type="GM_Curve"/></sequence><attributeGroup ref="IM_ObjectIdentification"/>
</complexType>
-not accepted by the OGC ”GML” community – A new ISO/TC211 workitem proposal has been accepted to create a new harmonized version of-GML and ISO 19118 (could be based on XMI 2.x ?)
19Arne J. Berre 19SINTEF
OGC GML2.0 schema exampleOGC GML2.0 schema example<complexType name="RiverType">
<complexContent><extension base="gml:AbstractFeatureType">
<sequence><element ref="gml:centerLineOf"/>
</sequence></extension>
</complexContent></complexType><complexType name="RoadType">
<complexContent><extension base="gml:AbstractFeatureType">
<sequence><element name="linearGeometry" type="gml:LineStringPropertyType"/><element name="classification" type="string"/><element name="number" type="string"/>
</sequence></extension>
</complexContent> </complexType>
20Arne J. Berre 20SINTEF
OpenGIS Web ServicesOpenGIS Web Services
21Arne J. Berre 21SINTEF
OGC Web ServicesOGC Web Services
Currently being done as XML request and response documents –specified by DTD and/or XML Schema. No platform independent UML models.
This is doable – but currently not viewed as necessary or initially feasible or useful.
Work to specify platform indepedent UML models is viewed asdocumentation ”clean-up” work – to be done by an ”idealistic” Documentation team – as the implementation specification group do nothave the tools and expertise to do this. I.e. To be done in the process ofsubmitting the models to the ISO191XX standardisation process.
22Arne J. Berre 22SINTEF
Experiences from use of UML for ISO/TC211 and OpenGIS standardsExperiences from use of UML for
ISO/TC211 and OpenGIS standards•Example of UML profile to use UML for normative standard specifications, including UML->XML mapping
• Introduction of basic types for UML implementation neutral models
•Specifying mandatory, optional – using multiplicity 0..*, Question on how to express optionality of associations and attributes (supporting NULL and EMPTY)
• Stereotypes for CodeList, Union and Leaf (Package)• ISO terminology comments on UML term definitions
•Question on expressing extensible enumerations
23Arne J. Berre 23SINTEF
Lessons learned, ISO/TC211, OGCLessons learned, ISO/TC211, OGC
-Need to have rules for well-defined and precise UML models (ISO 19103 –Conceptual Schema Language)
-Need to have automatic encoding of models into XML and other representations (i.e binary, proprietary) (ISO 19118 - Encoding), OGC GML
- Need to have an approach for service modeling for platform independent and platform specific models (ISO 19119 - Services)
- Neeed to have rules for how to do application specific modeling (ISO 19109 –Rules for application schema)
-Need to have tool-support (?) and tool-neutral diagram interchange format (?) –to give a development and usage advantage
-Need to have knowledge and resources to do the appropriate UML modeling (?)
-Need to manage integrated use of large models
- Need to go from current Model Harmonisation Team (ISO) and Documentation committee (OGC) – to use UML as the initial specification approach
24Arne J. Berre 24SINTEF
ConclusionConclusion
• Well defined rules and tools for creating platform-independent service and information models
• Well defined rules and tools for mappings to platform-specific models for the most important platforms: Web services/XML, CORBA, J2EE/EJB, SQL, ...
• A version of XMI (2.0?) that can produce human readable (HUTN) XML – similar to the handcreated XML schema specifications currently being made –(necessary to be accepted in the ”XML” communities)
• A tool-independent model diagram interchange format that can be used to support interoperability between multiple UML tools (the diagram interchange RFP!)
To support ISO/TC211 and OGC and other similar domain standardisationorganisations, OMG should as soon as possible produce the following: