re: [ciq] An important question between Schema and DTD

[David RR Webber - XMLGlobal <Gnosis_@compuserve.com>]

Message text written by Ram Kumar
>
Do you have any views on how much of the work of RELAX is expected to be
adopted by V2.0 of XML? Do you know when they expect to release V2.0 and
what is coming in V2.0?

>>>>>>>>>  Ram -  you did not hear this from me ; -)   However you look at
the current new TAG team make-up and see the way that wind wants 
to blow.   The W3C cannot eat crow and adopt RELAX - but its like a
new racing car design - the official line is NO - its illegal - but the 
following season all the new team cars look just like that illegal one....
I ask a simple question - two years from now - do you think the 
W3C will be coming out with a Schema that is :

a) almost identical to current specs'

b) includes significant rationalization and changes / clean-up / 
     consolidation.

c) is as different as DTD and Schema are today.

So my thrust is on designing systems that make minimal use of
extended features - just plain-old-XML instead.


<<<<

> To me this all has AVOID written all over it.   I'm strongly of the
opinion
> that namespace is a vaccination for a disease that few people have 
> been found to actually contracted - and where the vaccine is far worse
> than the disease itself.

Whatever I read about namespaces, it says that the W3C were in a rush to 
introduce namespaces without clearly having a business view/impact in mind 
and completely forgot about DTD and its usage of namespaces. The real issue

is how to handle two or more XML documents that share common names. For 
example, I am working on a client project that takes multiple XML documents

from many sources outside the organisation and is trying to use them. Name 
conflicts is
a big issue here. They want to keep it simple, but it appears to be not
that 
easy. 
<
<<<<<<<<<<<<

My approach is to use a parent group tag and let the XPath do the business

<SomeContent>
    <identicaltagname/>
</SomeContent>
<SomeMoreContent>
   <identicaltagname/>
</SomeMoreContent>

DW.