Home | History | Annotate | Download | only in relaxng

Lines Matching full:entity

10 <!ENTITY XML.version "1.0">
11 <!ENTITY doc.date "10 February 1998">
12 <!ENTITY iso6.doc.date "19980210">
13 <!ENTITY w3c.doc.date "02-Feb-1998">
14 <!ENTITY draft.day '10'>
15 <!ENTITY draft.month 'February'>
16 <!ENTITY draft.year '1998'>
18 <!ENTITY WebSGML
21 <!ENTITY lt "<">
22 <!ENTITY gt ">">
23 <!ENTITY xmlpio "'&lt;?xml'">
24 <!ENTITY pic "'?>'">
25 <!ENTITY br "\n">
26 <!ENTITY cellback '#c0d9c0'>
27 <!ENTITY mdash "--"> <!-- &#x2014, but nsgmls doesn't grok hex -->
28 <!ENTITY com "--">
29 <!ENTITY como "--">
30 <!ENTITY comc "--">
31 <!ENTITY hcro "&amp;#x">
32 <!-- <!ENTITY nbsp "?"> -->
33 <!ENTITY nbsp "&#160;">
34 <!ENTITY magicents "<code>amp</code>,
41 <!ENTITY doc.audience "public review and discussion">
42 <!ENTITY doc.distribution "may be distributed freely, as long as
161 change expansion of entity WebSGML,
225 Add WFC requiring encoding decl to come first in an entity.
263 <sitem>1997-03-29 : CMSMcQ : some Henry Thompson (on entity handling),
274 vice versa for entity text and Literal. (I'd call it Entity Text,
285 WWW conference April 1997: restore some of the internal entity
304 Don't require exposure of entity boundaries.
306 Reserve entity names of the form u-NNNN.
313 Add new rhs to entity declaration, for parameter entities.</sitem>
319 <sitem>1996-10-31 : TB : Add Entity Handling section</sitem>
335 introduce some EBNF for entity declarations.</sitem>
385 def="dt-entity">entities</termref>, which contain either parsed
575 def="dt-entity">entities</termref>. An entity may <termref
578 def="dt-docent">document entity</termref>.
654 <p><termdef id="dt-text" term="Text">A parsed entity contains
679 vary from entity to entity. All XML processors must accept the UTF-8
826 <termref def="dt-entref">entity references</termref>,
843 They are also legal within the <termref def='dt-litentval'>literal entity
844 value</termref> of an internal entity declaration; see
846 <!-- FINAL EDIT: restore internal entity decl or leave it out. -->
1085 <termref def='dt-extent'>external entity</termref>) containing markup
1096 an <termref def="dt-entdecl">entity declaration</termref>, or
1153 <p>Parameter-entity
1160 <termref def='dt-PERef'>parameter-entity reference</termref>,
1166 <termref def='dt-PERef'>parameter-entity references</termref>
1179 or <termref def="dt-PERef">parameter-entity references</termref>.
1205 <termref def="dt-PERef">parameter-entity references</termref>
1226 This has the effect that entity and attribute-list declarations in the
1235 to an application; examples are attribute defaults and entity
1240 the <termref def='dt-docent'>document entity</termref>.
1257 entity</termref> (either in the DTD external subset, or in an
1258 external parameter entity referenced from the internal subset)
1355 wherever an external parsed entity or the literal entity value
1356 of an internal parsed entity contains either the literal
1597 <head>No External Entity References</head>
1599 Attribute values cannot contain direct or indirect entity references
1605 <p>The <termref def='dt-repltext'>replacement text</termref> of any entity
1803 <p>Parameter-entity
1810 <termref def='dt-PERef'>parameter entity</termref>,
1813 if a parameter-entity reference appears in a
1963 <rhs>| 'ENTITY'</rhs>
2006 <head>Entity Name</head>
2008 Values of type <kw>ENTITY</kw>
2014 name of an <termref def="dt-unparsed">unparsed entity</termref> declared in the
2171 <item><p>an entity reference is processed by recursively processing the
2172 replacement text of the entity</p></item>
2176 parsed entity or the literal entity value of an internal parsed
2177 entity</p></item>
2256 parameter-entity reference, the parameter entity must be replaced by its
2260 <eg>&lt;!ENTITY % draft 'INCLUDE' >
2261 &lt;!ENTITY % final 'IGNORE' >
2302 <p><termdef id="dt-entity" term="Entity">An XML document may consist
2305 (except for the document entity, see below, and
2309 Each XML document has one entity
2310 called the <termref def="dt-docent">document entity</termref>, which serves
2314 <termdef id="dt-parsedent" term="Text Entity">A <term>parsed entity's</term>
2320 <p><termdef id="dt-unparsed" term="Unparsed Entity">An
2321 <term>unparsed entity</term>
2324 Each unparsed entity
2328 that an XML processor make the identifiers for the entity and
2333 Parsed entities are invoked by name using entity references;
2334 unparsed entities by name, given in the value of <kw>ENTITY</kw>
2337 <p><termdef id='gen-entity' term='general entity'
2341 to with the unqualified term <emph>entity</emph> when this leads
2343 <termdef id='dt-PE' term='Parameter entity'>Parameter entities
2347 Furthermore, they occupy different namespaces; a parameter entity and
2348 a general entity with the same name are two distinct entities.
2352 <head>Character and Entity References</head>
2379 <p><termdef id="dt-entref" term="Entity Reference">An <term>entity
2380 reference</term> refers to the content of a named entity.</termdef>
2381 <termdef id='dt-GERef' term='General Entity Reference'>References to
2385 <termdef id='dt-PERef' term='Parameter-entity reference'>
2386 <term>Parameter-entity references</term> use percent-sign (<code>%</code>) and
2391 <head>Entity Reference</head>
2411 <head>Entity Declared</head>
2413 DTD subset which contains no parameter entity references, or a document with
2415 the <nt def='NT-Name'>Name</nt> given in the entity reference must
2417 <titleref href='sec-entity-decl'>entity declaration</titleref>, except that
2420 The declaration of a parameter entity must precede any reference to it.
2421 Similarly, the declaration of a general entity must precede any
2428 an entity must be declared is a well-formedness constraint only
2432 <head>Entity Declared</head>
2435 the <nt def='NT-Name'>Name</nt> given in the entity reference must <termref
2437 <titleref href='sec-entity-decl'>entity declaration</titleref>.
2441 The declaration of a parameter entity must precede any reference to it.
2442 Similarly, the declaration of a general entity must precede any
2448 <head>Parsed Entity</head>
2450 An entity reference must not contain the name of an <termref
2451 def="dt-unparsed">unparsed entity</termref>. Unparsed entities may be referred
2453 be of type <kw>ENTITY</kw> or <kw>ENTITIES</kw>.
2459 A parsed entity must not contain a recursive reference to itself,
2466 Parameter-entity references may only appear in the
2470 <p>Examples of character and entity references:
2474 <p>Example of a parameter-entity reference:
2475 <eg><![CDATA[<!-- declare the parameter entity "ISOLat2"... -->
2476 <!ENTITY % ISOLat2
2482 <div2 id='sec-entity-decl'>
2483 <head>Entity Declarations</head>
2485 <p><termdef id="dt-entdecl" term="entity declaration">
2488 <head>Entity Declaration</head>
2496 <rhs>'&lt;!ENTITY' <nt def='NT-S'>S</nt> <nt def='NT-Name'>Name</nt>
2501 <rhs>'&lt;!ENTITY' <nt def='NT-S'>S</nt> '%' <nt def='NT-S'>S</nt>
2519 The <nt def='NT-Name'>Name</nt> identifies the entity in an
2520 <termref def="dt-entref">entity reference</termref> or, in the case of an
2521 unparsed entity, in the value of an <kw>ENTITY</kw> or <kw>ENTITIES</kw>
2523 If the same entity is declared more than once, the first declaration
2531 <p><termdef id='dt-internent' term="Internal Entity Replacement Text">If
2532 the entity definition is an
2534 the defined entity is called an <term>internal entity</term>.
2536 storage object, and the content of the entity is given in the
2538 Note that some processing of entity and character references in the
2539 <termref def='dt-litentval'>literal entity value</termref> may be required to
2543 <p>An internal entity is a <termref def="dt-parsedent">parsed
2544 entity</termref>.</p>
2545 <p>Example of an internal entity declaration:
2546 <eg>&lt;!ENTITY Pub-Status "This is a pre-release of the
2553 <p><termdef id="dt-extent" term="External Entity">If the entity is not
2555 entity</term>, declared as follows:
2557 <head>External Entity Declaration</head>
2577 entity</termref>; otherwise it is a parsed entity.</termdef></p>
2587 is called the entity's <term>system identifier</term>. It is a URI,
2588 which may be used to retrieve the entity.</termdef>
2597 resource within which the entity declaration occurs.
2599 <termref def='dt-docent'>document entity</termref>, to the entity
2601 or to some other <termref def='dt-extent'>external parameter entity</termref>.
2611 An XML processor attempting to retrieve the entity's content may use the public
2617 <p>Examples of external entity declarations:
2618 <eg>&lt;!ENTITY open-hatch
2620 &lt;!ENTITY open-hatch
2623 &lt;!ENTITY hatch-pic
2649 by reference to a parsed entity.
2651 an external parsed entity.</p>
2655 <p>The document entity is well-formed if it matches the production labeled
2658 parsed entity is well-formed if it matches the production labeled
2661 entity is well-formed if it matches the production labeled
2664 <head>Well-Formed External Parsed Entity</head>
2674 An internal general parsed entity is well-formed if its replacement text
2689 <termref def='dt-entref'>entity reference</termref>
2690 can begin in one entity and end in another.</p>
2695 <p>Each external parsed entity in an XML document may use a different
2728 In the <termref def='dt-docent'>document entity</termref>, the encoding
2760 it is an <termref def="dt-error">error</termref> for an entity including
2764 of an external entity, or for
2765 an entity which begins with neither a Byte Order Mark nor an encoding
2772 encounters an entity with an encoding that it is unable to process.</p>
2781 entity references, and invocations of unparsed entities might appear and the
2803 attribute which has been declared as type <kw>ENTITY</kw>, or as one of
2807 <gitem><label>Reference in Entity Value</label>
2809 within a parameter or internal entity's
2810 <termref def='dt-litentval'>literal entity value</termref> in
2811 the entity's declaration; corresponds to the nonterminal
2823 <td bgcolor='&cellback;' align='center' valign='bottom' colspan='4'>Entity Type</td>
2885 special significance; thus, what would be parameter entity references in the
2893 <p><termdef id="dt-include" term="Include">An entity is
2907 as an entity-reference delimiter.)
2914 <p>When an XML processor recognizes a reference to a parsed entity, in order
2919 If the entity is external, and the processor is not
2922 include the entity's replacement text.
2925 read, the entity.</p>
2927 provided by the SGML and XML entity mechanism, primarily designed
2930 Browsers, for example, when encountering an external parsed entity reference,
2931 might choose to provide a visual indication of the entity's
2941 <termref def='dt-unparsed'>unparsed entity</termref>.
2943 <item><p>the appearance of any character or general-entity reference in the
2946 <item><p>a reference to an external entity in an attribute value.</p>
2953 <p>When an <termref def='dt-entref'>entity reference</termref> appears in an
2954 attribute value, or a parameter entity reference appears in a literal entity
2962 <eg><![CDATA[<!ENTITY % YN '"Yes"' >
2963 <!ENTITY WhatHeSaid "He said &YN;" >]]></eg>
2965 <eg>&lt;!ENTITY EndAttr "27'" >
2971 entity</termref> appears as a token in the
2972 value of an attribute of declared type <kw>ENTITY</kw> or <kw>ENTITIES</kw>,
2976 identifiers for both the entity and its associated
2981 <p>When a general entity reference appears in the
2982 <nt def='NT-EntityValue'>EntityValue</nt> in an entity declaration,
2990 When a parameter-entity reference is recognized in the DTD
3002 <head>Construction of Internal Entity Replacement Text</head>
3005 useful to distinguish two forms of the entity's value.
3006 <termdef id="dt-litentval" term='Literal Entity Value'>The <term>literal
3007 entity value</term> is the quoted string actually
3008 present in the entity declaration, corresponding to the
3011 text</term> is the content of the entity, after
3012 replacement of character references and parameter-entity
3016 <p>The literal entity value
3017 as given in an internal entity declaration
3019 parameter-entity, and general-entity references.
3021 literal entity value.
3027 literal entity value; however,
3028 general-entity references must be left as-is, unexpanded.
3031 <eg><![CDATA[<!ENTITY % pub "&#xc9;ditions Gallimard" >
3032 <!ENTITY rights "All rights reserved" >
3033 <!ENTITY book "La Peste: Albert Camus,
3035 then the replacement text for the entity "<code>book</code>" is:
3038 The general-entity reference "<code>&amp;rights;</code>" would be expanded
3049 <p><termdef id="dt-escape" term="escape">Entity and character
3068 <eg><![CDATA[<!ENTITY lt "&#38;#60;">
3069 <!ENTITY gt "&#62;">
3070 <!ENTITY amp "&#38;#38;">
3071 <!ENTITY apos "&#39;">
3072 <!ENTITY quot "&#34;">
3076 are doubly escaped to meet the requirement that entity replacement
3094 entity and attribute-list declarations and in attribute specifications,
3114 value, attribute definition, or entity declaration. They may
3125 <div2 id='sec-doc-entity'>
3126 <head>Document Entity</head>
3128 <p><termdef id="dt-docent" term="Document Entity">The <term>document
3129 entity</term> serves as the root of the entity
3133 not specify how the document entity is to be located by an XML
3134 processor; unlike other entities, the document entity has no name and might
3153 <termref def='dt-docent'>document entity</termref> and any
3167 <termref def='dt-docent'>document entity</termref>, including
3173 internal DTD subset and in any parameter entity that they
3175 to a parameter entity that they do <emph>not</emph> read; that is to
3184 <termref def='dt-entdecl'>entity declarations</termref> or
3186 encountered after a reference to a parameter entity that is not
3187 read, since the entity may have contained overriding declarations.
3196 part of the document other than the document entity.
3202 <titleref href='wf-entdeclared'>Entity Declared</titleref>,
3203 <titleref href='wf-textent'>Parsed Entity</titleref>, and
3897 <head>Expansion of Entity and Character References</head>
3899 sequence of entity- and character-reference recognition and
3903 <eg><![CDATA[<!ENTITY example "<p>An ampersand (&#38;#38;) may be escaped
3904 numerically (&#38;#38;#38;) or with a general entity
3908 when it parses the entity declaration, and resolve them before
3910 value of the entity "<code>example</code>":
3912 numerically (&#38;#38;) or with a general entity
3922 numerically (&#38;) or with a general entity
3932 4 <!ENTITY % xx '&#37;zz;'>
3933 5 <!ENTITY % zz '&#60;!ENTITY tricky "error-prone" >' >
3941 and the parameter entity "<code>xx</code>" is stored in the symbol
3943 is not rescanned, the reference to parameter entity "<code>zz</code>"
3947 expanded immediately and the parameter entity "<code>zz</code>" is
3949 "<code>&lt;!ENTITY tricky "error-prone" ></code>",
3950 which is a well-formed entity declaration.</p></item>
3955 ("<code>&lt;!ENTITY tricky "error-prone" ></code>") is parsed.
3956 The general entity "<code>tricky</code>" has now been
3959 in line 8, the reference to the general entity "<code>tricky</code>" is
4010 entity, indicating which character encoding is in use. Before an XML
4019 entity in normal cases. Also, in many cases other sources of information
4022 depending on whether the XML entity is presented to the
4027 Because each XML entity not in UTF-8 or UTF-16 format <emph>must</emph>
4111 work if any software changes the entity's character set or encoding
4114 of the internal and external information used to label the entity.
4116 <p>The second possible case occurs when the XML entity is accompanied
4130 <item><p>If an XML entity is in a file, the Byte-Order Mark
4135 <item><p>If an XML entity is delivered with a
4141 <item><p>If an XML entity is delivered