Task #2103
Feature #1764: Finalize dataoneTypes schema for public release
Separating "low" and "high" level types?
Status:
Closed
Priority:
Normal
Assignee:
Category:
Documentation
Target version:
Start date:
2011-12-07
Due date:
% Done:
100%
Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:
Description
Would it make sense to separate, in the documentation, types that are used for conveying information and types that are used for specifying formats? So, put NonEmptyString and DateTime away from ObjectFormatIdentifier, etc.
History
#1 Updated by Matthew Jones about 13 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
After evaluation, its not clear what this separation would really represent. I think the simplest organization is via the Simple type/complex type dichotomy that we have, and alphabetical within that. Evaluation: no action to be performed.
