This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
RE: docbook-xml42, docbook-xsl, xmlto (RE: Pending package status (09 May 2003))
- From: "Peter Ring" <pri at ddf dot dk>
- To: "Andreas" <news dot Andreas at gmx dot net>, <cygwin-apps at cygwin dot com>
- Date: Wed, 21 May 2003 23:36:41 +0200
- Subject: RE: docbook-xml42, docbook-xsl, xmlto (RE: Pending package status (09 May 2003))
I'm reading up on implementations of XML Catalog.
The OASIS Entity Resolution Technical Committee [1] is
currently updating the XML Catalog Committee Spec.
The first committee specification is at [2]. The newest
working draft is at [3]; it will probably move to committee
spec on Tuesday, 27 May 2003.
There's some inspiration to be found in two different
implementation guidelines here [4] and here [5]. Mark
Johnson's guidelines [5] has been submitted to the OASIS
Entity Resolution Technical Committee as an example of
what guidelines might look like.
I'll try to extract the essential features, the basic
design decisions behind these two designs.
Meanwhile, what are the requirements in the Cygwin
environment, apart from 'doing a bit of DocBook now and
then'?
[1] http://www.oasis-open.org/committees/entity
[2] http://www.oasis-open.org/committees/entity/spec-2001-08-06.html
[3]
http://www.oasis-open.org/committees/download.php/1721/wd-entity-xml-catalog
s-1.0.html
[4] http://xmlsoft.org/guidelines.html#Catalog
[5]
http://people.debian.org/~mrj/oasis/XML-Catalogs/Implementation-Guide.html
kind regards
--
\|/
<@ @> Peter Ring
+-oOO-(_)-OOo---------------------------
| Address Ceresvej 16, st.
| DK-1863 Frederiksberg C
| Phone +45 3331 4216
| EMail pri@ddf.dk
-----Original Message-----
From: cygwin-apps-owner@cygwin.com
[mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Peter Ring
Sent: 21. maj 2003 09:16
To: Andreas; cygwin-apps@cygwin.com
Subject: RE: docbook-xml42, docbook-xsl, xmlto (RE: Pending package
status (09 May 2003))
Executive summary: doing the Right Thing wrt. XML resources
implies a growing number of packages. A scheme for bundling
XML resources in 'virtual' packages could be useful.
A scheme for maintenance of XML catalogs is crucial.
<snip />