Lines Matching full:processor
172 normative since we do not require the processor to enforce any
181 system identifiers (processor 'may' signal an error).
252 Tag definition of validating processor and link to it.
333 have values supplied by processor.</sitem>
394 <p><termdef id="dt-xml-proc" term="XML Processor">A software module
395 called an <term>XML processor</term> is used to read XML documents
397 id="dt-app" term="Application">It is assumed that an XML processor is
400 required behavior of an XML processor in terms of how it must read XML
454 definitions and in describing the actions of an XML processor:
481 which a conforming <termref def="dt-xml-proc">XML processor</termref>
484 processor may continue
487 the processor may make unprocessed data from the document (with
489 Once a fatal error is detected, however, the processor must not
896 processor may, but need not, make it possible for an application to
1234 as passed from an <termref def="dt-xml-proc">XML processor</termref>
1259 which affect the information passed from the XML processor to
1316 <p>An <termref def='dt-xml-proc'>XML processor</termref>
1319 validating XML processor</termref> must also inform the application
1358 #xD, an <termref def='dt-xml-proc'>XML processor</termref> must
1458 The application, not the XML processor, is responsible for this '
1686 At user option, an XML processor may issue a warning
1912 user option, an XML processor may issue a warning if attributes are
1928 For interoperability, an XML processor may at user option
2028 <p>The XML processor must normalize attribute values before
2097 the attribute's presence is required, and if not, how an XML processor should
2121 the XML processor must inform the application
2131 is declared, when an XML processor encounters an omitted attribute, it
2167 XML processor must normalize it as follows:
2182 <p>If the declared value is not CDATA, then the XML processor must
2257 content before the processor decides whether to
2276 <head>XML Processor Treatment of Logical Structure</head>
2277 <p>When an XML processor encounters a start-tag, it must make
2312 processor</termref> and may contain the whole document.</p>
2328 that an XML processor make the identifiers for the entity and
2425 external parameter entities, a non-validating processor is
2524 encountered is binding; at user option, an XML processor may issue a
2591 an XML processor may signal an error if a fragment identifier is
2603 <p>An XML processor should handle a non-ASCII character in a URI by
2611 An XML processor attempting to retrieve the entity's content may use the public
2612 identifier to try to generate an alternative URI. If the processor
2707 <p>Although an XML processor is required to read only entities in
2761 an encoding declaration to be presented to the XML processor
2771 <p>It is a <termref def='dt-fatal'>fatal error</termref> when an XML processor
2779 <head>XML Processor Treatment of Entities and References</head>
2782 required behavior of an <termref def='dt-xml-proc'>XML processor</termref> in
2914 <p>When an XML processor recognizes a reference to a parsed entity, in order
2916 the document, the processor must
2919 If the entity is external, and the processor is not
2921 processor <termref def="dt-may">may</termref>, but need not,
2973 a validating processor must inform the
3096 processor or its client application to locate a helper application
3118 application to call a processor for data in the notation described. (It
3121 the system where the XML processor or application is running.)</p>
3131 processor</termref>.</termdef>
3134 processor; unlike other entities, the document entity has no name and might
3135 well appear on a processor input stream
3156 <p><termdef id="dt-validating" term="Validating Processor">
3192 <p>The behavior of a validating XML processor is highly predictable; it
3195 Less is required of a non-validating processor; it need not read any
3200 reading external entities, may not be detected by a non-validating processor.
3208 <item><p>The information passed from the processor to the application may
3209 vary, depending on whether the processor reads
3211 For example, a non-validating processor may not
3907 then the XML processor will recognize the character references
4011 processor can read the internal label, however, it apparently has to
4023 processor without, or with, any accompanying
4029 must be '<code><?xml</code>', any conforming processor can detect,
4095 ASCII characters, a processor can reliably read the entire encoding
4104 Once the processor has detected the character encoding in use, it can
