Re: [sca-assembly] Inconsistent use of ##other vs. ##any

Folks,

The Assembly TC took a decision some
time ago that all extension elements and attributes should come from any
namespace 

other than the SCA namespace - ie ##other
should be used rather than ##any.  This was decided by the resolution
of ASSEMBLY-23

http://www.osoa.org/jira/browse/ASSEMBLY-23

There is one exception in the Assembly
XSDs - the definition of the SCAPropertyBase type is special in that it
can contain literally

anything for the type of a property
- so this is ##any.

However, you rightly point out that
the Assembly XSDs contain some other ##any declarations and these are in
error.  I will raise 

an issue to get these changed.  Similar
issues should be raised in other TCs for similar occurrances of ##any.

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:  

From:
David Booz <>

To:


Date:
27/03/2009 17:40

Subject:
[sca-assembly] Inconsistent use of ##other
vs. ##any

On the Java TC call today, Anish remembered that there
was a decision made that our schemas would use the ##other namespace on
extensibility elements. I happened to be modifying one of the java schemas
today to apply a issue resolution and noticed that there's a mix of ##any
and ##other across the board...seemingly across all TCs.

Can someone confirm that ##other was chosen for all uses of <any>
and <anyAttribute> in our schemas? If so, we'll have to get some
issues opened across the TCs.

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:

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