Tiêu chuẩn iso ts 19115 3 2016

Table 2 — C nformance clas es for metadata inter hang e a C nformanc clas URI b mdb /1.0 /conf/metadata-minimal-nstance Minimum XML metadata instance document mds/ 1.0 /conf/metadata-dat

Geog raphic information —

Part 3:

In ormation g o ra hique — Métado n es —

Partie 3: Mise en oeuvre p r des sch mas XML

COPYRIGHT PROTECTED DOCUMENT

© ISO 2016, P blshed in Sw itz rlan

A ll rig hts r eserved Unles otherw ise spe ified, nopar of this p blc tion ma y be r epr od c d or utilz d otherw ise in an form

or b an me ns, ele tr onic or me hanic l, inclu in p oto opying , or postin on the internet or an intranet , w ithout prior

written permis ion Permis ion c n be req esed from either ISO at the ad r es below or ISO’s member bod y in the c u try of

Introduction v

1 Sc ope 1

2 Co for manc e 1

2.1 General 1

2.2 Conformanc clas es for metadata mod les 2

2.3 Conformanc clas es for metadata interchang e document 3

3 Nor mati ve r eferenc es 3

4 Terms an definitions 3

5 Symbols and abbreviated terms 4

5.1 A cronyms 4

5.2 Namesp c s 5

6 Req irements 8

6.1 Automated g eneration of X ML schema 8

6.2 Multi ng ual ada tabi ty an p lymorphism 8

6.3 Intr od ction to r eq ir ement clas es 8

6.4 Cor e Req ir ement 9

6.5 Req ir ement for metadata modules 9

6.6 Req ir ement for metadata inter chang e document 1

6.7 Req ir ement dependency diag rams 24

7 Ex tensio s to the UML mo els in the ISO g eog raphic infor matio ser ies of Inter national Standar ds for this s hema 25 8 Enc oding appr oach and r ules 26 8.1 UML p ckag es an X ML namesp c s 2

8.2 UML model for X ML implementation 2

8.3 Implementation a pr oach for de ouplng X ML p ckag es 2

8.3.1 General 2

8.3.2 Implementation a pr oach to de ouple o tional clas es 2

8.4 X ML encoding rules .3

8.5 Default v lues 3

A nne x A (normative) A bstract test suite 33 A nne x B (informative)Geog raphic metadata X ML r eso rc es .47

A nne x C (informative) E c oding des r iptions 49

A nne x D (informative) Implementatio examples 51

Biblog raphy 64

b dies (ISO membe b dies) The work of pr p ring Int ernational Stan ards is normaly car ied out

through ISO t ech ical committ ees Each membe b dy int er st ed in a subje t for w hich a t ech ical

committ ee has be n es a lshed has the right t o be r pr sent ed on that committ ee Int ernational

org nizations, g ove nmental an non-g ove nmental, in laison with ISO, also take part in the work

ISO cola orat es closely with the Int ernational Ele trot ech ical C mmis ion (IEC) on al matt ers of

ele trot ech ical s an ardization

The proc d r s used t o develo this document an those int en ed for it furthe maint enanc ar

desc ibed in the ISO/IEC Dir ctives, Part 1 In p rticular the dife ent a pro al c it eria ne ded for the

dife ent ty es of ISO document should be not ed This document was draft ed in ac ordanc with the

edit orial rules of the ISO/IEC Dir ctives, Part 2 ( e www.iso.org dir ctives)

A tt ention is drawn t o the p s ibi ity that some of the element of this document ma be the subje t of

p t ent right ISO shal not be held r sponsible for identifying any or al such p t ent right Detais of

any p t ent right identified d ring the develo ment of the document wi be in the Introd ction an / r

on the ISO ls of p t ent de larations r c ived ( e www.iso.org p t ent )

Any trade name used in this document is information given for the convenienc of use s an does not

cons itut e an en orsement

For an ex lanation on the meaning of ISO spe ific t erms an ex r s ions r lated to conformity as es ment,

as wel as information a out ISO’s adhe enc to the Wor ld Trade Org nization (WTO) principles in the

Te h ical Bar ie s to Trade (TBT) se the folowing URL: www.iso.org/ iso/for word.html

The committ ee r sp nsible for thisdocument is ISO/TC2 1, G eo ra hic in ormatio /G eomatic s

A l s of al p rt in theISO 1 1 5 se ies can be fou d on the ISO websit e

information r sour es b defining metadata entities, element an t erminolo y, an es a lshing

an ext ension proc d r for ad itional metadata cont ent ISO 1 1 5-1:2 14, Annex G desc ibes the

r visions from ISO 1 1 5:2 0 The r vised cont ent model also incorp rat es metadata element

def ined in ISO 1 1 9:2 0 an ISO 1 1 9:2 0 /Amd 1:2 08 for metadata desc ibing web se vic s

Mor detaied metadata for g eo ra hic data ty es an data q alty ar def ined in othe ISO g eo ra hic

information s an ards (e.g ISO 1 1 0 an ISO 1 1 7) Whe e ne es ary, int erpr tations of some othe

ISO g eo ra hic information s an ards ar incorp rat ed for this implementation

ISO 1 1 5- 2 ext en s ISO 1 1 5-1 b ad ing models for acq isition information an ext en ing the models

for metadata (MD_Metadata), data q alty (DQ_DataQualty, now in ISO 1 1 7), spatial r pr sentation

(MD_SpatialR epr sentation), an cont ent information (MD_ Cont entInformation)

ISO 1 1 5-1 an ISO 1 1 5- 2 def ine conc ptual models for metadata cont ent that ar in epen ent of

any particular encoding scheme ISO/TS 1 1 9 an ISO/TS1 1 9- 2 def ine eX t ensible Mark p Languag e

(XML) schemas for encoding that cont ent This document defines XML encodings for ISO 1 1 5-1

an ISO 1 1 5- 2 metadata cont ent This int egrat ed schema makes it pos ible t o use conc pt

from ISO 1 1 5-1 an ISO 1 1 5- 2 t og ethe in metadata ins anc document , efe tively r placing

ISO/TS 1 1 9 an ISO/TS 1 1 9- 2 an ena les aut omat ed v ldation and int er hang e of ISO 1 1 5-1

an ISO 1 1 5- 2, metadata cont ent using s an ard sof war t ools

The int egrat ed schema we e de ived from ISO 1 1 5-1 an ISO 1 1 5- 2 conc ptual models using the

