ietf-openproxy
[Top] [All Lists]

Re: OMML and svc descriptions

2001-08-01 12:45:55

Ben,

For example, say ACME Ltd. writes the, "ACME Language Translation"
service which can translate English HTML pages into Russian, uses the
OMML DTD, and deploys it to the edge. What is the point of having a
(machine readable) DTD to describe the meta-data of the service if it
cannot capture the fact that this service *translates*, and does so into
*Russian*?  Without this knowledge how will any rules ever be written to
trigger this service? Even if rule authors need not reference specific
URI's for callout services (e.g. use indirection), how will the OPES
engine "match" ACME's Russian translation service to a condition that
someone would like Russian representation?  Maybe i'm missing the role
of the human-administrator?  ..

I would image that there's always a human admisistrator, who selects a
suitable service for his customer (e.g. selects a specific translation
service for a customer who wants translation from English into
Russion). Once a suitable (translation) service has been selected,
something like OMML (i.e. meta-data about the application/service)
could provide more specific technical information about the selected
service and what it does. This service specific information could then
be used for additional checks or optmization (e.g. in the rule
parser).

The OMML Draft was an approach to collect and write some of these
ideas down. We've to see whether the basic ideas make sense in this
context, and whether and how they would fit into the OPES model.

-Markus

<Prev in Thread] Current Thread [Next in Thread>
  • Re: OMML and svc descriptions, Markus Hofmann <=