DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Vitaly Ostanin [EMAIL PROTECTED] was heard to say: | DocBook DTD doesn't support 'xml:base' attribute from XInclude. I think we're planning to fix that[1]. | Yes, this attribute appear to content model, and useful for many | of included documents - 'xml:base' could be useful for getting | uniq values of 'id', uniq names of images in graphics in the | all set of documents. Base URIs have no bearing on ID values. Be seeing you, norm [1] http://lists.oasis-open.org/archives/docbook-tc/200211/msg00012.html - -- Norman Walsh [EMAIL PROTECTED] | Time is the old justice that http://www.oasis-open.org/docbook/ | examines all Chair, DocBook Technical Committee | offenders.--Shakespeare -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE97KPLOyltUcwYWjsRAk8IAJ0aGQBG7KT8FPuV83+5Z1IjGTcuTwCeLbF/ qe4bT9QPLEHA2JvArJzbqW0= =eXmr -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
On Tue, 03 Dec 2002 07:30:03 -0500 Norman Walsh [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Vitaly Ostanin [EMAIL PROTECTED] was heard to say: | DocBook DTD doesn't support 'xml:base' attribute from | XInclude. I think we're planning to fix that[1]. Thanks. | Yes, this attribute appear to content model, and useful for | many of included documents - 'xml:base' could be useful for | getting uniq values of 'id', uniq names of images in | graphics in the all set of documents. Base URIs have no bearing on ID values. ID values used for linking and must be uniq, right? In modular set of docbook/xml after processing XInclude some documents may to have duplicates of ID. I think what using 'xml:base' + 'filename' + 'id' can produce uniq values as result. In this case final value of 'xml:base' can be calculated also from 'xml:base' of parent tags (if there exists relative values). This changes appear 'idref' of xref/ and link/. For images we have a similar problem - files with images must have uniq names. BTW, all html build exist in the one dir (except sitemap of olinking schema from Bab Stayton). 'xml:base' could be useful for split documents into separate dirs. Sorry for disturb. skipped/ -- Regards, Vyt mailto: [EMAIL PROTECTED] JID: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
At 16:00 2002 12 03 +0300, Vitaly Ostanin wrote: On Tue, 03 Dec 2002 07:30:03 -0500 Norman Walsh [EMAIL PROTECTED] wrote: Base URIs have no bearing on ID values. ID values used for linking and must be uniq, right? It is a validation error if there are duplicate IDs in a document. In modular set of docbook/xml after processing XInclude some documents may to have duplicates of ID. True, and this would be a validation error. The same is true if you used external parsed entities. XInclude does nothing to solve the ID uniqueness problem. In particular, if you reuse the same chunk of XML in two places in the same document and any element therein contains an ID, you will end up with a document that is not valid (whether you use external parsed entities or XInclude). I think what using 'xml:base' + 'filename' + 'id' can produce uniq values as result. Maybe, but that isn't how things work in XML. paul
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
On Tue, 03 Dec 2002 09:19:19 -0600 Paul Grosso [EMAIL PROTECTED] wrote: skipped/ In modular set of docbook/xml after processing XInclude some documents may to have duplicates of ID. True, and this would be a validation error. The same is true if you used external parsed entities. XInclude does nothing to solve the ID uniqueness problem. In particular, if you reuse the same chunk of XML in two places in the same document and any element therein contains an ID, you will end up with a document that is not valid (whether you use external parsed entities or XInclude). You right. Thanks for the answer. skipped/ -- Regards, Vyt mailto: [EMAIL PROTECTED] JID: [EMAIL PROTECTED]
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
On Sun, 01 Dec 2002 21:07:45 -0800 Bob Stayton [EMAIL PROTECTED] wrote: skipped/ It isn't that we (the DocBook Technical Committee) don't want to add an xinclude element, or that we think it is not needed. It would be easy to add an xinclude element to the DTD. But that isn't enough, because the xinclude element must appear in content models for it to be useful. The problem is that it is hard to write the content models for all cases of possible xinclude usage. An xinclude can replace just about any content, including required elements. That means just about every part of each element's content model needs to change somestuff to (somestuff | xinclude ). IMHO, no - document should be valid _after_ xinclude processing, so DTD must not have support for xi:include/. DocBook DTD doesn't support 'xml:base' attribute from XInclude. Yes, this attribute appear to content model, and useful for many of included documents - 'xml:base' could be useful for getting uniq values of 'id', uniq names of images in graphics in the all set of documents. Now DocBook DTD and stylesheets not have full support of modular documents. PS Sorry for bad English skipped -- Regards, Vyt mailto: [EMAIL PROTECTED] JID: [EMAIL PROTECTED]
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
Daniel Veillard [EMAIL PROTECTED] writes: You should really start accepting that URL can be used as identifiers like any other string, sigh ... It can, but a SYSTEM identifiers is not canonical (= it is not fixed). Let's hope somebody will finish the LSB some time soon regarding XML. Scrollkeeper seems to prefer the SYSTEM identifier, though. All in all, XML is nicely complex (and limited nevertheless ;) ). -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Bob Stayton [EMAIL PROTECTED] was heard to say: | I started to extend the DocBook DTD to permit xi:include, | but I think it is kind of impossible (except for maybe | Norm 8^). The xi:include element can replace *any* | element or group of elements, so the content models of | every element would get hopelessly complex. Try adding xi:include to ndxterm.mix. It's a bit of a hack, but that'll allow it anywhere indexterm is allowed and that's most places. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | The happiest people seem to be http://www.oasis-open.org/docbook/ | those that have no particular Chair, DocBook Technical Committee | reason for being happy except that | they are so.--W. R. Inge -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1BSOyltUcwYWjsRAnh8AJ98pV8R0+ZpxNiLFd61L9dwHZpv9QCfbIri gajqczAMYRwccLXf1TSxONs= =v86b -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Bob Stayton [EMAIL PROTECTED] was heard to say: | Try modelling these examples in a chapter element | declaration: | | chapter | xi:include href=AllChapterContent/ | /chapter Ah, yes, if you want xi:include to replace required elements, you're not going to get the DTD to do that without a lot of work. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | The voice of the intellect is a http://www.oasis-open.org/docbook/ | soft one, but it does not rest Chair, DocBook Technical Committee | until it has gained a | hearing.--Freud -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1FaOyltUcwYWjsRAlY7AJ98LldqUTttSe160bT+NDGJVBF+YQCgieXx yhz7t/72K7jM8bgMbB+Mn9I= =84+G -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Peter Ring [EMAIL PROTECTED] was heard to say: | maintenance a no-brainer. BTW, the catalog.dtd that you get from | http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd is | version 1.7, while the one in the spec is version 1.9. So much for entity | resolution over the net ;) Ooops. Ah, well, I'm in the middle of edits for a new spec release so I'll fix that :-) Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | Nothing is worth more than this http://www.oasis-open.org/docbook/ | day.--Goethe Chair, DocBook Technical Committee | -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1HaOyltUcwYWjsRAgV0AKCea3d5zA+eXYIitzPsv5+3JaumiACfTgp1 RrFK+N2OeqiFT4IHyrENusg= =bosU -END PGP SIGNATURE-
Re: DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
On Thu, Oct 03, 2002 at 02:28:27PM +0200, Karl Eichwalder wrote: Peter Ring [EMAIL PROTECTED] writes: First I'd like to lobby for keeping your local copies of DTDs and stylesheets as a mirror or cache of the canonical URLs. There is no such thing like a canonical URL. Use a catalog and map PUBLIC identifiers to local resources. There is even for docBook stylesheets. I asked Norm in this list before generalizing XML Catalog support in Gnome the answer was yes, http://docbook.sourceforge.net/release/xsl/current http://docbook.sourceforge.net/release/xsl/$version You should really start accepting that URL can be used as identifiers like any other string, sigh ... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
Peter Ring [EMAIL PROTECTED] writes: First I'd like to lobby for keeping your local copies of DTDs and stylesheets as a mirror or cache of the canonical URLs. There is no such thing like a canonical URL. Use a catalog and map PUBLIC identifiers to local resources. Note, PSGML implements a concept how to map PULIC identifiers to local resources and to read it from there without a catalog. -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
