Re: [sdd] Thoughts on glossary updates

[Thomas Studwell <studwell@us.ibm.com>]

Kishimoto-san,
thank you for your comments. My only comment is to (c). Since the specification will use the terminology normatively and the glossary will be part of the specification, the only terms we've chosen to include in the glossary are those we believe require normative definitions. Where exceptions exist, we will indicate that the term is informative.

Thomas W. Studwell
Senior Technical Staff Member, Autonomic Computing Architecture
IBM Software Group
B140/Bldg 500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038
studwell@us.ibm.com

"There is a word for complaining about a problem without proposing a solution - it's called whining." Ric Telford 2006
Hiro Kishimoto <hiro.kishimoto@jp.fujitsu.com>

Hiro Kishimoto <hiro.kishimoto@jp.fujitsu.com>

04/19/2006 09:39 PM

To	sdd@lists.oasis-open.org
cc
Subject	Re: [sdd] Thoughts on glossary updates

Hi all,

Based on experiences of our GGF OGSA Glossary development,
the following is the food for thoughts;

(a) Define nouns only, not verb or adjective
    If necessary, Give "See <noun form of term>."

(b) Make words or phrases in "italics" which are themselves defined
    in the glossary.

(c) Normative or informative
    I think glossary is informative instead of normative.
    I guess the following text on page 4 of the current draft comes
    from standard OASIS document template and should be fixed.

    "All text is normative unless otherwise noted."

FYI: OGSA Glossary's URL;
http://www.ggf.org/documents/GFD.44.pdf

Thanks,
----
Hiro Kishimoto

Christine Draper wrote:
>
>
>
>
> I did a skim of the requirements document versus the glossary and found the
> following.
>
> Used without much context, probably need a glossary definition:
> payload
> component
> target environment (vs target)
> verify/verification
> rollback
> undo
> repair
> update, upgrade (used mainly as verbs but defined as nouns - maybe this is
> OK)
> apply (application) of fixes
>
> Deployment lifecycle operations: planning, installation, configuration,
> maintenance, upgrade, migration and uninstallation   (should be same list
> of terms in glossary, and should define each term, consistently as either a
> noun or a verb)
>
> Possibly should be defined, but likely have enough context:
> feature
> metadata
> localization
> change plan
>
> discreet units => individual (discrete) packages?
>
> Regards,
> Christine
>
> Senior Technical Staff Member
> IBM, 11501 Burnet Road, Mail Point 901-6B10
> Austin, TX 78758
> 1-512-838-3482 tl 678-3482