OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   XML Message Interface Documention Methods

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org
  • Subject: XML Message Interface Documention Methods
  • From: Jacquo Johnson <genxgeek@gmail.com>
  • Date: Mon, 19 Sep 2005 12:58:13 -0600
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=brS0Ht54CaSV6Pa2duqBSgKDByIsMKlgJTSyuGGyCtUtb3KRxyCpUcTK+rnQB9viWQmRpJwYlN8CSB16FBYWLe5Kt89ZP4o9UK7bEQlSI7wElqQoRStEY0kcqxAzSvA8156zGbLwWcRWdzD84yjNvg6F0FM88j3q3w6fDd31Kpg=
  • Reply-to: genxgeek@gmail.com

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!




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS