Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" #217

MartinePaepen · 2021-05-04T17:02:33Z

At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata.
Validation was always possible however now some links are broken.
How can we update our metadata files using the currently applicable xsd schema's?

Attached you can find an example that doesn't validate any more.
example INSPIRE file.txt

The validation error is:
The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid.
Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd' referenced by xs:import definition does not refer to a valid schema document.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta / title
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta / link
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta / link / link
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta / link / link / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Neither an element declaration nor a type definition is known for element . Strict assessment failed.
Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta
Details
cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed.
.......
......
....
src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition.
'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type.
Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type
Details
src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition.
Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors.

ejbleys · 2021-05-05T04:27:54Z

Your location for schemas seems correct <?xml version="1.0" encoding="utf-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" version="0.1" xmlns:xs="http://www.w3.org/2001/XMLSchema">  <xs:annotation> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gmx" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd"/> <xs:include schemaLocation="metadataEntitySet.xsd"/> <xs:include schemaLocation="contentInformation.xsd"/> <xs:include schemaLocation="dataQualityInformation.xsd"/> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> </xs:schema> It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 I substituted the above for http://www.isotc211.org/2005/gmi in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) Cheers e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***

…

On 2021-05-05, at 3:02 am, MartinePaepen ***@***.***> wrote: At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. Validation was always possible however now some links are broken. How can we update our metadata files using the currently applicable xsd schema's? Attached you can find an example that doesn't validate any more. example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> The validation error is: The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta / title Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta / link Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta / link / link Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta / link / link / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. Neither an element declaration nor a type definition is known for element . Strict assessment failed. Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta Details cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. ....... ...... .... src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> Details src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>.

ejbleys · 2021-05-05T04:43:13Z

Apologies It appears that the substitution LE_ClassName for LI_ClassName fails Interesting - didn’t fail first round - I will investigate E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***

…

On 2021-05-05, at 2:27 pm, Evert J Bleys ***@***.***> wrote: Your location for schemas seems correct <?xml version="1.0" encoding="utf-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0>" xmlns:gco="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco>" xmlns:gmd="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd>" xmlns:gmx="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx>" xmlns:gss="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss>" version="0.1" xmlns:xs="http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema>">  <xs:annotation> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd>" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd <https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd>"/> <xs:import namespace="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco>" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd <https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd>"/> <xs:import namespace="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss>" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd <https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd>"/> <xs:import namespace="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx>" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd <https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd>"/> <xs:include schemaLocation="metadataEntitySet.xsd"/> <xs:include schemaLocation="contentInformation.xsd"/> <xs:include schemaLocation="dataQualityInformation.xsd"/> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> </xs:schema> It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0> I substituted the above for http://www.isotc211.org/2005/gmi <http://www.isotc211.org/2005/gmi> in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) Cheers e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** ***@***.***> Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.*** ***@***.***> > On 2021-05-05, at 3:02 am, MartinePaepen ***@***.*** ***@***.***>> wrote: > > > At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. > Validation was always possible however now some links are broken. > How can we update our metadata files using the currently applicable xsd schema's? > > Attached you can find an example that doesn't validate any more. > example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> > The validation error is: > The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. > Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta / title > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta / link > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta / link / link > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta / link / link / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Neither an element declaration nor a type definition is known for element . Strict assessment failed. > Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta > Details > cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > ....... > ...... > .... > src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. > 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. > Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> > Details > src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. > Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>. >

ejbleys · 2021-05-05T04:44:02Z

Retract Does work e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***

…

On 2021-05-05, at 2:43 pm, Evert J Bleys ***@***.***> wrote: Apologies It appears that the substitution LE_ClassName for LI_ClassName fails Interesting - didn’t fail first round - I will investigate E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** ***@***.***> Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.*** ***@***.***> > On 2021-05-05, at 2:27 pm, Evert J Bleys ***@***.*** ***@***.***>> wrote: > > Your location for schemas seems correct > > <?xml version="1.0" encoding="utf-8"?> > <xs:schema elementFormDefault="qualified" > targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0>" > xmlns:gco="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco>" > xmlns:gmd="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd>" > xmlns:gmx="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx>" > xmlns:gss="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss>" > version="0.1" > xmlns:xs="http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema>"> >  > <xs:annotation> > <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> > </xs:annotation> >  > <xs:import namespace="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd>" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd <https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd>"/> > <xs:import namespace="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco>" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd <https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd>"/> > <xs:import namespace="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss>" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd <https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd>"/> > <xs:import namespace="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx>" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd <https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd>"/> > <xs:include schemaLocation="metadataEntitySet.xsd"/> > <xs:include schemaLocation="contentInformation.xsd"/> > <xs:include schemaLocation="dataQualityInformation.xsd"/> > <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> > </xs:schema> > > It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0> > I substituted the above for http://www.isotc211.org/2005/gmi <http://www.isotc211.org/2005/gmi> in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) > > Cheers > e > Evert Bleys > 4 Tudor Place > HUGHES ACT 2605 > Australia > email: ***@***.*** ***@***.***> > Mob: +61 (0)411 483 876 > Land: +61 (0)2 6281 1773 > Skype: ***@***.*** ***@***.***> > > > > >> On 2021-05-05, at 3:02 am, MartinePaepen ***@***.*** ***@***.***>> wrote: >> >> >> At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. >> Validation was always possible however now some links are broken. >> How can we update our metadata files using the currently applicable xsd schema's? >> >> Attached you can find an example that doesn't validate any more. >> example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> >> The validation error is: >> The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. >> Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / title >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> ....... >> ...... >> .... >> src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. >> 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. >> Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> >> Details >> src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. >> Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. >> >> — >> You are receiving this because you are subscribed to this thread. >> Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>. >> >