rules def ined in ISO 1 1 8:2 1 , Annex A, ISO/TS 1 1 9 a pled t o an ado t ed implementation-r ady

UML version of the conc ptual models as desc ibed in Clause 8 The implementation a pro ch ena les

mod larization an eases r use of element of the conc ptual models Abs ract clas es we e ad ed

t o the ISO g eo ra hic information harmoniz d model, without alt ering the semantics, t o c eat e an

implementation model that was used for this XML implementation ( e Clause 8 for detais)

The primary use case envisioned for this XML implementation is the ex chang e of g eo ra hic

metadata in a clent-se ve environment ex emplfied b the World W ide Web, in w hich the int ernal

manag ement and s ructur of metadata cont ent is in ependent of the encoding used for ex chang e

of metadata information Ado tion of this g eo ra hic metadata XML schema within an

information-sharing commu ity wi l g rne the benef it of s an ardization for r sour e disco e y, ac es , use, an

un e s an ing

Part 3:

This document defines an int egrat ed XML implementation of ISO 1 1 5-1, ISO 1 1 5- 2, an conc pt

from ISO/TS 1 1 9 b def ining the folowing art efact :

a) a set of XML schema r q ir d t o v ldat e metadata ins anc document conforming t o conc ptual

model element def ined in ISO 1 1 5-1, ISO 1 1 5- 2, an ISO/TS 1 1 9;

b) a set of ISO/IEC 1 7 7-3 ( Schematron) rules that implement v ldation cons raint in the

ISO 1 1 5-1 an ISO 1 1 5- 2 UML models that ar not v ldat ed b the XML schema;

c) an Ext ensible Sty leshe t L nguag e Trans ormation (XSLT) for trans orming ISO 1 1 5-1 metadata

encoded using the ISO/TS 1 1 9 XML schema an ISO 1 1 5- 2 metadata encoded using the

ISO/TS 1 1 9- 2 XML schema int o an eq iv lent document that is v ld a ains the XML schema

defined in this document

This document desc ibesthe proc d r used t o g ene at e XML schema from ISO g eo ra hic information

conc ptual models r lat ed t o metadata The proc d r inclu es c eation of an UML model for XML

implementation de ived from the conc ptual UML model

This implementation model does not alt er the semantics of the targ et conc ptual model, but ad s

a s ract clas es that r move depen encies betwe n model p ckag es, ta g ed v lues an st er oty es

r q ir d b the UML t o XML trans ormation sof war , an r fact ors the p cka ing of a few element

int o XML namesp c s The XML schema has be n g ene at ed sy st ematical y from the UML model for

XML implementation ac ording t o the rules defined in ISO/TS 1 1 9or ISO 1 1 8

In orde t o claim conformanc t o a conformanc clas defined in this document, an XML ins anc shal

v ldat e a ains the t es proc d r s spe ified in An ex A These t es s inclu e v ldation using a spe if ic

XML schema document, as wel as S hematron rule document that t es conformanc with cons raint

spe if ied b the b se conc ptual model that ar not t est ed b XML schema v ldation Each namesp c

mod le an int er hang e document schema def ined b the implementation car ies with it an implcit

conformanc clas for xml ins anc document This conformanc clas t es s the r q ir ment that

xml element an at ribut e ins anc s from the namespac shal be wel formed and v ld The t es is

v ldation with a spe ific XML schema and S hematron rule set if ne es ary The framework, conc pt ,

an methodolo y for t es ing, an the c it eria t o be achieved t o claim conformanc ar spe ified in

ISO 1 1 5

implementations Each mod le is p ckag ed in a sep rat e XML namesp c Ta le 1 ls s the mod le

defined in this document

Table 1 — Co formance clas es defined for metadata mo ules

/mac / 1.0 /conf/ acq isition-xml Valid XML instance of metadata for acq isition

namespace (ISO 1 1 5-2:2 0 , A.2.5)

/mco / 1.0 /conf/constraints-xml Valid XML instance of constraints namespace

r q ir ment an conformanc clas , an a namesp c URI t o identify the document ty e Ta le 2 l s s

these int er hang e document schemes

Table 2 — C nformance clas es for metadata inter hang e

a

C nformanc clas URI

b

mdb /1.0 /conf/metadata-minimal-nstance Minimum XML metadata instance document

mds/ 1.0 /conf/metadata-data-or -service-

instance

Complet e valid XML metadata instance document

md1/ 1.0 /conf/metadata-e ten ed-ty es-

instance

Valid XML metadata instance document with

e ten ed ty es

/md2/ 1.0 /conf/ xt en ed-metadata-nstance Valid XML metadata instance document with

e ten ed cont ent model

/cat/ 1.0 /conf/catalo ue-nstance Valid XML catalo ue instance document

/mda/ 1.0 /conf/metadata-ap lication-nstance Valid XML instance of metadata ap lication

The folowing document ar r fe r d t o in the t ext in such a wa that some or al of their cont ent

cons itut es r q ir ment of this document F or dat ed r fe enc s, only the edition cit ed a ples F or

un at ed r fe enc s, the lat es edition of the r fe enc d document ( inclu ing any amen ment ) a ples

ISO 1 1 0, G eo ra hic in ormatio — Meth dolo y fr featur c atalo uin

ISO 1 1 5-1:2 14, G eo ra hic in ormatio — Metadata — Part 1: Fu damental s

ISO 1 1 5- 2:2 0 , Geo ra hic inormatio — Metadata — Part 2 : Ex tens io s fr ima er y a d grid ed data

ISO 1 1 6, G eo ra hic inormatio — G eo ra h Markup L n u ge (GML)

ISO 1 1 7, G eo ra hic inormatio — Data q alt y

ISO/TS 1 1 9:2 0 , G eo ra hic inormatio — Metadata — XML schema implementatio

4 Terms and definitions

F or the purposes of this document, the folowing t ermsand definitions a ply

ISO an IEC maintain t erminolo ical data ases for use in s an ardization at the folowing ad r s es:

Not e 1 t o entry: The combination of a namespace URI an element or at ribute name are inten ed to b a glo al y

u iq e identif ier for that model element

[ SOURCE:W3 XML Namesp c s:1 9 ]

4.2

packag e

<UML> g ene al purp se me hanism for org nizing element int o groups

E AMP E Identif ication information packa e, metadata entity set information packa e, constraint

information packa e

Not e 1 to entry: Packag es may b nested within other packa es Both model elements an dia rams may ap e r

