[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: xsd, dtd and sample cpp and cpa
I have already done it. XLink is not alone. Here is mine. I'm having problems like this with the TRP 98b also. Made my own XMLDSig and SOAPEnveope conversions also. I have edited our xsd's to reference the import to my own filesystem for several of these. Here is the stuff I am using so far -- and have been able to get a complete validation with no errors -- so now have a clean instance schema-only environment with both CPA and TRP, even though it is my own modified world. ---- NOTE: THE ATTACHED FILES ARE *NOT* THE OFFICIAL EBXML FILES AND ARE LIKELY MODIFIED OR OTHERWISE BUT MAY BE USEFUL IF YOU FIND YOURSELF WITHOUT WHAT YOU NEED OR HAVING PROBLEMS. UNOFFICIAL. ---------- (See attached file: xlink.xsd)(See attached file: trp98b.xsd)(See attached file: envelope.xsd)(See attached file: xmldsig-core-schema.xsd)(See attached file: cpp-cpa-093.xsd) Scott Hinkelman, Senior Software Engineer XML Industry Enablement IBM e-business Standards Strategy 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) srh@us.ibm.com, Fax: 512-838-1074 christopher ferris <chris.ferris@east.sun.com>@xtacy.East.Sun.COM on 03/28/2001 02:08:44 PM Sent by: cferris@xtacy.East.Sun.COM To: Scott Hinkelman/Austin/IBM@IBMUS cc: ebxml-tp@lists.ebxml.org Subject: Re: xsd, dtd and sample cpp and cpa Yes, I'm working on this. It should be a ref="xlink:type" ... but there IS no XLink xsd to import!!! I'm working on an approach recommended by the local schema experts (define my own XSD for xlink) Cheers, Chris Scott Hinkelman wrote: > > Chris, > I don't think we can name prefix an xsd:attribute's name. We have this is > the 93 xsd: > > <xsd:attribute name="xlink:href" type="xsd:uriReference"/> > > Have you seen problems with this? > > Scott Hinkelman, Senior Software Engineer > XML Industry Enablement > IBM e-business Standards Strategy > 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) > srh@us.ibm.com, Fax: 512-838-1074 > > christopher ferris <chris.ferris@east.sun.com>@xtacy.East.Sun.COM on > 03/28/2001 12:01:44 PM > > Sent by: cferris@xtacy.East.Sun.COM > > To: "Moberg, Dale" <Dale_Moberg@stercomm.com> > cc: Martin W Sachs/Watson/IBM@IBMUS, ebxml-tp@lists.ebxml.org > Subject: Re: xsd, dtd and sample cpp and cpa > > Dale, > > Please see below. > > Cheers, > > Chris > > "Moberg, Dale" wrote: > > > > > It would mean (I gather) that Override would also > > > require an IDREF to packagingId, no? > > > > > Wasn't override mainly for transport overrides? > > If packaging has overrides, then yes it would need one too. > > Override is for DeliveryChannel, not just Transport. > > > > > > One further question on Packaging is that I am > > > still unclear as to how one specifies how a given > > > message "fits in" to a given packaging construct. > > > > > > > > Specifically, if I have a message with two parts > > > (say the PO and a JPG "attachment") how does the Packaging > > > get applied? > > > > > > > Well, the MIME content-type is what really says that > > a given content fits in this here package slot... > > > > So if we had a multipart/related with 3 simple parts > > (the header, the PO, and the jpeg), > > we would just list them in order in the SimplePart section. > > This is interesting... WSDL uses a similar approach. > There is still something missing IMHO in both approaches > (I think). > > > > > I will write up your example and post later. > > I think I still would like to put the namespaceUsed element > > in under the SimplePart element because otherwise it will > > be hard to tell what namespace goes with what chunk of xml > > in a multipart having several XML parts. > > Ahh, I see what you were getting at now... Can't wait for > your next posting;-) > > > > > ------------------------------------------------------------------ > > To unsubscribe from this elist send a message with the single word > > "unsubscribe" in the body to: ebxml-tp-request@lists.ebxml.org > > ------------------------------------------------------------------ > To unsubscribe from this elist send a message with the single word > "unsubscribe" in the body to: ebxml-tp-request@lists.ebxml.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC