I suggest the OMML be more general rather than restricitng it to
the proxylet. Maybe the root element can be OpesIrInfo with a type
attribute specifying if it is a proxylet, ICAPcallout etc.
Also, doesn't the description attribute belong in this element rather
than in the owner element (as intuitively it does not describe the owner)
Section 5.2 (There is some numbering mistake, but 5.2 is unique) seems to
be incomplete. Was the intention to specify how the rules specified in
the metadata gets "and"ed with the rules in the rule module ? If not, what
was the intention and where will this "and"ing be specified ?
(The DTD as written has no way of specifying these additional rules)
Re: modified-header element, should we have a special header value of "any"
or do we allow regexp and have the user specify * ?
sherif
X-Mozilla-Status: 0801
Date: Fri, 23 Feb 2001 17:35:07 -0500
From: Markus Hofmann <hofmann(_at_)bell-labs(_dot_)com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18)
Gecko/20010131
Netscape6/6.01
X-Accept-Language: en
MIME-Version: 1.0
To: OPES List <ietf-openproxy(_at_)imc(_dot_)org>
Subject: New ID on OMML submitted
List-Archive: <http://www.imc.org/ietf-openproxy/mail-archive/>
List-Unsubscribe:
<mailto:ietf-openproxy-request(_at_)imc(_dot_)org?body=unsubscribe>
List-ID: <ietf-openproxy.imc.org>
Hi,
we just submitted the attached ID on OMML, a language for describing
OPES meta-data. Comments and feedback are highly appreciated.
Thanks to Christian for taking the lead on the draft!
-Markus