Return-Path: <j3322ptm@yahoo.de>
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 55328 invoked from network); 7 May 2003 19:40:22 -0000
Received: from mail.datazug.ch (212.4.65.100)
  by daedalus.apache.org with SMTP; 7 May 2003 19:40:22 -0000
Received: from yahoo.de [212.4.88.68] by mail.datazug.ch with ESMTP
  (SMTPD32-7.15) id A13515D901F6; Wed, 07 May 2003 21:40:37 +0200
Message-ID: <3EB96127.7080409@yahoo.de>
Date: Wed, 07 May 2003 21:40:23 +0200
From: "J.Pietschmann" <j3322ptm@yahoo.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: Roles (was: antlib)
References: <747F247264ECE34CA60E323FEF0CCC0C0F50F1@london.cellectivity.com>
 <b9a4iv$hf7$1@main.gmane.org> <200305071009.54397.peter.reilly@corvil.com>
In-Reply-To: <200305071009.54397.peter.reilly@corvil.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

peter reilly wrote:
>       -  namespaces of attributes is not handled yet - the
>          code uses getQName() on the attributes and does
>          not pass the URI of the attributes to the attribute list given
>          to
Most vocabularies don't use namespaces for attributes, the reason being
that the semantics of attributes with the same name can be derived with
the help of the elements where the attributes appear.
An example:
   <lang:translate src="en_US" dst="de"/>
and
   <task:translate src="foo.svg" dst="foo.jpg"/>
The src attribute obviously serves a different purposes for the different
elements, but it is assumed the element provides enough context to handle
this.
An exception are attributes where more than one attribute with the same
local name can be expected to be attached to an element
An example
   <product electrical:class="high voltage" fireproof:class="flammable"
     healthhazard:class="toxic"/>
(or shorter: <product e:class="high voltage" f:class="flammable"
    h:class="toxic"/> )
The example may strike you as stupid, but this kind of vocabulary
may really evolve from merging simpler stuff. I'd think Ant can avoid this,
or at least try.


> 2) The usage of Project#createTask/DataType(name) will not work for
>     tasks loaded as a result of XML namespaces, a Project#createTask/DataType(
>     uri, name) method will need to be added.
Some projects migrated to namespaced XML by passing
   ns-uri+"^"+name
internally through the APIs.

J.Pietschmann