Re: Terminology - uppercased key words: proposal
Are these keywords tagged as such in the .sgml source of the written
specification? If not then patches may be better than paper and pen.
However, I'm not sure which tag to use and if there is one that existing
style sheets will do case mapping (or something) on. Manual case shifting
( '~' in vi, M-u in emacs) may still be a good idea.
Albert.
Andrew Josey wrote:
>
> I'm not sure about using UPPERCASE, but agree that
> uses of the key terms in the specification need validating,
>
> For example according to the terms, a requirement on the implementation
> should use "shall"
> and a requirement on the application should use "must".
>
> I suspect there may be many instances where this is the wrong
> way round.
>
> If I get time before the spec review I will attempt a pass of the
> document (although this stuff is simpler to report with paper and pen:-)
> I would also encourage others to do so.
>
> regards
> Andrew
>
> On May 9, 11:59pm in "Terminology - upperc", Alfonso De Gregorio wrote:
> > Hi Everyone,
> >
> > in my opinion, key words for use in LSB specifications, and
> > specified in section 1.8 (Terminology), should be used uppercased.
> >
> > If we use, for example, the verb "must" we should discriminate
> > something that is an absolute requirement of the specification
> > (eg. "The __GROUP argument must be 0 or the behavior is undefined")
> > from something that is necessary to be done (eg. "the full implications
> > must be understood and carefully weighed before choosing a different
> > course"). Analogous examples exist for the others key words.
> >
> > If you agree, we should review the current specifications paying
> > a special attention to the real semantic of each key word instance,
> > and replace the appropriate ones.
> >
> > Thanks,
> > alfonso
> >
>
> --
>
> To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
> with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org
--
Albert den Haan, Lead Developer @ Linux Port Team . Corel Corporation
albertd@corel.com (613) 728-0826 x 5318
--
The address in the headers is not the poster's real email address. Do not send
private mail to the poster using your mailer's "reply" feature. CC's of mail
to mailing lists are OK. Problem reports to "postmaster@umail.corel.com".
The poster's email address is "albertd@corel.com".
Reply to: