I think the attribute should be dropped from <unit> and <group>
The other possible fix would be to have them as strings with undefined defaults, but the usability and interoperability of such would be pretty limited.
I'd say we are rectifying an omission by killing type on the unit and group lists. If there is an appetite for having type on those levels with predefined values, this should slip to 2.x possibly 2.1
Cheers
dF
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Fri, Mar 14, 2014 at 5:07 AM, Tom Comerford <> wrote:
In the description for the core attribute ‘type’ (section 4.3.1.40), there’s no value description and no default value for <group> or <unit>. Also the ‘used in’ section doesn’t include these elements. However, they are referenced by those elements (section 4.2.2.4 group, section 4.2.2.5 unit).
