| To: | Donn Terry <yyyy@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Definition of "can" in XBD |
| From: | Eric Vought <yyyy@xxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 7 Jul 1999 10:46:28 -0400 (EDT) |
| Cc: | Don Cragun <yyyyyyyyyy@xxxxxxxxxxx>, yyyyyyyyyyyy@xxxxxxxxxxxxx, yyyy@xxxxxxxxxxxxxxxxxxxxxx |
As you say, once the distinction between functionality available to the application and functionality provided by the implementation is made, the meanings become obvious. It would be great if a trimmed version of Don's explanation and his example could find their way into the document. These are terms that are absolutely critical to understanding how to use or implement this spec. > No disagreement with Don, but a thought: *if* you already know > the distinction between shall/must and may/can, the definitions > are obvious. If you don't, they aren't particularly obvious. > A few words of coaching in the definitions, or even just italicizing > (for emphasis) the words "implementation" and "application" would > probably help other new readers. > > Eric: as a recent victim of that subtlety, what would have helped > you? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Definition of "can" in XBD, Shirley Bockstahler-Brandt |
|---|---|
| Next by Date: | Re: Definition of "can" in XBD, Eric Vought |
| Previous by Thread: | Re: Definition of "can" in XBD, Donn Terry |
| Next by Thread: | Re: Definition of "can" in XBD, Andrew Josey |
| Indexes: | [Date] [Thread] [All Lists] |