I see the logic. Reading it, however, brings out
the journeyman developer response of: "this is too &^%$$# much work and too
easy to screw up in my code." This will take real, by the numbers,
"UOM for Dummies" documentation for about 85% of the folks working in our
domain. And that may be generous. If we follow this we are going to
need lots of very clear examples. Especially, since it would require us to
break our current rule of avoiding attributes as much as
possible.
Gary A.
Ham
Senior Research
Scientist
Battelle Memorial
Institute
540-288-5611
(office)
703-869-6241 (cell)
"You
would be surprised what you can accomplish when you do not care who gets the
credit." - Harry S. Truman
From: Carl Reed OGC Account
[mailto:]
Sent: Tuesday, March 28, 2006 12:43
PM
To:
Subject: [emergency]
RE: OGC UoM Best Practices guidance
As I mentioned.
Carl Reed, PhD
CTO and Executive Director Specification
Program
OGC
The OGC: Helping the World to Communicate Geographically
---------------------
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any use, copying, disclosure,
dissemination or distribution is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately by return email
and delete this communication and destroy all copies.
"The important thing is not to stop questioning." -- Albert Einstein
