Без темы
<<  Immigrants and Religious Conflict Impress with Prezi  >>
Implementation of ISO 19118 Encoding
Implementation of ISO 19118 Encoding
Objectives
Objectives
ISO 19118 encoding & Data interchange
ISO 19118 encoding & Data interchange
Requirements/referencens
Requirements/referencens
Encoding process
Encoding process
Configuration, XML-schema/DTD
Configuration, XML-schema/DTD
Mapping from GML format to ISO 19118 XML
Mapping from GML format to ISO 19118 XML
XML Data binding
XML Data binding
Sun’s XML Data Binding Specification – a higher level API
Sun’s XML Data Binding Specification – a higher level API
Overall summary
Overall summary
Summary
Summary
Feedback to ISO 191xx standards
Feedback to ISO 191xx standards
Feedback to ISO 191xx standards
Feedback to ISO 191xx standards
Http://www
Http://www

Презентация на тему: «Implementation of ISO 19118 Encoding». Автор: it tjenesten. Файл: «Implementation of ISO 19118 Encoding.ppt». Размер zip-архива: 247 КБ.

Implementation of ISO 19118 Encoding

содержание презентации «Implementation of ISO 19118 Encoding.ppt»
СлайдТекст
1 Implementation of ISO 19118 Encoding

Implementation of ISO 19118 Encoding

Joint Nordic Implementation project

Morten Borreb?k Norwegian Mapping Authority, Email: morten.borrebaek@statkart.no

2 Objectives

Objectives

verification for ISO/TC 211 that its model-based approach to interoperability is feasible and beneficial feedback to the standardsproposal in the 19100-series increased awareness of the ISO 19100 standards family (among the participating countries and in the rest of the world) hands-on experience for further use in Finland ,Norway, Denmark , Sweden and Iceland

3 ISO 19118 encoding & Data interchange

ISO 19118 encoding & Data interchange

System A

d

System B

ISO 19118 Encoding

i

Application schema UML

Encoding service R

Data transfer

Internal schema A

Internal schema B

i

M

M

Encoding service

R

d

Transfer services

Transfer services

Internal data system dependent

Internal databasel

Internal databasel

Application schema structure, system dependent

Application schema structure, system independent ENCODED DATASET)

System boundary

System boundary

File

File

system

system

Defines

Data flow

AC

CB

-1

4 Requirements/referencens

Requirements/referencens

Rational Rose 98 or higher (modeler edition). Breeze XML Studio version 2.2 (www.breezefactor.com) Java runtime version

NLS Cadaster Application Schema, version 1.0, 2000-12-07 ISO CD 19118.2 Encoding, ISO/TC 211 N917, 2000-05-09 and ISO 19118 XML Based encoding rules, 2000-09-25, which outlines the changes planned in ISO CD 19118.3. ISO/DIS 19107 Spatial, ISO/TC211 N1032, 2000-12-19 ISO/DIS 19115 Metadata, ISO/TC211 N1024, 2000-12-12 ISO CD 19103.1 Conceptual Schema Language ISO/TC211 N755, 1999-07-21 (updated for comment in WG1 autumn 2000). Sun’s XML Data Binding (XDB): java.sun.com/xml

Software

References

5 Encoding process

Encoding process

System B

System A

Norway

Finland

NLS Application Schema

(UML)

UML to XML

XML Schema/DTD

GML to ISOXML

ISO XML document

GML XML document

Java XDB API

The goal of the test case is to demonstrate information exchange between two different systems using the ISO/TC 211 model-based approach. The systems are selected by the Finnish Mapping Authority (Kartakeskus Oy) (System B) and by the Norwegian Mapping Authority (System A). System B is capable of exporting a XML document based on OpenGIS GML specification.

19118 XML Encoding

validates

6 Configuration, XML-schema/DTD

Configuration, XML-schema/DTD

Equal for 19107p and 19115c.

The UML2CFG.ebs were used to produce the following three configuration files:

Produces automaticly the corresponding DTD and XSD files using the bat-files:

CFG2DTD CFG2XSD

Configuration files:

XML Schema and DTD production

NLS Application Schema

(UML)

Configuration file

XML Schema

DTD

UML model Configuration file NLS Application Schema.mdl NLS.cfg.xml All ISO Combined.mdl 19107p.cfg.xml 19115c.cfg.xml

