[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1394) Next version of OData protocol should support full-fledged 8601-1 duration for Edm.Duration.
Christof Sprenger created ODATA-1394: ---------------------------------------- Summary: Next version of OData protocol should support full-fledged 8601-1 duration for Edm.Duration. Key: ODATA-1394 URL: https://issues.oasis-open.org/browse/ODATA-1394 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Reporter: Christof Sprenger Next version of OData [protocolÂ|[https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html]] should support full-fledged duration for Edm.Duration . The [ABNF|[https://docs.oasis-open.org/odata/odata/v4.01/os/abnf/odata-abnf-construction-rules.txt]] today states duration value is  Â[ SIGN ] "P" [ 1*DIGIT "D" ] [ "T" [ 1*DIGIT "H" ] [ 1*DIGIT "M" ] [ 1*DIGIT [ "." 1*DIGIT ] "S" ] ] i.e. no years or month as defined by W3C's XML dayTimeDuration. In contrast,ÂISO 8601-1 2019 5.5.2.2 allows to specify Years and Months. There are well understood libraries that do support the notion of ISO 8601-1, for example Joda's Period classÂ[https://www.joda.org/joda-time/key_period.html] To notion of weeks or month as a duration makes it possible to model calendar recurrence patterns in a less custom way. -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]