[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help
- From: Jiri Jirat <Jiri.Jirat@idoox.com>
- To: Purvesh <purvesh@whizlabs.com>
- Date: Thu, 06 Sep 2001 16:18:12 +0200
Hello,
try:
http://zvon.org/php/Search/w3c.php?query=XML
http://zvon.org/php/Search/w3c.php?query=XSL
etc.
This will give you relevant links to different
specifications.
Regards
Jirka
Purvesh wrote:
>
> Can somebody give me exact links for specifications of the following:
>
> XML
> XSL
> CSS
> DTD
> Schema
> SAX
> DOM
>
> Thanks in advance..
> Purvesh
> ----- Original Message -----
> From: <Tony.Coates@reuters.com>
> To: <xml-dev@lists.xml.org>
> Sent: Thursday, September 06, 2001 3:39 AM
> Subject: RE: XML Schemas: Best Practices ? Versioning
>
> >
> > On 05/09/2001 19:56:47 Michael Brennan wrote:
> >
> > >I don't think 3 and 4 are reliable. #3 makes the incorrect assumption
> that
> > >"instance documents give the name and location of the associated schema".
> This
> > >is undoubtedly the prevalent case, but as sound entity resolution
> mechanisms
> > >gain more widespread use, I'm inclined to believe there will be less and
> less
> > >of this. You cannot assume a consuming application is relying upon the
> > >"schemaLocation" attribute (or even paying any attention to it). I think
> > >changing the target namespace is the only reliable approach.
> >
> > Once again, too much emphasis on the belief that everything should work
> even if there is no "schemaLocation" given. I really believe that taking
> this view, which does not seem to be the view of the W3C people I've talked
> to, will just lead to more complication than is necessary.
> >
> > >In spite of the complications it poses, I think #2 is the best practice.
> > >True, instance documents and schemas that include the relevant schema
> must
> > >change to reference the new version, but that is often a good thing. You
> don't
> > >want those references to indiscriminately change to reference a new
> schema
> > >without assurance that there are no incompatibility issues. Indeed, by
> > >changing the namespace, you can permit concurrent use of different
> versions of
> > >a schema, allowing users time to migrate to the new version as
> compatibility
> > >is assured.
> >
> > The same is true if you insist on a versioned "schemaLocation".
> >
> > Cheers,
> > Tony.
> > ========
> > Anthony B. Coates
> > (1) Content Distribution Architect - Project Gazelle
> > (2) Leader of XML Architecture & Design - Chief Technology Office
> > Reuters Plc, London.
> > Tony.Coates@reuters.com
> > ========
> >
> >
> >
> > -----------------------------------------------------------------
> > Visit our Internet site at http://www.reuters.com
> >
> > Any views expressed in this message are those of the individual
> > sender, except where the sender specifically states them to be
> > the views of Reuters Ltd.
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > initiative of OASIS <http://www.oasis-open.org>
> >
> > The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.xml.org/ob/adm.pl>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
--
<name firstName="Jirka" surname="Jirat"/>
<mail> jiratj@idoox.com </mail>
<support> http://www.zvon.org </support>
<zvonMailingList> http://www.zvon.org/index.php?nav_id=4
</zvonMailingList>