MartinePaepen · 2021-05-06T08:41:40Z

Dearn Evert, Thanks for the feedback. However I have replaced the schema: gmi:MI_Metadata xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <gmd:language> <gmi:MI_Metadata xsi:schemaLocation="http://standards.iso.org/iso/19115/-2/gmi/1.0 http://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd" xmlns:gmi="http://standards.iso.org/iso/19115/-2/gmi/1.0" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> And the validation error is still: [Altova XMLSpy - [INSPIRE (4).txt *]] So there seems to be a redirect to the schema's which doesn't exist anymore. Could you please check? Many thanks, Martine From: ejbleys ***@***.***> Sent: Wednesday, 5 May 2021 06:44 To: ISO-TC211/XML ***@***.***> Cc: Paepen Martine ***@***.***>; Author ***@***.***> Subject: Re: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) Retract Does work e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.***<mailto:***@***.***> Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***<mailto:***@***.***>

On 2021-05-05, at 2:43 pm, Evert J Bleys ***@***.***<mailto:***@***.***>> wrote: Apologies It appears that the substitution LE_ClassName for LI_ClassName fails Interesting - didn't fail first round - I will investigate E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > On 2021-05-05, at 2:27 pm, Evert J Bleys ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: > > Your location for schemas seems correct > > <?xml version="1.0" encoding="utf-8"?> > <xs:schema elementFormDefault="qualified" > targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0><http://standards.iso.org/iso/19115/-2/gmi/1.0%20%3chttp:/standards.iso.org/iso/19115/-2/gmi/1.0%3e>" > xmlns:gco="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" > xmlns:gmd="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" > xmlns:gmx="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" > xmlns:gss="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" > version="0.1" > xmlns:xs="http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema><http://www.w3.org/2001/XMLSchema%20%3chttp:/www.w3.org/2001/XMLSchema%3e>"> >  > <xs:annotation> > <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> > </xs:annotation> >  > <xs:import namespace="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd <https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd><https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%3e>"/> > <xs:import namespace="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd <https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd><https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%3e>"/> > <xs:import namespace="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd <https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd><https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%3e>"/> > <xs:import namespace="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd <https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd><https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%3e>"/> > <xs:include schemaLocation="metadataEntitySet.xsd"/> > <xs:include schemaLocation="contentInformation.xsd"/> > <xs:include schemaLocation="dataQualityInformation.xsd"/> > <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> > </xs:schema> > > It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0> > I substituted the above for http://www.isotc211.org/2005/gmi <http://www.isotc211.org/2005/gmi> in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) > > Cheers > e > Evert Bleys > 4 Tudor Place > HUGHES ACT 2605 > Australia > email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > Mob: +61 (0)411 483 876 > Land: +61 (0)2 6281 1773 > Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > > > > >> On 2021-05-05, at 3:02 am, MartinePaepen ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: >> >> >> At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. >> Validation was always possible however now some links are broken. >> How can we update our metadata files using the currently applicable xsd schema's? >> >> Attached you can find an example that doesn't validate any more. >> example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> >> The validation error is: >> The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. >> Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / title >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta >> Details >> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >> ....... >> ...... >> .... >> src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. >> 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. >> Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> >> Details >> src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. >> Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. >> >> - >> You are receiving this because you are subscribed to this thread. >> Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>. >> >

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FISO-TC211%2FXML%2Fissues%2F217%23issuecomment-832407236&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603352307%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=brmf3%2FtGRvaHQGho5pGIAfO7WZqbGeo2bUn1daceXw8%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLMHWFZ7SXPRODGPY2F7LTTMDEKBANCNFSM44DCZSXA&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603362301%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W6W10ZnAJlja4pVSHied6iQ6yeexXpz%2BY5Br6dyVe8I%3D&reserved=0>. VITO Disclaimer: http://www.vito.be/e-maildisclaimer

MartinePaepen · 2021-05-06T10:02:59Z

Dear Evert, As you can see in the https://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" version="0.1">  <xs:annotation> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gmx" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmx/gmx.xsd"/> <xs:include schemaLocation="metadataEntitySet.xsd"/> <xs:include schemaLocation="contentInformation.xsd"/> <xs:include schemaLocation="dataQualityInformation.xsd"/> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> </xs:schema> They refer to http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd Which don't exist. Kind regards, Martine

MartinePaepen · 2021-05-06T10:10:36Z

