This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 19"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
Because this is a datatype flavor, it may not be critical to get done right away. It is not necessarily required for the ISO document. | Because this is a datatype flavor, it may not be critical to get done right away. It is not necessarily required for the ISO document. | ||
| + | |||
| + | |||
| + | Added. --[[User:GrahameGrieve|GrahameGrieve]] 05:56, 20 June 2007 (CDT) | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Latest revision as of 10:56, 20 June 2007
Data Types Issue 19: Add Bounded PIVL (BPVL)
Introduction
Need for a datatype flavor at the universal level called GTS.BOUNDEDPIVL. Essentially this is a constraint on GTS that only allows a union of IVL<TS> and PIVL<TS>. It allows you to capture a frequency together with an outer time boundary and is useful for things like dosage instructions.
Discussion
Because this is a datatype flavor, it may not be critical to get done right away. It is not necessarily required for the ISO document.
Added. --GrahameGrieve 05:56, 20 June 2007 (CDT)
Links
Back to Data Types R2 issues
