Parameter Entity Example in a DTD

Suppose you define the invoice parameter entity as an internal entity as follows:

<!ENTITY % customer "name, street, city, state, zipcode">
               

            

The percent sign ( %) after the ENTITY keyword indicates that this is a parameter entity. Later in the DTD, you can reference this parameter entity as follows:

<!ELEMENT invoice (%customer;, item, price, date)>
               

            

When this DTD is processed, it is as if you had specified the following:

<!ELEMENT invoice (name, street, city, state, zipcode, item, price, date)>
               

            

Why XQuery - The Case for XQuery

Read "The Case for XQuery" - an article that debuted in the November 2005 issue of SOA WebServices Journal, written by Jerry King, Vice President of DataDirect Technologies.

Validating X12 Documents with XML Schemas

Either before or after transforming X12 EDI content, generated XML Schemas will make sure that we have all of the necessary components, our codes are all according to the standard codelists, and every little delimiter is in the right place.

OASIS Catalog Support

Stylus Studio's features for working with OASIS catalogs allow you to incorporate any vendor's catalog - or one of your own - in your XML, making writing correct and robust XML easier than ever.

Convert EDIFACT to XML Schema

Convert EDIFACT to XML with Stylus Studio's XML Schema and legacy data integration tools.

Stylus Most Wanted

 
Free Stylus Studio XML Training:
W3C Member