Dear Evert, I get always the same errors because of unexisting http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd"/<http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd%22/>> Taking https://www.isotc211.org/2005/gmi/gmi.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1">  <xs:annotation> <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:37 ====== </xs:documentation> </xs:annotation>  <xs:include schemaLocation="../gmi/metadataEntitySet.xsd"/> <xs:include schemaLocation="../gmi/acquisitionInformation.xsd"/> <xs:include schemaLocation="../gmi/dataQualityInformation.xsd"/> <xs:include schemaLocation="../gmi/spatialRepresentationInformation.xsd"/> <xs:include schemaLocation="../gmi/contentInformation.xsd"/>    </xs:schema> https://www.isotc211.org/2005/gmi/acquisitionInformation.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gmd="http://www.isotc211.org/2005/gmd" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1">  <xs:annotation> <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:36 ====== </xs:documentation> <xs:documentation>2012-12-08: Documentation of MI_Objective_Type. Typo reported by XMG: "temportal" replaced by "temporal".</xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/>    <xs:complexType name="MI_Requirement_Type"> <xs:annotation> <xs:documentation>Description: requirement to be satisfied by the planned data acquisition - shortName: Requirement</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="gco:AbstractObject_Type"> <xs:sequence> <xs:element name="citation" type="gmd:CI_Citation_PropertyType" minOccurs="0"/> <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType"/> <xs:element name="requestor" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> <xs:element name="recipient" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> <xs:element name="priority" type="gmi:MI_PriorityCode_PropertyType"/> <xs:element name="requestedDate" type="gmi:MI_RequestedDate_PropertyType"/> <xs:element name="expiryDate" type="gco:DateTime_PropertyType"/> <xs:element name="satisifiedPlan" type="gmi:MI_Plan_PropertyType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>  <xs:element name="MI_Requirement" type="gmi:MI_Requirement_Type"/>  <xs:complexType name="MI_Requirement_PropertyType"> <xs:sequence> <xs:element ref="gmi:MI_Requirement" minOccurs="0"/> </xs:sequence> <xs:attributeGroup ref="gco:ObjectReference"/> <xs:attribute ref="gco:nilReason"/> </xs:complexType>  <xs:complexType name="MI_Objective_Type"> <xs:annotation> <xs:documentation>Description: Describes the characteristics, spatial and temporal extent of the intended object to be observed - shortName: TargetId</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="gco:AbstractObject_Type"> <xs:sequence> <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType" maxOccurs="unbounded"/> <xs:element name="priority" type="gco:CharacterString_PropertyType" minOccurs="0"/> <xs:element name="type" type="gmi:MI_ObjectiveTypeCode_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="function" type="gco:CharacterString_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="extent" type="gmd:EX_Extent_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="pass" type="gmi:MI_PlatformPass_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="sensingInstrument" type="gmi:MI_Instrume

MartinePaepen · 2021-05-06T13:20:55Z

There seems to be an issue with:
https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd

The targetNamespace is still: targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0"

==> this generates anerror while validating /
Shouldn't it be ==> https://schemas.isotc211.org/19115/-2/gmi/1.0

<xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" version="0.1">

xs:annotation
xs:documentationThis file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation>
</xs:annotation>

<xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/gmx" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd"/>
<xs:include schemaLocation="metadataEntitySet.xsd"/>
<xs:include schemaLocation="contentInformation.xsd"/>
<xs:include schemaLocation="dataQualityInformation.xsd"/>
<xs:include schemaLocation="spatialRepresentationInformation.xsd"/>
</xs:schema>

MartinePaepen · 2021-05-06T15:01:39Z

It works when using: xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd
However which is the recommended xsd to be used for MI_metadata?
http://www.isotc211.org/2005/gmi/gmi.xsd
or
https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd

ejbleys · 2021-05-06T20:53:06Z

Hi The location for the schemas should be https://schemas.isotc211.org/... I’m doing this on my phone so I might have misunderstood E Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

…

