Q: how about future services, extendability, backward compatibility?
A: reason is domain or vocabular not enough: domain specific.
stakeholder must
documentation
different version, compatibility, versioning can be handled at api management
rdf mapping, etc
Q: how the language capture heterogeneous user requirements?
A: future works maybe
Q: how to make modle more user centric, easier for user to understand the semantic
A: generation of description,
Q: the work is project specific, praxis. What kind of requirements to use the realized system (assumptions, etc)?
A: service selection, protocols support, etc, federation, secrity
Q: how to map conformity in domain
A: XACML, for service conformance declaration bei registraion
Q: role, stakeholder model in user centric service description? or is this for developer
A: many users
market place manager
user: search
Q (küppel): Why using ruby as DSL
A:
Q: why the providers form federation? define federation rules, characteristic?
A: there are framework and technique for members, eduGain
Q: How the evaluation, interview were carried out? checklist, questionairs
A:
focus group: formula
survey
Why not broad publics
→ not fully completed
Q: can proxy be provided by a provider as service?
A: cloudflare, google, middlebox providers.