Incorrect URLs in xsi:schemaLocation

[ericthewizard]

Some of the XML files have incorrect URLs in the schema location, e.g.

https://github.com/hpde/NASA/blob/master/NumericalData/MMS/4/FIELDS/FGM/Survey/Level2/PT0.125S.xml

has the URL:

http://www.spase-group.org/data/schema/spase-2-5-0.xsd

It should probably be:

https://www.spase-group.org/data/schema/spase-2.5.0.xsd

[tressahelvey]

I have edited the xml to change the spase schema version.
Tressa

[ericthewizard]

I have edited the xml to change the spase schema version. Tressa

Thanks!

I think there are many others; I just did a search for the broken URL:

https://github.com/search?q=repo%3Ahpde%2FNASA%20http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2-5-0.xsd&type=code

and found it in 184 other files.

[tressahelvey]

Zach is working on a fix.

[lfb12345]

I will be sending a new SPASE XSD file shortly after writing this comment. This XSD file will allow use to use:

https://spase-group.org/data/schema/

https://spase-group.org/data/schema/spase-[12].[0-7].[0-9].xsd

For instance for SPASE 2.7.0 the Spase line would be as follows:

highly preferable (best practice!!!) with all text on one line.

Note that the XML Name Space designation, http://www.w3.org/2001/XMLSchema-instance, cannot be updated to https.
This is just reality currently, see:

https://stackoverflow.com/questions/17094247/where-is-the-xsd-file-for-http-www-w3-org-2001-xmlschema-instance

Note that 2.7.0 and 2_7_0 both work. That is:

https://spase-group.org/data/schema/spase-2_7_0.xsd

https://spase-group.org/data/schema/spase-2.7.0.xsd

At present, the underscore version, i.e., 2_7_0 for the current SPASE base model version, is found in ~90% of the NASA git SPASE descriptions.

Finally, if we do update the Spase lines in our metadata, every single resource description would need to be updated. I feel strongly that we should do this.

[lfb12345]

Opps, here is the example SPASE 2_7_0 line:

Again, preferably all on one text line.

[lfb12345]

Example Spase line does to display? I will send the example by e-mail.

[Kurokio]

This issue has been corrected for all NumericalData and DisplayData records.