-
```
This is a discussion about whether and how to support the ISO 8601 "duration"
datatype as described in http://www.w3.org/TR/xmlschema-2/#duration
Example: P3DT5H30M
This is: 3 days, 5 hours, 30 …
-
This ticket exists as a reminder to Council to remove the code in odds/odd2dtd.xsl that looks inside `` for an FPI. We only use `` nowadays.
E.g., `( tei:idno[@type eq 'FPI'], tei:altIdent[@type eq…
sydb updated
4 months ago
-
We should add a marker command that separates the different editing sessions. It could be something like this, using [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) to store the unambiguous timesta…
-
As a follow-up from #1349, once EDTF dates are supported / supportable then we should expand our date data types to include both ISO 8601 levels 1 & 2.
This may depend on / be helped along by effo…
-
https://github.com/preston/vha-kbs-knarts/blob/61c0978b327137459871c86b3c6604e58ede2d69/content/cardiology_catheterization/o18/CDSK_KRprt_OS_O18PreCardCath.xml#L322
Please check all medication orde…
-
Dear A5 Flights team,
I have seemed to stumble upon a minor issue - the date format…
-
When calling `/api/packages/{package}/{version}/info` via the API I see dates in the correct ISO-8601 format like `2013-04-17T09:38:57Z`, but when calling `/api/packages/{package}/info` the time zone …
-
Support for the timestamp extension would be great.
https://github.com/msgpack/msgpack/blob/master/spec.md#timestamp-extension-type
Of course the format for the JSON side needs to be decided. My p…
-
**Problem**
The application accepts a time of 2400, which it takes as 12 am on the next day
**To reproduce bug**
enter `edit app 1 d/1-1-21 2400`
**Expected behaviour**
Throws error
**Actual behavi…
-
## Steps to reproduce ##
`robot -t "3. Get Correct Ordered Revision History of Versioned Composition Of Existing EHR With Two Composition Versions (JSON)" robot/COMPOSITION_TESTS/GET_VERSIONED_COM…