UML2CFG.ebs

CFG2XSD

CFG2DTD

7 Mapping from GML format to ISO 19118 XML

Mapping from GML format to ISO 19118 XML

Two XSLT scripts implement a mapping from GML format to ISO 19118 XML Encoding format. There is currently no XSLT mapping from ISO 19118 XML format to GML format. There are two mappings that results in almost equal XML files. The difference is that one is validated against a DTD, the other against an XML Schema.

Finland

GML2ISOXML-dtd.xsl GML2ISOXML-schema.xsl

XML Schema/DTD

GML XML document

GML to ISOXML

ISO XML document

validates

8 XML Data binding

XML Data binding

The goal is to provide the users with a set of Java classes for accessing the elements modelled in the Application Schema. Preferably the Java classes provide (Alt 2):

ISO 19109

Java memory

structure with

XML r/w

an API for accessing the Java memory structure corresponding as close as possible to the elements modelled in the UML Application Schema.

an API for building the Java memory structure from an XML file/stream and for writing the Java memory structure to an XML file.

The XML file/stream referred to in the previous item is conforming to the XML Schema/DTD according to ISO 19118, which again is derived from the UML Application Schema.

Alt 1

XML Schema /DTD

according

Alt 2

to

ISO 19118

XML doc

Data Instances

(ISO format)

Conforming to

Application

Schema(UML)

9 Sun’s XML Data Binding Specification – a higher level API

Sun’s XML Data Binding Specification – a higher level API

An implementation of XDB (XML Data Bindings) specification takes an XML Schema/DTD as input and generates Java classes. The generated Java classes will be directly corresponding to the XML elements defined in the XML Schema/DTD. The Java classes will have an API for accessing the properties of each class as well as marshall- and unmarshall-methods, that is methods for write and read of XML from and to Java memory structure

XML Schema/ DTD

Sun’s XML

input

Data Binding

impl

output

Java

follows

classes

instance of

XML

Java objects

Document

Unmarshall

Marshall

10 Overall summary

Overall summary

The results show that it is possible to use software tools to automate the generation of XML Schema (or DTD) based on an application schema expressed in UML using the XML Encoding rules. However, on several points the UML diagrams in the different standards are not sufficient clear to allow a model-based approach. The resulting manual interpretation indicates that the standards need further work to achieve the goal of interoperability.

11 Summary

Summary

The software tools created in this project demonstrates that the generation of XML Schema (or DTD) based on application schemas expressed in UML using the XML Encoding rules can be automated with minimal human intervention. However, manual intervention is sometimes required. Imprecise UML models and/or the wish for a more efficient encoding result in the need to define exceptions from the general XML Encoding rules and thus manual intervention. This may be caused by imprecise modelled classes that needs further interpretation, for example that some classes should have been modelled as basic types instead of data types or as data types instead of classes. Or that extensive use of inheritance has led to classes having a number of inherited attributes that are superfluous or inconsistent.

On several points the UML diagrams in the different standards are not sufficient clear to allow a model-based approach

12 Feedback to ISO 191xx standards

Feedback to ISO 191xx standards

CSL: The current version of CSL cannot be used for a model-based approach. The Conceptual Schema Language standard defines the basic types used in the different standards and in application schemas. These types need to be defined in a consistent way. Currently the data types are modelled as plain classes even if they are basic types. Does that mean that they should have identity? It is therefore a need to introduce a new stereotype <<BasicType>>, i.e. a type that has defined a canonical encoding. A number of explicit modelled attributes and operations should either be explained or removed from the models.

13 Feedback to ISO 191xx standards

Feedback to ISO 191xx standards

Spatial: A profile of the Spatial schema had to be developed from scratch and could not be based directly on the existing Spatial UML model. This because the textual conformance clauses override the UML model and the correlation between the text and the model is insufficient.

Metadata: Only a citation subset of the metadata schema was used. The only problem found was the definition of a class URL, which clearly is a basic data type.

14 Http://www

Http://www

statkart.no/standard/jnip

«Implementation of ISO 19118 Encoding»
http://900igr.net/prezentacija/anglijskij-jazyk/implementation-of-iso-19118-encoding-79740.html
cсылка на страницу
Урок

Английский язык

29 тем
Слайды