-
Notifications
You must be signed in to change notification settings - Fork 57
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
fixes #545 - units type AXISUNITS #549
Conversation
Because this corrects a syntax error that interrupts validation, it is high-priority to resolve. |
travis-ci fails with this message:
The changes that fail travis-ci are the addition of NXlog child groups to NXentry and NXsubentry. The travis-ci failure is technical, related to inability to download the specific commit and we can ignore it. |
@@ -51,12 +45,14 @@ | |||
needed to describe the position and orientation of any movable or fixed device. | |||
|
|||
There will be one or more transformations (axes) defined by one or more fields | |||
for each transformation. The all-caps name ``AXISNAME`` designates the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AXISNAME
should not be changed here
* ``NX_LENGTH`` for ``translation`` | ||
* ``NX_ANGLE`` for ``rotation`` | ||
* ``NX_UNITLESS`` for axes for which no transformation type is specified. | ||
</xs:documentation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This definition should be applied as a union, similar to NX_NUMBER
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BUT, the anyUnitsAttr
is defined as <xs:restriction base="xs:string">
with <xs:enumeration value=...
. These enumerations have no capability of <xs:union
content. The refactor of anyUnitsAttr
from xs:restriction
to <xs:union
could have other consequences.
That, in itself using only the existing schema, is worth exploring in its own branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That branch is off this PR, not master
as discussed at the [telco](http://www.nexusformat.org/Telco_20170405.html)
merge conflict was a tangle, restarted this in a new branch: schema_update_555 |
defines a new units type
NX_TRANSFORMATION
to provide the desired feature