wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Semantic Web Services for Manufacturing Industry 65-7
DES cluster space
DES space
operator
Cluster
space
Cluster
space
Inter-space
protocol
Cluster
space
1. Write
(publish)
Agent
Cluster
4. Read (find)
2. Subscribe
(discover)
3. Notify
Agent
Agent
Cluster
Searching handler
Matching
engine
Agent
SR UI
Feedback
Http router
Polling handler
Indices
Feed cache
Agent
SP UI
Wiki and atom
protocol
Wiki
server
Indexing
manager
Work
Crawler
Work2Wiki
Knowledge
base
Request
Response/data flow
Component
Connector
FIGURE 65.1
SOA-based system architecture for multisite production.
The notified service requesters “read” triples that match with the template within a particular
transaction or the entire concrete space, and further process the triples accordingly. It provides intelligent
middleware (broker like), to manage the spaces without requesting each service provider and
requester to either download or search through the entire space. Moreover, it needs to provide security
and trust while keeping the system scalable and the usage simple. [Krummenacher 05] proposed a
minimal architecture for such provider middleware. [Bussler 05] identified a number of requirements
for Triple Spaces (providers): autonomy (including four basic forms of autonomy, viz., time, location,
reference, and data schema), simplicity, efficiency, scalability, decentralized architecture, security and
trust mechanisms, persistent communications, and history. In order to overcome the lack of support for
semantics-aware matching, Triple Space utilizes RDF to represent and match the machine-processable
semantics. It is a promising, if immature, Web services architectural style and may represent the future
paradigm for designing and implementing a truly service-oriented architecture. Based on our analysis
and the criticism from the literature, we develop an SOA architectural design with the extended “Web-
Oriented” style. [Dillon 07b], based on the extension of the triple space paradigm. We think of the Web
as a platform of services, and applications are built by composing services. We utilize Web 2.0 ideas in
developing these compositions. In current Web2.0 settings, service composition comes as the Mashup,
© 2011 by Taylor and Francis Group, LLC