XHTML & Schemas
oren at capella.co.il
Thu Sep 2 15:22:42 BST 1999
James Tauber <jtauber at jtauber.com> wrote:
> I wrote:
> > That's well and good, but we can't wait until the XSchema recommendation
> > finalized. XHTML is due to be finalized much earlier, and as we've seen
> > depends on what the decision in XSchema will be. I don't know how the
> > process handles such a conflict. What will happen if XHTML makes a
> > and the XSchema draft then changes so it no longer makes sense?
> Which is one reason why I think XHTML should perhaps go with zero
> for now and the W3C should address the broader issue ASAP. Although, it
> could be said that the W3C *has* addressed the issue and he has already
> his mind up :-)
Actually, that's a real worry. After all, how would we know about such a
decision except for its expression in the various drafts? So far, the facts
I'm aware of are consistent with the W3C deciding to go in the "namespace ==
schema" way, and are inconsistent with any other interpretation.
It isn't as if we really expect someone at the W3C to send a message to this
group saying "look, guys, stop arguing about this - we've made up our minds,
and it will be <this> way.", right?
The problem is that if they have made this decision, any request to change a
specific draft would be ignored - since it would make it inconsistent with
the system as a whole; and there's no easy way you could appeal the basic
decision itself, since it isn't part of any draft.
Could someone more knowledgeable of the W3C process shed some light on this?
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev