Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML Schema generation

From: Sandy <sandeep.rec@-----.--->
To: NULL
Date: 8/1/2008 6:50:00 AM
I need some help from the forum for designing the xml schema. The
scenario is client service architecture.
I have some configuration files(our own proprietary format, can be
considered as some form of text file) at server.
user can populate the required fields.
Since we are moving from text file format to xml file to store the
date. we have to convert all these configuration files to
XML files manually. or we can retain the same configuration file but
we should create mechanism so that these
files are converted to XML. Is there any way create to create a
Generalized schema so that it could accomodate
all the scenarios described below.Now i need to create a generalized
schema to accomodate multiple configuration files.
I am attaching some configuration files for the reference.


********************* File 1******************

configr-format-name:    xyz
configr-format-type:    IEEE
configr-description:    "abc"

#Field Name                        Size  Type                 Match
Value
#----------                        ----  ----
-----------

"Destination Address"              6
STRING
"Source Address"                   6
STRING
"Ether Type"                       2     STRING                INTVAL
A-N
"Version + IHL"                    1
-
"Type of Service"                  1
-
"Total Length"                     2
-
"Identification"                   2
-
"Flags + Fragment Off"             2
-
"Time to Live"                     1
-
"Protocol"                         1
STRING
"Header Checksum"                  2
-
"Source Address"                   4
STRING
"Destination Address"              4     STRINGSTRING


*********************** File 2 ********************

fconfigr-format-name:    xyz1
configr-format-type:    IEEE
configr-description:    "abcd"

#Field Name                        Size  Type       Match
Value
#----------                        ----  ----
-----------

"Destination Address"              6     STRING
"Source Address"                   6     STRING
"Ether Type"                       2     STRING      INTVAL A-N
"Version + IHL"                    1     -
"Type of Service"                  1     -
"Total Length"                     2     -
"Identification"                   2     -
"Flags + Fragment Off"             2     -
"Time to Live"                     1     -
"Protocol"                         1     STRING         INTVAL A-N
"Header Checksum"                  2     -
"Source Address"                   4     STRING
"Destination Address"              4     STRING
"Source Port"                      2     STRING
"Destination Port"                 2     STRING      INTVAL A-N
"Sequence Number"                  4     -
"Acknowledgement Number"           4     -
"Offset & Reserved"                1     -
"Window Control Bits"              1     -
"Window"                           2     -
"Checksum"                         2     -
"Urgent Pointer"                   2     -
"Options"                          1     -


*********************** File 3 ********************
fconfigr-format-name:    xyz1
configr-format-type:    IEEE
configr-description:    "abcd"

#Field Name                        Size  Type       Match
Value
#----------                        ----  ----       -----------
"Source SAP"        1    -
"Destination SAP"    1    -
"Control"            1    -

*********************** File 4 ********************
fconfigr-format-name:    xyz1
configr-format-type:    IEEE
configr-description:    "abcd"


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent