Lines Matching full:processor
154 normative since we do not require the processor to enforce any
163 system identifiers (processor 'may' signal an error).
234 Tag definition of validating processor and link to it.
315 have values supplied by processor.</sitem>
375 <p><termdef id="dt-xml-proc" term="XML Processor">A software module
376 called an <term>XML processor</term> is used to read XML documents
377 and provide access to their content and structure.</termdef> <termdef id="dt-app" term="Application">It is assumed that an XML processor is
380 required behavior of an XML processor in terms of how it must read XML
434 definitions and in describing the actions of an XML processor:
460 which a conforming <termref def="dt-xml-proc">XML processor</termref>
463 processor may continue
466 the processor may make unprocessed data from the document (with
468 Once a fatal error is detected, however, the processor must not
870 processor may, but need not, make it possible for an application to
1206 as passed from an <termref def="dt-xml-proc">XML processor</termref>
1231 which affect the information passed from the XML processor to
1287 <p>An <termref def="dt-xml-proc">XML processor</termref>
1290 validating XML processor</termref> must also inform the application
1329 #xD, an <termref def="dt-xml-proc">XML processor</termref> must
1429 The application, not the XML processor, is responsible for this '
1652 At user option, an XML processor may issue a warning
1874 user option, an XML processor may issue a warning if attributes are
1890 For interoperability, an XML processor may at user option
1990 <p>The XML processor must normalize attribute values before
2058 the attribute's presence is required, and if not, how an XML processor should
2082 the XML processor must inform the application
2092 is declared, when an XML processor encounters an omitted attribute, it
2128 XML processor must normalize it as follows:
2143 <p>If the declared value is not CDATA, then the XML processor must
2218 content before the processor decides whether to
2237 <head>XML Processor Treatment of Logical Structure</head>
2238 <p>When an XML processor encounters a start-tag, it must make
2273 processor</termref> and may contain the whole document.</p>
2288 that an XML processor make the identifiers for the entity and
2384 external parameter entities, a non-validating processor is
2481 encountered is binding; at user option, an XML processor may issue a
2548 an XML processor may signal an error if a fragment identifier is
2560 <p>An XML processor should handle a non-ASCII character in a URI by
2568 An XML processor attempting to retrieve the entity's content may use the public
2569 identifier to try to generate an alternative URI. If the processor
2664 <p>Although an XML processor is required to read only entities in
2718 an encoding declaration to be presented to the XML processor
2728 <p>It is a <termref def="dt-fatal">fatal error</termref> when an XML processor
2736 <head>XML Processor Treatment of Entities and References</head>
2739 required behavior of an <termref def="dt-xml-proc">XML processor</termref> in
2871 <p>When an XML processor recognizes a reference to a parsed entity, in order
2873 the document, the processor must
2876 If the entity is external, and the processor is not
2878 processor <termref def="dt-may">may</termref>, but need not,
2930 a validating processor must inform the
3053 processor or its client application to locate a helper application
3075 application to call a processor for data in the notation described. (It
3078 the system where the XML processor or application is running.)</p>
3088 processor</termref>.</termdef>
3091 processor; unlike other entities, the document entity has no name and might
3092 well appear on a processor input stream
3113 <p><termdef id="dt-validating" term="Validating Processor">
3149 <p>The behavior of a validating XML processor is highly predictable; it
3152 Less is required of a non-validating processor; it need not read any
3157 reading external entities, may not be detected by a non-validating processor.
3165 <item><p>The information passed from the processor to the application may
3166 vary, depending on whether the processor reads
3168 For example, a non-validating processor may not
3864 then the XML processor will recognize the character references
3968 processor can read the internal label, however, it apparently has to
3980 processor without, or with, any accompanying
3986 must be '<code><?xml</code>', any conforming processor can detect,
4052 ASCII characters, a processor can reliably read the entire encoding
4061 Once the processor has detected the character encoding in use, it can
