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 Schema help

[ Lists Home | Date Index | Thread Index ]

Title: RE: [xml-dev] XML Schema help

Hi Joseph,
As i described you the detail problem. I could understood how would i parse the output from a command. But I couldnt understand how would i use xml schema to write a structure of a command e.g. i need to generate a command based upon the parameters. Can you suggest me something on it or probably some gud document for it.

thanks
-tarun


-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Thu 19-Jan-06 18:05
To: Tarun Sharma (WT01 - Software Products & OSS); xml-dev@lists.xml.org
Subject: RE: [xml-dev] XML Schema help

So that someone may best answer your question: Please first describe any
challenges you have encountered in creating an XML schema that
"represents" your XML document below. From your message, it looked like
you were looking for some sort of tutorial, but that may not be the
case. What is your specific concern?

Kind Regards,
Joseph Chiusano
Associate
Booz Allen Hamilton

700 13th St. NW, Suite 1100
Washington, DC 20005
O: 202-508-6514 
C: 202-251-0731
Visit us online@ http://www.boozallen.com <http://www.boozallen.com/>



________________________________

        From: sharma.tarun@wipro.com [mailto:sharma.tarun@wipro.com]
        Sent: Thursday, January 19, 2006 7:06 AM
        To: xml-dev@lists.xml.org
        Cc: sharma.tarun@wipro.com
        Subject: [xml-dev] XML Schema help
        Importance: High
       
       

        Hi,

        I am very new user of XML and first time writing some XML schema
for parsing commands input as well as response. My commands have some
structure like this:

        RUNTCP:PORT=124,IP1=192,IP2=168,IP3=10,IP4=12,RIP="230.164.12.8"

        

        The requirement is such that I need to generate commands from
the given attributes or parameters.  The whole program should be
independent of the commands and their parameters.

        

        Similarly I get the output in following format

        

        RUNTCP OUTPUT DATA

        

        PORT   IP1    IP2    IP3    IP4 

        Port1   ip1      ip2    ip3     ip4

        .

        .

        .

        .

        .

        ERROR CODE

        BROKEN PIPE

        END

        

        The other example could be

        

        GETTCP

        PORT   IP1    IP2    IP3    IP4 

        Port1   ip1      ip2    ip3     ip4

        

        Port2

        

        Port3

        .

        .

        .

        .

        .

        NONE

        ERROR CODE

        BROKEN PIPE

        END

        

        Only ports are getting repeated in this case.

        

        

        

        Which means that the output will give us some parameters and it
can give some errors like ERROR CODE

         or BROKEN PIPE  etc. Finally it ends with the end.

        

        

        

        I also need to parse this output to get the desired results.
Here is the example schema I wrote for the output:

        <?xml version="1.0" ?>

        - <GATEWAY>

        - <command name="RUNTCP" versions="4.0">

           - <output start=" RUNTCP OUTPUT DATA" end="END" none="NONE"
error="ERROR CODE" bp="BROKEN PIPE">

                    - <section start="MG" end="MG" repeatable="yes"
mandatory="yes">

                                - <paramset start="PORT"
mandatory="yes">

                                            <param name="PORT" key="yes"
mandatory="yes" />

                                </paramset>

        

                                - <paramset start="IP1" mandatory="yes">

                                            <param name="IP1"
mandatory="yes" />

                                </paramset>

        

                                - <paramset start="IP2" mandatory="yes">

                                            <param name="IP2"
mandatory="yes" />

                                </paramset>

                   

                                - <paramset start="IP3" mandatory="no">

                                            <param name="IP3"
mandatory="yes" />

                                </paramset>

                   

                                - <paramset start="IP4" mandatory="no">

                                            <param name="IP4"
mandatory="yes" />

                                </paramset>

                     </section>

          </printout>

         </command>

        

        Can anybody suggest me some solution schema for it.

        

        

        Thanks in advance

        Regards

        Tarun sharma


The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

www.wipro.com
       



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com




 

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

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