Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 46391 invoked from network); 1 Apr 2006 11:34:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Apr 2006 11:34:32 -0000 Received: (qmail 99607 invoked by uid 500); 1 Apr 2006 11:34:31 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 99545 invoked by uid 500); 1 Apr 2006 11:34:31 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 99528 invoked by uid 99); 1 Apr 2006 11:34:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Apr 2006 03:34:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=MSGID_FROM_MTA_HEADER,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.121.192.7] (HELO mail.e-wire.net.au) (203.121.192.7) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Apr 2006 03:34:29 -0800 Received: from developer (mail.e-wire.net.au [127.0.0.1]) by mail.e-wire.net.au (8.13.1/8.13.1) with ESMTP id k31BUx5R011189 for ; Sat, 1 Apr 2006 19:31:00 +0800 Message-Id: <200604011131.k31BUx5R011189@mail.e-wire.net.au> Received: from 203-121-204-130.e-wire.net.au [203.121.204.130] for mail.e-wire.net.au (EHLO developer) via SMTP; Sat, 01 Apr 2006 19:31:01 +0800 Reply-To: From: "Gav...." To: Subject: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher Date: Sat, 1 Apr 2006 19:34:03 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20060331224144.GD13559@igg.indexgeo.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcZVE/iW9hycizTZTWicH0rbETscIgAX/Qwg X-BitDefender-SpamStamp: 1.1.4 049000040111ABAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAQAAAI X-BitDefender-Spam: No (0) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi All, > -----Original Message----- > From: David Crossley [mailto:crossley@apache.org] > Sent: Saturday, 1 April 2006 6:42 AM > To: dev@forrest.apache.org; brightoncomputers@brightontown.com.au > Subject: Re: [jira] Updated: (FOR-639) define terminology for the various > aspects of Dispatcher > > Gav.... wrote: > > Ok, Paul has also mentioned this so needs sorting, I'll see what I can > come > > up with in the next day or two. > > > > What we have so far it terms of Dispatcher Docs published:- > > > > dispatcher.html > > howto-structurer-install.html > > howto-dispatcher-quickstart.html > > howto-structurer-dsl.html > > howto-structurer-contracts.html > > > > The howto-structurer-install.html is actually describing how to > > Install the "Dispatcher" so I think should be renamed to avoid > > Further confusion. > > Yes, i have wondered about that too. > Today i will 'svn move' the documents, > amend all the links and references, and > create .htaccess redirects for the website. > > > The howto-structurer-dsl is out of date and contains incorrect > > Contract examples. Is there an upto date version of this or > > Shall I attempt to correct the examples given. > > Also, I would like an example of what is meant by > > "Domain Specific" in this context (of -dsl) > > > > This FOR is about clarifying and defining terminology used. So do we > > Want a new page called dispatcher-terminology.html or similar and how > > Do we want the content presented - in example form, or in a strict > > Dictionary type arrangement leaving the examples on the howto pages? > > There was a mailing list discussion about this. > Need to find that. > > One really good idea was to create the new Glossary plugin > http://issues.apache.org/jira/browse/FOR-755 > and use that. Ok, I have started this, created the basic Glossary output plugin, Now need to configure it. I have questions (never done a plugin before so bear with me) :- I'm referring to the attachments provided on FOR-755 here - 1. Does glossary.xmap get renamed to and therefore replace output.xmap ? 2.Where do the .dtd and .mod files need to go? 3a. I have put glossary2document.xsl in resources/stylesheets, is this correct? 3b. And will I need to rename it to glossary-to-document.xsl ? 3c. If yes to 3b, anything else to change? 4. Glossary.xml is placed in the xdocs directory, this is the main file we Need to add our Terminology. Looking quickly, its an A-Z arrangement, can we and should we have a separate A-Z for Dispatcher Terminology, therefore a separate dispatcher-glossary.xml file, or will ALL Forrest terminology reside in the same Glossary.xml file? I am doing this in Whiteboard at the moment, is this ok? I am not creating samples, I could rename Ross's original Glossary.xml to something else and use that as a sample ? Anything else? Lots of 'Q''s in there, sorry. 1 hour later ... Ant Test - Build Failed die to could not validate Glossary.xml, I guess that's because the .dtd and .mod files are in the wrong place. Gav... > > Failing that, i reckon just use an ordinary document > with concise definitions that link to examples in > the other documents. I have started this also, in fact started in when your idea of Using the Glossary Plugin came through. Hmm, I wonder which I'll Finish first :) > > However it gets done is good. > > -David On it, Gav...