Narrowing down the elements and attributes in IS 29500 that might need measurement units

[Chris Rae]

Let's discuss this on the call tomorrow - I am of the opinion that, although this is not without merit, the volume of effort to integrate these changes would dwarf anything else WG4 has taken on and would be better invested elsewhere at the moment.

I'd be in favour of deferring this to a revision (or later) - I don't want to close it.

Chris

-----Original Message-----
From: MURATA Makoto (FAMILY Given) [mailto:eb2m-mrt at asahi-net.or.jp] 
Sent: 26 April 2011 22:58
To: e-SC34-WG4 at ecma-international.org
Subject: Re: Narrowing down the elements and attributes in IS 29500 that might need measurement units

Dear colleagues,

I extracted all element and attribute declarations containing byte,  decimal,  double,  float, int,  integer,  long,  short,  unsignedByte,  unsignedInt,  unsignedLong, and unsignedShort.  candidatesInStrict.txt is a list of such declarations in S, whild candidatesInTransitional.txt is a list for such dcls in T.

 992 candidatesInStrict.txt
1204 candidatesInTransitional.txt

Certainly, quite a few of them are irrelevant.  But 

  egrep "([Bb]ottom)|([Tt]op)|([Ww]idth)|([Hh]eight)|([Ll]ength)|([Pp]osition)|(\}sz )|(\}x )|(\}y )" candidatesInStrict.txt | wc -l

returns 85.

Three make files aond one XSLT stylesheet (on top of  Cygwin) do the job.

Cheers,
Makoto