Lists Home |
Date Index |
Describe the discovery behavior.
a) For what reason is it initiated
b) By what mechanism is it accomplished
c) What entity evolves as a result of
acquiring the behavior?
d) How is a message type shared and how
after it is shared is it discarded/forgotten
as a type (pruning the theory lattice)?
The realistic answer to c) is the client.
In an ontologically endowed SOA, the client
must be able to consume a service as a result
of using the ontology (which itself can be
delivered by a service), but it can also
produce an ontology and return it as a
theory to the emitter. So discovery
is a feedback-enabled behavior such that
the act of using it improves it and
evolves the system. A model/theory/ontology
submitted can then be shared and such
sharing is the semantic equivalent of
the Google PageRank.
SOAs are described as a framework of
shared messages and it is the evolution
of the message set that should be examined
because this is the standardization behavior.
Multiple SOAs that are ontologically distinct
but share overlapping message types are
information ecosystems. Such systems are
not boundaryless. In fact, the standardization
behavior creates boundaries and these affect
the survival and propagation of any member
of a distinct information community.
Next, we must better understand the evolution
of distinct situations which involve members
of multiple information communities and how
these affect the standardization behaviors
over these messages.
From: Chiusano Joseph [mailto:email@example.com]
"Bullard, Claude L (Len)" wrote:
> A simple question, but one that could get to
> the heart of whether or not we should expect
> to see growth in the semantic web business:
> What are some services that SemWeb
> applications could expose for discovery
> and integration into web client applications
> including mobile applications? In other
> words, how and where do the Sem Web and
> Service Oriented Architectures meet?
This should be a good thread. I could go on and on about this, but at
the most rudimentary level (being very simple with the language, and
making some basic assumptions):
- A primary foundation of SOA is shared services
- Semantic Web services will be described in a semantically rich-enough
manner so as to be efficiently discovered (by "efficiently", I mean both
easily and according to the service discoverer's criteria such as QoS
- SOA + Semantic Web = More easily discovered services that are better
tailored to a service discoverer's (human or machine) needs, thereby
enabling service providers to broaden their reach, and service
discoverers to have their processing needs more easily met (higher
"service satisfaction") - which translates into better service for their
customers (if a customer-oriented scenario).