Re: [ebxml-bp] Proposal for minOccurs and maxOccurs attributes toAttachment

[YANO Keisuke (矢野啓介 ) <yano@jp.fujitsu.com>]

Monica,

> >In my understanding, condition expression and variable are shared
> >information between parties (e.g., referencing a part of an exchanged
> >business document).
> >
> >On the other hand, whether a party wants to attach a defined
> >Attachment or not depends on the party's own decision, not on the
> >shared information.
> >
> mm1: Yano-san, one of the base tenets of the ebXML specs are they are 
> grounded in the public process.

I agree.

> If the information is internal decision 
> making by a party and is not to be divulged to the other party(ies), is 
> it any longer considered public? Would not the other party need to know 
> during the process lifecycle if an attachment would or would not be 
> expected? Thanks.

In my proposal, the range of number of attachments is shared between 
parties. For example, when an attachment is defined as minOccurs="0" 
and maxOccurs="1", the receiving party can expect the number of 
attachments is zero or one. Never two or more.

I have to emphasize that JEITA's requirement is that a party can
decide whether a defined attachment(s) should be attached or not.

Please think of business document.  A business document definition is
a part of 'public process' that is an agreement between parties.  In
such a business document definition or an XML schema, there are
several optional items.  You can consider my proposal is like that.

Thanks,

Yano Keisuke