in a packa e

Not e 2t o entry: A packa e provides a n mes pac e (4.1)for the grou ed elements

[ SOURCE:ISO 1 1 3:2 1 , 4.2 , modified — Ex mples an not es t o entry ha ebe n ad ed.]

4.3

re l zatio

semantic r lationship betwe n clas if ie s, w he ein one clas if ie spe ifies a contract that anothe

clas if ie guarant eest o car y out

[ SOURCE:ISO/TS1 1 9:2 0 , 4.3]

4.4

charact eris ic of being a le t o as ign a dife ent meaning or usag e t o something in dife ent cont ext

– spe if ical y, t o alow an entity such as a v ria le, a fu ction, or an o je t t o ha e mor than one form

Not e 1t o entry: Re li zation(4.3) in icates in eritance of b haviour without in eritance of structure

[ SOURCE:ISO/TS1 1 9:2 0 , 4.4, modif ied — Not e 1 t o entry has be n ad ed.]

HTML Hy e Text Mark p L nguag e

UML Unif ied Modelng Languag e

URI Unive sal R esour e Identif ie

XML Ext ensible Mark p L nguag e

XSL Ext ensible Sty leL nguag e

a br viation, N is the major ve sion n mbe , and M is the minor ve sion n mbe De efe encing the

namesp c URI as a r sour e locat or wi r trieve a desc iption of the namesp c , lnks t o desc iption

of the cont ent of the namesp c , an lnks t o the b se spe if ication the namesp c implement an t o

the normative XML schema location

Be a use the ful URI is cumbe some for r ading, writing, and in h man discus ion, this document

wi r fe t o the namesp c s using a br viations Ta le 3 ls s namesp c s from othe spe if ications

imp rt ed b this implementation, and the short s ring in the lef column of Ta le 3 is the as ociat ed

a br viation used t o r fe enc the namesp c an t o as ociat e an XML element with the namesp c

URI in a ful y q al fied name The se on column contains an E gl sh-languag e desc iption of the

namesp c , an thes ring in the right column is the URI that identif ies the namespac Ta les 4 an 5 l s

a br viations an othe information for namesp c s used for UML p ckag es defined in ISO 1 1 5-1 an

for namesp c s def ined in this document that imp rt multiple XML namesp c s t o def ine int er hang e

s hema

Table 4 — Namespace URIs and namespace ab reviation co ventio s defined and used in this

d cument for packag es defined in ISO 1 11 -1

catalo ues, an e ample

catalo ues from

citation, identif ication,

Elements for cultural

an linguistic adapta ility

reference

sy stem

Spatial reference system

for resour e content

service resour es,

in erited from ISO 1 1 9

UML pa kages are defined in ISO 191 5-1 u les noted otherwise

Table 5 — Namespace URIs and namespace abbreviatio co ventions to identify metadata

inter hang e document types that a gre ate multiple namespaces

properties for minimal

metadata properties

req ired by ISO 1 1 5-1

des ribing resour e

col ections with

hierar hical metadata

des ribing packag es of

data for transfer

A major design o je tive for ISO g eo ra hic information s an ards information models is t o ena le

prod ction of XML schema folowing s an ard rules an implementation p tt erns such that machine

proc s ing of UML models can g ene at e the XML schema The int ention is t o promot e pr dicta i ity,

ext ensibi ty, r use of schema, an int ero e a i ity with othe ISO g eo ra hic information s an ards

implementations The r sulting XML schemas ar alg orithmical y de ived from the normative UML

models for ISO g eo ra hic information s an ards, w hich promot es consist ency in the r sulting schema

The r sulting schemas ar pr dicta le sinc UML clas es, at ribut es, as ociations, et c ar encoded

folowing consist ent rules an p tt erns

Anothe r q ir ment of this implementation is t o mod lariz the encoding of ISO 1 1 5-1 cont ent

b def ining XML element in seve al namesp c s, with a minimum of depen encies betwe n them

of information r pr sentation ca a i ty that faci tat e r use in othe a pl cations The cont ent of

several XML namesp c s ar defined in this document, w hich ma be r used b importing int o othe

XML schema Use of an exis ing XML schema is adv ntag eous be ause it r d c s the amou t of new

schema develo ment r q ir d, and be a use exis ing sof war ma be a ai a le that can proc s model

element conforming t o an exis ing XML schema

The ISO 1 1 5-1 metadata conc ptual schema isdesigned t o sup ort trans e of r sour e documentation

(metadata) among an within use commu ities A third o je tive of the implementation for this

document is t o define s an ard document ty es that inclu e element from multiple namesp c

mod les, designed for spe if ic information ex chang e sc narios Six “a gr g tion” namesp c s ar

defined that imp rt multiple mod les t o me t v rious r q ir ment ( e 6.5)

6.2 Multi ing ual adaptabi ity and pol ymorphism

Cultural an l nguis ic ada ta i ity is a r q ir ment for metadata element with t ext cont ent In

ISO 1 1 5-1:2 14, Annex F, the e isan informative discus ion of multi ingual t extual metadata element

In orde t o ena le the int ero e a i ty of multi ingual ins anc document , the XML implementation

for this document olow s the implementation spe if ied in ISO/TS 1 1 9 The pro e ty ty e encodings

desc ibed in ISO/TS 1 1 9:2 0 , 8.4, ena le ext ensions t o the XML schema that implement pro e ty

