You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Donald Ball <ba...@webslingerZ.com> on 2001/04/30 23:45:37 UTC
[c2] problems with xincludesaxconnector
my issues:
1. why should this be a saxconnector instead of a filter?
2. the schema upon which it operates doesn't conform to the official
xinclude spec, but it operates on the official xinclude namespace. one or
the other needs to change. specifically, at the least, the src attribute
should be an href attribute and the ns and prefix attributes don't exist.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 1 May 2001, giacomo wrote:
> > my issues:
> >
> > 1. why should this be a saxconnector instead of a filter?
>
> What's a filter? If you mean a Transformer then it's because a
> transformer doesn't gets to a sitemap instance to request internal
> resources (and I have to say I like the way it is now because I don't
> think it make sense to sitemap components to have a instance of a
> sitemap at hand). With the SAXConnectors C2 has transparent XInclude
> capability which I think is totally cool.
i mean transformer, yes. i still don't see why it's necessarily desirable
to do automatic xinclude processing, but i'm happy to use the
NullSAXConnector. it bothers me that we have two pieces of code that do
the same thing though - that's a maintenance hassle if nothing else.
> > 2. the schema upon which it operates doesn't conform to the official
> > xinclude spec, but it operates on the official xinclude namespace. one or
> > the other needs to change. specifically, at the least, the src attribute
> > should be an href attribute and the ns and prefix attributes don't exist.
>
> The ns attribute is a suggestion from Stefano and the prefix comes from
> the recent sitemap aggregate discussion. I think both (ns and prefix)
> are totally necessary because you cannot prevent name collisions without
> it. Stefano also suggest to promote that to the w3c (but I think nobody
> took it there)
i don't think either of these attributes is necessary, honestly, if you
want a default namespace for the included document and you don't think it
has one already, you can set one for the xinclude element itself:
<xinclude:include href="foo" xmlns="http://example.com/xml/foo/1.0"/>
using the standard namespace attribute semantics. in any case, i'm adamant
that if we don't conform to the xinclude semantics, then we must operate
on another namespace.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by giacomo <gi...@apache.org>.
On Mon, 30 Apr 2001, Donald Ball wrote:
> my issues:
>
> 1. why should this be a saxconnector instead of a filter?
What's a filter? If you mean a Transformer then it's because a
transformer doesn't gets to a sitemap instance to request internal
resources (and I have to say I like the way it is now because I don't
think it make sense to sitemap components to have a instance of a
sitemap at hand). With the SAXConnectors C2 has transparent XInclude
capability which I think is totally cool.
> 2. the schema upon which it operates doesn't conform to the official
> xinclude spec, but it operates on the official xinclude namespace. one or
> the other needs to change. specifically, at the least, the src attribute
> should be an href attribute and the ns and prefix attributes don't exist.
The ns attribute is a suggestion from Stefano and the prefix comes from
the recent sitemap aggregate discussion. I think both (ns and prefix)
are totally necessary because you cannot prevent name collisions without
it. Stefano also suggest to promote that to the w3c (but I think nobody
took it there)
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 1 May 2001, Stuart Roebuck wrote:
> There are also problems with the almost arbitrary attributing of
> namespaces to elements processed with the new xincludesaxconnector. Look
> at the resulting source output of the aggregation example in CVS and
> you'll see what I mean.
yeah, the xincludesaxconnector doesn't process namespaces in the way that
the xinclude spec says it should. we need to decide whether to try to
implement xinclude or develop our own inclusion language.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by giacomo <gi...@apache.org>.
On Fri, 4 May 2001, Stuart Roebuck wrote:
> Giacomo,
>
> Thanks for your help, it looks like Sylvain has spotted the problem.
Yeah!
> Apologies if my explanation wasn't very clear!
No problem. If I don't understand it I simply ask :)
Thanks
Giacomo
>
> Stuart.
>
>
> On Thursday, May 3, 2001, at 08:23 pm, giacomo wrote:
> > On Thu, 3 May 2001, Stuart Roebuck wrote:
> >
> >> I'm no namespace expert myself, so I'm not the best person to ask.
> >> However,
> >> for certain, none of the HTML should have alternative namespaces, so I
> >> reckon that the example I gave should at least look like:
> >>
> >>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
> >>> xmlns:ns2="http://foo.bar.
> >>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> >>> <BODY>
> >>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
> >>> xmlns="http://foo.bar.com/slashdot">
> >>> <table width="100%" border="0">
> >>> <tr >
> >>> <td STYLE="background-color : #B0E0E6; font : x-small
> >>> Arial, Helvetica,
> >>> sans-serif;" colspan="5">
> >>> <CENTER >
> >>> <b >Current News from Slashdot</b>
> >>> </CENTER>
> >>> </td>
> >>> </tr>
> >>> <tr STYLE="background-color : lightgrey; font : x-small
> >>> Arial, Helvetica,
> >>> sans-serif;">
> >>> <td>
> >>> <CENTER>
> >>> <IMG BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> >>> ALT="topichumor.gif"/>
> >>
> >> I suspect <page> and <slashdot> shouldn't have them either, and the three
> >> namespaces at the beginning don't need to be there if they are not used
> >> later on.
> >
> > This is a SAX problem. How to know a declared namespace isn't used
> > afterward? And as the definition of the aggregation states that there
> > should be namespaces attached to the page and slashdot elements they
> > should appear there.
> >
> > Sorry, I still don't see what the aggregator is doing wrong.
> >
> > Giacomo
> >
> >>
> >> Stuart.
> >>
> >>
> >> On Wednesday, May 2, 2001, at 07:12 pm, giacomo wrote:
> >>
> >>>
> >>> Hi Stuart
> >>>
> >>> Thanks for your test. I'm in no way a namespace expert, so, could you
> >>> give me some suggestion on what we have to change to make it right?
> >>>
> >>> TIA
> >>>
> >>> Giacomo
> >>>
> >>> On Tue, 1 May 2001, Stuart Roebuck wrote:
> >>>
> >>>> Giacomo,
> >>>>
> >>>> Sorry for being a bit brief. Here's the first 15 lines of the HTML
> >>>> output
> >>>> from Cocoon (CVS about 12 hours ago), looking at the
> >>>> "news/aggregate.xml"
> >>>> match. The current defaults use the xincludesaxconnector:
> >>>>
> >>>>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
> >>>>> xmlns:ns2="http://foo.bar.
> >>>>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> >>>>> <BODY>
> >>>>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
> >>>>> xmlns="http://foo.bar.com/slashdot">
> >>>>> <table xmlns="http://foo.bar.com/slashdot" width="100%"
> >>>>> border="0">
> >>>>> <tr xmlns="http://foo.bar.com/slashdot">
> >>>>> <td xmlns="http://foo.bar.com/slashdot"
> >>>>> STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
> >>>>> sans-serif;" colspan="5">
> >>>>> <CENTER xmlns="http://foo.bar.com/slashdot">
> >>>>> <b xmlns="http://foo.bar.com/slashdot">Current
> >>>>> News from Slashdot</b>
> >>>>> </CENTER>
> >>>>> </td>
> >>>>> </tr>
> >>>>> <tr xmlns="http://foo.bar.com/slashdot"
> >>>>> STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
> >>>>> sans-serif;">
> >>>>> <td xmlns="http://foo.bar.com/slashdot">
> >>>>> <CENTER xmlns="http://foo.bar.com/slashdot">
> >>>>> <IMG xmlns="http://foo.bar.com/slashdot"
> >>>>> BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> >>>>> ALT="topichumor.gif"/>
> >>>>
> >>>> As you can see, the 'myspace' and 'slashdot' namespaces have been
> >>>> attributed to HTML tags for no apparent reason. If you revert to the
> >>>> old
> >>>> saxconnector, these go away. In most browsers this doesn't seem to
> >>>> make
> >>>> much difference, but it confused OmniWeb enough to alert me to
> >>>> something
> >>>> being wrong.
> >>>>
> >>>> Another issue that is longstanding is that Cocoon outputs HTML with
> >>>> namespace declarations at the beginning for namespaces used during the
> >>>> processing even when they are no-longer required in the final output.
> >>>> Whist it doesn't cause any problems, it is potentially confusing for
> >>>> anyone trying to make sense of the source-code. Perhaps this is a
> >>>> feature!
> >>>> :-)
> >>>>
> >>>> Stuart.
> >>>>
> >>>>
> >>>> On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
> >>>>
> >>>>>
> >>>>>
> >>>>> On Tue, 1 May 2001, Stuart Roebuck wrote:
> >>>>>
> >>>>>> There are also problems with the almost arbitrary attributing of
> >>>>>> namespaces to elements processed with the new xincludesaxconnector.
> >>>>>> Look
> >>>>>> at the resulting source output of the aggregation example in CVS and
> >>>>>> you'll see what I mean.
> >>>>>
> >>>>> Stuart, could you please explain to me what you've found is the
> >>>>> problem
> >>>>> in more detail so that one can use it to correct the behaviour?
> >>>>>
> >>>>> TIA
> >>>>>
> >>>>> Giacomo
> >>>>>
> >>>>>>
> >>>>>> Stuart.
> >>>>>>
> >>>>>> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
> >>>>>>
> >>>>>>> my issues:
> >>>>>>>
> >>>>>>> 1. why should this be a saxconnector instead of a filter?
> >>>>>>>
> >>>>>>> 2. the schema upon which it operates doesn't conform to the
> >>>>>>> official
> >>>>>>> xinclude spec, but it operates on the official xinclude namespace.
> >>>>>>> one
> >>>>>>> or
> >>>>>>> the other needs to change. specifically, at the least, the src
> >>>>>>> attribute
> >>>>>>> should be an href attribute and the ns and prefix attributes don't
> >>>>>>> exist.
> >>>>>>>
> >>>>>>> - donald
> >>>>>>>
>
>
> -------------------------------------------------------------------------
> Stuart Roebuck stuart.roebuck@adolos.com
> Lead Developer Java, XML, MacOS X, XP, etc.
> ADOLOS <http://www.adolos.com/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Stuart Roebuck <st...@adolos.co.uk>.
Giacomo,
Thanks for your help, it looks like Sylvain has spotted the problem.
Apologies if my explanation wasn't very clear!
Stuart.
On Thursday, May 3, 2001, at 08:23 pm, giacomo wrote:
> On Thu, 3 May 2001, Stuart Roebuck wrote:
>
>> I'm no namespace expert myself, so I'm not the best person to ask.
>> However,
>> for certain, none of the HTML should have alternative namespaces, so I
>> reckon that the example I gave should at least look like:
>>
>>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
>>> xmlns:ns2="http://foo.bar.
>>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
>>> <BODY>
>>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
>>> xmlns="http://foo.bar.com/slashdot">
>>> <table width="100%" border="0">
>>> <tr >
>>> <td STYLE="background-color : #B0E0E6; font : x-small
>>> Arial, Helvetica,
>>> sans-serif;" colspan="5">
>>> <CENTER >
>>> <b >Current News from Slashdot</b>
>>> </CENTER>
>>> </td>
>>> </tr>
>>> <tr STYLE="background-color : lightgrey; font : x-small
>>> Arial, Helvetica,
>>> sans-serif;">
>>> <td>
>>> <CENTER>
>>> <IMG BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
>>> ALT="topichumor.gif"/>
>>
>> I suspect <page> and <slashdot> shouldn't have them either, and the three
>> namespaces at the beginning don't need to be there if they are not used
>> later on.
>
> This is a SAX problem. How to know a declared namespace isn't used
> afterward? And as the definition of the aggregation states that there
> should be namespaces attached to the page and slashdot elements they
> should appear there.
>
> Sorry, I still don't see what the aggregator is doing wrong.
>
> Giacomo
>
>>
>> Stuart.
>>
>>
>> On Wednesday, May 2, 2001, at 07:12 pm, giacomo wrote:
>>
>>>
>>> Hi Stuart
>>>
>>> Thanks for your test. I'm in no way a namespace expert, so, could you
>>> give me some suggestion on what we have to change to make it right?
>>>
>>> TIA
>>>
>>> Giacomo
>>>
>>> On Tue, 1 May 2001, Stuart Roebuck wrote:
>>>
>>>> Giacomo,
>>>>
>>>> Sorry for being a bit brief. Here's the first 15 lines of the HTML
>>>> output
>>>> from Cocoon (CVS about 12 hours ago), looking at the
>>>> "news/aggregate.xml"
>>>> match. The current defaults use the xincludesaxconnector:
>>>>
>>>>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
>>>>> xmlns:ns2="http://foo.bar.
>>>>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
>>>>> <BODY>
>>>>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
>>>>> xmlns="http://foo.bar.com/slashdot">
>>>>> <table xmlns="http://foo.bar.com/slashdot" width="100%"
>>>>> border="0">
>>>>> <tr xmlns="http://foo.bar.com/slashdot">
>>>>> <td xmlns="http://foo.bar.com/slashdot"
>>>>> STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
>>>>> sans-serif;" colspan="5">
>>>>> <CENTER xmlns="http://foo.bar.com/slashdot">
>>>>> <b xmlns="http://foo.bar.com/slashdot">Current
>>>>> News from Slashdot</b>
>>>>> </CENTER>
>>>>> </td>
>>>>> </tr>
>>>>> <tr xmlns="http://foo.bar.com/slashdot"
>>>>> STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
>>>>> sans-serif;">
>>>>> <td xmlns="http://foo.bar.com/slashdot">
>>>>> <CENTER xmlns="http://foo.bar.com/slashdot">
>>>>> <IMG xmlns="http://foo.bar.com/slashdot"
>>>>> BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
>>>>> ALT="topichumor.gif"/>
>>>>
>>>> As you can see, the 'myspace' and 'slashdot' namespaces have been
>>>> attributed to HTML tags for no apparent reason. If you revert to the
>>>> old
>>>> saxconnector, these go away. In most browsers this doesn't seem to
>>>> make
>>>> much difference, but it confused OmniWeb enough to alert me to
>>>> something
>>>> being wrong.
>>>>
>>>> Another issue that is longstanding is that Cocoon outputs HTML with
>>>> namespace declarations at the beginning for namespaces used during the
>>>> processing even when they are no-longer required in the final output.
>>>> Whist it doesn't cause any problems, it is potentially confusing for
>>>> anyone trying to make sense of the source-code. Perhaps this is a
>>>> feature!
>>>> :-)
>>>>
>>>> Stuart.
>>>>
>>>>
>>>> On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, 1 May 2001, Stuart Roebuck wrote:
>>>>>
>>>>>> There are also problems with the almost arbitrary attributing of
>>>>>> namespaces to elements processed with the new xincludesaxconnector.
>>>>>> Look
>>>>>> at the resulting source output of the aggregation example in CVS and
>>>>>> you'll see what I mean.
>>>>>
>>>>> Stuart, could you please explain to me what you've found is the
>>>>> problem
>>>>> in more detail so that one can use it to correct the behaviour?
>>>>>
>>>>> TIA
>>>>>
>>>>> Giacomo
>>>>>
>>>>>>
>>>>>> Stuart.
>>>>>>
>>>>>> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
>>>>>>
>>>>>>> my issues:
>>>>>>>
>>>>>>> 1. why should this be a saxconnector instead of a filter?
>>>>>>>
>>>>>>> 2. the schema upon which it operates doesn't conform to the
>>>>>>> official
>>>>>>> xinclude spec, but it operates on the official xinclude namespace.
>>>>>>> one
>>>>>>> or
>>>>>>> the other needs to change. specifically, at the least, the src
>>>>>>> attribute
>>>>>>> should be an href attribute and the ns and prefix attributes don't
>>>>>>> exist.
>>>>>>>
>>>>>>> - donald
>>>>>>>
-------------------------------------------------------------------------
Stuart Roebuck stuart.roebuck@adolos.com
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by giacomo <gi...@apache.org>.
On Thu, 3 May 2001, Stuart Roebuck wrote:
> I'm no namespace expert myself, so I'm not the best person to ask. However,
> for certain, none of the HTML should have alternative namespaces, so I
> reckon that the example I gave should at least look like:
>
> > <HTML xmlns:ns3="http://foo.bar.com/isyndicate" xmlns:ns2="http://foo.bar.
> > com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> > <BODY>
> > <page xmlns="http://foo.bar.com/myspace"> <slashdot
> > xmlns="http://foo.bar.com/slashdot">
> > <table width="100%" border="0">
> > <tr >
> > <td STYLE="background-color : #B0E0E6; font : x-small
> > Arial, Helvetica,
> > sans-serif;" colspan="5">
> > <CENTER >
> > <b >Current News from Slashdot</b>
> > </CENTER>
> > </td>
> > </tr>
> > <tr STYLE="background-color : lightgrey; font : x-small
> > Arial, Helvetica,
> > sans-serif;">
> > <td>
> > <CENTER>
> > <IMG BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> > ALT="topichumor.gif"/>
>
> I suspect <page> and <slashdot> shouldn't have them either, and the three
> namespaces at the beginning don't need to be there if they are not used
> later on.
This is a SAX problem. How to know a declared namespace isn't used
afterward? And as the definition of the aggregation states that there
should be namespaces attached to the page and slashdot elements they
should appear there.
Sorry, I still don't see what the aggregator is doing wrong.
Giacomo
>
> Stuart.
>
>
> On Wednesday, May 2, 2001, at 07:12 pm, giacomo wrote:
>
> >
> > Hi Stuart
> >
> > Thanks for your test. I'm in no way a namespace expert, so, could you
> > give me some suggestion on what we have to change to make it right?
> >
> > TIA
> >
> > Giacomo
> >
> > On Tue, 1 May 2001, Stuart Roebuck wrote:
> >
> >> Giacomo,
> >>
> >> Sorry for being a bit brief. Here's the first 15 lines of the HTML
> >> output
> >> from Cocoon (CVS about 12 hours ago), looking at the "news/aggregate.xml"
> >> match. The current defaults use the xincludesaxconnector:
> >>
> >>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
> >>> xmlns:ns2="http://foo.bar.
> >>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> >>> <BODY>
> >>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
> >>> xmlns="http://foo.bar.com/slashdot">
> >>> <table xmlns="http://foo.bar.com/slashdot" width="100%" border="0">
> >>> <tr xmlns="http://foo.bar.com/slashdot">
> >>> <td xmlns="http://foo.bar.com/slashdot"
> >>> STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
> >>> sans-serif;" colspan="5">
> >>> <CENTER xmlns="http://foo.bar.com/slashdot">
> >>> <b xmlns="http://foo.bar.com/slashdot">Current
> >>> News from Slashdot</b>
> >>> </CENTER>
> >>> </td>
> >>> </tr>
> >>> <tr xmlns="http://foo.bar.com/slashdot"
> >>> STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
> >>> sans-serif;">
> >>> <td xmlns="http://foo.bar.com/slashdot">
> >>> <CENTER xmlns="http://foo.bar.com/slashdot">
> >>> <IMG xmlns="http://foo.bar.com/slashdot"
> >>> BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> >>> ALT="topichumor.gif"/>
> >>
> >> As you can see, the 'myspace' and 'slashdot' namespaces have been
> >> attributed to HTML tags for no apparent reason. If you revert to the old
> >> saxconnector, these go away. In most browsers this doesn't seem to make
> >> much difference, but it confused OmniWeb enough to alert me to something
> >> being wrong.
> >>
> >> Another issue that is longstanding is that Cocoon outputs HTML with
> >> namespace declarations at the beginning for namespaces used during the
> >> processing even when they are no-longer required in the final output.
> >> Whist it doesn't cause any problems, it is potentially confusing for
> >> anyone trying to make sense of the source-code. Perhaps this is a
> >> feature!
> >> :-)
> >>
> >> Stuart.
> >>
> >>
> >> On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
> >>
> >>>
> >>>
> >>> On Tue, 1 May 2001, Stuart Roebuck wrote:
> >>>
> >>>> There are also problems with the almost arbitrary attributing of
> >>>> namespaces to elements processed with the new xincludesaxconnector.
> >>>> Look
> >>>> at the resulting source output of the aggregation example in CVS and
> >>>> you'll see what I mean.
> >>>
> >>> Stuart, could you please explain to me what you've found is the problem
> >>> in more detail so that one can use it to correct the behaviour?
> >>>
> >>> TIA
> >>>
> >>> Giacomo
> >>>
> >>>>
> >>>> Stuart.
> >>>>
> >>>> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
> >>>>
> >>>>> my issues:
> >>>>>
> >>>>> 1. why should this be a saxconnector instead of a filter?
> >>>>>
> >>>>> 2. the schema upon which it operates doesn't conform to the official
> >>>>> xinclude spec, but it operates on the official xinclude namespace.
> >>>>> one
> >>>>> or
> >>>>> the other needs to change. specifically, at the least, the src
> >>>>> attribute
> >>>>> should be an href attribute and the ns and prefix attributes don't
> >>>>> exist.
> >>>>>
> >>>>> - donald
> >>>>>
>
> -------------------------------------------------------------------------
> Stuart Roebuck stuart.roebuck@adolos.com
> Lead Developer Java, XML, MacOS X, XP, etc.
> ADOLOS <http://www.adolos.com/>
> >>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Stuart Roebuck <st...@adolos.co.uk>.
I'm no namespace expert myself, so I'm not the best person to ask. However,
for certain, none of the HTML should have alternative namespaces, so I
reckon that the example I gave should at least look like:
> <HTML xmlns:ns3="http://foo.bar.com/isyndicate" xmlns:ns2="http://foo.bar.
> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> <BODY>
> <page xmlns="http://foo.bar.com/myspace"> <slashdot
> xmlns="http://foo.bar.com/slashdot">
> <table width="100%" border="0">
> <tr >
> <td STYLE="background-color : #B0E0E6; font : x-small
> Arial, Helvetica,
> sans-serif;" colspan="5">
> <CENTER >
> <b >Current News from Slashdot</b>
> </CENTER>
> </td>
> </tr>
> <tr STYLE="background-color : lightgrey; font : x-small
> Arial, Helvetica,
> sans-serif;">
> <td>
> <CENTER>
> <IMG BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> ALT="topichumor.gif"/>
I suspect <page> and <slashdot> shouldn't have them either, and the three
namespaces at the beginning don't need to be there if they are not used
later on.
Stuart.
On Wednesday, May 2, 2001, at 07:12 pm, giacomo wrote:
>
> Hi Stuart
>
> Thanks for your test. I'm in no way a namespace expert, so, could you
> give me some suggestion on what we have to change to make it right?
>
> TIA
>
> Giacomo
>
> On Tue, 1 May 2001, Stuart Roebuck wrote:
>
>> Giacomo,
>>
>> Sorry for being a bit brief. Here's the first 15 lines of the HTML
>> output
>> from Cocoon (CVS about 12 hours ago), looking at the "news/aggregate.xml"
>> match. The current defaults use the xincludesaxconnector:
>>
>>> <HTML xmlns:ns3="http://foo.bar.com/isyndicate"
>>> xmlns:ns2="http://foo.bar.
>>> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
>>> <BODY>
>>> <page xmlns="http://foo.bar.com/myspace"> <slashdot
>>> xmlns="http://foo.bar.com/slashdot">
>>> <table xmlns="http://foo.bar.com/slashdot" width="100%" border="0">
>>> <tr xmlns="http://foo.bar.com/slashdot">
>>> <td xmlns="http://foo.bar.com/slashdot"
>>> STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
>>> sans-serif;" colspan="5">
>>> <CENTER xmlns="http://foo.bar.com/slashdot">
>>> <b xmlns="http://foo.bar.com/slashdot">Current
>>> News from Slashdot</b>
>>> </CENTER>
>>> </td>
>>> </tr>
>>> <tr xmlns="http://foo.bar.com/slashdot"
>>> STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
>>> sans-serif;">
>>> <td xmlns="http://foo.bar.com/slashdot">
>>> <CENTER xmlns="http://foo.bar.com/slashdot">
>>> <IMG xmlns="http://foo.bar.com/slashdot"
>>> BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
>>> ALT="topichumor.gif"/>
>>
>> As you can see, the 'myspace' and 'slashdot' namespaces have been
>> attributed to HTML tags for no apparent reason. If you revert to the old
>> saxconnector, these go away. In most browsers this doesn't seem to make
>> much difference, but it confused OmniWeb enough to alert me to something
>> being wrong.
>>
>> Another issue that is longstanding is that Cocoon outputs HTML with
>> namespace declarations at the beginning for namespaces used during the
>> processing even when they are no-longer required in the final output.
>> Whist it doesn't cause any problems, it is potentially confusing for
>> anyone trying to make sense of the source-code. Perhaps this is a
>> feature!
>> :-)
>>
>> Stuart.
>>
>>
>> On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
>>
>>>
>>>
>>> On Tue, 1 May 2001, Stuart Roebuck wrote:
>>>
>>>> There are also problems with the almost arbitrary attributing of
>>>> namespaces to elements processed with the new xincludesaxconnector.
>>>> Look
>>>> at the resulting source output of the aggregation example in CVS and
>>>> you'll see what I mean.
>>>
>>> Stuart, could you please explain to me what you've found is the problem
>>> in more detail so that one can use it to correct the behaviour?
>>>
>>> TIA
>>>
>>> Giacomo
>>>
>>>>
>>>> Stuart.
>>>>
>>>> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
>>>>
>>>>> my issues:
>>>>>
>>>>> 1. why should this be a saxconnector instead of a filter?
>>>>>
>>>>> 2. the schema upon which it operates doesn't conform to the official
>>>>> xinclude spec, but it operates on the official xinclude namespace.
>>>>> one
>>>>> or
>>>>> the other needs to change. specifically, at the least, the src
>>>>> attribute
>>>>> should be an href attribute and the ns and prefix attributes don't
>>>>> exist.
>>>>>
>>>>> - donald
>>>>>
-------------------------------------------------------------------------
Stuart Roebuck stuart.roebuck@adolos.com
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by giacomo <gi...@apache.org>.
Hi Stuart
Thanks for your test. I'm in no way a namespace expert, so, could you
give me some suggestion on what we have to change to make it right?
TIA
Giacomo
On Tue, 1 May 2001, Stuart Roebuck wrote:
> Giacomo,
>
> Sorry for being a bit brief. Here's the first 15 lines of the HTML output
> from Cocoon (CVS about 12 hours ago), looking at the "news/aggregate.xml"
> match. The current defaults use the xincludesaxconnector:
>
> > <HTML xmlns:ns3="http://foo.bar.com/isyndicate" xmlns:ns2="http://foo.bar.
> > com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> > <BODY>
> > <page xmlns="http://foo.bar.com/myspace"> <slashdot
> > xmlns="http://foo.bar.com/slashdot">
> > <table xmlns="http://foo.bar.com/slashdot" width="100%" border="0">
> > <tr xmlns="http://foo.bar.com/slashdot">
> > <td xmlns="http://foo.bar.com/slashdot"
> > STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
> > sans-serif;" colspan="5">
> > <CENTER xmlns="http://foo.bar.com/slashdot">
> > <b xmlns="http://foo.bar.com/slashdot">Current
> > News from Slashdot</b>
> > </CENTER>
> > </td>
> > </tr>
> > <tr xmlns="http://foo.bar.com/slashdot"
> > STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
> > sans-serif;">
> > <td xmlns="http://foo.bar.com/slashdot">
> > <CENTER xmlns="http://foo.bar.com/slashdot">
> > <IMG xmlns="http://foo.bar.com/slashdot"
> > BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> > ALT="topichumor.gif"/>
>
> As you can see, the 'myspace' and 'slashdot' namespaces have been
> attributed to HTML tags for no apparent reason. If you revert to the old
> saxconnector, these go away. In most browsers this doesn't seem to make
> much difference, but it confused OmniWeb enough to alert me to something
> being wrong.
>
> Another issue that is longstanding is that Cocoon outputs HTML with
> namespace declarations at the beginning for namespaces used during the
> processing even when they are no-longer required in the final output.
> Whist it doesn't cause any problems, it is potentially confusing for
> anyone trying to make sense of the source-code. Perhaps this is a feature!
> :-)
>
> Stuart.
>
>
> On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
>
> >
> >
> > On Tue, 1 May 2001, Stuart Roebuck wrote:
> >
> >> There are also problems with the almost arbitrary attributing of
> >> namespaces to elements processed with the new xincludesaxconnector. Look
> >> at the resulting source output of the aggregation example in CVS and
> >> you'll see what I mean.
> >
> > Stuart, could you please explain to me what you've found is the problem
> > in more detail so that one can use it to correct the behaviour?
> >
> > TIA
> >
> > Giacomo
> >
> >>
> >> Stuart.
> >>
> >> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
> >>
> >>> my issues:
> >>>
> >>> 1. why should this be a saxconnector instead of a filter?
> >>>
> >>> 2. the schema upon which it operates doesn't conform to the official
> >>> xinclude spec, but it operates on the official xinclude namespace. one
> >>> or
> >>> the other needs to change. specifically, at the least, the src attribute
> >>> should be an href attribute and the ns and prefix attributes don't
> >>> exist.
> >>>
> >>> - donald
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >>> For additional commands, email: cocoon-dev-help@xml.apache.org
> >>>
> >>
>
> -------------------------------------------------------------------------
> Stuart Roebuck, BSc, MBA Tel.: 0131 228 4853 / Fax.: 0870 054 8322
> Managing Director Alpha Numeric Pager: 07654 588898
> ADOLOS <http://www.adolos.com/>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >> For additional commands, email: cocoon-dev-help@xml.apache.org
> >>
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 1 May 2001, Stuart Roebuck wrote:
> Another issue that is longstanding is that Cocoon outputs HTML with
> namespace declarations at the beginning for namespaces used during the
> processing even when they are no-longer required in the final output.
> Whist it doesn't cause any problems, it is potentially confusing for
> anyone trying to make sense of the source-code. Perhaps this is a feature!
actually, this is a real problem - it can increase the size of the page by
a factor of two or more if you have several namespaces that are
erroneously being set on a lot of elements.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Stuart Roebuck <st...@adolos.co.uk>.
Giacomo,
Sorry for being a bit brief. Here's the first 15 lines of the HTML output
from Cocoon (CVS about 12 hours ago), looking at the "news/aggregate.xml"
match. The current defaults use the xincludesaxconnector:
> <HTML xmlns:ns3="http://foo.bar.com/isyndicate" xmlns:ns2="http://foo.bar.
> com/moreover" xmlns:ns1="http://foo.bar.com/slashdot">
> <BODY>
> <page xmlns="http://foo.bar.com/myspace"> <slashdot
> xmlns="http://foo.bar.com/slashdot">
> <table xmlns="http://foo.bar.com/slashdot" width="100%" border="0">
> <tr xmlns="http://foo.bar.com/slashdot">
> <td xmlns="http://foo.bar.com/slashdot"
> STYLE="background-color : #B0E0E6; font : x-small Arial, Helvetica,
> sans-serif;" colspan="5">
> <CENTER xmlns="http://foo.bar.com/slashdot">
> <b xmlns="http://foo.bar.com/slashdot">Current
> News from Slashdot</b>
> </CENTER>
> </td>
> </tr>
> <tr xmlns="http://foo.bar.com/slashdot"
> STYLE="background-color : lightgrey; font : x-small Arial, Helvetica,
> sans-serif;">
> <td xmlns="http://foo.bar.com/slashdot">
> <CENTER xmlns="http://foo.bar.com/slashdot">
> <IMG xmlns="http://foo.bar.com/slashdot"
> BORDER="0" HEIGHT="25" WIDTH="25" SRC="topichumor.gif"
> ALT="topichumor.gif"/>
As you can see, the 'myspace' and 'slashdot' namespaces have been
attributed to HTML tags for no apparent reason. If you revert to the old
saxconnector, these go away. In most browsers this doesn't seem to make
much difference, but it confused OmniWeb enough to alert me to something
being wrong.
Another issue that is longstanding is that Cocoon outputs HTML with
namespace declarations at the beginning for namespaces used during the
processing even when they are no-longer required in the final output.
Whist it doesn't cause any problems, it is potentially confusing for
anyone trying to make sense of the source-code. Perhaps this is a feature!
:-)
Stuart.
On Tuesday, May 1, 2001, at 10:07 am, giacomo wrote:
>
>
> On Tue, 1 May 2001, Stuart Roebuck wrote:
>
>> There are also problems with the almost arbitrary attributing of
>> namespaces to elements processed with the new xincludesaxconnector. Look
>> at the resulting source output of the aggregation example in CVS and
>> you'll see what I mean.
>
> Stuart, could you please explain to me what you've found is the problem
> in more detail so that one can use it to correct the behaviour?
>
> TIA
>
> Giacomo
>
>>
>> Stuart.
>>
>> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
>>
>>> my issues:
>>>
>>> 1. why should this be a saxconnector instead of a filter?
>>>
>>> 2. the schema upon which it operates doesn't conform to the official
>>> xinclude spec, but it operates on the official xinclude namespace. one
>>> or
>>> the other needs to change. specifically, at the least, the src attribute
>>> should be an href attribute and the ns and prefix attributes don't
>>> exist.
>>>
>>> - donald
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>> For additional commands, email: cocoon-dev-help@xml.apache.org
>>>
>>
-------------------------------------------------------------------------
Stuart Roebuck, BSc, MBA Tel.: 0131 228 4853 / Fax.: 0870 054 8322
Managing Director Alpha Numeric Pager: 07654 588898
ADOLOS <http://www.adolos.com/>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>> For additional commands, email: cocoon-dev-help@xml.apache.org
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by giacomo <gi...@apache.org>.
On Tue, 1 May 2001, Stuart Roebuck wrote:
> There are also problems with the almost arbitrary attributing of
> namespaces to elements processed with the new xincludesaxconnector. Look
> at the resulting source output of the aggregation example in CVS and
> you'll see what I mean.
Stuart, could you please explain to me what you've found is the problem
in more detail so that one can use it to correct the behaviour?
TIA
Giacomo
>
> Stuart.
>
> On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
>
> > my issues:
> >
> > 1. why should this be a saxconnector instead of a filter?
> >
> > 2. the schema upon which it operates doesn't conform to the official
> > xinclude spec, but it operates on the official xinclude namespace. one or
> > the other needs to change. specifically, at the least, the src attribute
> > should be an href attribute and the ns and prefix attributes don't exist.
> >
> > - donald
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
>
> -------------------------------------------------------------------------
> Stuart Roebuck, BSc, MBA Tel.: 0131 228 4853 / Fax.: 0870 054 8322
> Managing Director Alpha Numeric Pager: 07654 588898
> ADOLOS <http://www.adolos.com/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [c2] problems with xincludesaxconnector
Posted by Stuart Roebuck <st...@adolos.co.uk>.
There are also problems with the almost arbitrary attributing of
namespaces to elements processed with the new xincludesaxconnector. Look
at the resulting source output of the aggregation example in CVS and
you'll see what I mean.
Stuart.
On Monday, April 30, 2001, at 10:45 pm, Donald Ball wrote:
> my issues:
>
> 1. why should this be a saxconnector instead of a filter?
>
> 2. the schema upon which it operates doesn't conform to the official
> xinclude spec, but it operates on the official xinclude namespace. one or
> the other needs to change. specifically, at the least, the src attribute
> should be an href attribute and the ns and prefix attributes don't exist.
>
> - donald
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
-------------------------------------------------------------------------
Stuart Roebuck, BSc, MBA Tel.: 0131 228 4853 / Fax.: 0870 054 8322
Managing Director Alpha Numeric Pager: 07654 588898
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org