On 6 May 2021, at 20:10, MartinePaepen ***@***.***> wrote: Dear Evert, I get always the same errors because of unexisting http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd"/<http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd%22/>> Taking https://www.isotc211.org/2005/gmi/gmi.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1">  <xs:annotation> <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:37 ====== </xs:documentation> </xs:annotation>  <xs:include schemaLocation="../gmi/metadataEntitySet.xsd"/> <xs:include schemaLocation="../gmi/acquisitionInformation.xsd"/> <xs:include schemaLocation="../gmi/dataQualityInformation.xsd"/> <xs:include schemaLocation="../gmi/spatialRepresentationInformation.xsd"/> <xs:include schemaLocation="../gmi/contentInformation.xsd"/>    </xs:schema> https://www.isotc211.org/2005/gmi/acquisitionInformation.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gmd="http://www.isotc211.org/2005/gmd" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1">  <xs:annotation> <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:36 ====== </xs:documentation> <xs:documentation>2012-12-08: Documentation of MI_Objective_Type. Typo reported by XMG: "temportal" replaced by "temporal".</xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/>    <xs:complexType name="MI_Requirement_Type"> <xs:annotation> <xs:documentation>Description: requirement to be satisfied by the planned data acquisition - shortName: Requirement</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="gco:AbstractObject_Type"> <xs:sequence> <xs:element name="citation" type="gmd:CI_Citation_PropertyType" minOccurs="0"/> <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType"/> <xs:element name="requestor" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> <xs:element name="recipient" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> <xs:element name="priority" type="gmi:MI_PriorityCode_PropertyType"/> <xs:element name="requestedDate" type="gmi:MI_RequestedDate_PropertyType"/> <xs:element name="expiryDate" type="gco:DateTime_PropertyType"/> <xs:element name="satisifiedPlan" type="gmi:MI_Plan_PropertyType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>  <xs:element name="MI_Requirement" type="gmi:MI_Requirement_Type"/>  <xs:complexType name="MI_Requirement_PropertyType"> <xs:sequence> <xs:element ref="gmi:MI_Requirement" minOccurs="0"/> </xs:sequence> <xs:attributeGroup ref="gco:ObjectReference"/> <xs:attribute ref="gco:nilReason"/> </xs:complexType>  <xs:complexType name="MI_Objective_Type"> <xs:annotation> <xs:documentation>Description: Describes the characteristics, spatial and temporal extent of the intended object to be observed - shortName: TargetId</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="gco:AbstractObject_Type"> <xs:sequence> <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType" maxOccurs="unbounded"/> <xs:element name="priority" type="gco:CharacterString_PropertyType" minOccurs="0"/> <xs:element name="type" type="gmi:MI_ObjectiveTypeCode_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="function" type="gco:CharacterString_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="extent" type="gmd:EX_Extent_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="pass" type="gmi:MI_PlatformPass_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="sensingInstrument" type="gmi:MI_Instrume From: Paepen Martine Sent: Thursday, 6 May 2021 12:03 To: ISO-TC211/XML ***@***.***>; ISO-TC211/XML ***@***.***> Cc: Author ***@***.***> Subject: RE: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) Dear Evert, As you can see in the https://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd This XML file does not appear to have any style information associated with it. The document tree is shown below. <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" version="0.1">  <xs:annotation> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> </xs:annotation>  <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gmx" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmx/gmx.xsd"/> <xs:include schemaLocation="metadataEntitySet.xsd"/> <xs:include schemaLocation="contentInformation.xsd"/> <xs:include schemaLocation="dataQualityInformation.xsd"/> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> </xs:schema> They refer to http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd Which don't exist. Kind regards, Martine From: Paepen Martine Sent: Thursday, 6 May 2021 10:42 To: 'ISO-TC211/XML' ***@***.******@***.***>>; ISO-TC211/XML ***@***.******@***.***>> Cc: Author ***@***.******@***.***>> Subject: RE: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) Dearn Evert, Thanks for the feedback. However I have replaced the schema: gmi:MI_Metadata xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd<http://www.isotc211.org/2005/gmi%20http:/www.isotc211.org/2005/gmi/gmi.xsd>" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <gmd:language> <gmi:MI_Metadata xsi:schemaLocation="http://standards.iso.org/iso/19115/-2/gmi/1.0 http://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd<http://standards.iso.org/iso/19115/-2/gmi/1.0%20http:/standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd>" xmlns:gmi="http://standards.iso.org/iso/19115/-2/gmi/1.0" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> And the validation error is still: [Altova XMLSpy - [INSPIRE (4).txt *]] So there seems to be a redirect to the schema's which doesn't exist anymore. Could you please check? Many thanks, Martine From: ejbleys ***@***.******@***.***>> Sent: Wednesday, 5 May 2021 06:44 To: ISO-TC211/XML ***@***.******@***.***>> Cc: Paepen Martine ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) Retract Does work e Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.***<mailto:***@***.***> Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***<mailto:***@***.***> > On 2021-05-05, at 2:43 pm, Evert J Bleys ***@***.***<mailto:***@***.***>> wrote: > > Apologies > It appears that the substitution LE_ClassName for LI_ClassName fails > Interesting - didn't fail first round - I will investigate > > E > Evert Bleys > 4 Tudor Place > HUGHES ACT 2605 > Australia > email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > Mob: +61 (0)411 483 876 > Land: +61 (0)2 6281 1773 > Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > > > > >> On 2021-05-05, at 2:27 pm, Evert J Bleys ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: >> >> Your location for schemas seems correct >> >> <?xml version="1.0" encoding="utf-8"?> >> <xs:schema elementFormDefault="qualified" >> targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0><http://standards.iso.org/iso/19115/-2/gmi/1.0%20%3chttp:/standards.iso.org/iso/19115/-2/gmi/1.0%3e>" >> xmlns:gco="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" >> xmlns:gmd="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" >> xmlns:gmx="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" >> xmlns:gss="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" >> version="0.1" >> xmlns:xs="http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema><http://www.w3.org/2001/XMLSchema%20%3chttp:/www.w3.org/2001/XMLSchema%3e>"> >>  >> <xs:annotation> >> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> >> </xs:annotation> >>  >> <xs:import namespace="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd <https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd><https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%3e>"/> >> <xs:import namespace="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd <https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd><https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%3e>"/> >> <xs:import namespace="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd <https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd><https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%3e>"/> >> <xs:import namespace="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd <https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd><https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%3e>"/> >> <xs:include schemaLocation="metadataEntitySet.xsd"/> >> <xs:include schemaLocation="contentInformation.xsd"/> >> <xs:include schemaLocation="dataQualityInformation.xsd"/> >> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> >> </xs:schema> >> >> It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0> >> I substituted the above for http://www.isotc211.org/2005/gmi <http://www.isotc211.org/2005/gmi> in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) >> >> Cheers >> e >> Evert Bleys >> 4 Tudor Place >> HUGHES ACT 2605 >> Australia >> email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> >> Mob: +61 (0)411 483 876 >> Land: +61 (0)2 6281 1773 >> Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> >> >> >> >> >>> On 2021-05-05, at 3:02 am, MartinePaepen ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: >>> >>> >>> At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. >>> Validation was always possible however now some links are broken. >>> How can we update our metadata files using the currently applicable xsd schema's? >>> >>> Attached you can find an example that doesn't validate any more. >>> example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> >>> The validation error is: >>> The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. >>> Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta / title >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta / link >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta / link / link >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta >>> Details >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. >>> ....... >>> ...... >>> .... >>> src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. >>> 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. >>> Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> >>> Details >>> src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. >>> Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. >>> >>> - >>> You are receiving this because you are subscribed to this thread. >>> Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>. >>> >> > - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FISO-TC211%2FXML%2Fissues%2F217%23issuecomment-832407236&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603352307%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=brmf3%2FtGRvaHQGho5pGIAfO7WZqbGeo2bUn1daceXw8%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLMHWFZ7SXPRODGPY2F7LTTMDEKBANCNFSM44DCZSXA&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603362301%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W6W10ZnAJlja4pVSHied6iQ6yeexXpz%2BY5Br6dyVe8I%3D&reserved=0>. VITO Disclaimer: http://www.vito.be/e-maildisclaimer — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

