1. Towards bottom up Semantic
Services Definition (poster)
Cristian Vasquez
cvasquez@vub.ac.be
28/04/11 | pag. 1
2. Towards bottom up Semantic Services Definition
Motivation:
Service elicitation in
Decentralized and
Heterogeneous environments
How to construct systems that honor the
characteristics and the dynamics of such
systems?
28/04/11 | pag. 2
4. Towards bottom up Semantic Services Definition
Traditionally, how we perform the process of
service elicitation?
Business
Domain
ΩA
Stakeholder interactions
Services
To map the models
28/04/11 | pag. 4
Authorities,
Standards,
Experts etc.
5. Towards bottom up Semantic Services Definition
Business
Domain A
ΩA
Stakeholder
Group A
Business
Domain B
ΩB
Traditionally, how we perform the process of
service elicitation?
Stakeholder
Group B
Stakeholder interactions
Services
28/04/11 | pag. 5
6. Towards bottom up Semantic Services Definition
Authority A
Traditionally, how we perform the process of
service elicitation?
Ω
Authorities,
Standards,
Experts etc.
Stakeholder interactions
Services
Stakeholder Business
Domain A
Group A
ΩA
28/04/11 | pag. 6
Business
Domain B
ΩB
Stakeholder
Group B
7. Towards bottom up Semantic Services Definition
Highly decentralized
environments?
28/04/11 | pag. 7
-> To empower the participants.
8. Combine
Transform
Stakeholder
Management
Area (SMA)
By design we want to explore the use of
artifacts to hold the distinct semantics or
intended meaning of the stakeholders.
Externalize
Organize
Formalize
Refine
Adopt
-> They are owned by the community.
Service design
or “playground”
Area
Services
Import
Receive
(SMA)
28/04/11 | pag. 8
Export
Share
(SMA)
Artifacts
(Services)
9. Blackboards as a network
Service design area
or “playground” Area:
Blackboard networks
Blackboards adopts Wiki paradigm
Using relations to other blackboards (links)
Stakeholder
Applications
is a
is a
is a
Part of
Stakeholder
Applications
28/04/11 | pag. 9
10. Blackboards as a network
Service design area
or “playground” Area:
Blackboard networks
Blackboards adopts Wiki paradigm
Using relations to other blackboards (links)
Stakeholder
Applications
Similarity
cycle
Stakeholder
Applications
Composition
28/04/11 | pag. 10
Dealing with rising complexity:
Participant Awareness +
Pattern recognition etc.
11. Blackboards
Business Domain
+ Stakeholder A
Web
Blackboard
(Public space)
Business Domain
+ Stakeholder B
Observers
Blackboard's
Metadata
Referent (observed subject)
Model
Model
Representation
Layer
28/04/11 | pag. 11
12. Blackboards
Business Domain
+ Stakeholder A
Web
Blackboard
(Public space)
Business Domain
Stakeholder B
Observers
Blackboard's
Metadata
Models
RDF
Referent (observed subject)
Instances
Semantic layer
Implementation
Data layer
Controlled
Vocabulary
Natural
Language
Semantic layer
Stakeholder B
private space
28/04/11 | pag. 12
13. Blackboards evolution
Blackboard Evolution profits from:
Suitable for the following situations:
GIT
Mercurial Etc...
Widely used on decentralized versioning
Convergence and divergence capability
28/04/11 | pag. 13
17. Conclusion
Conclusion
We explore an approach that aims to support (by design):
- A group of stakeholders in their collaborative definition of services.
- Promote decentralization, heterogeneity and traceability on such
systems.
28/04/11 | pag. 17
18. Questions
Several questions to answer
What should be the agreement mechanisms between the stakeholders that
commit to a blackboard?
How we can profit from blackboard networks to compose and orchestrate
semantically enabled services?
How these networks evolve? How can we manage their complexity?
28/04/11 | pag. 18
