RE: [cam] Choices

[<martin.me.roberts@bt.com>]

Another attempt.  I just walked through my previous suggestion and it
fails.

I need to go away and write down the use cases we are trying to sort out
and then address them all.  I am convinced that the current doc does not
work for the use cases I have in mind.

Use Case:

	1) Make everything under this node a choice - only on allowed
		Already covered: setChoice="//element" - 
			I would prefer to have it set to every element
in XPATH becomes part of choice group
	2) Add a set of nodes to a choice group - not all children to be
included
		Would work if we made change suggested above is
setChoice(//element/*) to get all children
	3) The ability to select a choice element by a friendly name/ID
to help with programming
		I think needs the ability to define choice grouping and
ID seperately.
		i.e. setID and SetChoice -- selection by useChoiceByID
	4) The ability to select a choice of sequences of elements -
i.e. more than one node in each item in the choice
		This one flaws me at present.
	5) combination of 3 and 4
		This one flaws me at present.

The useCase 4 and 5 that really give us problems and I believe our
document needs to change.

Martin Roberts 
xml designer, 
BT Exact
e-mail: martin.me.roberts@bt.com 
tel: +44(0) 1473 609785  clickdial
fax: +44(0) 1473 609834
Intranet Site :http://twiki.btlabs.bt.co.uk/twiki



-----Original Message-----
From: David RR Webber [mailto:david@drrw.info] 
Sent: 22 March 2004 16:53
To: cam@lists.oasis-open.org; Roberts,MME,Martin,XSG3 R
Subject: Re: [cam] Choices


Martin,

I see the issue here - its a more fine-grained need than
the average choiceID use - and clearly we must document
that ability to do sub-selections within selections, and
where a choice may involve picking one or more as
valid allowed items.

One can envision in large very complex documents - such
as a PO with 10,000 line item types - there would be
a need to do this - so people can select many pieces
of the document with a single choiceID - and then
within that point out specific sub-choices.

My sense here is that we have enough syntax - and
we just need usage notes - to clarify how this should
work here exactly - so we can cover this alternate
use pattern clearly - and keep it simple and distinct -
and in the BusinessContextRules section allow
people to specify what behaviour they need.

Thanks, DW.

----- Original Message ----- 
From: <martin.me.roberts@bt.com>
To: <cam@lists.oasis-open.org>
Sent: Monday, March 22, 2004 8:41 AM
Subject: [cam] Choices


> Martin Roberts added the following comment to the
OASIS-CAM-Specifications-1_0-RC-017C-021904.doc document in the OASIS
Content Assembly Mechanism TC Group.
>
> I think there is some confusion over choices:  examine the following:
>
> <root>
> <choiceTypeOne>
> <!-- choices are indicated because they have the same ID--> <choice1 
> as:choiceID="123">one</choice1> <choice2 
> as:choiceID="123">two</choice2> </choiceTypeOne>
> <choiceTypeTwo>
> <!-- Choices have independant ID -->
> <choice1 as:choiceID="123">one</choice1>
> <choice2 as:choiceID="345">two</choice2>
> </choiceTypeTwo>
> <choiceTypeThree>
> <!-- what doe sthis mean? -->
> <!-- either it is two choices of type one -->
> <!-- or two groups of elements that are mutually exclusive -->
> <choice1 as:choiceID="123">one</choice1>
> <choice2 as:choiceID="123">two</choice2>
> <choice3 as:choiceID="123">three</choice3>
> <choice4 as:choiceID="345">four</choice4>
> <choice5 as:choiceID="345">five</choice5>
> </choiceTypeThree>
> </root>
>
> I have shown three choices and I think the last needs to be allowed in
either interpretation but how do we get the predicates right.
>
> View Document Details and Comments:
>
http://www.oasis-open.org/apps/org/workgroup/cam/document.php?document_i
d=5914
>
> Download Document:
>
http://www.oasis-open.org/apps/org/workgroup/cam/download.php/5914/OASIS
-CAM-Specifications-1_0-RC-017C-021904.doc
>
> PLEASE NOTE:  If the above links do not work for you, your email
application
> may be breaking the link into two pieces.  You may be able to copy and
paste
> the entire link address into the address field of your web browser.
>
> - Administration
>
>
> To unsubscribe from this mailing list (and be removed from the roster 
> of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup
.php.
>
>