Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change namespaces to use https #341

Closed
mbjones opened this issue Jul 24, 2019 · 6 comments
Closed

change namespaces to use https #341

mbjones opened this issue Jul 24, 2019 · 6 comments
Assignees
Milestone

Comments

@mbjones
Copy link
Member

mbjones commented Jul 24, 2019

Current eml namespaces use a custom URI that starts with eml://, such as eml://ecoinformatics.org/eml-2.1.1 and eml://ecoinformatics.org/eml-dataset-2.1.1. Because these are not registered URIs, and because some people prefer https URIs (even if they are just names that don't necessarily resolve), a request has been made to switch to this convention.

Proposal

New namespaces for EML 2.2.0 would have the form:

  • https://eml.ecoinformatics.org/eml-2.2.0
  • https://eml.ecoinformatics.org/eml-dataset-2.2.0
  • https://eml.ecoinformatics.org/eml-resource-2.2.0
  • etc.

Software (Metacat, MetacatUI, XSLT, etc) will need to be updated to recognize this new namespace format.

Comments appreciated.

@mbjones mbjones added this to the EML2.2.0 milestone Jul 24, 2019
@mbjones mbjones self-assigned this Jul 24, 2019
@mobb
Copy link
Contributor

mobb commented Jul 25, 2019

EDI has been testing the EML 2.2 changes as they progress, and would like to test this one too. So go ahead and push the namespace change, and we will test again. Probably there is no objection.

mbjones added a commit that referenced this issue Jul 29, 2019
The new namespace is of the form `https://eml.ecoinformatics.org/eml-2.2.0`.  XSD files, stylesheets, and test documents were updated. Work related to issue #341.
@mbjones
Copy link
Member Author

mbjones commented Jul 29, 2019

New namespace names were implemented as proposed (https://eml.ecoinformatics.org/eml-2.2.0). The internal ant tests are passing. Need to test and make code changes for the following:

@amoeba
Copy link
Contributor

amoeba commented Aug 2, 2019

I've just finished testing the DataONE indexing stack, Metacat, and MetacatUI (sans editor) with the new namespace change and things look good. I'm awaiting reviews on PRs but hope I can get comments by next week and @taojing2002 can help me do some testing. An example EML 2.2.0 doc can be see on https://neutral-cat.nceas.ucsb.edu/view/5ddefe83-0d65-4316-8301-1e40b51468b7 with the matching Solr index contenet at https://neutral-cat.nceas.ucsb.edu/metacat/d1/mn/v2/query/solr/?q=id:%225ddefe83-0d65-4316-8301-1e40b51468b7%22.

@mbjones
Copy link
Member Author

mbjones commented Aug 3, 2019

Awesome, thanks @amoeba!

@luciaV86
Copy link

Hi,
I am working on an XSL Transformation to allow a mapping from EML2.1.1 to EML2.2.0 but I have an issue with the namespace declaration, an issue that arises also for the transformation that @mbjones has developed (https://github.com/NCEAS/eml/blob/main/style/eml211to220.xsl).

Given for example as input an XML file that starts with:
<eml:eml
xsi:schemaLocation="eml://ecoinformatics.org/eml-2.1.1 http://rs.gbif.org/schema/eml-gbif-profile/1.1/eml.xsd"
packageId="xxx"
system=“xxx” xml:lang="en">

…..

<eml:eml packageId="edi.1073.1" system="https://pasta.edirepository.org"
xsi:schemaLocation="https://eml.ecoinformatics.org/eml-2.2.0 https://nis.lternet.edu/schemas/EML/eml-2.2.0/xsd/eml.xsd">

I have the following error: “Namespace prefix eml on eml is not defined in Entity”

I have tried with different EML2.1.1 files from different sources but the result is always the same.

If I add the following two lines to the input file:
xmlns:eml="https://eml.ecoinformatics.org/eml-2.2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

and hence the file becomes:
<eml:eml
xmlns:eml="https://eml.ecoinformatics.org/eml-2.2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="eml://ecoinformatics.org/eml-2.1.1 http://rs.gbif.org/schema/eml-gbif-profile/1.1/eml.xsd"
packageId="eml.1.1"
system=“xxx” xml:lang="en">

…..

the transformation works fine and gives the desired output, but I cannot modify the input files that I will use as harvesting source.
How did you managed this when testing your transformation?

Thank you very much in advance!

@mbjones
Copy link
Member Author

mbjones commented Feb 11, 2022

@luciaV86 Let's open this in a new ticket, as it is unrelated to this topic in this closed issue #341. I copied your thread across to a new ticket #383 and will address your question there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants