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

Make dumbing down "smarter" and keep external vocabulary info #4

Open
twagoo opened this issue Jul 21, 2016 · 0 comments
Open

Make dumbing down "smarter" and keep external vocabulary info #4

twagoo opened this issue Jul 21, 2016 · 0 comments

Comments

@twagoo
Copy link
Member

twagoo commented Jul 21, 2016

Downgrading a component gets rid of all CMDI 1.2 features, which also means some harmless but potentially useful information gets lost, most importantly the external vocabularies. This means that "dumbed down" 1.2 specs and their schema are dumber than necessary.

A relatively easy way to improve this is to transfer the external vocabulary attributes (@URI, @ValueProperty and @ValueLanguage of ValueScheme/Vocabulary) to the downgraded spec (possibly in a separate namespace) and re-instantiate them when upgrading. Optionally this can be done only in a special mode of the downgrade operation (which is only called by the Component Registry when dumbing down) so as not to 'pollute' the CMDI 1.1 versions of specifications.

Similarly, the header items Status, StatusComment, Successor and DerivedFrom could be kept as well as the value of the Autovalue element.

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

1 participant