Pittsburgh Watercolor Society’s 71st Annual International ...
® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC...
-
Upload
archibald-nichols -
Category
Documents
-
view
212 -
download
0
Transcript of ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC...
![Page 1: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/1.jpg)
®
© 2009 Open Geospatial Consortium, Inc.© 2009 Open Geospatial Consortium, Inc.
Towards a common information model Towards a common information model for waterfor water
71st OGC Technical Committee
Mountain View, CA. USA
Rob AtkinsonPresented by Peter Fitch
December 8, 2009
Sponsored and hosted by
![Page 2: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/2.jpg)
OGC®
ScopeScope
• Charter implies Who, Why– WMO auspices– Multiple stakeholders– Experiences around the table– Route to implementation
• What?– Core requirements
• Technical – How?
• Practical– Who– When
![Page 3: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/3.jpg)
OGC®
What is the role of a common information model?
INSPIREModel
WMOMetadataProfile
WMOId:definition InspireId:definition
lineage geometry
Rhine
Common concept, need to link or share data across domains
<GML>
![Page 4: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/4.jpg)
OGC®
Design
INSPIREModel 1
WMOMetadataProfile
InspireId:ref
lineage geometry
DomainModel
Id:definition
WMO_Id:ref
INSPIREModel 2
relatedFeature:ref
Model 2 not dependent on detail of model 1
![Page 5: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/5.jpg)
OGC®
Identifiers
• Identifiers are not trivial…• Architectural specification
– e.g WFS 1.0 doesn’t allow gml:name to be queried using gml:name@codespace qualifier (oops!)
– relationship of identifiers to a common model– Global scope of identifiers or ability to declare relationships?
• Implementation choices…
![Page 6: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/6.jpg)
OGC®
INSPIRE base types
![Page 7: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/7.jpg)
OGC®
An example
No direct link to base types in model
![Page 8: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/8.jpg)
OGC®
• <Watercourse xmlns="urn:x-inspire:specification:gmlas:HydroPhysicalWaters:3.0" <gml:identifier codeSpace="inspire....">Rhine</gml:identifier>
<inspireId> <Identifier xmlns="urn:x-inspire:specification:gmlas:BaseTypes:3.2"> <localId>a123-3312-abfg-2334-44501</localId> <namespace>UUID</namespace> </Identifier> </inspireId> <Hydroid>
<localId>Rhine</localId> <namespace>GRDC</namespace>
</Hydroid> <drainsBasin gml:href="urn:some_id"/>
…• </Watercourse>
![Page 9: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/9.jpg)
OGC®
Multiple patterns
Common Agreement
Class1
BaseClass
- id: Identifier
Class2
+ myId: Identifier
«<<datatype...Identifier
Class3
+ knownID: someType
ID known by name or type?
ClassWithImplicitId
Implementation adds an ID, known in context
![Page 10: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/10.jpg)
OGC®
Possible solution
• Model identity explicitly in a conceptual (semantic) framework and always explicitly map implementation models back to this.
• C.f. the “identity carrier pattern” Atkinson et al, IJSDI vol2
• Can be retrofitted to INSPIRE suit of specs (and solutions)
BasicRealization::ApplicationObject
+ att1: CharacterString
«MappingClass»Class1_ApplicationObjectConceptualModel::Class1
+ att1: CharacterString 1
mapsto
1
Name:Package:Version:Author:
PIM to PIMP Mapping Diagram«MappingPackage» BasicRealizationMapping1MDA Tools Add-In
“idiom” to be refined, but mapping is external to both source and target
(like RDF model), and can be retrofitted.
![Page 11: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/11.jpg)
OGC®
An architectural option..
• Separate common domain model from implementation profiles– Allow multiple implementations to be mapped to common semantics– Common semantics can be used to support identifier mapping– “model-mapping” is part of any overall system model– Mappings do not need to “pollute” either implementation or
conceptual model– Mappings become “evidence of implementation” of domain model,
using existing systems– Decouples governance cycle of key aspects– Versioning key to keep multiple mappings up to date,
![Page 12: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/12.jpg)
OGC®
Testing
• It is possible to test a common domain model by mapping available implementations to it.
• Are there Use Cases out there not supported by current implementations?
• Who is willing to provide a minimal set of real data as test cases for the model?– Need someone willing to create mapping to common model– CSIRO can assist with some tools– HUMBOLDT project may provide mapping tools too– (CSIRO to at least interoperate with HUMBOLDT mappings)
![Page 13: ® © 2009 Open Geospatial Consortium, Inc. Towards a common information model for water 71st OGC Technical Committee Mountain View, CA. USA Rob Atkinson.](https://reader035.fdocuments.net/reader035/viewer/2022072015/56649eb55503460f94bbd921/html5/thumbnails/13.jpg)
OGC®
Towards a common domain model..
• Scope– identifiers of real world objects independent of implementation
profiles– WMO definition consistent– Link between WaterML and Hydrology Feature Types– Informative mappings to key implementations
• Next step: decisions– UML as normative – is there a realistic alternative?– Which version – ISO HMWG compatible, not INSPIRE idiom?– Where (Registry Owner – SDSC alongside WaterML)– Who (WMO is Register Owner, who is Register Control Body?)– CSIRO can play role as model editors (Register Manager)