RE: [xsl] AltovaXML and fragment identifier

["Michael Kay" <mike@xxxxxxxxxxxx>]

One other point here is that Saxon is stretching the rules by interpreting a
fragment identifier in cases where it doesn't actually know the media type.
Arguably, if the document is in filestore then you don't know the media type
and therefore the fragment identifier is meaningless.

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

> -----Original Message-----
> From: David Carlisle [mailto:davidc@xxxxxxxxx] 
> Sent: 17 March 2009 16:24
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] AltovaXML and fragment identifier
> 
> 
> 
> > Isn't that error XTDE1170 only supposed to be thrown if a fragment 
> > identifier is used in a URI passed to the unparsed-text function?
> 
> yes I think that is correct, this is the wrong code, however 
> a system is allowed to reject any URI at all and if it 
> chooses to reject all uri with fragids passed to doc() or 
> document() it can do that, but it should raise [err:FODC0005]. 
> 
> 
> f&o spec says:
> 
> ...If the Available documents provides no mapping for the 
> string, an error is raised [err:FODC0005]. 
> 
> 
> David
> 
> 
> ______________________________________________________________
> __________
> The Numerical Algorithms Group Ltd is a company registered in 
> England and Wales with company number 1249803. The registered 
> office is:
> Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
> 
> This e-mail has been scanned for all viruses by Star. The 
> service is powered by MessageLabs. 
> ______________________________________________________________
> __________