Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 27075 invoked from network); 12 May 2005 23:46:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 May 2005 23:46:27 -0000 Received: (qmail 17990 invoked by uid 500); 12 May 2005 23:50:34 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 17924 invoked by uid 500); 12 May 2005 23:50:33 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 17910 invoked by uid 99); 12 May 2005 23:50:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from vuwunicosmtp003.vuw.ac.nz (HELO vuwunicosmtp003.vuw.ac.nz) (130.195.86.28) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 12 May 2005 16:50:33 -0700 Received: from coso.staff.vuw.ac.nz (coso.staff.vuw.ac.nz [130.195.85.188]) by vuwunicosmtp003.vuw.ac.nz (8.12.11/8.12.11) with ESMTP id j4CNkJJZ029440 for ; Fri, 13 May 2005 11:46:19 +1200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Document publishing worklow (was Re: Expert pre-defined/community post-defined?) Date: Fri, 13 May 2005 11:46:17 +1200 Message-ID: <802926B6AB8533408C33ADBCA3EE5C2A021EC140@coso.staff.vuw.ac.nz> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Document publishing worklow (was Re: Expert pre-defined/community post-defined?) Thread-Index: AcVXFsOd+wTWm4gJQjuujtDL1Q2F8wAMkRKw From: "Conal Tuohy" To: X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ross Gardler wrote: > Stefano Mazzocchi wrote: >=20 > > I like the notion of > >=20 > > daisy -> forrest -> out > >=20 > > makes very good sense. > >=20 > > Now we just need to find a way to automate a little that=20 > workflow, but=20 > > without introducing security vulnerabilities. >=20 > How about this (bullet summaries followed by textual description. >=20 > Daisy as editing environment. > - anyone can edit > - people are given quick "committership" here > - change mails are sent out by Daisy for docs committer review > - docs committers review changes and publish to the=20 > daisy repo >=20 > Forrest as publishing tool > - cocoon committers manage a > - brings together XDocs, wiki docs, Daisy docs etc. > - publish to (or dynamically host on) a staging server >=20 > Offical Docs site > - live Apache site is pulled from staging server Regarding the structuring of the resulting documentation (as opposed to the content) ... can you comment on that aspect? Does Daisy have support for tagging (whether "folksonomy" or controlled vocabularies of some sort)? How might these tags integrate with the "core" concepts in xdocs, the Forrest sitemap, etc? I've been working recently on a website upgrade project which uses XML Topic Maps to deal with these issues - the site was relaunched just last week. Now I'm wondering if the Cocoon community might benefit from using XTM. It looks like a classic application for topic maps. I think they could help by providing a set of logical "hooks" to tag content with, and tools for harvesting metadata, merging topics, querying etc.=20 Con