v lues using element ty es not inclu ed in the base XML schema Such p lymorphism ( e def inition

This p tt ern is used t o pro ide cultural an l nguis ic ada ta i ty sup ort through metadata ins anc

document containing cont ent in one or mor languag es that do not violat e cardinalty rules def ined in

ISO 1 1 5-1 The lan namespac def ines a Charact er tring pro e ty ty e that inclu es a Charact er tring

v lue, an z ro t o many PT_Fr eText element , each of w hich is a languag e-localz d charact er s ring

that ma be inclu ed inlne or b r fe enc Using this ext ension, a single metadata document ma

inclu e cont ent s rings in a v riety of languag es, but clent that ar not pro rammed for multi ingual

cont ent wi s i l work be ausethe s an ard Charact er tring element is pr sent

Anothe ex mple of p lymorphism is the name at ribut e of ty e Charact er tring in the CI_In ivid al

clas in ISO 1 1 5-1; if a mor s ructur d r pr sentation is r q ir d (e.g f irs , mid le, an las name

element ), polymorphism alow s ext ension of the name element implementation in a user-def ined

namesp c that ma be subs itut ed for Charact er tring within a metadata ins anc These ext ensions

wi be un e s an a le t o use s w ho r co niz theext ension namesp c , but in g ene al such ext ensions

wi not int ero e at e with clent of war not designed t o work with them

6.3 Introduction to requir ements clas es

The r q ir ment t o c eat e v ld XML metadata ins anc s for the conc ptual model pr sent ed in

ISO 1 1 5-1 ar def ined in 6.4 through 6.7 In Ta les 6 through 1 , HTTP URIs ar used t o identify clauses

for metadata mod les that def ine the v rious component of metadata cont ent, an r q ir ment for

actual metadata int er hang e document that ar as embled b imp rting col e tions of mod les The

metadata mod les ar designed t o minimiz depen encies between mod les t o faci tat e their r use in

othe a plcation schema

6.4 Cor e Requir ements

The r q ir ment clas spe ified in Ta le 6 defines r q ir ment that shal be met b any XML ins anc

document b sed on this document

Table 6 — Requirements for metadata core

R equir ment clas

Targ et ty e XML instance document

Name Core req irements for metadata properties

Depen ency ht p://stan ards.iso.org iso / 19 39/spec#8.4.1

R equir ment / eq/ metadata-core /pro e ty-ty e-cont ent

A property element instance SHAL have e actly one of inline cont ent by-value) that is

a s hema-valid XML Clas instance, a xlin :href at ribute (by-reference value), or a

gco:nilR eason at ribute (nil value)

R equir ment / eq/ metadata-core /ins anc -v ldation

XML instance documents SHAL b wel formed an valid.A conformance clas is def ined

on this req irement or e ch namespace that specif ies the normative XML s hema an

Schematron rule (if ap lica le) f iles that are used to test conformance

R equir ment / eq/ metadata-core /b se-data-ty es

Base data ty es SHAL b implemented ac ording t o rules set forth in ISO /TS 1 1 9

A cole tion of mod lar XML namesp c s ar used t o implement the v rious cont ent p ckag es def ined

in ISO 1 1 5-1 and ISO 1 1 5- 2 The mod les ar summariz d in Ta le 7, an the r q ir ment for

XML ins anc s of each mod le ar def ined an as igned identifie s in Ta le 8 These identifie s ar

r fe enc d in the def inition of conformanc clas es an t es s in Annex A

Table 7 — Summary of metadata modules defined by this document

Metadata common clas es ht p:/ stan ards.iso.org iso / 19 1

clas es neces ary for encoding

optional clas property ty es def ined

in ISO 1 1 5-1 ac ording t o the

implementation ap ro ch des rib d

There is a circular depen ency between the citation an c mmon clas es pa kages, b t be ause of the polcy that

the implementation pa kage should match the base abs ra t schema (ISO 191 5-1) pa kagin , these are implemented as

separate namespa es

/cat/1.0 /req/catalo ue-

instance

/req/metadata-core,

/req/langua e-

localisation-nstance

/req/catalo ue-nstance /validation

/req/citation/in ivid al-name

An instance of CI_In ivid alSHAL have

either a “ name” property value or a

“ positionName” property value

/req/citation/ rg nisation-name

An instance of CI_Org nisation SHAL

have either a “ name” property value or a

“lo o” property value

/g cx /1.0 /req/ xten ed-

/req/g eospatial-e t ent-nstance /

value-req ired

If an E _Ext ent element is instantiat ed,

then a value for either “des ription”,

“g o rap ic -Element” , “t emporalElement

or “verticalElement SHAL b present

/req/g eospatial-e t ent-nstance /

vertical-c s

If an E _VerticalExtent element is

instantiated, then a value for either

/req/ ml-wrap er/implementation

Property ty es implemented by GML

(ISO 1 1 6)SHAL b implemented

as property ty es as specif ied in

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that defines the XML schema an

S hemat on rule set used to tes valdation

/lan/ 1.0 /req/langua e-

localisation-nstance

Codelist values for Languag eCode should

b from the ISO 63 -2 list

Codelist values for Cou try ode should

b from the ISO 3 6 -1 list

Codelist values for C aracterS tCode

should b from the IA A character set

