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

[David RR Webber <david@drrw.info>]

Yano-san,

I was assuming it was already declared as optional in the schema definition.

Thanks, DW

p.s. I was confused by the English translate of your article as it 
referred to
you as Mr. Yano - my apologies.

YANO Keisuke (矢野啓介) wrote:

>David,
>
>Thanks for your reply.
>
>One important point of JEITA's requirement is that an Attachment can
>be optional.
>
>If 'repeatable' and 'limit' attributes can express that an Attachment
>is optional, those attributes are good.  If not, one possible solution
>is to add 'isOptional' boolean attribute in addition to them.
>
>Thanks,
>
>Yano Keisuke
>
>P.S. Please call me Yano-san.
>
>
>From: David RR Webber <david@drrw.info>
>Subject: Re: [ebxml-bp] Proposal for minOccurs and maxOccurs attributes to Attachment
>Date: Thu, 07 Oct 2004 22:13:39 -0400
>
>  
>
>>Yano,
>>
>>The only thing I see with this is that this is a bit confusing when schema
>>itself
>>already uses these terms - I'd prefer to use 'repeatable' true/false and
>>then 'limit'.
>>
>>Otherwise seems reasonable.
>>
>>Thanks, DW
>>
>>----- Original Message ----- 
>>From: <YANO Keisuke ($BLpLn7<2p(B) <yano@jp.fujitsu.com>)>
>>To: <ebxml-bp@lists.oasis-open.org>
>>Sent: Thursday, October 07, 2004 10:08 PM
>>Subject: [ebxml-bp] Proposal for minOccurs and maxOccurs attributes to
>>Attachment
>>
>>
>>    
>>
>>>ebBP TC members,
>>>
>>>I would like to propose to add the minOccurs and maxOccurs attributes
>>>to the Attachment element of BPSS.  An example is following:
>>>
>>>    <Attachment name="SpecificationAttachment"
>>>        businessDocument="BD:SpecAttachment" businessDocumentIDRef="att"
>>>        mimeType="application/pdf"
>>>        minOccurs="0" maxOccurs="5"/>  <!-- here -->
>>>
>>>These attributes are similar to the same name attributes of the
>>>Constituent element of ebXML CPPA.  The XML schema fragment for these
>>>attributes in the Attachment element definition may be following.
>>>
>>>    <xsd:attribute name="minOccurs" type="xsd:nonNegativeInteger"/>
>>>    <xsd:attribute name="maxOccurs" type="xsd:nonNegativeInteger"/>
>>>
>>>This proposal is based on the requirement of the ECALGA business
>>>process specifications developed by JEITA [1].  They need to specify
>>>that an attachment is optional (i.e., minOccurs="0" and
>>>maxOccurs="1").  Also, it is likely that they will want to specify
>>>that the number of attachments is arbitrary in the future.
>>>
>>>FYI, ECALGA is a B2B electronic commerce specification that adopts
>>>BPSS, CPA, and ebMS for electronics and IT industries.  You might be
>>>insterested in my article [2] on JEITA's interoperability test using
>>>ebXML.
>>>
>>>[1] Japan Electronics and Information Technology Industries Association,
>>>    http://ec.jeita.or.jp/
>>>[2] Original Japanese version:
>>>     http://xml.fujitsu.com/jp/column/frontline/ebxml_2.html
>>>    English translation:
>>>
>>>      
>>>
>>http://www.fujitsu.com/services/solutions/xml/frontline/XML_ebxml2.html
>>    
>>
>>>Regards,
>>>
>>>Yano Keisuke
>>>
>>>      
>>>
>>    
>>