Thanks to everyone who responded. The discussion seems
to have gone quiet, so it is time to summarise.
I am not going to call a Vote on this, rather just do it.
If anyone thinks otherwise then say so.
These are the original set of issues. I have added comments
based on the discussion, and added t
- Original Message -
From: "David Crossley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 16, 2004 2:50 AM
Subject: Re: [Proposal] add DTDs to Apache website
> Roger I Martin PhD wrote:
> > There are schema definitions at
> >
Roger I Martin PhD wrote:
> There are schema definitions at
>
> C:\apache\cocoon-2.1\src\blocks\databases\samples\xsp\esql.xsd for esql
> C:\apache\cocoon-2.1\src\documentation\xdocs\drafts\sitemap-2.1-draft.xsd
> for *.xmap
>
> Are these to be organised with the DTDs of this proposal?
No, there
Stefano Mazzocchi wrote:
> Juan Jose Pablos wrote:
>
> > Stefano Mazzocchi wrote:
> >
> >
> >> Stefano, who has been waiting for some 18 months for somebody else to
> >> come up with the idea of having forrest pregenerating the .htaccess
> >> file to do some sort of poor-man multichannel or c
Stefano Mazzocchi wrote:
> David Crossley wrote:
> > Dave Brondsema wrote:
> >> David Crossley wrote:
> >>
> >>> 6) What will be the URLs for the DTDs?
> >>> http://xml.apache.org/forrest/dtd/...
> >>> We presume that Forrest will not be a top-level project soon.
> >>
> >> The forrest docs and forr
Stefano,
Stefano Mazzocchi wrote:
nono, you guys don't get it: it was a social experiment about cross
pollination between the java/xml world and the httpd world.
Are you talking about forrest?, I did like the idea but I do not know
what would be posible to do with .htaccess. To tell you the tru
On 15 Jan 2004, at 16:15, Juan Jose Pablos wrote:
Stefano Mazzocchi wrote:
Stefano, who has been waiting for some 18 months for somebody else to
come up with the idea of having forrest pregenerating the .htaccess
file to do some sort of poor-man multichannel or content negotiation,
but has
efano Mazzocchi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 10:01 AM
Subject: Re: [Proposal] add DTDs to Apache website
>
> On 15 Jan 2004, at 05:05, David Crossley wrote:
>
> > Joerg Heinicke wrote:
&
Stefano Mazzocchi wrote:
Stefano, who has been waiting for some 18 months for somebody else to
come up with the idea of having forrest pregenerating the .htaccess
file to do some sort of poor-man multichannel or content negotiation,
but has lost hope so it's time to inject notion in the syst
On 15 Jan 2004, at 05:05, David Crossley wrote:
Joerg Heinicke wrote:
David Crossley wrote:
3) The Forrest website is built using the "stable" version of
Forrest (currently v0.5.1). So how will DTDs from the current
CVS (v0.6-dev) get into the website CVS [3]? Manual copy? See 4).
4) If some comm
On 15.01.2004 05:05, David Crossley wrote:
9) We will never know if the Catalog Entity Resolver gets
broken after an upgrade. Forrest will still work but will
be slower, doing downloads of the DTD and supporting files
on each document parse. We can probably add a test document
in the "forrest seed
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> ...
> > 2) The Forrest build system is complex. It would be good to automate
> > the publishing of DTD versions, but that may not be possible.
>
> Could you please explain a bit more?
I was mainly hinting that it might need to be a manual task.
Joerg Heinicke wrote:
> David Crossley wrote:
>
> > 3) The Forrest website is built using the "stable" version of
> > Forrest (currently v0.5.1). So how will DTDs from the current
> > CVS (v0.6-dev) get into the website CVS [3]? Manual copy? See 4).
> >
> > 4) If some committer changes the DTDs i
I'm not CCing Forrest as I'm not subscribed there and they don't
moderate my mails through.
On 14.01.2004 05:53, David Crossley wrote:
3) The Forrest website is built using the "stable" version of
Forrest (currently v0.5.1). So how will DTDs from the current
CVS (v0.6-dev) get into the website C
David Crossley wrote:
...
2) The Forrest build system is complex. It would be good to automate
the publishing of DTD versions, but that may not be possible.
Could you please explain a bit more? If it's just about placing the
schema dir, or some of those dirs, in a predefined place, it can be done
On Jan 14, 2004, at 11:46 AM, David Crossley wrote:
David Crossley wrote:
7) Does the Apache webserver deliver the supporting files using
the appropriate Content-Type? Is that "text/plain"? Does it matter?
We have *.dtd and *.mod and *.pen and *.ent extensions.
This is what the webserver reports:
David Crossley wrote:
> David Crossley wrote:
> > Marshall Roch wrote:
>
> >
> > > You've convinced me that it's not worth the effort to get
> > > the DTDs online. See below. (...about configuration notes.)
> >
> > It is worth the effort. We get way too many questions from users.
>
> One of mai
David Crossley wrote:
>
> 7) Does the Apache webserver deliver the supporting files using
> the appropriate Content-Type? Is that "text/plain"? Does it matter?
> We have *.dtd and *.mod and *.pen and *.ent extensions.
This is what the webserver reports:
*.dtd ... Content-Type: application/xml-dt
18 matches
Mail list logo
