Re: [sca-j] Specifications for Public Review

[Simon Nash <oasis@cjnash.com>]

Dave,
These annotations and APIs are not only for the "POJO" implementation
type.  They are also for Spring, EJB, JEE, etc.  So I don't think we
should call them POJO annotations.

How about using the term "SCA-J" instead of "POJO"?  This gives
the following name for the CAA spec:
  Service Component Architecture SCA-J Common Annotations and APIs Specification Version 1.1

We could consider also using this term for the CI spec, which would
then be called:
  Service Component Architecture SCA-J Component Implementation Specification Version 1.1

For the CI spec, I am more open to using POJO as it is technically
accurate and readily understood.

   Simon

David Booz wrote:
> I feel like we need to get something Java-like into the title of the CAA 
> spec. Here's some possible variants:
> 
> (a) Service Component Architecture Common Annotations and APIs for POJOs 
> Specification
> 
> (b) Service Component Architecture POJO Common Annotations and APIs 
> Specification
> 
> (c) Service Component Architecture Common POJO Annotations and APIs 
> Specification
> 
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
> 
> Inactive hide details for Mike Edwards ---05/29/2009 03:30:03 
> AM---Folks, I'm OK with Anish's suggestions, given that we can't Mike 
> Edwards ---05/29/2009 03:30:03 AM---Folks, I'm OK with Anish's 
> suggestions, given that we can't use "Java" in the
> 
> 
> From:	
> Mike Edwards <mike_edwards@uk.ibm.com>
> 
> To:	
> "OASIS Java" <sca-j@lists.oasis-open.org>
> 
> Date:	
> 05/29/2009 03:30 AM
> 
> Subject:	
> Re: [sca-j] Specifications for Public Review
> 
> ------------------------------------------------------------------------
> 
> 
> 
> 
> Folks,
> 
> I'm OK with Anish's suggestions, given that we can't use "Java" in the 
> title of either specification.
> 
> Yours, Mike.
> 
> Strategist - Emerging Technologies, SCA & SDO.
> Co Chair OASIS SCA Assembly TC.
> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
> Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
> Email: mike_edwards@uk.ibm.com
> 
> From: 	Anish Karmarkar <Anish.Karmarkar@oracle.com>
> To: 	sca-j@lists.oasis-open.org
> Cc: 	Mary McRae <mary.mcrae@oasis-open.org>, David Booz <booz@us.ibm.com>
> Date: 	29/05/2009 06:23
> Subject: 	Re: [sca-j] Specifications for Public Review
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> How about 'I-can't-believe-its-not-Java'?
> 
> But seriously, I'm not sure replacing Java with J makes a meaningful
> title. The JCI spec would then be titled:
> Service Component Architecture J Component Implementation Specification
> Version 1.1
> 
> A better name perhaps is:
> Service Component Architecture POJO Component Implementation
> Specification Version 1.1
> 
> For the JCAA spec, I suppose we could just drop the 'Java' and have it be:
> Service Component Architecture Common Annotations and APIs Specification
> Version 1.1
> 
> Comments?
> 
> -Anish
> --
> 
> Mary McRae wrote:
>  > I was just about to send these out and noticed that the Specification
>  > titles use the word "Java" - this is prohibited by the OASIS TC Process
>  > Policy, in the same way that it was prohibited from being used in the
>  > name of the TC.
>  >
>  >  From section 2.18 Specification Quality:
>  > "All documents and other files produced by the TC, including
>  > specifications at any level of approval, must use the OASIS file naming
>  > scheme, and must include the OASIS copyright notice. All document files
>  > must be written using the OASIS document authoring templates, which
>  > shall be published and maintained by the TC Administrator. The name of
>  > any specification may not include any trademarks or service marks not
>  > owned by OASIS."
>  >
>  > I can simply edit the files and replace "Java" with "J" or you can
>  > provide updated files; whichever you prefer.
>  >
>  > Regards,
>  >
>  > Mary
>  >
>  > Mary P McRae
>  > Director, Standards Development
>  > Technical Committee Administrator
>  > OASIS: Advancing open standards for the information society
>  > email: mary.mcrae@oasis-open.org
>  > web: _www.oasis-open.org_
>  > twitter: fiberartisan  #oasisopen
>  > phone: 1.603.232.9090
>  >
>  > Standards are like parachutes: they work best when they're open.
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe from this mail list, you must leave the OASIS TC that
>  > generates this mail.  Follow this link to all your TCs in OASIS at:
>  > _https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php_
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:_
> __https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php_ 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> /
> /
> 
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number 
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU/
> 
> 
> 
> 
>