Saxon XSLT and XQuery Processor

Unfortunately the W3C have the irritating habit of changing the namespace
each time a new draft spec comes out. It's now 2005/02
 
Mike


  _____  

From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Cary Millsap
Sent: 11 February 2005 23:34
To: saxon-help@...
Subject: [saxon] 8.3 and xdt namespace



I just upgraded from 8.2 to 8.3 (still using JDK1.5), but my previously
working project now fails with "XP0003: .There is no imported schema for
namespace http://www.w3.org/2004/10/xpath-datatypes" followed by a sequence
of complaints about functions not found in
{http://www.w3.org/2004/10/xpath-functions}.

 

??

 

Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Nullius in verba

Upcoming events:
- Performance  <http://www.hotsos.com/courses/PD101.php> Diagnosis 101: 2/23
Houston, 3/16 Salt Lake City
- SQL Optimization <http://www.hotsos.com/courses/OP101.php>  101: 2/7
Dallas
- Hotsos  <http://www.hotsos.com/events/SYM05.php?event_id=36> Symposium
2005: March 6-10 Dallas
- Visit http://www.hotsos.com for schedule details...

Fortunately, I had to update only two FXSL modules -- can't imagine
hoe long it would take to make the change in 100 files...

What is the best way of protection against such changes -- something
like referencing an external entity?


Cheers,

Dimitre Novatchev


On Fri, 11 Feb 2005 23:57:35 -0000, Michael Kay <mike@...> wrote:
> Unfortunately the W3C have the irritating habit of changing the namespace
> each time a new draft spec comes out. It's now 2005/02
> =20
> Mike
> ________________________________
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of Cary Millsap
> Sent: 11 February 2005 23:34
> To: saxon-help@...
> Subject: [saxon] 8.3 and xdt namespace
>=20
>=20
>=20
> I just upgraded from 8.2 to 8.3 (still using JDK1.5), but my previously
> working project now fails with "XP0003: =E2=80=A6There is no imported sch=
ema for
> namespace http://www.w3.org/2004/10/xpath-datatypes" followed by a sequen=
ce
> of complaints about functions not found in
> {http://www.w3.org/2004/10/xpath-functions}.
>=20
> =20
>=20
> ??
>=20
> =20
>=20
> Cary Millsap
> Hotsos Enterprises, Ltd.
> http://www.hotsos.com
> Nullius in verba
>=20
> Upcoming events:
> - Performance Diagnosis 101: 2/23 Houston, 3/16 Salt Lake City
> - SQL Optimization 101: 2/7 Dallas
> - Hotsos Symposium 2005: March 6=E2=80=9310 Dallas
> - Visit http://www.hotsos.com for schedule details...
>=20
>

So, was it my 8.3 upgrade that surfaced the problem? Or did it actually
happen that today's the day w3c invalidated the 2004/10 namespace name?

I'm interested, too, in how to prevent external factors over which I =
have no
control from spontaneously creating problems in applications I've =
shipped.


Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
* Nullius in verba *

Upcoming events:
- Performance Diagnosis 101: 2/23 Houston, 3/16 Salt Lake City
- SQL Optimization 101: 2/7 Dallas
- Hotsos Symposium 2005: March 6-10 Dallas
- Visit http://www.hotsos.com for schedule details...


-----Original Message-----
From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Dimitre
Novatchev
Sent: Friday, February 11, 2005 6:09 PM
To: saxon-help@...
Subject: Re: [saxon] 8.3 and xdt namespace

Fortunately, I had to update only two FXSL modules -- can't imagine
hoe long it would take to make the change in 100 files...

What is the best way of protection against such changes -- something
like referencing an external entity?


Cheers,

Dimitre Novatchev


On Fri, 11 Feb 2005 23:57:35 -0000, Michael Kay <mike@...> =
wrote:
> Unfortunately the W3C have the irritating habit of changing the =
namespace
> each time a new draft spec comes out. It's now 2005/02
> =20
> Mike
> ________________________________
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of Cary =
Millsap
> Sent: 11 February 2005 23:34
> To: saxon-help@...
> Subject: [saxon] 8.3 and xdt namespace
>=20
>=20
>=20
> I just upgraded from 8.2 to 8.3 (still using JDK1.5), but my =
previously
> working project now fails with "XP0003: .There is no imported schema =
for
> namespace http://www.w3.org/2004/10/xpath-datatypes" followed by a
sequence
> of complaints about functions not found in
> {http://www.w3.org/2004/10/xpath-functions}.
>=20
> =20
>=20
> ??
>=20
> =20
>=20
> Cary Millsap
> Hotsos Enterprises, Ltd.
> http://www.hotsos.com
> Nullius in verba
>=20
> Upcoming events:
> - Performance Diagnosis 101: 2/23 Houston, 3/16 Salt Lake City
> - SQL Optimization 101: 2/7 Dallas
> - Hotsos Symposium 2005: March 6-10 Dallas
> - Visit http://www.hotsos.com for schedule details...
>=20
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id=14396&opk
_______________________________________________
saxon-help mailing list
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

I simply use a global edit across all the files in a directory every =
time it
changes.

Michael Kay=20

> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of=20
> Dimitre Novatchev
> Sent: 12 February 2005 00:09
> To: saxon-help@...
> Subject: Re: [saxon] 8.3 and xdt namespace
>=20
> Fortunately, I had to update only two FXSL modules -- can't imagine
> hoe long it would take to make the change in 100 files...
>=20
> What is the best way of protection against such changes -- something
> like referencing an external entity?
>=20
>=20
> Cheers,
>=20
> Dimitre Novatchev
>=20
>=20
> On Fri, 11 Feb 2005 23:57:35 -0000, Michael Kay=20
> <mike@...> wrote:
> > Unfortunately the W3C have the irritating habit of changing=20
> the namespace
> > each time a new draft spec comes out. It's now 2005/02
> > =20
> > Mike
> > ________________________________
> > From: saxon-help-admin@...
> > [mailto:saxon-help-admin@...] On Behalf=20
> Of Cary Millsap
> > Sent: 11 February 2005 23:34
> > To: saxon-help@...
> > Subject: [saxon] 8.3 and xdt namespace
> >=20
> >=20
> >=20
> > I just upgraded from 8.2 to 8.3 (still using JDK1.5), but=20
> my previously
> > working project now fails with "XP0003: .There is no=20
> imported schema for
> > namespace http://www.w3.org/2004/10/xpath-datatypes"=20
> followed by a sequence
> > of complaints about functions not found in
> > {http://www.w3.org/2004/10/xpath-functions}.
> >=20
> > =20
> >=20
> > ??
> >=20
> > =20
> >=20
> > Cary Millsap
> > Hotsos Enterprises, Ltd.
> > http://www.hotsos.com
> > Nullius in verba
> >=20
> > Upcoming events:
> > - Performance Diagnosis 101: 2/23 Houston, 3/16 Salt Lake City
> > - SQL Optimization 101: 2/7 Dallas
> > - Hotsos Symposium 2005: March 6-10 Dallas
> > - Visit http://www.hotsos.com for schedule details...
> >=20
> >
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick
> _______________________________________________
> saxon-help mailing list
> saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>=20

> So, was it my 8.3 upgrade that surfaced the problem? Or did 
> it actually
> happen that today's the day w3c invalidated the 2004/10 
> namespace name?

I deliberately scheduled the Saxon 8.3 release for the same day as the
publication of the new working drafts, and the new namespace is built into
8.3.
> 
> I'm interested, too, in how to prevent external factors over 
> which I have no
> control from spontaneously creating problems in applications 
> I've shipped.
> 

I think this W3C policy is probably designed to remind people that they are
using draft specifications that are subject to change, and that an
application written against one version of the spec won't necessarily work
against the next version.

Of course if your shipped application includes the version of Saxon that it
was tested with, this isn't a problem: the problem only arises when you try
to migrate to a new version.

Michael Kay
http://www.saxonica.com/