This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Datatypes R2 Issue 71"

From HL7Wiki
Jump to navigation Jump to search
 
Line 20: Line 20:
  
 
Motion (Mark Tucker / Doug Pratt): Leave it grey and do not create a datatype for this purpose. Approved (4-0-0)
 
Motion (Mark Tucker / Doug Pratt): Leave it grey and do not create a datatype for this purpose. Approved (4-0-0)
 +
 +
 +
We don't see that having a grey class is problem.
  
 
== Links ==
 
== Links ==
 
Back to [[Data Types R2 issues]]
 
Back to [[Data Types R2 issues]]

Latest revision as of 21:58, 11 January 2007

Data Types Issue 71: Datatype for LanguageCommunication

Introduction

Create a special datatype for languageCommunication so it can be removed from the RIM (the sole "Grey class")

? backwards compatibility -> would produce a RIM Change, but is compatible on the wire

Discussion

We could create a datatype for LanguageCommunication Class so the sole grey class can be removed

The datatype has the same attribute semantics and names as the class, and is introduced as a attribute with the name languageCommunication : Set<LanguageCommunication>

This means that the wire format is the same.

Motion (Mark Tucker / Doug Pratt): Leave it grey and do not create a datatype for this purpose. Approved (4-0-0)


We don't see that having a grey class is problem.

Links

Back to Data Types R2 issues