I am trying to sort out some weird behavior with respect to including
system configurations and augmenting detection capabilities. In
particular, I have included a system configuration and added another
detection section to the parent configuration. My first problem is that
with the additional detection section, the included detection no longer
seems to work. Is there any way to add new detection functionality to
a previous set?
My second problem is that a given detection rule doesn't seem to match,
and I'm not entirely sure why. The detection rule is of the form:
<cfg:detect>
<cfg:dtdSystemId>http://some.where/some.dtd</cfg:dtdSystemId>
</cfg:detect>
But this is not matching an external entity reference of the form:
<!DOCTYPE root PUBLIC "-//Group//Some PubidLiteral//EN"
"http://some.where/some.dtd";>
It is not entirely clear from the documentation (perhaps the bug lies
there), but it might be that <cfg:dtdSystemId> only matches the
SystemLiteral[0] of a SYSTEM external entity reference and that
<cfg:dtdPublicId> only matches the PubidLiteral of a PUBLIC external
entity reference. If this is the case, then I seek the ability to match
on the SystemLiteral of the PUBLIC external entity reference. This may
be a non-issue, as it may be true that I can always match on the
PubidLiteral instead, but I am concerned about allocating PubidLiterals
(but not SystemLiterals) to information sets which I am developing.
Take care,
John L. Clark
[0] http://www.w3.org/TR/2004/REC-xml-20040204/#NT-ExternalID
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040209/f599f749/attachment.sig
