Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <3F210AE6.8060004@che-che.com>
Date: Fri, 25 Jul 2003 12:48:06 +0200
From: Juan Jose Pablos <cheche@che-che.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.2.1) Gecko/20030311 Debian/1.2.1-10
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Update action element (was:Re: %20 in breadcrumb trail.)
References: <3F200010.8030509@che-che.com> <3F20C65E.2070209@apache.org>
 <3F20E491.7080300@che-che.com> <3F20EA13.3060401@apache.org>
 <3F20F682.7000304@che-che.com> <3F210491.1030600@apache.org>
In-Reply-To: <3F210491.1030600@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Nicola,

I would not want to add attributes if there is no one is going to 
updated them.

I was not sure of the name, possibly we need to get a definition more 
general that gives an idea of the difficulty, time, amount of code 
requiere and impact on the system.

Can anyone think of a better name to define this?

Cheers,
Cheche


> 
> 
> I like the idea.
> 
> What about this instead (or something like it)
> 
> 
>   <!ENTITY % types "add|remove|update|fix">
>   <!ENTITY % contexts "build|docs|code|admin|design">
>  +<!ENTITY % difficulty "easy|medium|hard|wizard">
>  +<!ENTITY % time "little|medium|much|unknown">
> 
>   <!-- =============================================================== -->
>   <!-- Common elements -->
>  @@ -54,6 +55,7 @@
>   <!ATTLIST action %common.att;
>             dev  IDREF  #REQUIRED
>             type (%types;)  #IMPLIED
>  +          difficulty (%change;)  #IMPLIED
>  +          time (%change;)  #IMPLIED
>             context (%contexts;) #IMPLIED
>             due-to CDATA #IMPLIED
>             due-to-email CDATA #IMPLIED
>