re ister (ht p:/ www.iana.org/as

/req/acq isition- nstance /validation

/mas/ 1.0 /req/ap lication-

clas es-nstance

/req/metadata-core /req/common-clas es-nstance /validation

If a MD_Le alConstraint element is

instantiant ed, then it SHAL have a

property value for at le st one of

A value may b provided for the

otherConstraints property ONLY if the

code value of an ac es Constraints or

useConstraints property is eq al to

”otherR estrictions”

/req/constraints-nstance /rele sa ility

If a MD_R ele sa ility element is

instantiat ed, then it SHAL have a

property value for at le st one of

“ad res e ” or “ tatement

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that def ines the XML schema an

S hemat on rule set used to tes valdation

/mdb / 1.0 /req/metadata-b se-

instance

/req/metadata-core

/req/common-clas es-

instance /req/langua e-

localisation-nstance

/req/metadata-b se-nstance /validation

instance /identif ication

A metadata instance SHAL have an

identif ication element that is in the XML

substitution grou for a stract

mc :_R esour eDes ription

/req/metadata-b se-nstance /langua e

If the langua e of the metadata content is

not he def ined default value (E glish, se

8.3), then a value shal b provided for

“defaultLocale.PT_Locale.langua e”

property consistent with the langua e

content of the metadata instance

/req/metadata-b se-nstance /

character -encoding

If the character encoding of the metadata

content is not he def ined default value

(UT -8, se 8.3), then a value shal b

provided for

defaultLocale.PT _Locale.character -

E coding property consist ent with the

character encoding of the metadata

instance

/req/metadata-b se-nstance /

metadata-s ope-name

If a MD_Metadata cope element is present,

the name property SHAL have a value if

resour e-Scope is not eq al to “dataset

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that defines the XML schema an

S hemat on rule set used to tes valdation

Values for the o lig tion,

ma imumOc ur ence an domainValue

properties in instances of MD_Exten ed-

ElementInformation SHAL b provided,

EXCE T when the dataT pe property

code value is one of (codelist,

en meration, codelistElement)

/req/metadata-e t ension-

instance /con itional-con ition

A value for the con ition property SHAL

b provided when the code value of the

o lig tion property is eq al to

“ on itional”

/req/metadata-e t ension- nstance /

code-man at ory

If the code value of the ‘dataT pe’

property is one of (codelist, en meration,

codelistElement), then a value SHAL b

provided for the “ ode” property

/req/metadata-e t ension-

instance /conceptname-man at ory

If the code value of the dataT pe property

is one of (codelist, en meration,

codelistElement), then a value SHAL b

provided for the conceptName property

/req/metadata-e t ension- nstance /

name-pros rib d

If the code value of the dataT pe

property is one of (codelist, en meration,

codelistElement)the name property shal

b a nil value with a nilR eason =

“ notAp lica le” at ribut e value

/mmi/ 1.0 /req/maint enance-

information-nstance

/req/metadata-core /req/maint enance- nformation-

instance /validation

c

/req/maint enance- nformation-

instance / freq ency: If a

MD_MaintenanceInformation element is

instantiat ed, then a value for either the

maint enanceAn Up at eFreq ency or

userDef inedMaintenanceFreq ency

property shal b present

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that def ines the XML schema an

S hemat on rule set used to tes valdation

instance /req/langua e-

localisation-nstance /

If a MD_F eatureCatalo ueDes ription is

instantiated, then either the value for

inclu edWithDataset SHAL b “true”,

or a wel formed an valid

MD_Fe tureCatalo ue instance SHAL

b inclu ed in the metadata record, or a

value SHAL b provided for the

“MD_Fe tureCatalo ueDes ription

fe ture-Catalo ueCitation” property

/req/resour e-content-nstance /

inline-fe ture-catalo ue

If a MD_F eatureCatalo ue instance is

inclu ed with inline “fe tureCatalo ue”

property content, the namespace for the

XML s hema that implements an

ISO 1 1 0 fe ture catalo ue shal b

declared in the instance document A valid

xsi:s hemaLocation SHOULD b provided

that wil retrieve an xml s hema t o

validat e the fe ture catalo ue instance

/req/resour e-content-

instance /dimension-u its

If a MD_S mpleDimension element is

instantiat ed an at le st one of the

“max Value “ minValue or “me nValue”

properties has a value, then a v alue

SHAL b provided for the “ units” property

/req/resour e-content-nstance /

b n -dimension-u its

If a MD_Ban element is instantiated,

then the value of the “ units” property

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that defines the XML schema an

S hemat on rule set used to tes valdation

If a MD_Medium element is instantiated

an a value for the “density” property is

present, then a value for the ‘density Units’

instance /req/ e spatial-

e tent-nstance /req/

gml-wrap er

/req/resour e-dentif ication-

instance /validation

c

/req/resour e-dentif ication-nstance /title

A resour e identif ication instance SHAL

provide a “title” property value that is a

character string

/req/resour e-dentif ication-

instance /abstract

A resour e identif ication instance SHAL

provide an “a stract property value that

is a charact er string

/req/resour e-dentif ication-

instance /topic -cat eg ry

If no value for the MD_Metadata

metadata-Scope property is provided,

/req/resour e-dentif ication-

instance /as ociated-resour e

If a MD_As ociatedR esour e element is

instantiat ed, then a value for either the

“ name” or “ metadataR eference” property

SHAL b provided

R ecommen ation: If the resour e

des rib d by a metadata instance

contains t extualinformation, then a

value should b provided for

MD_DataIdentif ication defaultLocale

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that def ines the XML schema an

S hemat on rule set used to tes valdation

/mrl/ 0 /req/line g -nstance /req/metadata-core

/req/line g -nstance /line g -content

If a LI_Line g element is instantiated

an no value is provided for the

LI_Line g statement property, then at

le st one of “ proces Step” or “ our e”

SHAL have a value

/req/line g -nstance /sour e

If an LI_S ur e element is instantiat ed,

then either the “des ription” or “scope”

property SHAL have a value

R ecommen ation: If the

“ heck ointAvaila ility” property has a

value of “true” (1), then a value should b

provided for the ‘check ointDes ription’

A SV_S rviceIdentif ication instance SHAL

have a value for either the “ ontainsC ain”

or the “ ontainsOperation” property

/req/service-metadata- nstance /

cou led-resour e-e ists

If the “ ou ledR esour e” property has a

value, then the “ ou lingT pe” property

SHAL have a value

/req/service-metadata- nstance /

operated-or -operates-on

A SV_S rviceIdentif ication instance

SHAL NOT contain values for b th the

“operatesOn” an “operat edDataset

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that defines the XML schema an

S hemat on rule set used to tes valdation

/req/service-metadata- nstance /

cou led-resour e-def ined

If a SV_Cou ledR esour e element is

instantiat ed, then either the

“ resour eR eference” or the “ resour e”

property SHAL have a value

/req/service-metadata- nstance /

cou led-resour e-lin a e

A SV_Cou ledR esour e instance SHAL

NOT contain values for b th the “ resour e”

an “ resour eR eference” properties

R ecommen ation: If the value of

MD_Metadata.metadata cope

-MD_Metadata cope.resour e cope

property is eq al t o “service”,then one

instance of MD_K eyword should have a

“keyword” property value that is a t erm

from the service tax onomy def ined in

Valdation req irement are al the same Ea h mod le has a valdation req irement that refle t the valdation

req irement of the c re req irement , an is as o iated with a c nformanc clas that def ines the XML schema an

S hemat on rule set used to tes valdation

6.6 Requirements for metadata interchang e documents

In orde t o fost er metadata int ero e a i ty, this document defines conformanc clas esfor 6 metadata

ins anc document ty es that implement pro r s ively mor ca a i ty for desc ibing r sour es an

their r lationships ( e Ta le 9) The simples is the Minimal-Metadata-Ins anc r q ir ment clas ,

w hich def ines a metadata document that uses element in namesp c s defined b this document that

ar r q ir d t o me t the minimum man at ory cont ent r q ir ment spe if ied b the ISO 1 1 5-1

model for dataset metadata

The metadata for data or se vic s r q ir ment clas defines a document ty e that uses namesp c

mod les def ined in this document t o implement al pro e ties def ined for a metadata r cord spe if ied

b ISO 1 1 5-1 an ISO 1 1 5- 2 models, ex clu ing ty e ext ensions (g cx) an metadata ext ensions

(mex) This document ty e ena les a complet e metadata r cord desc ibing any ty e of g eosp tial

r sour e or se vic , inclu ing the acq isition information defined in ISO 1 1 5- 2

The metadata with ext en ed ty es r q ir ment clas spe if ies a document ty e that ext ends the

metadata for data or se vic s r q ir ment b al owing subs itutions for charact er s rings from the

g eosp tial common ext ension (g cx)namesp c (original y def ined b ISO/TS 1 1 9)

The metadata with ext en ed cont ent r q ir ment clas spe if ies a document ty e that ext en s the

metadata for data or se vic s r q ir ment b alowing b th subs itutions for charact er s rings from

the g eosp tial common ext ension (g cx) namesp c , an for ext ensions of themetadata scheme def ined

b ISO 1 1 5-1 an ISO 1 1 5- 2 using the metadata ext ension namesp c an proc d r def ined in

ISO 1 1 5-1:2 14, 6.5.1 Use prof iles an ext ensions ar desc ibed for metadata in ISO 1 1 5-1:2 14,

An ex C, with rules r lat ed t o the pro e analy sis of the r q ir ment for the ext ension an the r sulting

documentation t o desc ibe the ext ension R ules spe ifying r q ir ment for implementation of dife ent

ty es ofext ension desc ibed in ISO 1 1 5-1:2 14, C.2 ar en me at ed in ISO/TS 1 1 9:2 0 , A.3 an

conc ptual model spe if ies a bi-dir ctional as ociation betwe n DS_R esour e an the Metadata

Information: MD_Metadata element Implementation of the bi-dir ctional as ociation makes

mod larization of the metadata model impos ible be a use of cir ular depen encies it introd c s

This document, th s, only implement the as ociation from DS_R esour e t o MD_Metadata, but not the

r ve se as ociation from MD_Metadata t o DS_R esour e This is b sed on the analy sis that in actual

a plcations, the desir d sc nario is t o l n from a r sour e t o the metadata desc ibing the r sour e,

an that the as ociat edR esour e pro e ty on MD_Identification can be used t o implement l nkag e from

a metadata r cord t o desc ibed r sour e ins anc s w hen ne es ary

The metadata for data trans e ins anc r q ir ment clas spe ifies a document ty e that implement

the metadata for data trans e model defined in ISO/TS 1 1 9 This model is implement ed in this

document for comp tibi ty with ISO 1 1 5-1 It pro ides a catalo ue (def ined in the cat namesp c )

that l s s the cont ent of a dataset a gr g tion desc ibed b a metadata r cord, an alow s sup orting

files t o be as ociat ed with the a gr g t e or with comp nent dataset

Namesp c

URIb

/req/metadata-minimal-nstance /validation

A minimal metadata XML instance

document SHAL b wel formed an valid

/req/ metadata-minimal-nstance /

resour e-dentif ication

A metadata instance document conforming

to this document SHAL have

a conc ete element hat provides the

MD_Metadata.dataIdentif ication property

value that is either

mri:MD_DataIdentif ication or

s v:SV_S rviceIdentif ication

/req/metadata-minimal- nstance /

dataset-e tent

If no value for the

MD_Metadata.metadata cope property

is provided, or if the value of

MD_Metadata.metadata cope.MD_

Metadat-Scope.resour e cope property

is eq al t o “dataset , then a resour e

identif ication instance SHAL provide at

le st one “e tent property value that is

either an E _Ge grap icBou dingBo or

an EX_Ge grap icDes ription

/req/metadata-minimal- nstance /

alowed-namespaces

A minimal metadata XML instance

document SHAL inclu e inline elements

to instantiate a stract property value data

ty es that are def ined in the cit an mri

namespaces, an con itional y, in the s v

instance /validation

A metadata XML instance document

SHAL b wel formed an valid

/req/metadata-data-or -service-

instance /alowed-namespace

A data or service XML instance document

element SHAL only contain elements that

are def ined in one of these namespaces:

mdb, mc , cit, lan, mri, g co,mas, mco, mrl,

g x, mr , mrd, mpc, mr , ms , or s v, or a

namespace that implements one of the

a stract b se clas es from d c or fc

namespaces in the implementation of

/req/metadata-e ten ed-ty es-

instance /validation

A metadata e ten ed ty es XML instance

document SHAL b wel formed an valid

instance /validation

If a XML instance document contains

metadata XML elements that are children

of MD_Metadata an are not def ined in this

document, then the document

SHAL def ine the s hema location for the

namespace that inclu es the e t ension

elements such that the document can b

test ed t o determine that is it wel formed

an valid

/req/ xt en ed-metadata-

instance /e tension- nformation

If a XML instance document contains

metadata XML elements that are children

of MD_Metadata an are not def ined in this

document, then the document

SHAL inclu e at le st one

MD_MetadataExtensionInformation

element rom the

an valid that documents the e tension

elements

/req/ xt en ed-metadata-nstance /

new-section

An new metadata sections, elements,

or entities SHAL b ad ed in their own

namespace folowing the encoding rules

des rib d in ISO /TS 1 1 9:2 07, Clause 8

/req/ xt en ed-metadata-nstance /

new-codelist

New codelists SHAL b implemented by

folowing the encoding rules des rib d in

ISO/TS 1 1 9:2 07, 8.5.5

/req/ xt en ed-metadata-nstance /

new-element

New metadata elements SHAL b ad ed

via sub-clas ing e isting ISO g o rap ic

information stan ards clas es folowing

the guidelines in ISO/TS 1 1 9;2 07, 8.5.3

for encoding sub-clas es

/req/ xten ed-metadata-nstance /iso-ty e

The XML clas ty e (XCT)of an new

metadata element SHAL inclu e a

man atory XML at ribute named isoT pe

that is e pected to contain the name of the

ISO clas it derives from directly or

in irectly The namespace for the isoT pe

at ribute wil b the same as the

namespace of the new metadata element

/req/ xten ed-metadata-

instance /e t ension-by-restriction

R estriction of XML element or at ribute

cardinality or domain def ined in this

document SHAL b enfor ed

via a t ool other than an XML Schema

validat or

R ecommen ation:

New codelist elements (e pan ing a

codelist)SHO LD b ad ed in the codelist

re istry as des rib d in

instance /validation

A metadata XML instance document

SHAL b wel formed an valid

/req/metadata-ap lication-nstance /

ro t-element

A metadata a gre ate conforming to this

document SHAL have as its

ro t element an element in the substitution

grou for mda:DS_Ag re at e

/mdt/ 1.0 /req/data-transfer -

instance

/req/metadata-

ap lication-nstance

/req/catalo ue-nstance

/req/data-transfer -instance /validation

A metadata XML instance document

SHAL b wel formed an valid

Ta le 1 summariz s the element defined b ISO 1 1 5-1 t o be man at ory in eve y metadata ins anc

document that does not desc ibe a se vic

namesp c

Metadata entity (mdb) MD_Metadata ro t clas for metadata record, contains MD_Metadata element

Metadata common

clas es (mc )

MD_Metadata Def inition of a stract clas es neces ary to construct XML

s hema ac ording to implementation rule in 8.2 Data ty es

req ired for properties on various man atory elements:

_R esour eDes ription, _Ext ent, _T pedDat e, an

_R esponsibility T ese clas es do not ap e r in instance

documents, but he namespace s hema shal b imported

t o validate documents

Metadata common

clas es (mc )

MD_Metadata-Scope Def inition of shared clas neces ary to construct XML

s hema ac ording to ISO/TS 1 1 9 implementation rules

MD_Metadata cope.resour e cope.MD_ScopeCode

Langua e localization

(lan)

MD_Metadata Optional property MD_Metadata defaultLocale.PT _Locale;

Namespace s hema shal b imported to validate documents

Citation (cit) MD_Metadata Man atory property: MD_Metadata.contact.CI_R esponsibility;

import is req ired to provide conc ete element t o substitute

for mc :_R esponsibility

Metadata for resour e

identif ication (mri or

service metadata (s v)

MD_Metadata Man atory property: MD_Metadata.identif icationInfo

-MD_Identif ication.a stract; the a stract

_R esour eDes ription.MD_Identif ication may b implemented

by mri:MD_DataIdentif ication or s v:SV_S rviceIdentif ication

Citation (cit) MD_Identif ication Man atory property:

MD_Identif ication.citation.CI_Citation.title; import is req ired

to provide conc et e element o substitute for mc :_Citation

CI_Date Data ty e for man at ory property: date.DateTime

Ge spatial e tent g ex) MD_Identif ication If no value for the MD_Metadata.metadata cope property is

provided, or if the value of MD_Metadata.metadata cope

-MD_Metadata cope.resour e cope property is eq al to

”dataset , then a MD_Identif ication instance SHAL provide

at le st one “e tent property value that is either an

E _Ge grap icBou dingBo or an E _Ge grap icDes ription

Ge grap ic common

(g co)

SV_S rvice-

Identif ication

If MD_Identif ication is implemented by

s v:SV_S rviceIdentif ication, then serviceT pe.GenericName

is man at ory

NO E The req ired XML namespa e c lumn in ic tes a namespa e req ired to implement he c nformanc clas The

c ntainer clas c lumn in ic tes a clas in the pa kage that int od c s a depen ency The depen ency path c lumn is an

e planation of the path to a req ired element rom a namespa e that hal be impor ed

element from the namesp c s def ined in this document The depen encies between r q ir ment

clas es in the implementation model in icat e that a depen ent clas (he sour e of the as ociation)

inhe it al r q ir ment from the clas that is the targ et of the depen ency r lationship (he ar ow

p int t o the targ et clas ) Th sal r q ir ment clas es in e it he cor r q ir ment

Each of these r q ir ment clas es is as ociat ed with a conformanc clas that defines t es s t o

det ermine that ins anc document me t r q ir ment spe if ied Not e the ad ition of r q ir ment

clas es that spe ify metadata r cords incorporating al the o tional metadata cont ent mod les (ful

(an ext ernal schema in some cases) The namespac URIs as ociat ed with these r q ir ment clas es

ar simply used astarg et namesp c at ribut e v lues in the schema an ins anc document t o in icat e

conformanc t o that r q ir ment clas The URI schema locations point t o the XML schema used t o

v ldat e conformanc with a particular conformanc clas

NOTE Ar ows in the dia ram imply that the req irements for a clas at he sour e en of the ar ow inclu e

al req irements inclu ed in the clas at he targ et en of the ar ow

Figure 1 — Dependencies betwe n enco ing requirements clas es

7 Ex tensions to the UML models in the ISO g eog raphic information series of

International Standards for this schema

This implementation inclu es the model ext ensions def ined in ISO/TS 1 1 9 for web environment

(g eospatial common ext ended ty es), cultural an l nguis ic ada ta i ity, an catalo ues Be ause

The proc d r used t o encode conc pt from ISO 1 1 5 int o XML, desc ibed in ISO/TS 1 1 9, combined

conc pt from many UML packag es int o a single XML namespac (gmd) This a pro ch simplfied the

r sulting XML ins anc document , but made it difficult t o in epen ently r use conc pt from spe if ic

UML packag es An important g oal of this document is t o def ine r lationships betwe n UML p ckag es an

XML namespac s in a wa that faci tat es mod larization an r use R ules control ing the r lationship

betwe n p ckag es an namespac s used in this document ar the folowing:

a) the XML implementation wi inclu e a minimum of one namesp c pe UML packag e in the

conc ptual model, i.e multiple UML p ckag es should not be combined int o single namesp c s;

b) UML packag es can be splt int o multiple namesp c s if ne es ary t o ease the implementation an

