search

ISO-TC211 / schemas

Official ISO/TC 211 XML Schemas (input to schemas.isotc211.org)
6 stars 8 forks source link

Mapping of ISO 19103 to 19115-3/gco/Record not correct #13

Open ejbleys opened 5 years ago

ejbleijs commented 4 years ago

It has been suggested that an XML implementation schema be generated for ISO 19103 to represent the sub-components of Record RecordType currently typed as CharacterString Record <> type [0..1] RecordType field [1..] RecordType <> fieldType [1..] FieldType Field <> value CharacterString type [0..*] FieldType FieldType <> fieldName CharacterString fieldType TypeName

PeterParslow commented 4 years ago

Will there be a similar thing for pretty much everything in Clause 7 of ISO 19103 - all the core data types?

Exceptions could be where ISO 19139-1 and ISO 19136 Annex E agree on a mapping that doesn't require a UML class. I haven't checked if there are any.

ejbleys commented 4 years ago

Peter Peter wrote:

Will there be a similar thing for pretty much everything in Clause 7 of ISO 19103 - all the core data types?

Response:

All Clause 7 will be managed

Peter wrote:

Exceptions could be where ISO 19139-1 and ISO 19136 Annex E agree on a mapping that doesn't require a UML class. I haven't checked if there are any.

Response: Yes/No - As the existing standards will not be amended purely for this, no exceptions are required Once those standards are updated, the changes would be applied in those amendments/updates

Cheers e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ejbleys@gmail.com Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ejbleijs@gmail.com

On 2019-12-12, at 2:02 pm, Peter Parslow notifications@github.com wrote:

Will there be a similar thing for pretty much everything in Clause 7 of ISO 19103 - all the core data types?

Exceptions could be where ISO 19139-1 and ISO 19136 Annex E agree on a mapping that doesn't require a UML class. I haven't checked if there are any.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ISO-TC211/schemas/issues/13?email_source=notifications&email_token=AIBGJZ4PXTCIW7XGAOOLPWTQYHAWXA5CNFSM4I6XYS72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGVPA7A#issuecomment-564850812, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBGJZ4ZDF5OOX4BE3DUHX3QYHAWXANCNFSM4I6XYS7Q.

PeterParslow commented 4 years ago

"Exceptions": I was meaning things like ISO 19103 CharacterString, which both ISO 19139-1 (7.8.2) & ISO 19136 (Table D.2) map to xs:string.

I thought that would mean that those parts of ISO 19103 Clause 7 won't need to be represented by XML schema fragments.

ejbleys commented 4 years ago

Sorry my misunderstanding We should adopt xs: types wherever available E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ejbleys@gmail.com Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ejbleijs@gmail.com

On 2019-12-12, at 3:43 pm, Peter Parslow notifications@github.com wrote:

"Exceptions": I was meaning things like ISO 19103 CharacterString, which both ISO 19139-1 (7.8.2) & ISO 19136 (Table D.2) map to xs:string.

I thought that would mean that those parts of ISO 19103 Clause 7 won't need to be represented by XML schema fragments.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ISO-TC211/schemas/issues/13?email_source=notifications&email_token=AIBGJZ4ILJ3YXQPCIRUMIU3QYHMQXA5CNFSM4I6XYS72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGVURRY#issuecomment-564873415, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBGJZ3Q2IWRR5BOKRVAXQLQYHMQXANCNFSM4I6XYS7Q.