CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 02:43:28 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:30:33 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 02:43:28 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cb02941d8acb77
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=AXkXScv97OCGa5NM.7WhP3PAgFWL4W82cKV_6mj09no-1760150608-1.0.1.1-.MAo0cTtJAv3anKvro1974tuxk6k.iH4_yDXUcfr69rNImvklA8s2_EJCiz7Xvyq4MCeWze9QxEGsg3IL8jV53eb43JqYdZMC2SIyA.x2HE; path=/; expires=Sat, 11-Oct-25 03:13:28 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cb02941d8acb77-BLR
alt-svc: h3=":443"; ma=86400
Processor vs parser from Lars Marius Garshol on 2000-06-24 (xml-editor@w3.org from April to June 2000)
Processor vs parser
- From: Lars Marius Garshol <larsga@garshol.priv.no>
- Date: 24 Jun 2000 15:45:23 +0200
- To: xml-editor@w3.org
- Message-ID: <m3wvjfxkek.fsf@lambda.garshol.priv.no>
I just noticed that the XML recommendation in some places uses the term 'parser' where it really should have used 'processor'. The third paragraph of the recommendation introduces the term processor and this is used throughout, except in these cases: 3.3.3: "All attributes for which no declaration has been read should be treated by a non-validating parser as if declared CDATA." 4.4.3: "...If a non-validating parser does not include the replacement text..." E: "... because given an initial b the parser cannot know which b in the model is being matched..." There is also another occurrence just below. Clearly, in these cases 'processor' is really what is meant, and the term 'parser' is just a leftover from SGML terminology. As near as I can tell, this is not listed in the errata document, so I hope this is a new 'bug'. --Lars M.
Received on Saturday, 24 June 2000 09:45:14 UTC