Support EML 2.1.0 in Morpho
EML 2.1.0 release is coming. It is will be good if this release can support this new version of EML. Here are something we need to do:
1. The new generated eml documents will have EML 2.0.1 namespace.
2. Will give user an option to transfer EML 2.0.1 (2.0.0) to EML 2.1.0 documents when user open the old version eml documents(?)
3. Add EML 2.1.0 namespace into return document types in the path query.
#2 Updated by Margaret O'Brien almost 12 years ago
These 2 paths were mistakenly added to the eml schema. they should be removed from the from tree editor:
these paths are available in eml2.1. add these paths to tree editor:
#3 Updated by Jing Tao almost 12 years ago
I just double check and found out: we only need to remove
We should KEEP:
And the new element name is "description".So we should add
#5 Updated by Margaret O'Brien almost 12 years ago
Clarifying earlier comments
REMOVE from tree editor
#6 Updated by Jing Tao almost 12 years ago
Morpho is waiting the official release of eml-2.1.0. Here are somethings need to do after releasing eml-2.1.0:
1)If there are some documentation of eml schemas were changed, we need to update morphohelp.jar file. See first step on http://help.nceas.ucsb.edu/Morpho_installers_building_and_publishing. Currently morphohelp.jar has the eml-2.1.0-RC4 documentation.
2)After eml-2.1.0 is released, we need to change the eml-210-schema-tag and eml-210-style-tag in build.xml. Then tag morpho code and build new morpho installers.
#8 Updated by Margaret O'Brien over 11 years ago
rationale for the suggestion of 1.7:
A major feature of EML2.1 is that no empty elements are allowed, so some authors will need to add content as they upgrade to 2.1. Morpho will not be able to edit files until they have been converted to 2.1.
So it is very likely that some people will continue to create EML2.0.1 rather than upgrade. One option for them is to continue using Morpho-1.6.1 for maintaining 201. So the suggestion of Morpho-1.7 for the version that can handle EML2.1 was to make the distinction between them clear -- Morpho1.6.2 did not seem different enough.
However, this raises another issue: keeping 1.6.1 around will cause confusion between the pairs: Morpho161/EML201 vs. Morpho17/EML21. It would be better to add functionality to Morpho so that people can easily update 201 instead. "Easy" means dialog boxes that clearly state "content is needed here:___", and not simply a message that says 'something wrong with EML, cant continue', or defaulting to the tree editor.