[
Lists Home |
Date Index |
Thread Index
]
I was trying very hard to stay out of this but since
my name was invoked, leathery winged thing that I am,
I am compelled to answer.
... explosion from smoke box, low strings and horns
with slow timpani pulse in unison crescendo to brass section
fanfare and cymbal crash (really kitchy stuff)
<sigh>The Web is information resources identified by URIs.</sigh>
... wild applause at the obvious simple brilliance of that with
flowers thrown at feet of The Director and some discussion in the
box seats of giving him yet another prize with a $ amount and
an opportunity to speak to the general assembly of the UN...
You don't really want to open up that discussion again.
Mechanisms will mean real things like clients and servers, yes? Unless you
assume those definitions, then this is a discussion of as
one said, computer science or just patterns of open integrated
hypermedia systems. The Web hasn't contributed anything new
to that domain in terms of patterns of information use and
formation, so 'emergence' isn't exactly right: repackaged,
relabeled and patented are. We knew how to build component
architectures a long time ago. "THE WEB" == URI. Full stop.
Patterns of communication abstracted from their implementations
are describable without reference to The Web or mechanisms
implemented to use URIs, TCP/IP etc. just as the SOA RM
can be described without reference to web services. The SOA RM
is SOA's analog to XML's infoset (not buyable, but definitional).
The use of the SOA RM acts as an upper ontology (really, terms
and definitions) which can then be used in descriptions of Enterprise SOA
(the
services comprising a business of some type). The Enterprise
SOA is then used as the basis for describing services to be
procured. The vendor answers with a set of possibly web
services or other implementations that meet the requirements
of the Enterprise SOA. What you can actually price
are forms, reports, fields, interfaces, hardware
services and licenses.
So if this is a Pattern RM, one could start with:
o Publish/Subscribe
o Call/Response
o Get
o Post
o Push
o Pull
You aren't by any chance looking for the MEPs As Yet To Be
Named By URIs are you?
len
From: Peter Hunsberger [mailto:peter.hunsberger@gmail.com]
Huh? "physical virtual layer"?
You mean the layer that isn't really there?
(Maybe we can get Len to set it to music.)
|
