Re: XML in PHP5

From: Date: Sat, 01 Feb 2003 19:35:56 +0000
Subject: Re: XML in PHP5
References: 1  Groups: php.xml.dev 
Request: Send a blank email to php-xml-dev+get-21@lists.php.net to get a copy of this message
On 1 Feb 2003, Sterling Hughes wrote: SH>>> On Sat, 2003-02-01 at 11:33, Melvyn Sopacua wrote: SH>>> > At 14:21 1-2-2003, Marcus Börger wrote: SH>>> > SH>>> > >If we get a stable XML * core * component maybe we get more XML technologies SH>>> > >by extensions. And all XML related extensions will improve by this since SH>>> > >they SH>>> > >could better/easier work together/interact with each other. SH>>> > SH>>> > Right - especially if you have a datatype which can represent 'an XML SH>>> > document'. SH>>> > Thinking about this, you probably also need DOM methods, so that an SH>>> > extension can SH>>> > choose between XPath and DOM to get to the information they need when they SH>>> > need it. SH>>> > SH>>> > >The opposite of that is that some extensions need complete rewriting - but SH>>> > >they SH>>> > >would become easier in a maintanence view. SH>>> > SH>>> > In fact: it would be able to maintain compatibility for the end user. SH>>> > SH>>> SH>>> Can you expand on this, I'm afraid I don't understand you :-) If you have a core, that introduces a native XML datatype/structure, similar to streams, existing php extensions can keep compatibility, by chanching it's inner workings only. For instance - Sablotron can accept a struct with callbacks as it's input document, through it's SXP interface. As far as your previous mail - I don't see how you can seperate the two: 1 unified XML extension and a core that introduces XML functionality natively. It seems to me, that you have to agree on the core bit first and work on both the core and extension together, to see what is required from the core. -- With kind regards, Melvyn Sopacua <?php include("not_reflecting_employers_views.txt"); ?>

« previous php.xml.dev (#21) next »