Disallow unparsable timestamp

[omero-qa]

Create a new OME timestamp type that is a tighter restriction on the standard XSD timestamp. This will limit the object to what the code libraries we have available can actually process. Mostly this is limiting seconds to three decimal places.

The acceptable formats will follow these patterns

1111-11-11T11:11:11.111
1111-11-11T11:11:11.111Z
1111-11-11T11:11:11.111+11:11
1111-11-11T11:11:11.111-11:11
i.e.
YYYY-MM-DDThh:mm:ss.sss+HH:zz
Year
Month
Day
hour
minute 
second (with up to three decimal places)
Hour of time zone
z - minute of time zone

---

Was: Bug: Model supports only second resolution

​https://www.openmicroscopy.org/qa2/qa2/qa/feedback/7443/

Comment: The little coloured squares at the bottom of an image reporting the acquisition time for each channel don't work for images less than one second. So in a 3 channel image I only get 2 values (for green and red) for the first 6 z-sections with the last value (blue) appearing after that. I guess this is because of the values being rounded down to the nearest second, but it does look a bit odd.

AcquisitionTime? and TimeIncrement? have only second resolution; it's not possible for higher resolution timing to be stored at present.

[ajpatterson]

Schema does not need changed.

xsd:dateTime already has arbitrary precision for seconds.

see: ​http://www.w3.org/TR/xmlschema-2/#isoformats

Functions in the OME Model API will need updated.

Display code in OMERO.insight will need updated.

[jamoore]

This isn't a problem with the specification per-se, but there are no libraries for supporting all of the variants:

• In 4.4, we could put in a documentation change, not necessarily.
• In 5.x, we should disallow timestamps that aren't parse-able in our coding languages.