On Mon, 10 Nov 2003, Abbie Barbir wrote:
Can you please state your own definition of an OPES trace
I am still happy with the wording I proposed in May. Here is a
slightly polished version:
OPES trace:
application message information about
OPES entities that adapted the message
OPES tracing:
the process of creating, manipulating, or
interpreting an OPES trace
Note that the above trace definition assumes in-band tracing. This
dependency can be removed if desired. The definitions would be
accompanied by rules (e.g., "application bindings MUST define trace
format" or "OPES entities MAY perform tracing on behalf of other
entities").
I believe you did have definitions similar to the above in a few
revisions of the draft. The current definitions in the draft are:
In an OPES System tracing is defined as the inclusion of necessary
information within a message in an OPES Flow that identify the
collection of transformations or adaptations that have been
performed on it before its delivery to an end point (for example,
the data consumer application).
An OPES trace represents a snap shot of the tracing information
that have been added to a given application message.
A trace represents the collections of transformations on an
application message in the order that were performed.
HTH,
Alex.