OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Stylesheets considered limiting (was Re: XLink - where are we?)

[ Lists Home | Date Index | Thread Index ]
  • From: "W. Eliot Kimber" <eliot@dns.isogen.com>
  • To: xml-dev@ic.ac.uk
  • Date: Thu, 12 Nov 1998 07:55:04 -0600

At 08:53 AM 11/12/98, Peter Murray-Rust wrote:
>Does this imply that it's not XML-compatible at present? Because I suspect
>people will get increasingly frustrated with SGML-over-the-wire (e.g.
>Hybrick at present) because they don't know how to manage declarations and

It's perfectly XML compatible, but the draft as printed provides
architectural DTD declarations that assume the use of typical SGML features
(i.e., markup minimization) and does not provide an alternative set of
declarations that restricts itself to those SGML features used by XML.
Obviously anyone could create those declarations (as I did for HyTime in
developing my PHyLIS tool), but there's no reason for the editors not to
provide it directly given that it's an obvious requirement (and in fact, it
should have always been the policy that two forms of architectural
declarations be provided, one for SGML declarations that allow markup
minimization and one for SGML declarations that do not, which is the key
difference {whether or not start and end tag parameters are prohibited}). 

The concepts defined in the standard are independent of syntax.  If you're
simply implementing the semantics but not using true architectural
processing, then you don't care about the details of the declaration syntax
of the architectural meta-DTDs, using them simply as documentation and not
as processible data sets.

Remember that when defining any sort of SGML application (that is, an
application of SGML, not software that processes SGML), the *ONLY* thing
that would make it not usable with XML documents would be the requirement
that docments use an SGML feature that XML does not provide. As data
entities is the only feature of SGML not provided by XML that also has
significant *semantic* utility (as opposed to being a syntactic convenience
like markup minimization or the LINK feature), you'd have to go out of your
way to make your application not XML compatible.  And in any case, you can
get by without data attributes, although it's clumsy and suboptimal.



<Address HyTime=bibloc>
W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 75202.  214.953.0004

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS