Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 30109 invoked from network); 27 Dec 2003 15:21:29 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Dec 2003 15:21:29 -0000 Received: (qmail 25896 invoked by uid 500); 27 Dec 2003 15:21:24 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 25629 invoked by uid 500); 27 Dec 2003 15:21:23 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 25618 invoked from network); 27 Dec 2003 15:21:21 -0000 Received: from unknown (HELO openlib.org) (81.25.34.222) by daedalus.apache.org with SMTP; 27 Dec 2003 15:21:21 -0000 Received: from ivan by openlib.org with local (masqmail 0.2.6) id 1AaGGb-4MQ-00 for ; Sat, 27 Dec 2003 17:22:13 +0200 Date: Sat, 27 Dec 2003 17:22:12 +0200 From: Ivan Kurmanov To: forrest-dev@xml.apache.org Subject: Re: Allow "role" attribute in document DTD Message-ID: <20031227152212.GA3515@zetta> Mail-Followup-To: forrest-dev@xml.apache.org References: <3FECF5CF.8030109@wkwyw.net> <20031227052510.GB3190@expresso.localdomain> <3FED25D6.1020608@wkwyw.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FED25D6.1020608@wkwyw.net> User-Agent: Mutt/1.3.27i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm afraid of being out-of-context on this, but I'll just leave my comments. You decide if they are useful. On 03-12-27, Ross Gardler wrote: > > Suppose, we have a tutorial on how to build a Forrest web site. This > tutorial has a series of links. Some of which give extra detail about a > topic by linking to different tutorials. Some gice glossary definitions, > some define a trail through the training materials. Using role you can > indicate all of these. Consider the following code: > > An XML document ready for display by Forrest conforms to href="xdocDTD" role="forrestTrailIntermediate glossary">Document v1.2 > DTD, however, you need not write your documents in this format. > By configuring your sitemap.xmap accordingly and providing role="glossary">XSL you can cause Forrest to convert any source > format into the native XDoc format ready for display. In my own XHTML-based document markup language, I use tags for links. For links to other pages of the site I use tag with "ref" attribute, eg I'd write: An XML document ready for display by Forrest conforms to , however, you need not write your documents in this format. ... On the output this would turn into something like An XML document ready for display by Forrest conforms to Document v1.2 DTD, however, you need not write your documents in this format. ... > Here, we have three links. All of them have a role of "glossary", one > indicates it is part of the intermediate forrest trail, the other is > advanced. A client application can now be built that extracts all > glossary terms from a website (by retrieving the XDoc source), or it > could build a single document for the each of the forrest trails etc. If you want to extract all glossary terms from a website, it might be better to have all the terms marked-up respectively (as some kind of objects), then to extract that info from links. ...may be something like: Document v1.2 DTD New version of the DTD for documents... Then, if you want, you can render all references to glossary terms in some special way, no need to mark that up in every occurence of it in the documents--but define a rendering rule in match="a[@ref]" template. Does that make any sense? Kurmanov http://www.ahinea.com/