manag ement of the l fe-cycles of v rious comp nent ;

c) ex ceptions t o R ule 1 ma be r q ir d t o minimiz depen encies betwe n namesp c s, an

el minat e cir ular depen encies

8.2 UML model for X ML implementation

ISO 1 1 5-1 defines a n mbe of UML p ckag es and r lationships betwe n them These r lationships

r sult in depen encies betwe n p ckag es that make it imp s ible t o r use them without inclu ing the

entir model In orde t o faci itat e mod larization and a ut omat ed schema g ene ation, an XML-spe if ic

implementation la e was ad ed t o the UML model without afe ting the semantics This la e inclu es

a s ract clas es that alow de oupl ng of model p ckag es, addition of ta g ed v lues an st er oty es

r q ir d b the UML t o XML trans ormation sof war , an r fact oring of some model element

p ckag es w he e r q ir d t o elminat e cir ular dependencies betwe n XML namesp c s Abs ract

clas es ha e also be n c eat ed t o def ine subs itution groups for clas es that ar or might be used b

XML implementations of othe ISO models Abs ract clas es for l n ag e betwe n namespac s ar al

p ckag ed in a single p ckag e The modif ied UML model is cal ed an implementation model, an the XML

schema was g ene at ed aut omaticaly from this implementation model ac ording t o rules defined in

