Datatypes R2 Issue 31

Introduction

Null flavor co-occurrence constraints need to be more clear

Backwards compability: No change, just better documentation

Discussion

Thurs Q3 May 2006: Motion in favor of this.

Disposition

Well, the underlying confusion here is the contention that setting a datatype to null actually prohibits any properties from being populated. But generally this is not the case. There are some specific cases, and these are clearly documented. In fact, all the required co-occurence constraints are documented.

But that's waht we don't document. So the disposition to this is to add a general paragraph saying that.

Vote:
 For: Grahame
 Against: Lloyd (I understand the motion to be we won't document the constraints . . .)
 Abstrain:

Links

Back to Data Types R2 issues