Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 57707 invoked from network); 25 Feb 2005 13:32:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 25 Feb 2005 13:32:48 -0000 Received: (qmail 4468 invoked by uid 500); 25 Feb 2005 13:32:47 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 4443 invoked by uid 500); 25 Feb 2005 13:32:47 -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 Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 4429 invoked by uid 99); 25 Feb 2005 13:32:47 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from ns3.wkwyw.net (HELO ns3.wkwyw.net) (217.199.181.91) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 25 Feb 2005 05:32:46 -0800 Received: (qmail 14947 invoked from network); 25 Feb 2005 13:32:47 -0000 Received: from 82-69-78-226.dsl.in-addr.zen.co.uk (HELO ?192.168.0.4?) (82.69.78.226) by ns3.wkwyw.net with SMTP; 25 Feb 2005 13:32:47 -0000 Received: from 127.0.0.1 (AVG SMTP 7.0.300 [266.4.0]); Fri, 25 Feb 2005 13:32:37 +0000 Message-ID: <421F28F5.7030406@apache.org> Date: Fri, 25 Feb 2005 13:32:37 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: Metadata in Forrest (was Re: [RT] Per document skinconf...) References: <421C4D94.6070905@uidesign.de> <421C7040.3090901@apache.org> <421CBE22.3040904@apache.org> <421DB4C2.9090900@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: > Nicola Ken Barozzi wrote: > >> Ross Gardler wrote: > > ... > >>> All that being said, Forrest could be made to support both a separate >>> file or embedded data (there are use cases where the simplistic >>> solution is the best one). The problem with this is that we will have >>> two locations for storing the same data - could be confusing for users. >> >> >> IMHO the least we have to worry about is to confuse users. I have seen >> that if there is a simple and a more complete way, users would not get >> confused. >> >> The only confusion would come out of using both methods at the same >> time, with clashing metadata values. Ouch! >> >> I'll browse the web for 'rdf in html', 'xhtml metadata' etc to see how >> this is defined elsewhere. I want to try to reinvent the wheel the >> least possible. > > > And I did :-) > > From what I read it seems that making it possible to embed in xhtml > *and* be able to king to a metadata file is the solution to pursue. OK, I'm working on meta-data in an extension to Burrokeet soon (using Dublin Core). I'll follow up on these links and create a separate RT (after 0.7 release). Ross