Defining General Entities and Parameter Entities in DTDs

In DTDs, an entity allows you to define a symbol for a value. In the Tree view, you can define general entities and parameter entities. The value of a general entity can be just about anything. It can be

  • A short string that represents a longer string
  • A way to include another marked-up file
  • A reference to a graphical image
  • A placeholder for some non-XML data or an expression that needs special formatting

General entities are useful for things that change often, such as the name of a product in development. An entity allows you to change the value in one place and have the corrected value appear everywhere it is needed.

See also Description of Entity and Parameter Entity Properties in DTDs.

When you define a general entity, you specify a symbol that you can use in instance documents. When the XML parser finds a reference to a general entity, it replaces the symbol with the value you specified when you defined the general entity.

When you define a parameter entity, you specify a symbol that you can use elsewhere in the DTD. Again, when the XML parser finds a reference to a parameter entity, it replaces the reference with the value you specified when you defined the parameter entity.

In a DTD, the definition of an entity must appear before a reference to that entity. Therefore, it is good practice to put all entity declarations at the beginning of a DTD.

This section discusses the following topics:

WYSIWYG XSLT Designer

Stylus Studio's powerful and easy-to-use WYSIWYG ("What you see is what you get") XSLT Designer lets you create XSLT stylesheets without writing any code! Go from a blank slate to solid, robust XSLT in minutes, using simple drag-and-drop operations.

Translating XML documents to EDIFACT

In-place, via XSLT and via XQuery are all mechanisms supported for converting XML to EDIFACT

Getting EDI to XML and back to EDI Again: Round Trip Engineering using Stylus Studio URL Adapters

A free online video demonstration shows how to use Stylus Studio's Adapter URL technologies to convert EDI to XML and back again. Convert, validate, view and edit EDIFACT data directly in Stylus Studio.

Translating XML documents to X12

In-place, via XSLT and via XQuery are all mechanisms supported for converting XML to X12

Stylus Most Wanted

 
Free Stylus Studio XML Training:
W3C Member