On Tue, 22 Apr 2003, Oskar Batuner wrote:
Another place for SOAP in OPES is access to all reference and
information points.
While there is a trend to postpone (preferably indefinitely :) any
specs that go beyond the definition of the reference - still without
such specs OPES achitsture is incomplete. All references with
undefined information structure look more like a "fine print" - one
that is not supposed to be read.
If we move some programmatically accessible information to
references without providing access specs - all implementers are
forced to create proprietary access formats and interoperability
becomes a problem.
What do you mean by "providing access specs"? Would providing a
protocol name such as "http:" in a URI identifier be sufficient? You
are not talking about specifying how the referenced content is to be
composed or interpreted, are you?
Can you give a couple of specific examples where implementations would
access referenced content and auto-interpret it?
Thanks,
Alex.