[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Fw: [ebxml-msg] Fw: Please post (msg-header-2_0.xsd)
>2. I understand that the presence of DuplicateElimination element >is enough to deduce that duplicate elimination is desired; however, some XML >Schema to Java generation tools, I believe, >may not like such schema definitions when converting the element >schema to its corresponding Java Bean API. Do we want to do address the above issue reported by Zahid Ahmed? -Arvola -----Original Message----- From: Ahmed, Zahid <zahid.ahmed@commerceone.com> To: 'Arvola Chan' <arvola@tibco.com> Date: Monday, January 14, 2002 11:43 AM Subject: RE: [ebxml-msg] Fw: Please post (msg-header-2_0.xsd) >>The presence of the DuplicateElimination element indicates that >>duplicate elimination is desired. There is no need for any >>additional attribute within that element. > >1. Which version of the CPA are you refering to that has >the duplicateElimination attribute defined? > >In the draft-cpp-cpa-08b.xsd the schema does not seem >to have any attribute called duplicateElimination. > >2. I understand that the presence of DuplicateElimination element >is enough to deduce that duplicate elimination is desired; however, some XML >Schema to Java generation tools, I believe, >may not like such schema definitions when converting the element >schema to its corresponding Java Bean API. > >thanks, >Zahid > > > >-----Original Message----- >From: Arvola Chan [mailto:arvola@tibco.com] >Sent: Friday, January 11, 2002 7:28 PM >To: Ahmed Zahid; David Fischer >Cc: ebxml-msg@lists.oasis-open.org >Subject: Re: [ebxml-msg] Fw: Please post (msg-header-2_0.xsd) > > >In the CPA, there is a duplicateElimination attribute that can take on the >values "never", "always", or "perMessage". > >If it is "never", that means the two parties have agreed that duplication >elimination should never be done. In that case, the ebXML message MUST not >include a DuplicateElimination element. > >If it is "always", that means the two parties have agreed that duplication >should always be done. In that case, the ebXML message MUST always carry a >DuplicateElimination element. > >If it is "perMessage", then the application may determine on a per message >(actually per conversation) basis whether duplicate elimination should be >carried out. > >The presence of the DuplicateElimination element indicates that duplicate >elimination is desired. There is no need for any additional attribute within >that element. > >Regards, >-Arvola > >----- Original Message ----- >From: "Ahmed, Zahid" <zahid.ahmed@commerceone.com> >To: "'Arvola Chan'" <arvola@tibco.com>; "David Fischer" ><david@drummondgroup.com> >Cc: <ebxml-msg@lists.oasis-open.org> >Sent: Friday, January 11, 2002 7:12 PM >Subject: RE: [ebxml-msg] Fw: Please post (msg-header-2_0.xsd) > > >> Another question: >> >> In the msg-header-2_0.xsd schema, DuplicateElimination >> is defined as: >> >> <element name="DuplicateElimination"> >> </element> >> >> >> However, there is no duplicateElimination attribute >> defined for it to take the values: "perMessage" or >> "always". >> >> Amy I missing something? >> >> E.g., is this really an omisison in the latest >> schema. if yes, I suggest following modification of >> the msg-header-2_0.xsd schema: >> >> <element name="DuplicateElimination"> >> <simpleType> >> <restriction base="string"> >> <enumeration value="perMessage"/> >> <enumeration value="always"/> >> </restriction> >> </simpleType> >> </element> >> >> >> >> thanks, >> Zahid >> >> Zahid Ahmed >> Commerce Security Architect >> Commerce One, Inc. >> 408/517-3903 >> >> -----Original Message----- >> From: Arvola Chan [mailto:arvola@tibco.com] >> Sent: Monday, January 07, 2002 8:11 AM >> To: David Fischer; ian.c.jones@bt.com >> Cc: ebxml-msg@lists.oasis-open.org >> Subject: [ebxml-msg] Fw: Please post (msg-header-2_0.xsd) >> >> >> David and Ian: >> >> Should I ask Jeff to create a >> >> http://www.oasis-open.org/committees/ebxml-msg/doc >> >> directory as the home directory for the spec document? I can ask him for >> the passwords for the schema and doc directories so that we can maintain >> the files in these directories directly. >> >> Regards, >> -Arvola >> >> -----Original Message----- >> From: Jeffrey Lomas <jeff.lomas@oasis-open.org> >> To: Arvola Chan <arvola@tibco.com> >> Date: Monday, January 07, 2002 6:46 AM >> Subject: Re: Please post (msg-header-2_0.xsd) >> >> >> >Arvola, >> >I posted the document you requested. While on the server I noticed that >> the >> >ebxml-msg TC is set up to maintain its committee pages itself. This >means >> >that whoever has the user name and password to the ebxml-msg ftp >directory >> >can post documents to the schema directory. Let me know if I can ever be >> of >> >assistance. >> > >> >Regards, >> >Jeffrey Lomas >> >OASIS >> > >> >Arvola Chan wrote: >> > >> >> Jeffrey: >> >> >> >> Please post the attached file to >> >> >> >> >http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd >> >> >> >> Thanks, >> >> -Arvola >> >> >> > ----------------------------------------------------------------------- >> - >> >> Name: msg-header-2_0.xsd >> >> msg-header-2_0.xsd Type: unspecified type >> (application/octet-stream) >> >> Encoding: quoted-printable >> > >> >> >> ---------------------------------------------------------------- >> To subscribe or unsubscribe from this elist use the subscription >> manager: <http://lists.oasis-open.org/ob/adm.pl> >> >> ---------------------------------------------------------------- >> To subscribe or unsubscribe from this elist use the subscription >> manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC