|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XML Message Interface Documention Methods
Actually, I believe the original poster meant something different (I could be wrong). I don't believe they meant actual element names called "OptionalElement", "RequiredElement", etc. but rather the technique for representing these things (e.g. minOccurs="0", minOccurs="1", etc.). Joe Joseph Chiusano Booz Allen Hamilton O: 202-508-6514 <= new office number C: 202-251-0731 Visit us online@ http://www.boozallen.com > -----Original Message----- > From: Ian Hunter [mailto:ianh@t...] > Sent: Monday, September 19, 2005 3:34 PM > To: Chiusano Joseph; xml-dev@l... > Subject: RE: XML Message Interface Documention Methods > > Something like this? > > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" > elementFormDefault="qualified"> > <xs:element name="OptionalElement" type="xs:string"/> > <xs:element name="RequiredElement" type="xs:string"/> > <xs:element name="SomeMsgRequest"> > <xs:complexType> > <xs:sequence> > <xs:element ref="RequiredElement"/> > <xs:element > ref="OptionalElement" minOccurs="0" maxOccurs="unbounded"/> > </xs:sequence> > </xs:complexType> > </xs:element> > </xs:schema> > > > ________________________________________ > From: Chiusano Joseph [mailto:chiusano_joseph@b...] > Sent: Monday, September 19, 2005 3:23 PM > To: genxgeek@g...; xml-dev@l... > Subject: RE: XML Message Interface Documention Methods > > You'll get a variety of answers on this from XML-DEV > participants, but I would offer XML Schema (which is the same > as XSD) as one choice. > > Joe > > Joseph Chiusano > Booz Allen Hamilton > O: 202-508-6514 <= new office number > C: 202-251-0731 > Visit us online@ http://www.boozallen.com > > > ________________________________________ > From: Jacquo Johnson [mailto:genxgeek@g...] > Sent: Monday, September 19, 2005 2:58 PM > To: xml-dev@l... > Subject: XML Message Interface Documention Methods > Can somebody tell me a good way to document an xml message > interface from scratch. That is, I have the following > message format (something that is similar in nature): > > <SomeMsgRequest> > <RequiredElement/> > <OptionalElement/> > </SomeMsgRequest> > > And need a good way document the message and what tags are > required and which are optional. > Are there any tools out there that can help with > this...possibly using an xsd or schema? > > Any information is very much appreciated. > > Thanks! >
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








