XSD 19115/-3/msr/1.0/spatialRepresentationImagery.xsd references to the undeclared elements/types

[Intelligent2013]

In 19115/-3/msr/1.0/spatialRepresentationImagery.xsd there are a references to undeclared elements/types:

• msr:MD_Georectified
• msr:MD_Georectified_Type
• msr:MD_Georeferenceable
• msr:MD_Georeferenceable_Type

[ronaldtse]

This is blocking ISO-TC211/schemas.isotc211.org#18.

[ronaldtse]

@Intelligent2013 aren't these defined in :

https://github.com/ISO-TC211/schemas/blob/b70b661369619800a91bef0f32484f18780c17ec/19115/-3/msr/1.0/spatialRepresentationImagery.xsd ?

[Intelligent2013]

@ronaldtse there are only references, but aren't declarations. But here is a note from Altova XmlSpy:

May be we shouldn't build xsd documentation for this xsd, because it's a part of another xsd, i.e. it isn't standalone xsd? But how to determine for which of XSDs we need to build xsd documentation?

[ejbleys]

I will look at the code, but current version is .../19115/-1/msr/1.3.0/msr.xsd

Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

On 6 Apr 2021, at 05:37, Alexander Dyuzhev @.***> wrote:

 @ronaldtse there are only references, but aren't declarations. But here is a note from Altova XmlSpy:

May be we shouldn't build xsd documentation for this xsd, because it's a part of another xsd, i.e. it isn't standalone xsd? But how to determine for which of XSDs we need to build xsd documentation?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[ronaldtse]

@Intelligent2013 we can only build documentation for valid XSDs, so let’s keep a separate file (YAML) to contain the list of XSD files we want to build.

@ejbleys if we encounter errors in non-current XSDs, should we correct them or should we let them linger on?

[ejbleys]

commission errors - correct omissions errors - ignore E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia +61 (0)2 62811773 +61 (0)411 483 876 @. Skype @.

On 2021-04-06, at 11:14 am, Ronald Tse @.***> wrote:

@Intelligent2013 https://github.com/Intelligent2013 we can only build documentation for valid XSDs, so let’s keep a separate file (YAML) to contain the list of XSD files we want to build.

@ejbleys https://github.com/ejbleys if we encounter errors in non-current XSDs, should we correct them or should we let them linger on?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ISO-TC211/schemas/issues/36#issuecomment-813753149, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBGJZ5OOVEFXYECJA3TZVTTHJN6JANCNFSM42M52DBA.

[ejbleys]

Corrected in https://github.com/ISO-TC211/schemas/blob/master/19115/-3/msr/1.0/spatialRepresentation.xsd https://github.com/ISO-TC211/schemas/blob/master/19115/-3/msr/2.0/spatialRepresentation.xsd https://github.com/ISO-TC211/schemas/blob/master/19115/-1/msr/1.3.0/spatialRepresentation.xsd had not correctly element:substitutionGroup= and extension:base= to msr:AbstractMD_SpatialRepresentation (was msr:MD_SpatialRepresentation)

Cheers e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia +61 (0)2 62811773 +61 (0)411 483 876 @. Skype @.

On 2021-04-06, at 12:47 pm, Evert Bleys @.***> wrote:

commission errors - correct omissions errors - ignore E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia +61 (0)2 62811773 +61 (0)411 483 876 @. @.> Skype @. @.>

On 2021-04-06, at 11:14 am, Ronald Tse @. @.>> wrote:

@Intelligent2013 https://github.com/Intelligent2013 we can only build documentation for valid XSDs, so let’s keep a separate file (YAML) to contain the list of XSD files we want to build.

@ejbleys https://github.com/ejbleys if we encounter errors in non-current XSDs, should we correct them or should we let them linger on?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ISO-TC211/schemas/issues/36#issuecomment-813753149, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBGJZ5OOVEFXYECJA3TZVTTHJN6JANCNFSM42M52DBA.

[Intelligent2013]

@Intelligent2013 we can only build documentation for valid XSDs, so let’s keep a separate file (YAML) to contain the list of XSD files we want to build.

@ronaldtse I've added a file schemas.yml processing for list of XSD files (in https://github.com/ISO-TC211/schemas.isotc211.org/pull/19)

[ronaldtse]

Thanks @ejbleys and @Intelligent2013 . @Intelligent2013 is this issue done now?

[ejbleys]

Hi Ron I believe it is sorted E

Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

On 15 Apr 2021, at 02:58, Ronald Tse @.***> wrote:

 Thanks @ejbleys and @Intelligent2013 . @Intelligent2013 is this issue done now?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Intelligent2013]

Yes, fixed. Thank you. Closing.

[ronaldtse]

Thanks!