XML schema defines both dayTimeDuration and yearMonthDuration.
If we anticipate that we may wish to add CSDL support for YearMonthDuration later, then perhaps Duration should be renamed to DayTimeDuation now.
(Note for comparison how we renamed Point to GeographyPoint, since there is also GeometryPoint)
Field | Original Value | New Value |
---|---|---|
Proposal |
Close with no action. The general consensus in naming this "Duration" was that the likelihood of adding yearMonthDuration in the future was low enough that we should optimize for simplicity in the more common dayTimeDuration by calling it simply Duration. |
|
Environment | [Proposed] |
Fix Version/s | V4.0_WD01 [ 10247 ] |
Proposal |
Close with no action. The general consensus in naming this "Duration" was that the likelihood of adding yearMonthDuration in the future was low enough that we should optimize for simplicity in the more common dayTimeDuration by calling it simply Duration. |
Close with no action. The general consensus in naming this "Duration" was that the likelihood of adding yearMonthDuration in the future was low enough that we should optimize for simplicity in the more common dayTimeDuration by calling it simply Duration. Accepted: https://www.oasis-open.org/committees/download.php/48622/odata-meeting-30_on-20130321-minutes.html#odata-299 |
Status | New [ 10000 ] | Closed [ 6 ] |
Environment | [Proposed] | [Closed] |
Status | Closed [ 6 ] | Open [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Applied [ 10002 ] |
Status | Applied [ 10002 ] | Closed [ 6 ] |
Reporter | Evan Ireland [ evan.ireland ] | Evan Ireland [ evan.ireland.2 ] |
We had a long discussion on exactly this issue when we added Duration.
The general consensus was that the likelihood of adding yearMonthDuration in the future was low enough that we should optimize for simplicity in the more common dayTimeDuration by calling it simply Duration.