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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] XML Message Interface Documention Methods

[ Lists Home | Date Index | Thread Index ]
  • To: Chiusano Joseph <chiusano_joseph@bah.com>, xml-dev@lists.xml.org
  • Subject: Re: [xml-dev] XML Message Interface Documention Methods
  • From: Jacquo Johnson <genxgeek@gmail.com>
  • Date: Mon, 19 Sep 2005 19:22:35 -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:in-reply-to:mime-version:content-type:references; b=NkJk9dduJrR81NGn824L7bUFdyTcBaExS/6NKJCT4B+IUKSYcLSA1+Bux3EadNuTl0zvl4pqzMC9XMKQqvi6XXyL2eIvDWpmg1W78f5IpY3hvQRikTwlix91QAGTT34yQeCgo3Vsg4SKh8SD9GwpEj/UvBW63dw8set/BwA/j1c=
  • In-reply-to: <ed0f081d050919182028de8931@mail.gmail.com>
  • References: <74B14CBC0FEB9D4EB16969F09FA51F458C52D6@MCLNEXVS08.resource.ds.bah.com> <ed0f081d050919182028de8931@mail.gmail.com>
  • Reply-to: genxgeek@gmail.com



On 9/19/05, Jacquo Johnson <genxgeek@gmail.com> wrote:
Thanks all.  But how would I actually present the xsd or schema in a user friendly format for newbies that just know how to send messages...i.e. in some dumbed down html format?  Kind of like what a web service interface definition looks like when displayin the xml of what xml message format the service will accept?


On 9/19/05, Chiusano Joseph < chiusano_joseph@bah.com > wrote:
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
 


From: Jacquo Johnson [mailto:genxgeek@gmail.com]
Sent: Monday, September 19, 2005 2:58 PM
To: xml-dev@lists.xml.org
Subject: [xml-dev] 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!






 

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

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