ISO 1 1 8 an ISO/TS 1 1 9

8.3 Implementation approach for dec oupl ng X ML packag es

8.3.1 General

The implementation a pro ch uses a s ract clas es in pro e ty v lues that r q ir element from

imp rt ed namespac s Int er hang e document imp rt the b se scheme, the a s ract clas packag e

(w hich does not chang e between ve sions) an the schema that implement a conc et e element in the

subs itution group for an a s ract element New ve sions of a p rticular namesp c can de ive new

element def initions from that a s ract clas , alowing the new model t o be used b imp rting the new

namesp c in ins anc document This r q ir s no modification t o the implementation of the b se

schema This a pro ch is ex lained in mor detai in this subcla use

As ociations betwe n UML clas es ma be modeled as at ribut e v lues or as ociation en s The

implementation a pro ch defined he e is r q ir d in cases w he e an o tional at ribut e or as ociation

has a pro e ty ty e that is a clas from a dife ent packag e than the containing element XML ins anc

document ne d t o v ldat e with or without importing the namesp c that implement the o tional

pro e ty ty e clas This is ac omplshed b using an a s ract clas for the pro e ty v lue ty e in the

schema for the p r nt element (MD_Metadata in Figur 2) and a conc et e subs itut e for that a s ract

clas in the schema for the chid (LI_Lineag e in Figur 2)that pro ides the actual implementation of the

