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

Metadata schema: properly constrain all kinds of values #640

Open
cspurk opened this issue Oct 2, 2012 · 1 comment
Open

Metadata schema: properly constrain all kinds of values #640

cspurk opened this issue Oct 2, 2012 · 1 comment
Milestone

Comments

@cspurk
Copy link
Member

cspurk commented Oct 2, 2012

In the next version of the metadata schema, all kinds of values should be properly constrained.

For example, it makes no sense for height or weight under participantInfoType to have values of type xs:integer with a value space of at least 18 digits. Values of type xs:unsignedShort would be totally sufficient here. The values of ageRangeStart and ageRangeEnd would sufficiently be described with xs:unsignedByte values. And so on.

Another example where proper constraints would be helpful are enumerations of strings. Instead of xs:string, the type xs:token would probably better suited. This would also remedy problems like the trailing whitespace in the enumeration value of the current metadata schema.

@cspurk
Copy link
Member Author

cspurk commented Oct 22, 2012

#527 can be seen as a special case of properly constraining values, too.

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