Re: Re: [xml] mobile links for XInclude?

["Ben Decker" <bdeck lycos co uk>]

> FromDaniel Veillard <veillard redhat com>
> DateSat, 21 Jun 2003 19:34:17 -0400
> You make the data completely dependant on an environment variable.
> Which mean it will break for anybody not having this "magic" setup,


Not exactly. I was asking if it was possible at all *in general* to use *any* local system variable for local 
system 
XInclude resolution as an *option*. It could also be called $BENS_BIG_IDEA_ON_THIS_COMPUTER or whatever I 
feel is needed to create an infrastructure that meets the needs of the system I am deploying, you see. To be 
honest, I don't see how allowing the use of system variables *in general* would break XInclude. If the XML 
document happened to be resolved on another system that doesn't define that particular system variable used 
in the XInclude expression of that particular XML document, the resolution could default to NULL. That is:

xi:include href="$XML_WHATEVER/program/python.xml#xpointer(//python/libs)"
would simply default to "/program/python.xml" on a system that did not have $XML_WHATEVER defined.

It just made sense to me that something *like* that might somehow be possible. getenv() is part of the posix 
standard... it's even supported on simple systems like DOS :-) Apple MAC? Hmmmm... I don't know. But you are 
the boss, I understand that. 
It was all just a question I had...


> and XInclude being a W3C specification impacting generic XML processing
> this is totally unacceptable. So either you ask me to develop a
> non-standard extension which feels broken to me or you ask to extend
> the spec in a similary unacceptable way. In both case I'm strongly
> disagreeing with your suggestion. I think this is very broken as a 
> framework and I react accordingly, that's all.


No, wasn't asking for a change in W3C standards. I was just asking how *flexible* they were :-)


many regards,
Ben

This is your brain:
    bash-2.05$
This is your brain on drugs:
    Starting Windows XP...
Any questions?

250 business cards FREE! Create your own full-colour high-quality business cards easily online. Only at 
www.vistaprint.uk

--- Begin Message ---

• From: Daniel Veillard <veillard redhat com>
• To: Ben Decker <bdeck lycos co uk>
• Cc: libxml mailing list <xml gnome org>
• Subject: Re: [xml] mobile links for XInclude?
• Date: Sat, 21 Jun 2003 19:34:17 -0400

On Sat, Jun 21, 2003 at 07:08:59PM +0100, Ben Decker wrote:

would like to move the whole filetree to a different location. Would something like this ever be 
possible:
<xi:include href="$XMLDATA/program/python.xml#xpointer(//python/libs)" parse="xml"

 No. The href attribute content is an URI Reference as defined in RFC 2396.
So far this has been sufficient to build the Web, that should be sufficient
for XInclude. Use relative URI reference or HTTP redirects.
 If you really want to make something not portable and are ready to
design something that broken, then you can define your own entity handler
at the libxml2 level

Why so negetive? I have a problem and need a solution. What I have
learned so far doesn't offer one. I didn't see 
reason for such a reaction like this... Was this really warranted?

 You make the data completely dependant on an environment variable.
Which mean it will break for anybody not having this "magic" setup,
and XInclude being a W3C specification impacting generic XML processing
this is totally unacceptable. So either you ask me to develop a
non-standard extension which feels broken to me or you ask to extend
the spec in a similary unacceptable way. In both case I'm strongly
disagreeing with your suggestion. I think this is very broken as a 
framework and I react accordingly, that's all.

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

--- End Message ---