OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cam message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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_id=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.
>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]