Folks,
Sorry, I was trying to be too clever
by half.
Updated version of the proposal is here:
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33598/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136v2.pdf
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33597/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136v2.doc
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:
29/07/2009 19:06
Subject:
Re: [sca-assembly] ASSEMBLY-136:
Promoting a reference with multiplicity 1..n and targetsshould default
to 0..n - Updated Proposal
Hi Mike,
From the PDF:
1) lines 1466-1480 - Is there a formatting problem here or some typos?
The paragraph doesn't read well. Seems self contradictory.
This is caused by me not accepting the deletion
of the old form of the normative statement in the table in Appendix C -
if you don't do this, then the insertion
of the reference to it in the main text ends up containing both the old
deleted
version and the new replacement version.
I didn't check the text carefully enough. Sorry.
2) tables on lines 1484 and 1485 show checks and x's but the table in the
doc file shows numbers (4's and 5's)? Looks like 4's are checks and 5's
are x's. What's going on here?
Well, I was trying to use check marks and
crosses to indicate "allowed" and "not allowed" in
the table, since it looks more
effective on the page. So I chose the
WingDings font and then used the symbols from that font for check mark
and cross, which
happen to be "4" and "5"
on the keyboard. But I forgot that such fonts don't necessarily render
correctly on everyone's
system.
So I've gone back to a much less visually
effective form - "YES" and "NO" using the standard
font. But at least everyone will
see the same now...
3) As far as the technical content goes, it looks like what we talked about.
Thanks for writing it up.
Yes, I ended by being surprised by how relatively
little change there was, although I think that the proposal makes things
conceptually a lot simpler. The tables
are a useful clarification, although not strictly essential.
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:
Mike
Edwards ---07/29/2009 07:39:41 AM---Folks, Here is a proposal for Issue
136
From:
Mike Edwards <>
To:
"OASIS Assembly" <>
Date:
07/29/2009 07:39 AM
Subject:
[sca-assembly] ASSEMBLY-136: Promoting a reference with multiplicity 1..n
and targetsshould default to 0..n - Updated Proposal
Folks,
Here is a proposal for Issue 136
Concepts in the proposal:
1) A component reference can explicitly declare as many targets as are
compatible with its multiplicity
2) When a component reference is promoted, IF the composite reference(s)
is configured with at least 1
target (ie through the component that uses the composite) then the composite
reference targets OVERRIDE
the targets declared on the component reference (ie the component reference
targets are not used)
3) When a component reference is promoted, IF the composite reference(s)
has 0 targets configured
then any targets declared on the component reference are used (ie the declared
targets act as default targets)
4) For x..n component references, it is possible to mark the reference
@nonOverridable="true". In this case,
the set of targets which are used for the reference is the set configured
on any composite references which promote
the reference PLUS the set of targets declared on the reference itself.
5) For x..1 component references, @nonOverridable="true" means
that the reference cannot be promoted.
6) To set policy (etc) for "internal" references:
- use intents
- or attach policySets using ExternalAttachment
- or attach policySets directly
(since they can't be configured at all by promotion)
7) The default multiplicity of a composite reference is determined by:
- the multiplicities of the component references it promotes
- whether (all) the promoted component references have at least 1 target
declared
with the principle being that the multiplicity must be set to ensure that
the component references will have
their multiplicity satisfied - 0..x is allowed for the case where the component
reference is 1..x, if there is
a target declared on (all) the component references.
I've done the formal proposal as a marked up version of CD03-Rev2 (all
changes were accepted BEFORE
adding the changes for this proposal)
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33566/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136.pdf
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33565/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136.doc
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:
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
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
