Difference between revisions of "Datatypes R2 Issue 18"
| Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| + | Provide the ability to send a simplified representation of a GTS, in the form of an IVL_TS that includes all times included in the GTS (and maybe others). | ||
| + | |||
| + | This could be done as an outer hull – ie be included in the GTS expression – however it may be that the translation would be generated separately from the rest of the GTS – so it would be better if it could be stored separately. | ||
| + | While my immediate requirement is for an outer hull interval – there may be other summary requirements – such as a TS that is the “central point” of the GTS, a textual rendering of the GTS, and maybe others. I would therefore suggest a generic solution would allow a translation with two components – the value (GTS) and a translationType code. | ||
| + | The ability to share these simplified versions of the GTS has a performance benefit, and this is the main motivation for the proposal | ||
| + | |||
| + | |||
| + | backward compatible: This would be an additional component to a GTS, and could be ignored by systems that do to recognize it. | ||
| − | |||
== Discussion == | == Discussion == | ||
| + | The restricted case is already possible. You can write a constraint in text that it must always be populated. You can hack your schema if you want | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 17:20, 3 May 2007
Data Types Issue 18: GTS.translation
Introduction
Provide the ability to send a simplified representation of a GTS, in the form of an IVL_TS that includes all times included in the GTS (and maybe others).
This could be done as an outer hull – ie be included in the GTS expression – however it may be that the translation would be generated separately from the rest of the GTS – so it would be better if it could be stored separately. While my immediate requirement is for an outer hull interval – there may be other summary requirements – such as a TS that is the “central point” of the GTS, a textual rendering of the GTS, and maybe others. I would therefore suggest a generic solution would allow a translation with two components – the value (GTS) and a translationType code. The ability to share these simplified versions of the GTS has a performance benefit, and this is the main motivation for the proposal
backward compatible: This would be an additional component to a GTS, and could be ignored by systems that do to recognize it.
Discussion
The restricted case is already possible. You can write a constraint in text that it must always be populated. You can hack your schema if you want
Links
Back to Data Types R2 issues
