You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Steven Noels <st...@outerthought.org> on 2002/05/16 11:54:05 UTC
[vote] DTD management
Hi folks,
As it is now, Cocoon will be the prime showcase of Forrest, so we have
lot of interest keeping everything in sync. Diana has been proposing
some new DTDs on the Forrest-list, which we would be glad to host and
nurture. Some issues however:
- We will try to keep the migration path of 'old' documentation as
simple as possible, ie providing you with an XSLT to do a docv10->docv11
transformation. Nevertheless, we would like new documentation to be
authored/generated using the new v11 DTD if possible.
- We would like all new DTDs to be based (importing/re-using) on the
work-in-progress (i.e. document-v11) in Forrest and not on the older
DTD's anymore.
So this brings me to the following ballot:
[ ] all new DTDs (both in the Cocoon/Forrest project) should be using
the new document-v11 and not the older ones
[ ] Forrest is the de-facto DTD repository (+ we will also maintain
archives for that matter of older versions) for both projects, we'll
have a separate portion of the website dedicated to this
Regards,
</Steven>
Re: [vote] DTD management
Posted by David Crossley <cr...@indexgeo.com.au>.
Steven Noels wrote:
> Hi folks,
>
> As it is now, Cocoon will be the prime showcase of Forrest, so we have
> lot of interest keeping everything in sync. Diana has been proposing
> some new DTDs on the Forrest-list, which we would be glad to host and
> nurture. Some issues however:
>
> - We will try to keep the migration path of 'old' documentation as
> simple as possible, ie providing you with an XSLT to do a docv10->docv11
> transformation. Nevertheless, we would like new documentation to be
> authored/generated using the new v11 DTD if possible.
>
> - We would like all new DTDs to be based (importing/re-using) on the
> work-in-progress (i.e. document-v11) in Forrest and not on the older
> DTD's anymore.
>
> So this brings me to the following ballot:
>
> [ ] all new DTDs (both in the Cocoon/Forrest project) should be using
> the new document-v11 and not the older ones
+1 ... and for keeping these v10 to v11 changes to be simple.
Let us progress gradually, i.e. i do not not to see a wild leap to
some radically different document structure at this stage.
> [ ] Forrest is the de-facto DTD repository (+ we will also maintain
> archives for that matter of older versions) for both projects, we'll
> have a separate portion of the website dedicated to this
+1
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [vote] DTD management
Posted by David Crossley <cr...@indexgeo.com.au>.
Steven Noels wrote:
> Hi folks,
>
> As it is now, Cocoon will be the prime showcase of Forrest, so we have
> lot of interest keeping everything in sync. Diana has been proposing
> some new DTDs on the Forrest-list, which we would be glad to host and
> nurture. Some issues however:
>
> - We will try to keep the migration path of 'old' documentation as
> simple as possible, ie providing you with an XSLT to do a docv10->docv11
> transformation. Nevertheless, we would like new documentation to be
> authored/generated using the new v11 DTD if possible.
>
> - We would like all new DTDs to be based (importing/re-using) on the
> work-in-progress (i.e. document-v11) in Forrest and not on the older
> DTD's anymore.
>
> So this brings me to the following ballot:
>
> [ ] all new DTDs (both in the Cocoon/Forrest project) should be using
> the new document-v11 and not the older ones
+1 ... and for keeping these v10 to v11 changes to be simple.
Let us progress gradually, i.e. i do not not to see a wild leap to
some radically different document structure at this stage.
> [ ] Forrest is the de-facto DTD repository (+ we will also maintain
> archives for that matter of older versions) for both projects, we'll
> have a separate portion of the website dedicated to this
+1
--David
Re: [CMS] What about Slide?
Posted by Gianugo Rabellino <gi...@apache.org>.
Ivelin Ivanov wrote:
> Xincon looks promising. Is it in the xindice trunk yet?
>
Jan is an Xindice committer, and we are working on a xincon rewrite
which will eventually be Avalon based. Skeleton code is already in
Xindice scratchpad but ATM I don't have a minute to follow this baby.
Anyway WebDAV support is on top of my wish list for Xindice.
Ciao,
--
Gianugo Rabellino
Re: [CMS] What about Slide?
Posted by Ivelin Ivanov <iv...@apache.org>.
Xincon looks promising. Is it in the xindice trunk yet?
----- Original Message -----
From: "Nicola Ken Barozzi" <ni...@apache.org>
To: <fo...@xml.apache.org>
Sent: Thursday, May 16, 2002 6:40 AM
Subject: Re: [CMS] What about Slide?
> From: "Steven Noels" <st...@outerthought.org>
>
> > Or Xindice / Xincon...?
> >
> > http://www.mucl.de/~jmetzner/xincon/
>
> Cool! I didn't even know it existed! :-O
>
> > Point is that we currently don't have the hardware infrastructure
> > available to host such a CMS system on an Apache-scale.
>
> Yup.
>
> > I'd prefer to focus the energy on what we have (CVS, Cocoon rendering
> > static information et al.) until we have a showcase that can convince
> > infrastructure@apache.org we need access to Nagoya.
>
> Yes, you know I agree, it was just a RFC since I've heard of XIndice
before
> on the list but not Slide.
>
> Anyway, I think that we can make a more dynamic system using what we
have...
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
Re: [CMS] What about Slide?
Posted by Diana Shannon <te...@mac.com>.
On Thursday, May 16, 2002, Nicola Ken Barozzi wrote:
>> I'd prefer to focus the energy on what we have (CVS, Cocoon rendering
>> static information et al.) until we have a showcase that can convince
>> infrastructure@apache.org we need access to Nagoya.
>
> Yes, you know I agree, it was just a RFC since I've heard of XIndice
> before
> on the list but not Slide.
>
> Anyway, I think that we can make a more dynamic system using what we
> have...
Agreed. Then there are developers who ask for comments, from time to
time, about building components that *may* be useful once the Cocoon
site has such infrastructure available. Shouldn't people like that get
some feedback from Forrest? Is it appropriate to plant seeds for the
future? Or should they be working on a scratchpad contribution? Or
should people like that go join another open source CMS project?
I'm just trying to understand the utility of these varying types of
discussions.
Diana
Re: [CMS] What about Slide?
Posted by Nicola Ken Barozzi <ni...@apache.org>.
From: "Steven Noels" <st...@outerthought.org>
> Or Xindice / Xincon...?
>
> http://www.mucl.de/~jmetzner/xincon/
Cool! I didn't even know it existed! :-O
> Point is that we currently don't have the hardware infrastructure
> available to host such a CMS system on an Apache-scale.
Yup.
> I'd prefer to focus the energy on what we have (CVS, Cocoon rendering
> static information et al.) until we have a showcase that can convince
> infrastructure@apache.org we need access to Nagoya.
Yes, you know I agree, it was just a RFC since I've heard of XIndice before
on the list but not Slide.
Anyway, I think that we can make a more dynamic system using what we have...
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
RE: [CMS] What about Slide?
Posted by Steven Noels <st...@outerthought.org>.
Or Xindice / Xincon...?
http://www.mucl.de/~jmetzner/xincon/
Point is that we currently don't have the hardware infrastructure
available to host such a CMS system on an Apache-scale.
I'd prefer to focus the energy on what we have (CVS, Cocoon rendering
static information et al.) until we have a showcase that can convince
infrastructure@apache.org we need access to Nagoya.
</Steven>
[CMS] What abut Slide?
Posted by Nicola Ken Barozzi <ni...@apache.org>.
http://jakarta.apache.org/slide/
:-?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [vote] DTD management
Posted by Konstantin Piroumian <KP...@protek.com>.
From: "Steven Noels" <st...@outerthought.org>
> Hi folks,
>
> As it is now, Cocoon will be the prime showcase of Forrest, so we have
> lot of interest keeping everything in sync. Diana has been proposing
> some new DTDs on the Forrest-list, which we would be glad to host and
> nurture. Some issues however:
>
> - We will try to keep the migration path of 'old' documentation as
> simple as possible, ie providing you with an XSLT to do a docv10->docv11
> transformation. Nevertheless, we would like new documentation to be
> authored/generated using the new v11 DTD if possible.
>
> - We would like all new DTDs to be based (importing/re-using) on the
> work-in-progress (i.e. document-v11) in Forrest and not on the older
> DTD's anymore.
>
> So this brings me to the following ballot:
>
> [ ] all new DTDs (both in the Cocoon/Forrest project) should be using
> the new document-v11 and not the older ones
+ 1
I've already started rewriting i18n transformer docs using it.
But I still think that we need something more document oriented instead of
the book DTD for the documentation part (like I've suggested:
area/book/section/**/section/page). I have also a few suggestion about URI
space and pagination. Expect more help and comments in a week or so.
> [ ] Forrest is the de-facto DTD repository (+ we will also maintain
> archives for that matter of older versions) for both projects, we'll
> have a separate portion of the website dedicated to this
+0
I don't have a full vision of how projects are to be integrated with Forrest
(or vice versa), so I don't have an idea of how Cocoon docs can be generated
by Forrest using its DTD repository and entity catalogs.
Regards,
Konstantin
>
> Regards,
>
> </Steven>
>
RE: [vote] DTD management
Posted by Steven Noels <st...@outerthought.org>.
Carlos,
>
> Just one question:
>
> Will you make forrest's available on the Cocoon CVS? I think
> it's only fair
> since you are making them required
>
> Carlos
>
Sure, no problem.
Does anyone else has an opinion about DTD ownership? :-|
</Steven>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [vote] DTD management
Posted by Carlos <ca...@cvc.edu>.
Just one question:
Will you make forrest's available on the Cocoon CVS? I think it's only fair
since you are making them required
Carlos
On 5/16/02 5:52 AM, "Diana Shannon" <te...@mac.com> wrote:
>
> On Thursday, May 16, 2002, at 05:54 AM, Steven Noels wrote:
>
>> - We would like all new DTDs to be based (importing/re-using) on the
>> work-in-progress (i.e. document-v11) in Forrest and not on the older
>> DTD's anymore.
> +1
> Let's not create any unnecessary confusion for new authors.
>
>> So this brings me to the following ballot:
>>
>> [ ] all new DTDs (both in the Cocoon/Forrest project) should be using
>> the new document-v11 and not the older ones
> +1
>> [ ] Forrest is the de-facto DTD repository (+ we will also maintain
>> archives for that matter of older versions) for both projects, we'll
>> have a separate portion of the website dedicated to this
> +1
>
>
>
> Diana
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
--
Carlos E. Araya
---+ WebCT Administrator/Trainer
P | California Virtual Campus
- | C/O De Anza College
G | 21250 Stevens Creek Blvd
---+ Cupertino, CA 95014
email carlos@cvc.edu
web http://www.cvc1.org/ (work)
http://www.silverwolf-net.net (personal)
phone 408 257 0420 (work)
PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
"Do not meddle in the affairs of dragons....for you are crunchy and taste
good with ketchup and mayonnaise.."
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [vote] DTD management
Posted by Diana Shannon <te...@mac.com>.
On Thursday, May 16, 2002, at 05:54 AM, Steven Noels wrote:
> - We would like all new DTDs to be based (importing/re-using) on the
> work-in-progress (i.e. document-v11) in Forrest and not on the older
> DTD's anymore.
+1
Let's not create any unnecessary confusion for new authors.
> So this brings me to the following ballot:
>
> [ ] all new DTDs (both in the Cocoon/Forrest project) should be using
> the new document-v11 and not the older ones
+1
> [ ] Forrest is the de-facto DTD repository (+ we will also maintain
> archives for that matter of older versions) for both projects, we'll
> have a separate portion of the website dedicated to this
+1
Diana
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org