Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


replacing ref elements to inline elements

From: "De Heer, Robert S - San Mateo, CA - Contractor" <Robert.S.DeHeer@----.--->
To: <xml-dev@-----.---.--->
Date: 12/2/2005 12:14:00 AM
Title: replacing  ref elements to inline elements




<!---->

I have a question regarding programmatically replacing ref tags with the appropriate block of XML. Is there a standard/recommended way to do this? The refs make design easier, but are a headache in certain development processes. 

For example, replace refs: 

<xs:sequence>

    <xs:element ref="requestor"/>

    <xs:group ref="typeFacilitySpecifier"/>

</xs:sequence> 

with:

<xs:element name="requestor">

    <xs:simpleType>

      <xs:restriction base="xs:token">

        <xs:enumeration value="U"/>

      </xs:restriction>

    </xs:simpleType>

</xs:element>

<xs:group name="typeFacilitySpecifier">

    <xs:sequence>

      <xs:element ref="financeNumber"/>

      <xs:element ref="reportingUnitNumber"/>

    </xs:sequence>

</xs:group>

Thanks,

Rob


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