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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: EMBED and validation

[ Lists Home | Date Index | Thread Index ]
  • From: Gavin McKenzie <gmckenzi@JetForm.com>
  • To: "'xml-dev@ic.ac.uk'" <xml-dev@ic.ac.uk>
  • Date: Tue, 2 Dec 1997 19:56:58 -0500

Just some comments on this issue of 'inclusion'.  I apologize if this
sounds like a ramble...

I understand the purpose and usefullness of declaring an entity in the
internal DTD subset and employing this mechanism as the proper and valid
way to include some (potentially marked up) text.  But, echoing Rob
McDougall's closing statements, for *many* applications it is simply too
difficult for the application to 'predict' these inclusion points and
place a corresponding declaration in the internal DTD subset.  In fact,
I would venture to say that most of my customers would walk away from
XML based on this issue alone.

Heavens, so many data processing shops still want to continue writing
data out in fixed length COBOL style records; and while it may be the
nineties, they are resistant to change.  As much as it may seem to be a
stretch to bring these type of data producers into the XML world, I
(naively) think it is possible.

So, after reading all the previous submissions (especially Peter's
display of the overhead for setting up a GIF reference via the external
entity method) I too wish to use an XLL based mechanism for expressing
an 'inclusion' linkage, and pine for some agreement on the semantics.

Although one thing remains unclear, despite the dozens of submissions
I've read:  Is it, or is it not acceptable for an application to choose
to act upon an XLL linkage in a way that causes the target linked
content to be included and validated.  Another way, if I create an XML
derived format, and document that a processor of this derived format
should view a particular usage of an XLL construct as instructions to
"retrieved and include 'inline' the target content, and validate it
against the originating document's DTD as if the target content was part
of the original document".

I'd much prefer that there was a way to express this in the syntax.


Gavin F. McKenzie           Vox:+1(613)230-3676 ext 5277
JetForm Corporation         Fax:+1(613)594-8886
http://www.jetform.com   mailto:gmckenzi@jetform.com

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