
Docbook-5.0b1 RNC xsl-1.69.1 saxon-6.5.4 eclpse-3.1 windows-XP oXygen-6.2 (eclipse plugin) Xml document: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE targetset SYSTEM "file:///_vhimSepOlinkDB_/targetdatabase.dtd" [ <!ENTITY vhimSepTargetsDB SYSTEM "file:///D:/workspace/vhimSEP/targets.db"> ]> <targetset> <targetsetinfo/> <sitemap> <dir name="vhimSEP"> <document targetdoc="Foo">&vhimSepTargetsDB;</document> </dir> </sitemap> </targetset> <!-- eof --> Target.db output (fragment): <div element="chapter" href="ch01.html" number="1"> <ttl>Purpose, Scope and Objectives</ttl> <xreftext>Chapter 1, <i>Purpose, Scope and Objectives</i> </xreftext> <div element="sect1" href="ch01s01.html" number="1.1"> <ttl>Introduction</ttl> <xreftext>Section 1.1, “Introductionâ€</xreftext> Note both the extended character set and inclusion of html formatting tags. Won’t validate. Please advise. Ray

Hello Ray, If you include a DTD inside the document oXygen will validate against that DTD and not against an eventually externally associated schema (assuming you associated a RNC schema externally with the document through the default schema association options). An external entity is replaced with its content and the validation is performed on that expanded content against the specified DTD. Probably your DTD does not define the elements that are present in your expanded document thus you get validation errors. I do not understand exactly against what DTD/schema you want your document to be valid. If a document is not valid against some DTD or schema you have two options: either correct the document to match the DTD/schema or change the DTD or schema to allow the content from your document. In version 7 (we made available a beta a few days ago [1]) you should be able to specify a Relax NG schema (using a PI inside the document, see the associate schema action in oXygen) and a DTD and configure oXygen to ignore the DTD for validation if a schema is also specified, thus you will get Relax NG validation and entities support through the DTD but no validation against the DTD will be performed. [1] http://www.oxygenxml.com/pipermail/oxygen-user/2005-December/000696.html Happy holidays, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Ray Miller wrote:
Docbook-5.0b1 RNC xsl-1.69.1 saxon-6.5.4 eclpse-3.1 windows-XP oXygen-6.2 (eclipse plugin)
Xml document:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE targetset
SYSTEM "file:///_vhimSepOlinkDB_/targetdatabase.dtd" [
<!ENTITY vhimSepTargetsDB SYSTEM "file:///D:/workspace/vhimSEP/targets.db">
]>
<targetset>
<targetsetinfo/>
<sitemap>
<dir name="vhimSEP">
<document targetdoc="Foo">&vhimSepTargetsDB;</document>
</dir>
</sitemap>
</targetset>
<!-- eof -->
Target.db output (fragment):
<div element="chapter" href="ch01.html" number="1">
<ttl>Purpose, Scope and Objectives</ttl>
<xreftext>Chapter 1, <i>Purpose, Scope and Objectives</i>
</xreftext>
<div element="sect1" href="ch01s01.html" number="1.1">
<ttl>Introduction</ttl>
<xreftext>Section 1.1, “Introductionâ€</xreftext>
Note both the extended character set and inclusion of html formatting tags.
Won’t validate.
Please advise.
Ray
------------------------------------------------------------------------
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

On Thursday, December 29, 2005, 8:49:47 AM, George wrote: GCB> [...] Probably your DTD does not define the elements that are GCB> present in your expanded document thus you get validation errors. GCB> I do not understand exactly against what DTD/schema you want your GCB> document to be valid. If a document is not valid against some DTD or GCB> schema you have two options: either correct the document to match the GCB> DTD/schema or change the DTD or schema to allow the content from your GCB> document. Neither of those options are universally applicable. Consider the common case where a DTD is used for infoset augmentation (eg, declaring an attribute to be of type ID) or for entity declaration, but is not intended to be used for validation. GCB> In version 7 (we made available a beta a few days ago [1]) you should be GCB> able to specify a Relax NG schema (using a PI inside the document, see GCB> the associate schema action in oXygen) and a DTD and configure oXygen to GCB> ignore the DTD for validation if a schema is also specified, thus you GCB> will get Relax NG validation and entities support through the DTD but no GCB> validation against the DTD will be performed. Excellent. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG

Hello Chris, As I said in v7 it will be possible to disable the DTD validation when a schema is also specified (in v6 that was possible only if an XML Schema was also specified). Do you need to disable the DTD validation even in cases when a schema of some sort is not specified and there is only a DTD specified? Best regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Chris Lilley wrote:
On Thursday, December 29, 2005, 8:49:47 AM, George wrote:
GCB> [...] Probably your DTD does not define the elements that are GCB> present in your expanded document thus you get validation errors.
GCB> I do not understand exactly against what DTD/schema you want your GCB> document to be valid. If a document is not valid against some DTD or GCB> schema you have two options: either correct the document to match the GCB> DTD/schema or change the DTD or schema to allow the content from your GCB> document.
Neither of those options are universally applicable.
Consider the common case where a DTD is used for infoset augmentation (eg, declaring an attribute to be of type ID) or for entity declaration, but is not intended to be used for validation.
GCB> In version 7 (we made available a beta a few days ago [1]) you should be GCB> able to specify a Relax NG schema (using a PI inside the document, see GCB> the associate schema action in oXygen) and a DTD and configure oXygen to GCB> ignore the DTD for validation if a schema is also specified, thus you GCB> will get Relax NG validation and entities support through the DTD but no GCB> validation against the DTD will be performed.
Excellent.

On Wednesday, January 4, 2006, 5:46:28 PM, George wrote: GCB> Hello Chris, GCB> As I said in v7 it will be possible to disable the DTD validation when a GCB> schema is also specified (in v6 that was possible only if an XML Schema GCB> was also specified). Yes - I was trying to demonstrate that this is a desirable feature. Not all features of a beta make it to the release version - and people don't always comment on features that they like. GCB> Do you need to disable the DTD validation even in GCB> cases when a schema of some sort is not specified and there is only a GCB> DTD specified? No, in that case the intention of the author is not clear, so validation should be offered. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
participants (3)
-
Chris Lilley
-
George Cristian Bina
-
Ray Miller