«

Hi,

I'm writing my own validating XML parser in C++ (it seemed like a good way to
understand the specification!) and I'm a bit stuck on the SystemLiteral. The
"rules" say it can be any valid character but the text also gives a "Definition"
saying it is a URI conforming to RFC2396 and RFC2732. So what should a
validating parser do if a SystemLiteral does not conform to these RFCs?

Specifically, what should a validating parser do if

1. A SystemLiteral is an invalid URI
2. It cannot access the resource given by the URI (which it needs to do to
validate the document).

And more generally, what should a validating parser do if a document does not
break any WFC or VC but does not agree with a "Definition"?

Mike.

In article <ZBBeb.8756$>,
Mike Reed <> wrote:
> The
>"rules" say it can be any valid character but the text also gives a
>"Definition"
>saying it is a URI conforming to RFC2396 and RFC2732.

First, make sure that you are taking account of all the errata. There
have been some amendments to the description of system identifiers.

Bascially system identifiers are "IRIs", though there is not standard
for that yet. That is, they are strings that are legal URIs after
escaping certain characters.

The natural approach is to defer most checking to the URI retrieval
level, and treat errors as resource errors (and probably abort) rather
than validity or well-formedness errors.

-- Richard
--
Spam filter: to mail me from a .com/.net site, put my surname in the headers.

FreeBSD rules!