ejbleys · 2021-05-06T21:03:02Z

Not 100% sure if the namespace URI is http://standards... but I am sure it is not https://schemas... E Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

…

On 7 May 2021, at 06:53, Evert J Bleys ***@***.***> wrote: Hi The location for the schemas should be https://schemas.isotc211.org/... I’m doing this on my phone so I might have misunderstood E Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876 >> On 6 May 2021, at 20:10, MartinePaepen ***@***.***> wrote: >> > > Dear Evert, > > I get always the same errors because of unexisting http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd"/<http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/.......xsd%22/>> > > Taking https://www.isotc211.org/2005/gmi/gmi.xsd > This XML file does not appear to have any style information associated with it. The document tree is shown below. > <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1"> >  > <xs:annotation> > <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:37 ====== </xs:documentation> > </xs:annotation> >  > <xs:include schemaLocation="../gmi/metadataEntitySet.xsd"/> > <xs:include schemaLocation="../gmi/acquisitionInformation.xsd"/> > <xs:include schemaLocation="../gmi/dataQualityInformation.xsd"/> > <xs:include schemaLocation="../gmi/spatialRepresentationInformation.xsd"/> > <xs:include schemaLocation="../gmi/contentInformation.xsd"/> >  >  >  > </xs:schema> > > https://www.isotc211.org/2005/gmi/acquisitionInformation.xsd > This XML file does not appear to have any style information associated with it. The document tree is shown below. > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gmd="http://www.isotc211.org/2005/gmd" targetNamespace="http://www.isotc211.org/2005/gmi" elementFormDefault="qualified" version="0.1"> >  > <xs:annotation> > <xs:documentation>This file was generated from ISO TC/211 UML class diagrams == 07-30-2010 11:34:36 ====== </xs:documentation> > <xs:documentation>2012-12-08: Documentation of MI_Objective_Type. Typo reported by XMG: "temportal" replaced by "temporal".</xs:documentation> > </xs:annotation> >  > <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> > <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> > <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/> >  >  >  > <xs:complexType name="MI_Requirement_Type"> > <xs:annotation> > <xs:documentation>Description: requirement to be satisfied by the planned data acquisition - shortName: Requirement</xs:documentation> > </xs:annotation> > <xs:complexContent> > <xs:extension base="gco:AbstractObject_Type"> > <xs:sequence> > <xs:element name="citation" type="gmd:CI_Citation_PropertyType" minOccurs="0"/> > <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType"/> > <xs:element name="requestor" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> > <xs:element name="recipient" type="gmd:CI_ResponsibleParty_PropertyType" maxOccurs="unbounded"/> > <xs:element name="priority" type="gmi:MI_PriorityCode_PropertyType"/> > <xs:element name="requestedDate" type="gmi:MI_RequestedDate_PropertyType"/> > <xs:element name="expiryDate" type="gco:DateTime_PropertyType"/> > <xs:element name="satisifiedPlan" type="gmi:MI_Plan_PropertyType" minOccurs="0" maxOccurs="unbounded"/> > </xs:sequence> > </xs:extension> > </xs:complexContent> > </xs:complexType> >  > <xs:element name="MI_Requirement" type="gmi:MI_Requirement_Type"/> >  > <xs:complexType name="MI_Requirement_PropertyType"> > <xs:sequence> > <xs:element ref="gmi:MI_Requirement" minOccurs="0"/> > </xs:sequence> > <xs:attributeGroup ref="gco:ObjectReference"/> > <xs:attribute ref="gco:nilReason"/> > </xs:complexType> >  > <xs:complexType name="MI_Objective_Type"> > <xs:annotation> > <xs:documentation>Description: Describes the characteristics, spatial and temporal extent of the intended object to be observed - shortName: TargetId</xs:documentation> > </xs:annotation> > <xs:complexContent> > <xs:extension base="gco:AbstractObject_Type"> > <xs:sequence> > <xs:element name="identifier" type="gmd:MD_Identifier_PropertyType" maxOccurs="unbounded"/> > <xs:element name="priority" type="gco:CharacterString_PropertyType" minOccurs="0"/> > <xs:element name="type" type="gmi:MI_ObjectiveTypeCode_PropertyType" minOccurs="0" maxOccurs="unbounded"/> > <xs:element name="function" type="gco:CharacterString_PropertyType" minOccurs="0" maxOccurs="unbounded"/> > <xs:element name="extent" type="gmd:EX_Extent_PropertyType" minOccurs="0" maxOccurs="unbounded"/> > <xs:element name="pass" type="gmi:MI_PlatformPass_PropertyType" minOccurs="0" maxOccurs="unbounded"/> > <xs:element name="sensingInstrument" type="gmi:MI_Instrume > > > From: Paepen Martine > Sent: Thursday, 6 May 2021 12:03 > To: ISO-TC211/XML ***@***.***>; ISO-TC211/XML ***@***.***> > Cc: Author ***@***.***> > Subject: RE: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) > > Dear Evert, > > As you can see in the > https://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd > This XML file does not appear to have any style information associated with it. The document tree is shown below. > <xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" version="0.1"> >  > <xs:annotation> > <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> > </xs:annotation> >  > <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd"/> > <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd"/> > <xs:import namespace="http://www.isotc211.org/2005/gss" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gss/gss.xsd"/> > <xs:import namespace="http://www.isotc211.org/2005/gmx" schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmx/gmx.xsd"/> > <xs:include schemaLocation="metadataEntitySet.xsd"/> > <xs:include schemaLocation="contentInformation.xsd"/> > <xs:include schemaLocation="dataQualityInformation.xsd"/> > <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> > </xs:schema> > > They refer to http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd > Which don't exist. > > Kind regards, > Martine > > > From: Paepen Martine > Sent: Thursday, 6 May 2021 10:42 > To: 'ISO-TC211/XML' ***@***.******@***.***>>; ISO-TC211/XML ***@***.******@***.***>> > Cc: Author ***@***.******@***.***>> > Subject: RE: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) > > Dearn Evert, > > Thanks for the feedback. > However I have replaced the schema: > gmi:MI_Metadata xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd<http://www.isotc211.org/2005/gmi%20http:/www.isotc211.org/2005/gmi/gmi.xsd>" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <gmd:language> > > > <gmi:MI_Metadata xsi:schemaLocation="http://standards.iso.org/iso/19115/-2/gmi/1.0 http://standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd<http://standards.iso.org/iso/19115/-2/gmi/1.0%20http:/standards.iso.org/iso/19115/-2/gmi/1.0/gmi.xsd>" xmlns:gmi="http://standards.iso.org/iso/19115/-2/gmi/1.0" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > > And the validation error is still: > [Altova XMLSpy - [INSPIRE (4).txt *]] > > So there seems to be a redirect to the schema's which doesn't exist anymore. > Could you please check? > > Many thanks, > Martine > > From: ejbleys ***@***.******@***.***>> > Sent: Wednesday, 5 May 2021 06:44 > To: ISO-TC211/XML ***@***.******@***.***>> > Cc: Paepen Martine ***@***.******@***.***>>; Author ***@***.******@***.***>> > Subject: Re: [ISO-TC211/XML] Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" (#217) > > Retract > Does work > e > Evert Bleys > 4 Tudor Place > HUGHES ACT 2605 > Australia > email: ***@***.***<mailto:***@***.***> > Mob: +61 (0)411 483 876 > Land: +61 (0)2 6281 1773 > Skype: ***@***.***<mailto:***@***.***> > > > > > > On 2021-05-05, at 2:43 pm, Evert J Bleys ***@***.***<mailto:***@***.***>> wrote: > > > > Apologies > > It appears that the substitution LE_ClassName for LI_ClassName fails > > Interesting - didn't fail first round - I will investigate > > > > E > > Evert Bleys > > 4 Tudor Place > > HUGHES ACT 2605 > > Australia > > email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > > Mob: +61 (0)411 483 876 > > Land: +61 (0)2 6281 1773 > > Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > > > > > > > > > >> On 2021-05-05, at 2:27 pm, Evert J Bleys ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: > >> > >> Your location for schemas seems correct > >> > >> <?xml version="1.0" encoding="utf-8"?> > >> <xs:schema elementFormDefault="qualified" > >> targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0><http://standards.iso.org/iso/19115/-2/gmi/1.0%20%3chttp:/standards.iso.org/iso/19115/-2/gmi/1.0%3e>" > >> xmlns:gco="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" > >> xmlns:gmd="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" > >> xmlns:gmx="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" > >> xmlns:gss="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" > >> version="0.1" > >> xmlns:xs="http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema><http://www.w3.org/2001/XMLSchema%20%3chttp:/www.w3.org/2001/XMLSchema%3e>"> > >>  > >> <xs:annotation> > >> <xs:documentation>This file was created by Ted Habermann during May 2015 to correct omissions (gmx, MI_EnvironmentalRecord) in existing gmi schema ====== </xs:documentation> > >> </xs:annotation> > >>  > >> <xs:import namespace="http://www.isotc211.org/2005/gmd <http://www.isotc211.org/2005/gmd><http://www.isotc211.org/2005/gmd%20%3chttp:/www.isotc211.org/2005/gmd%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd <https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd><https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd%3e>"/> > >> <xs:import namespace="http://www.isotc211.org/2005/gco <http://www.isotc211.org/2005/gco><http://www.isotc211.org/2005/gco%20%3chttp:/www.isotc211.org/2005/gco%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd <https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd><https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gco/1.0/gco.xsd%3e>"/> > >> <xs:import namespace="http://www.isotc211.org/2005/gss <http://www.isotc211.org/2005/gss><http://www.isotc211.org/2005/gss%20%3chttp:/www.isotc211.org/2005/gss%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd <https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd><https://schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gss/1.0/gss.xsd%3e>"/> > >> <xs:import namespace="http://www.isotc211.org/2005/gmx <http://www.isotc211.org/2005/gmx><http://www.isotc211.org/2005/gmx%20%3chttp:/www.isotc211.org/2005/gmx%3e>" schemaLocation="https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd <https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd><https://schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%20%3chttps:/schemas.isotc211.org/19139/-/gmx/1.0/gmx.xsd%3e>"/> > >> <xs:include schemaLocation="metadataEntitySet.xsd"/> > >> <xs:include schemaLocation="contentInformation.xsd"/> > >> <xs:include schemaLocation="dataQualityInformation.xsd"/> > >> <xs:include schemaLocation="spatialRepresentationInformation.xsd"/> > >> </xs:schema> > >> > >> It appears that the namespace for gmi is http://standards.iso.org/iso/19115/-2/gmi/1.0 <http://standards.iso.org/iso/19115/-2/gmi/1.0> > >> I substituted the above for http://www.isotc211.org/2005/gmi <http://www.isotc211.org/2005/gmi> in xmlns:gmi and in namespace component of xsi:schemaLocation - file then validated (in oXygen) > >> > >> Cheers > >> e > >> Evert Bleys > >> 4 Tudor Place > >> HUGHES ACT 2605 > >> Australia > >> email: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > >> Mob: +61 (0)411 483 876 > >> Land: +61 (0)2 6281 1773 > >> Skype: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > >> > >> > >> > >> > >>> On 2021-05-05, at 3:02 am, MartinePaepen ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>>> wrote: > >>> > >>> > >>> At VITO we have generated INSPIRE metadata files wrt the ISO 19115-2 gmi metadata. > >>> Validation was always possible however now some links are broken. > >>> How can we update our metadata files using the currently applicable xsd schema's? > >>> > >>> Attached you can find an example that doesn't validate any more. > >>> example INSPIRE file.txt <https://github.com/ISO-TC211/XML/files/6422713/example.INSPIRE.file.txt> > >>> The validation error is: > >>> The schemas referenced by attribute 'xsi:schemaLocation' at element gmi:MI_Metadata are not valid. > >>> Document 'http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd <http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd>' referenced by xs:import definition does not refer to a valid schema document. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta / title > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element <title>. Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta / link > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta / link / link > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> Error location: html / head / meta / meta / meta / meta / meta / link / link / meta / meta > >>> Details > >>> cvc-assess-elt.1: Neither an element declaration nor a type definition is known for element . Strict assessment failed. > >>> ....... > >>> ...... > >>> .... > >>> src-resolve: Value 'gco:AbstractObject_Type' of attribute 'base' doesn't resolve to a type definition. > >>> 'gmd:CI_Citation_PropertyType' must refer to an existing simple or complex type. > >>> Error location: xs:schema / xs:complexType / xs:complexContent / xs:extension / xs:sequence / xs:element / @type <https://github.com/type> > >>> Details > >>> src-resolve: Value 'gmd:CI_Citation_PropertyType' of attribute 'type' doesn't resolve to a type definition. > >>> Processing was aborted after reporting 100 error(s). Please increase the error limit to report additional errors. > >>> > >>> - > >>> You are receiving this because you are subscribed to this thread. > >>> Reply to this email directly, view it on GitHub <#217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ72ONLDV36DQJOLVZ3TMASEBANCNFSM44DCZSXA>. > >>> > >> > > > > - > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FISO-TC211%2FXML%2Fissues%2F217%23issuecomment-832407236&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603352307%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=brmf3%2FtGRvaHQGho5pGIAfO7WZqbGeo2bUn1daceXw8%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLMHWFZ7SXPRODGPY2F7LTTMDEKBANCNFSM44DCZSXA&data=04%7C01%7C%7C746aa219d9544ee0807208d90f807175%7C9e2777ed82374ab992782c144d6f6da3%7C0%7C0%7C637557866603362301%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W6W10ZnAJlja4pVSHied6iQ6yeexXpz%2BY5Br6dyVe8I%3D&reserved=0>. > > VITO Disclaimer: http://www.vito.be/e-maildisclaimer > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or unsubscribe.

