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

dependency field not defined as ComplexType #305

mbjones opened this issue May 2, 2018 · 1 comment

dependency field not defined as ComplexType #305

mbjones opened this issue May 2, 2018 · 1 comment


Copy link

@mbjones mbjones commented May 2, 2018

The current eml-software dependency element is defined as a global element in eml-software, and then used in the schema in other locations by referencing the global like so:

<xs:element ref="dependency" minOccurs="0" maxOccurs="unbounded">

We got rid of this style in favor of using named ComplexTypes, and this one should be no different. Rearrange the schema to make this a DependencyType Complext Type, and get rid of the ref references.

@mbjones mbjones added this to the EML2.2.0 milestone May 2, 2018
@mbjones mbjones self-assigned this May 2, 2018
@mbjones mbjones added in progress and removed next labels Jun 29, 2018
Copy link
Member Author

@mbjones mbjones commented Jun 29, 2018

Completed switch to ComplexType, and added software example for testing.

@mbjones mbjones closed this Jun 29, 2018
mbjones added a commit that referenced this issue Jun 29, 2018
Removed use of `ref` to a global element.  Details in issue #305.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant