On 20/03/2018 21:54, Pablo Pazos wrote:
Yep, I know
https://docs.oracle.com/javase/tutorial/datetime/iso/period.html
But this is not about anything Java specific, just giving an example
why Duration might not be good for an assumed type on the openEHR specs :)
just to give some background, 'Duration' was always intended to
represent a data type that could be considered like the ISO601 Duration
type (also the ISO8601 Date type etc), which is also a W3C type
(duration, gdate etc) - regardless of internal representation. For Java
programmers, the joda library provided this; recent Java and C# have
more modern things built in.
The Foundation Types spec now has a types cross-ref datatypes here
<http://www.openehr.org/releases/BASE/latest/docs/foundation_types/foundation_types.html#_type_cross_reference>.
No guarantee it is correct ;)
On the other hand... (re)thinking: assumed types should not be
considered as "supported by a programming language", but "supported by
a programming language or application" ***. For instance, it is not so
difficult to create a Duration class ourselves on any programming
language, or even use one of the many available libraries that deal
with Duration types and are compatible with ISO8601 durations.
Considering that, we might need to clarify:
1. What "assumed type" really is (it seems most tend to think that
should be supported by a programming language, need to double check
the specs to see how this is defined, maybe is clearly defined but not
highlighted enough).
we are moving away from this terminology 'assumed types', and just using
'primitive types', but the idea is the same - that it is assumed that
the programming environment has some equivalent that can be connected to
e.g. Duration, String etc, as they appear in the openEHR specs.
2. Clarify the use of the Duration class from CDuration where Duration
is not on the specs (we can say it is assumed considering assumed as
the definition ***)
it is now - in the Foundation Types spec
<http://www.openehr.org/releases/BASE/latest/docs/foundation_types/foundation_types.html>.
3. Complementing 2. we can propose support for Duration on many
programming languages by recommending certain libraries or core types.
This can be an ITS or just an addendum/errata to v1.0.2 specs.
right - that xref table referred to above is an attempt to do this. We
can expand that table to include more languages/technologies, or do it
some other way. If we can use this table, it means we can avoid
publishing another separate spec.
- thomas
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Team, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org/category/6044>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/>
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