ejbleys · 2021-05-06T21:06:47Z

Use https://schemas... Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

…

On 7 May 2021, at 01:02, MartinePaepen ***@***.***> wrote: It works when using: xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd However which is the recommended xsd to be used for MI_metadata? http://www.isotc211.org/2005/gmi/gmi.xsd or https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

MartinePaepen · 2021-05-07T06:16:17Z

There seems to be an issue with:
https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd

The targetNamespace in teh xsd is still: targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0"

==> this gives an error while validating /
Shouldn't it be ==> https://schemas.isotc211.org/19115/-2/gmi/1.0

<xs:schema xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://standards.iso.org/iso/19115/-2/gmi/1.0" version="0.1">

Thanks for your effort,
Martine

ejbleys · 2021-05-07T06:33:07Z

In XSDs, targetNamespace indicate the URI for the namespace not the location, the location would be https://schemas <https://schemas/>… E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia +61 (0)2 62811773 +61 (0)411 483 876 ***@***.*** Skype ***@***.***

…

MartinePaepen · 2021-05-07T07:36:00Z

Yes, I understand the namespace usage but why isn't it https://www.isotc211.org/2005/gmi/
which would be in line with the other namespaces in the xsd? (exapmle <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd"/> .....)

It is very confusing because for the namespace https://www.isotc211.org/2005/gmi/ there is also an xsd ( https://www.isotc211.org/2005/gmi/gmi.xsd ) which can be used and works fine for me.

AND if I compare with for example GMD metadata, I see:
Namespace https://www.isotc211.org/2005/gmd/ with xsd: https://www.isotc211.org/2005/gmd/gmd.xsd

However in the gmi.xsd is referred to
https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd

AND if I look in https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd , the targetnamespace is targetNamespace="http://www.isotc211.org/2005/gmd" Which seems OK but is different from the GMI.xsd targetNamespace.

==> the problem is that my validation tool (XMLSPY) has problems with this GMI targetNamespace in the xsd which is not the namespace which I can use in the xml as I need to use Namespace https://www.isotc211.org/2005/gmi/

ejbleys · 2021-05-07T08:25:05Z

It was not a 2005 standard Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

…

On 7 May 2021, at 17:36, MartinePaepen ***@***.***> wrote: Yes, I understand the namespace usage but why isn't it https://www.isotc211.org/2005/gmi/ which would be in line with the other namespaces in the xsd? (exapmle <xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd"/> <xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="https://schemas.isotc211.org/19139/-/gco/1.0/gco.xsd"/> .....) It is very confusing because for the namespace https://www.isotc211.org/2005/gmi/ there is also an xsd ( https://www.isotc211.org/2005/gmi/gmi.xsd ) which can be used and works fine for me. AND if I compare with for example GMD metadata, I see: Namespace https://www.isotc211.org/2005/gmd/ with xsd: https://www.isotc211.org/2005/gmd/gmd.xsd However in the gmi.xsd is referred to https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd AND if I look in https://schemas.isotc211.org/19139/-/gmd/1.0/gmd.xsd , the targetnamespace is targetNamespace="http://www.isotc211.org/2005/gmd" Which seems OK but is different from the GMI.xsd targetNamespace. ==> the problem is that my validation tool (XMLSPY) has problems with this GMI targetNamespace in the xsd which is not the namespace which I can use in the xml as I need to use Namespace https://www.isotc211.org/2005/gmd/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

MartinePaepen · 2021-05-07T09:18:25Z

Ok, it might not be a 2005 standard.
There is however a page https://www.isotc211.org/2005/gmi/ and even a mapping xsd.
This makes things even more confusing.

The solution for my (and probably others') problem is the replacement of the targetNamespace in the schema
https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd
==> use targetNamespace https://www.isotc211.org/2005/gmi/ in stead of: http://standards.iso.org/iso/19115/-2/gmi/1.0

This would also make it more in line with the other schema's :-)

ejbleys · 2021-05-07T11:41:34Z

The alternative would be to migrate to the newer versions of ISO 19115-1 & -2 Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876

…

On 7 May 2021, at 19:18, MartinePaepen ***@***.***> wrote: Ok, it might not be a 2005 standard. There is however a page https://www.isotc211.org/2005/gmi/ and even a mapping xsd. This makes things even more confusing. The solution for my (and probably others') problem is the replacement of the targetNamespace in the schema https://schemas.isotc211.org/19115/-2/gmi/1.0/gmi.xsd ==> use targetNamespace https://www.isotc211.org/2005/gmi/ in stead of: http://standards.iso.org/iso/19115/-2/gmi/1.0 This would alos make it more inline with the other schema's :-) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

chris-macdermaid mentioned this issue Apr 1, 2022

Update 19115-1/-3 writer to use schemas at schemas.isotc211.org instead of standards.iso.org adiwg/mdTranslator#226

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" #217

Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" #217

MartinePaepen commented May 4, 2021

ejbleys commented May 5, 2021 via email

ejbleys commented May 5, 2021 via email

ejbleys commented May 5, 2021 via email

MartinePaepen commented May 6, 2021 via email

MartinePaepen commented May 6, 2021 via email •

edited

Loading

MartinePaepen commented May 6, 2021 via email •

edited

Loading

MartinePaepen commented May 6, 2021

MartinePaepen commented May 6, 2021

ejbleys commented May 6, 2021 via email

ejbleys commented May 6, 2021 via email

ejbleys commented May 6, 2021 via email

MartinePaepen commented May 7, 2021 •

edited

Loading

ejbleys commented May 7, 2021 via email

MartinePaepen commented May 7, 2021 •

edited

Loading

ejbleys commented May 7, 2021 via email

MartinePaepen commented May 7, 2021 •

edited

Loading

ejbleys commented May 7, 2021 via email

Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" #217

Issue with validating ISO 19115-2 MI_Metadata due to removed schemaLocation="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" #217

Comments

MartinePaepen commented May 4, 2021

ejbleys commented May 5, 2021 via email

ejbleys commented May 5, 2021 via email

ejbleys commented May 5, 2021 via email

MartinePaepen commented May 6, 2021 via email

MartinePaepen commented May 6, 2021 via email • edited Loading

MartinePaepen commented May 6, 2021 via email • edited Loading

MartinePaepen commented May 6, 2021

MartinePaepen commented May 6, 2021

ejbleys commented May 6, 2021 via email

ejbleys commented May 6, 2021 via email

ejbleys commented May 6, 2021 via email

MartinePaepen commented May 7, 2021 • edited Loading

ejbleys commented May 7, 2021 via email

MartinePaepen commented May 7, 2021 • edited Loading

ejbleys commented May 7, 2021 via email

MartinePaepen commented May 7, 2021 • edited Loading

ejbleys commented May 7, 2021 via email

MartinePaepen commented May 6, 2021 via email •

edited

Loading

MartinePaepen commented May 6, 2021 via email •

edited

Loading

MartinePaepen commented May 7, 2021 •

edited

Loading

MartinePaepen commented May 7, 2021 •

edited

Loading

MartinePaepen commented May 7, 2021 •

edited

Loading