[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: URLs as system identifiers
--wuUGvGHayROCMC3J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 02, 2001 at 03:33:11PM -0500, Adam Di Carlo wrote: > > (The Red Hat Linux openjade RPMs build without http support; should I > > change this?) >=20 > Yes, I think so. Okay. > > The real solution would be for openjade to support XML Catalogs. On > > my system, a document that starts: >=20 > Uh, what's an XML Catalog? *blink* Do you mean SGML Open Catalogs? > Or is there really a perverse new standard, and if so, god help us? I mean XML Catalogs. http://www.oasis-open.org/committees/entity/spec.html "Abstract The requirement that all external identifiers in XML documents must provide a system identifier has unquestionably been of tremendous short-term benefit to the XML community. It has allowed a whole generation of tools to be developed without the added complexity of explicit entity management. However, the interoperability of XML documents has been impeded in several ways by the lack of entity management facilities: 1. External identifiers may require resources that are not always available. For example, a system identifier that points to a resource on another machine may be inaccessible if a network connection is not available. 2. External identifiers may require protocols that are not accessible to all of the vendors' tools on a single computer system. An external identifier that is addressed with the ftp: protocol, for example, is not accessible to a tool that does not support that protocol. 3. It is often convenient to access resources using system identifiers that point to local resources. Exchanging documents that refer to local resources with other systems is problematic at best and impossible at worst. The problems involved with sharing documents, or packages of documents, across multiple systems are large and complex. While there are many important issues involved and a complete solution is beyond the current scope, the OASIS membership agrees upon the enclosed set of conventions to address a useful subset of the complete problem. To address these issues, this Standard defines an entity catalog that maps both external identifiers and arbitrary URI references to URI references." Tim. */ --wuUGvGHayROCMC3J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE74yd8yaXy9qA00+cRAuxqAJ97oiwc2QNtbq90KQIm8HdUfuNa7gCeIK9E PYUruvm1luqR5IcPIQozg8s= =k+tl -----END PGP SIGNATURE----- --wuUGvGHayROCMC3J--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC