That is not XML.

I'm not quite sure how to interpret the multiple entries under same tag name can exist.. On the other hand tags can repeat an even values within tags can repeat (though there are better solutions). In both cases it is well formed XML.

With minor edits the example provided is well formed XML.

<?xml version="1.0" encoding="UTF-8"?>

<GEN_FSM xsi:noNamespaceSchemaLocation="Desktop/test.xsd" xmlns:xsi="h
+ttp://www.w3.org/2001/XMLSchema-instance">
<State>
<Name>POWERED</Name>
<Comment>USB POWERED State</Comment>
</State>
<State>
<Name>DEFAULT</Name>
<Comment>USB DEFAULT State</Comment>
</State>
<State>
<Name>ADDRESS</Name>
<Comment>USB ADDRESS State</Comment>
</State>
<Rst_Arc>
<To_State>DEFAULT</To_State>
<monitor_mode_event_name>HOT_RST</monitor_mode_event_name>
<monitor_mode_event_count>1</monitor_mode_event_count>
<comment>HOT_reset_to_DEFAULT</comment>
</Rst_Arc>
</GEN_FSM>
[download]

It can even be validated by a schema (auto generated):

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema elementFormDefault="qualified" xmlns:xsd="http://www.w3.or
+g/2001/XMLSchema">
    <xsd:element name="GEN_FSM">
        <xsd:complexType>
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element ref="State"/>
                <xsd:element ref="Rst_Arc"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="State">
        <xsd:complexType mixed="true">
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element ref="Name"/>
                <xsd:element ref="Comment"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="Name" type="xsd:string"/>
    <xsd:element name="Comment" type="xsd:string"/>
    <xsd:element name="Rst_Arc">
        <xsd:complexType mixed="true">
            <xsd:choice minOccurs="0" maxOccurs="unbounded">
                <xsd:element ref="To_State"/>
                <xsd:element ref="monitor_mode_event_name"/>
                <xsd:element ref="monitor_mode_event_count"/>
                <xsd:element ref="comment"/>
            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
    <xsd:element name="To_State" type="xsd:string"/>
    <xsd:element name="monitor_mode_event_name" type="xsd:string"/>
    <xsd:element name="monitor_mode_event_count" type="xsd:integer"/>
    <xsd:element name="comment" type="xsd:string"/>
</xsd:schema>
[download]

Cheers

Harry

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.