In most calendaring programs, you can set a calendar event to "Public" or "Private" - so those are common terms. We need to have at least those two.
>From my perspective, the simplified descriptions you propose are more >ambiguous, not less. -Adrian --- On Fri, 10/3/08, Jacques Le Roux <[EMAIL PROTECTED]> wrote: > From: Jacques Le Roux <[EMAIL PROTECTED]> > Subject: Re: WorkEffort.scopeEnumId > To: [email protected] > Date: Friday, October 3, 2008, 5:38 AM > Why not even simplify and just use the 1st parts of each > sentences ? > We would then have > General access > Restricted access > Very restricted access > Easier to translate, it avoid ambiguities, as an example > http://www.cnrtl.fr/synonymie/confidentiel : Confidentiel = > "Top secret" in > French > BTW translations are already done... > > Jacques > > From: "Adrian Crum" <[EMAIL PROTECTED]> > >I have a question about the scopeEnumId field in the > WorkEffort entity. > > > > In the work effort UI, the scopeEnumId drop-down has > three choices: > > > > General, public access > > Restricted, private access > > Very restricted, confidential access > > > > The third choice seems to be contradictory. > > > > The dictionary defines "Private" as: > > > > a. Secluded from the sight, presence, or intrusion of > others: a private hideaway. b. Designed or intended for > one's exclusive use: > > a private room. > > > > And it defines "Confidential" as: > > > > a. Done or communicated in confidence; secret. b. > Entrusted with the confidence of another: a confidential > secretary. > > > > So, it seems to me the three choices would be better > described as: > > > > General, public access > > Restricted, confidential access > > Very restricted, private access > > > > Meaning a private work effort is only visible to its > owner, and a confidential work effort is only visible to > persons the owner > > grants access to. > > > > What do you think? > > > > -Adrian > >