pro e ty v lue clas

actualy inclu e l neag e information Metadata for r sour e l neag e (mrl) namesp c does not ne d t o

imp rt the metadata b se (mdb) namespac t o v ldat e, alowing it t o be used as a s an alone mod le

in othe a plcation schema that wish t o as ociat e pro enanc with some model element

E AMP E 1 As ociation from b se metadata clas to a stract property ty e In the b se clas namespace

(mdb), def ine the b se metadata element that has optional property t o various metadata detail clas es (se

NOTE Packa e names are the pref ix names fol owed by “:” in the dia ram T e metadata information

packag e only req ires the line g e information packag e in cases for which a LI_Line g instance wil b pop lat ed

Figure 2 — E ample of an optio al pro erty with a data ty e clas that is defined in a packag e

diferent from the pro erty co tainer clas

< l m en m ax c u s "u b u ded" m in c u s "0" n m e="r s u c L n age"

t p = "mc :Abs tra t_LineageInfor at o _Pro erty yp "/

E AMP E 2 Def inition of a stract element in a stract clas es packa e (mc ); this packag e is the ne us for

using mod larized packa es The a stract elements have no cont ent

The XML clas glo al element cor esp n ing t o the clas (LI_Lineag e) that is the pro e ty ty e for the

o tional at ribut e (r sour eLineag e) in the b se clas ( e Figur 3)

NOTE An a stract clas is implement ed in the metadata common clas es namespace, an used as the targ t

of the optional property.In order to instantiate the property in an XML instance, the namespace that contains a

conc et e clas in the substitution grou for the a stract clas shal b imported (mrl.xsd in this dia ram)

Figure 3— Implementation patt ern for o tio al properties with a data ty e clas in a

dif erent packa e

Stan ard XML Clas Pro e ty Ty e encoding for a s ract clas pro e ty ty e:

< om pl x yp n m e="A bs r c _Li e ge n o m at o _Pr p r yTyp ">

< l m en n m e=" LI_Lineage" s b t t t o Gr u =" mc :Abs tra t_LineageInfor at o "

typ ="m rl:L _Li e ge_Typ "/

A metadata implementation that wi l use the LI_Lineag e element shal imp rt the mrl namespac

8.3.2 Implementation approach to dec ouple optio al clas es

The UML model for XML implementation uses the folowing p tt ern for clas es that ar the data

ty e for pro e ty v lues: w hen the pro e ty v lue ty e is a clas that is implement ed in the same

UML p ckag e as the owning clas , no chang e is made When a pro e ty v lue ty e is a clas that is

implement ed in a dife ent UML p ckag e also in this document (a s ract patt ern shown in Figur 4),

the namesp c s ar de oupled b introd cing an a s ract clas in the a s ract clas es p ckag e in the

implementation UML model Theconc et e clas that r al z sthe a s ract clas is defined in the packag e

for the implementation namesp c , as a spe ialzation of the a s ract clas , c eating a depen ency

betwe n the implementation packag e containing the clas an the a s ract clas es p ckag e This

UML patt ern is then implement ed using ISO/TS 1 1 9:2 0 , 8.5.2 encoding rules for a s ract clas es

Introd ction of the a s ract clas does not chang e the semantics of the model being implement ed, but

alow s for definition of new ve sions of the conc et e implementing clas without imp cting the schema

that uses the a s ract clas Ta le 6 is a l s of the ISO 1 1 5-1 clas es in this document’s UML for XML

implementation that use this p tt ern

The folowing ls detai s the st eps for encoding an a s ract clas t o al ow de oupl ng of XML

a) An a s ract clas an pro e ty ty e ar defined in the a s ract common clas es XML namesp c

packag e, w hich is identifie he e b the namespac a br viation “acn” This namesp c def ines

al a s ract clas es that ar used t o lnk mod les that ar int en ed for s an alone use Not e that

the a s ract clas p ckag e is introd c d in the implementation UML model, an is pur ly an

implementation art efact XML ins anc document wi l neve contain element from thisp ckag e

E AMP E 1 St ep a) def ines an a stract clas (named acn:AbstractClas 2 in this e ample) folowing

NOTE Properties inside of Clas 2 are not shown.

Figure 4 — Example of o tio al pro erty that has a clas property ty e

E AMP E 2 Step a) implementation of a property ty e with a value specif ied by the a stract clas from

e ample 1folowing ISO /TS 1 1 9:2 07, 8.5.2

b) Anothe namesp c ( identified with the a br viation “ ns1” in ex mple 3) contains a clas that has

an o tional pro e ty (cardinalty 0.1 or 0.*) that is spe ified b the a s ract clas def ined a o e

The XML namesp c implementing this clas shal imp rt he namespac that contains the shar d

a s ract element def initions [a br viation “can” ( e ex mples 1 an 2, a o e)]

E AMP E 3 Step b) implementation of XML s hema for a namespace (“ ns1”)that def ines a clas (Clas 1)with a

property that has a data ty e specif ied by the a stract clas from e amples 1an 2

The clas ty e def inition for Clas 1, with a pro e ty (named “ pro e ty” w hose v lue is spe if ied b

Abs ractClas 2 pro e ty ty e: