| To: | yyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Definition of "can" in XBD |
| From: | Eric Vought <yyyy@xxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 5 Jul 1999 18:41:10 -0400 (EDT) |
I have not submitted an aardvark on this yet because I do not understand what the real definition should be for this document: On XBD 1.2 (Terminology) lines 9-12, "can" is defined. This definition appears to be nonsensical. In one breath it says that the feature or behavior is optional (as would follow from the common English usage of "can"), then says that the feature or behavior is mandatory and can be depended on by application developers. The last part of the definition of "can" does not appear to be any different from "shall". |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: quoted characters, Ted Baker |
|---|---|
| Next by Date: | Re: Definition of "can" in XBD, Don Cragun |
| Previous by Thread: | Updated Agenda, Andrew Josey |
| Next by Thread: | Re: Definition of "can" in XBD, Don Cragun |
| Indexes: | [Date] [Thread] [All Lists] |