Dear BaseX Team,
I think I asked this a couple of months ago. We'd like to have XML catalog support when importing files into BaseX.
Or do you have another solution for the following issues:
1. - a customer uses XHTML documents enriched with some semantic tagging which is not XHTML markup - they refer to an XHTML DTD though - we need to use the DTD for resolving entities
Apart from the fact that it is obnoxious to retrieve the DTDs from W3C (and will be blocked if tried to heavily), the major advntage of catalogs will be that we can point BaseX to a modified XHTML DTD that is stored locally and that allows for the additional semantic tags.
=> alternative approach: Patch the data to use standard XHTML markup (such as <span class='supersemantic'>). This doesn't seem feasible because too many tools down the processing chain depend on these custom tags. => other approach: resolve all entities prior to import, discard DOCTYPE declaration. We can do that, but it seems second-best to using catalogs and unmodified data. => Patch data to refer to another DOCTYPE stored somewhere on their servers. This is clearly advisable, because these documents aren't XHTML documents. Need to install the necessary infrastructure. Catalogs are still desirable in this scenario
2. Some of their XML files refer to DTDs such as E:\book\book.dtd We need to resolve these to a DTD that is stored on the server where the import takes place. Again, we could patch the data to refer to some DTD stored centrally on one of their corporate HTTP servers Still, in order to speed up parsing, locally stored DTDs are desirable.
I remember when I proposed to use Apache XML commons resolver [1,2] that Christian replied you would put it on the wish list. I'm trying to prioritize this issue.
(N.B.: it's the same customer who paid someone of your team for solving the base-uri issue...)
Gerrit
[1] http://xml.apache.org/commons/ [2] mirrored at, e.g., http://apache.easy-webs.de//xml/commons/xml-commons-resolver-1.2.tar.gz
Dear Gerrit,
first of all, thanks for your detailed solutions for this problem. Your suggestion is still on our ToDo-List and didnt get lost. Actually our human ressources are limited so we do our best to work down the list.
Regarding the apache resolver...Actually we havent integrated any external packages in BaseX.
In near future we are offering commercial support for BaseX.
Kind regards, Andreas (BaseX Team)
Imsieke, Gerrit, le-tex schrieb:
Dear BaseX Team,
I think I asked this a couple of months ago. We'd like to have XML catalog support when importing files into BaseX.
Or do you have another solution for the following issues:
- a customer uses XHTML documents enriched with some semantic tagging
which is not XHTML markup
- they refer to an XHTML DTD though
- we need to use the DTD for resolving entities
Apart from the fact that it is obnoxious to retrieve the DTDs from W3C (and will be blocked if tried to heavily), the major advntage of catalogs will be that we can point BaseX to a modified XHTML DTD that is stored locally and that allows for the additional semantic tags.
=> alternative approach: Patch the data to use standard XHTML markup (such as <span class='supersemantic'>). This doesn't seem feasible because too many tools down the processing chain depend on these custom tags. => other approach: resolve all entities prior to import, discard DOCTYPE declaration. We can do that, but it seems second-best to using catalogs and unmodified data. => Patch data to refer to another DOCTYPE stored somewhere on their servers. This is clearly advisable, because these documents aren't XHTML documents. Need to install the necessary infrastructure. Catalogs are still desirable in this scenario
Some of their XML files refer to DTDs such as E:\book\book.dtd We need to resolve these to a DTD that is stored on the server where the import takes place. Again, we could patch the data to refer to some DTD stored centrally on one of their corporate HTTP servers Still, in order to speed up parsing, locally stored DTDs are desirable.
I remember when I proposed to use Apache XML commons resolver [1,2] that Christian replied you would put it on the wish list. I'm trying to prioritize this issue.
(N.B.: it's the same customer who paid someone of your team for solving the base-uri issue...)
Gerrit
[1] http://xml.apache.org/commons/ [2] mirrored at, e.g., http://apache.easy-webs.de//xml/commons/xml-commons-resolver-1.2.tar.gz
Dear Gerrit,
thanks for your reminder, and for the proposals on how to best tackle the issue. Michael S., who implemented the hierarchical collection features, will be back by the end of this month, so I'll pass this issue on to him. As Andreas mentioned, our current todo list is somewhat lengthy, so please don't expect miracles for now. Second, we still want to check if an elegant solution exists without embedding external libraries, and we have to find answers on conceptual issues (what's the best way to add DTDs to the resolver, etc.). Proposals are appreciated, from you and everyone else who might be interested in a better handling of external entities.
Christian
On Thu, Sep 23, 2010 at 12:12 PM, Andreas Weiler andreas.weiler@uni-konstanz.de wrote:
Dear Gerrit,
first of all, thanks for your detailed solutions for this problem. Your suggestion is still on our ToDo-List and didnt get lost. Actually our human ressources are limited so we do our best to work down the list.
Regarding the apache resolver...Actually we havent integrated any external packages in BaseX.
In near future we are offering commercial support for BaseX.
Kind regards, Andreas (BaseX Team)
Imsieke, Gerrit, le-tex schrieb:
Dear BaseX Team,
I think I asked this a couple of months ago. We'd like to have XML catalog support when importing files into BaseX.
Or do you have another solution for the following issues:
- a customer uses XHTML documents enriched with some semantic tagging
which is not XHTML markup
- they refer to an XHTML DTD though
- we need to use the DTD for resolving entities
Apart from the fact that it is obnoxious to retrieve the DTDs from W3C (and will be blocked if tried to heavily), the major advntage of catalogs will be that we can point BaseX to a modified XHTML DTD that is stored locally and that allows for the additional semantic tags.
=> alternative approach: Patch the data to use standard XHTML markup (such as <span class='supersemantic'>). This doesn't seem feasible because too many tools down the processing chain depend on these custom tags. => other approach: resolve all entities prior to import, discard DOCTYPE declaration. We can do that, but it seems second-best to using catalogs and unmodified data. => Patch data to refer to another DOCTYPE stored somewhere on their servers. This is clearly advisable, because these documents aren't XHTML documents. Need to install the necessary infrastructure. Catalogs are still desirable in this scenario
Some of their XML files refer to DTDs such as E:\book\book.dtd We need to resolve these to a DTD that is stored on the server where the import takes place. Again, we could patch the data to refer to some DTD stored centrally on one of their corporate HTTP servers Still, in order to speed up parsing, locally stored DTDs are desirable.
I remember when I proposed to use Apache XML commons resolver [1,2] that Christian replied you would put it on the wish list. I'm trying to prioritize this issue.
(N.B.: it's the same customer who paid someone of your team for solving the base-uri issue...)
Gerrit
[1] http://xml.apache.org/commons/ [2] mirrored at, e.g., http://apache.easy-webs.de//xml/commons/xml-commons-resolver-1.2.tar.gz
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
Hi Gerrit,
finally: the latest commit incorporates Catalog Resolving functionality in BaseX.
A catalog file/folder can either be chosen in the DB Create Dialog or via SET CATFILE file1;file2;file3
I hope it suits your customer's needs, feedback will be very welcome.
Kind regards Michael Am 23.09.2010 um 11:19 schrieb Imsieke, Gerrit, le-tex:
Dear BaseX Team,
I think I asked this a couple of months ago. We'd like to have XML catalog support when importing files into BaseX.
Or do you have another solution for the following issues:
- a customer uses XHTML documents enriched with some semantic tagging which is not XHTML markup
- they refer to an XHTML DTD though
- we need to use the DTD for resolving entities
Apart from the fact that it is obnoxious to retrieve the DTDs from W3C (and will be blocked if tried to heavily), the major advntage of catalogs will be that we can point BaseX to a modified XHTML DTD that is stored locally and that allows for the additional semantic tags.
=> alternative approach: Patch the data to use standard XHTML markup (such as <span class='supersemantic'>). This doesn't seem feasible because too many tools down the processing chain depend on these custom tags. => other approach: resolve all entities prior to import, discard DOCTYPE declaration. We can do that, but it seems second-best to using catalogs and unmodified data. => Patch data to refer to another DOCTYPE stored somewhere on their servers. This is clearly advisable, because these documents aren't XHTML documents. Need to install the necessary infrastructure. Catalogs are still desirable in this scenario
Some of their XML files refer to DTDs such as E:\book\book.dtd We need to resolve these to a DTD that is stored on the server where the import takes place. Again, we could patch the data to refer to some DTD stored centrally on one of their corporate HTTP servers Still, in order to speed up parsing, locally stored DTDs are desirable.
I remember when I proposed to use Apache XML commons resolver [1,2] that Christian replied you would put it on the wish list. I'm trying to prioritize this issue.
(N.B.: it's the same customer who paid someone of your team for solving the base-uri issue...)
Gerrit
[1] http://xml.apache.org/commons/ [2] mirrored at, e.g., http://apache.easy-webs.de//xml/commons/xml-commons-resolver-1.2.tar.gz
-- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke@le-tex.de, http://www.le-tex.de
Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930
Geschäftsführer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard Vöckler
Besuchen Sie uns auf der Frankfurter Buchmesse in Halle 4.2, Stand G446.
Mehr dazu unter www.le-tex.de/de/buchmesse.html _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
basex-talk@mailman.uni-konstanz.de
-
Andreas Weiler -
Christian Grün -
Imsieke, Gerrit, le-tex -
Michael Seiferle