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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Common XML (was Re: Internal entities)

[ Lists Home | Date Index | Thread Index ]

I agree with Eric here.

No matter how strict and simple "Common XML" standard is
people will always find ways to express same things differently.

But if I know how to translate Simon's knowledge into mine
and Eric's  knowledge into mine, I can set up processes
to accept both and enjoy.

However, if there is another person "X" who
uses tomorrow different syntax to express same meaning
or same syntax to express different meaning, etc...
(i.e. not being conservative)
than the best think I can do is to ignore his/her information at all.

This is actually a topic map authoring in a nut shell. :-))
Indeed, you can use RM4TM to "udermap"
(is it a good neologism ?) any markup.


Nikita Ogievetsky, nogievet@cogx.com;
Cogitech Inc.        http://www.cogx.com
Topic Maps Tutorials and Consultanting.
phone:  1 (917) 406 - 8734

----- Original Message -----
From: "Eric van der Vlist" <vdv@dyomedea.com>
To: <xml-dev@lists.xml.org>
Sent: Thursday, December 19, 2002 6:13 AM
Subject: Re: [xml-dev] Common XML (was Re: Internal entities)

> On Thu, 2002-12-19 at 15:03, Simon St.Laurent wrote:
> > The "troubles" are already built into the XML 1.0 specification, To some
> > extent, I've seen Common XML as a reponse to the conservatism that XML
> > 1.0 _allowed_ for non-validating parsers as regards skipping external
> > DTD subsets and entities.  Much of my motivation in writing Common XML
> > was to show readers how to avoid the landmines produced by tools being
> > conservative in what they accept and perhaps liberal in what they
> > discard.
> Isn't it what I have said ;-) ???
> The only way to cope with tool which are conservative in what they
> accept and perhaps liberal in what they discard is to be conservative in
> what you send!
> In any case, if the industry was going in that direction, we would need
> new types of schema languages: the current ones do filter the structure
> and content of XML documents without filtering any of the basic XML
> features. If XML "sub-profiles" (such as defined by SOAP) were to be
> widely used, we would also need schema languages to express the
> constraints defined by these profiles!
> Eric
> --
> Freelance consulting and training.
>                                             http://dyomedea.com/english/
> ------------------------------------------------------------------------
> Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
> (W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
> ------------------------------------------------------------------------


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

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