Folks - in specifying an "incoming" proxylet's meta-data, one uses the
OMML to talk about things like:
name, id, version, ... location, modified-headers, exec-env, date,
contact, etc.
How does OPES view what happens next in terms of the semantics of the
service?...
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? ..
Thanks,
Ben Falchuk
Research Scientist, Telcordia Technologies, Inc.