From FutureInternetWiki

Contents 1 Information 1.1 Categories for standards (can be extended) 1.2 Standardisation activity status types 1.3 Standardisation activity description model 2 Standardisation activities 2.1 Pre-publication 2.1.1 unnamed 2.1.2 BPEL extensions for compliant services 2.1.3 BPMN 2 revisions 2.1.4 Compliance Request Language 2.1.5 Mashup Description Language 2.1.6 PIM4Cloud 2.1.7 SOA-RM 2.1.8 UML 2 revisions 2.1.9 Widgets 2.2 Published 2.2.1 Delivery Context Ontology 2.2.2 SEE-RA 2.2.3 SEE-ROSOA 2.2.4 WS-Agreement 2.2.5 WS-Agreement Negotiation 2.2.6 WSMO Lite 2.2.7 W3C Federated Social Web 2.2.8 W3C Device API 2.3 Standard 2.3.1 Delivery Context Ontology 2.3.2 OCCI 2.3.3 OVF Open Virtualisation Format 2.3.4 SoaML

[edit] Information

[edit] Categories for standards (can be extended)

• context model : for describing context in which services are sought, consumed and combined
• business process model : includes execution of workflows/processes
• service model : description, i.e. what it does (functional and non-functional)
• infrastructure management :(data, resource)(cloud, grid)
• service registration : and repository
• service discovery : and query
• service lifecycle : and monitoring
• service execution : and API, i.e. how to get it to do what it does
• service mediation : inclues orchestration and choreography
• SLA : description, negotiation and contracting
• service marketplace : covers brokerage and billing

[edit] Standardisation activity status types

• pre-standardisation (e.g. STI WG, W3C XG...)
• published (outside of a standardisation track, e.g. W3C Member Submission)
• under standardisation (e.g. W3C WG, OASIS TC...)
• standard (also W3C recommendation)

[edit] Standardisation activity description model

• Date of last change in the activity
• Status of activity
• Category
• Acronym & Name of proposed standard
• Short description of purpose (gap filled)
• Responsible person & partner
• Involved projects from this unit
• URL(s)

[edit] Standardisation activities

Collected from NEXOF report 30 June 2010, IoS Collaboration Days Standardisation CWG session October 2010.

Responsibles are invited to update these entries!

[edit] Pre-publication

[edit] unnamed

• Category: Service monitoring
• Status: Under consideration (ETSI?)
• Date of last change in the activity:
• Acronym & Name of proposed standard:
• Short description of purpose (gap filled): monitoring of Platform-as-a-Service (PaaS)
• Responsible person & partner:
• Involved projects from this unit: SRT-15
• URL(s):

[edit] BPEL extensions for compliant services

• Category: Business Process Model
• Status: idea?
• Date of last change in the activity: 22 Dec 2009
• Acronym & Name of proposed standard: BPEL extensions for compliant services
• Short description of purpose (gap filled): augmentation of business processes with compliance
• Responsible person & partner: Steve Strauch, U Stuttgart
• Involved projects from this unit: COMPAS
• URL(s): http://www.compas-ict.eu project deliverable D4.2

[edit] BPMN 2 revisions

• Category: Service mediation
• Status: Under consideration (OMG)
• Date of last change in the activity:
• Acronym & Name of proposed standard: BPMN ?
• Short description of purpose (gap filled): Revision of BPMN 2, UML Profile for BPMN Processes
• Responsible person & partner:
• Involved projects from this unit: CHOReOS
• URL(s):

[edit] Compliance Request Language

• Category: SLA
• Status: idea?
• Date of last change in the activity: 31 July 2009
• Acronym & Name of proposed standard: CRL, Compliance Request Language
• Short description of purpose (gap filled): specification of compliance requirements
• Responsible person & partner: ERISS (Tilburg University, Netherlands)
• Involved projects from this unit: COMPAS
• URL(s): http://www.compas-ict.eu project deliverable D2.2 and D2.3

[edit] Mashup Description Language

• Category: Service model
• Status: Under consideration (Open Mashup Alliance)
• Date of last change in the activity:
• Acronym & Name of proposed standard: Mashup Description Language
• Short description of purpose (gap filled):
• Responsible person & partner:
• Involved projects from this unit: OMELETTE
• URL(s):

[edit] PIM4Cloud

• Category: Service model
• Status: In process of generating a Draft RFP (OMG)
• Date of last change in the activity:
• Acronym & Name of proposed standard: PIM4Cloud (a.k.a. CloudML)
• Short description of purpose (gap filled): extension of SoaML
• Responsible person & partner:
• Involved projects from this unit: FITTEST, REMICS
• URL(s):

[edit] SOA-RM

• Category: Service Model
• Status: Planned submission (OASIS)
• Date of last change in the activity: 20 May 2009
• Acronym & Name of proposed standard: SOA-RM, Service Oriented Architecture Reference Model
• Short description of purpose (gap filled): a common description of service functionality and available evidence
• Responsible person & partner: SAP, U Stuttgart
• Involved projects from this unit: MASTER
• URL(s): http://www.master-fp7.eu project deliverable D2.2.1

[edit] UML 2 revisions

• Category: Service lifecycle
• Status: Under consideration (OMG)
• Date of last change in the activity:
• Acronym & Name of proposed standard: UML2 Testing profile
• Short description of purpose (gap filled): extension to include SOA and Clouds
• Responsible person & partner:
• Involved projects from this unit: FITTEST
• URL(s):

[edit] Widgets

• Category: Service model
• Status: W3C Working Group
• Date of last change in the activity: 7 Jun 2011
• Acronym & Name of proposed standard: Widgets
• Short description of purpose (gap filled): contributing to the W3C WG, potentially specifying new extensions
• Responsible person & partner:
• Involved projects from this unit: OMELETTE
• URL(s):

[edit] Published

[edit] Delivery Context Ontology

• Category: context model
• Status: W3C WG note
• Date of last change in the activity: 29 Jun 2010
• Acronym & Name of proposed standard: Delivery Context Ontology
• Short description of purpose (gap filled): a formal model of the characteristics of the environment in which devices interact
• Responsible person & partner: José Fonseca, Telefónica I+D
• Involved projects from this unit: MyMobileWeb
• URL(s): [1]

[edit] SEE-RA

• Category: Service Execution
• Status: Initial Draft (OASIS)
• Date of last change in the activity: 13 Jan 2009
• Acronym & Name of proposed standard: SEE-RA, Semantic Execution Environment Reference Architecture
• Short description of purpose (gap filled): description of requirements to support semantic SOAs in terms of components and interactions
• Responsible person & partner: John Domingue, OU
• Involved projects from this unit: SOA4all
• URL(s): [2]

[edit] SEE-ROSOA

• Category: Infrastructure Management
• Status: Public Draft (OASIS)
• Date of last change in the activity: 5 Nov 2008
• Acronym & Name of proposed standard: SEE-ROSOA, Reference Ontology for Semantic Service Oriented Architectures
• Short description of purpose (gap filled):
• Responsible person & partner: John Domingue, OU
• Involved projects from this unit: SOA4all
• URL(s): [3]

[edit] WS-Agreement

• Category: SLA
• Status: Proposed Recommendation (OGF)
• Date of last change in the activity: 2007 ?
• Acronym & Name of proposed standard: WS-Agreement
• Short description of purpose (gap filled): one target Service Level Agreement model
• Responsible person & partner: Philipp Wieder, TU Dortmund
• Involved projects from this unit: SLA@SOI
• URL(s): OGF recommendation: [4]

[edit] WS-Agreement Negotiation

• Category: SLA
• Status: Draft (OGF)
• Date of last change in the activity: 31-01-2011
• Acronym & Name of proposed standard: WS-Agreement Negotiation
• Short description of purpose (gap filled): define a negotiation protocol and language for SLAs
• Responsible person & partner: Oliver Waeldrich, Fraunhofer SCAI
• Involved projects from this unit: SLA@SOI, RESERVOIR
• URL(s): Submitted draft to OGF: [5]

[edit] WSMO Lite

• Category: Service model
• Status: W3C submission
• Date of last change in the activity: 23-Aug-2010
• Acronym & Name of proposed standard: WSMO-Lite, Lightweight Semantic Descriptions for Services on the Web
• Short description of purpose (gap filled): we define a lightweight set of semantic service descriptions in RDFS that can be used for annotations of various WSDL elements using the SAWSDL annotation mechanism. These annotations cover functional, behavioral, nonfunctional and information semantics of Web services, and are intended to support tasks such as (semi-)automatic discovery, negotiation, composition and invocation of services
• Responsible person & partner: Dieter Fensel, University of Innsbruck
• Involved projects from this unit: SOA4all
• URL(s): W3C submission : [6]

[edit] W3C Federated Social Web

• Category: Service model

• Status: W3C XG

• Date of last change in the activity: 14 Jun 2011

• Short description of purpose (gap filled): contributing to the vision of Federated Social Web, contribution to the definition of SWAT interoperability test cases, presented SOICIETIES goals during Federated Social Web Summit in Berlin

• Responsible person & partner: Telecom Italia

• Involved projects from this unit: SOCIETIES

• URL(s): http://www.w3.org/2005/Incubator/federatedsocialweb/

[edit] W3C Device API

• Category: Service model

• Status: W3C WG

• Date of last change in the activity: 14 Jun 2011

• Short description of purpose (gap filled): contributing to the specification of APIs to access (mobile) device capabilities in a standard way from Web applications via Javascript

• Responsible person & partner: Telecom Italia

• Involved projects from this unit: SOCIETIES

• URL(s): http://www.w3.org/2005/Incubator/federatedsocialweb/

[edit] Standard

[edit] Delivery Context Ontology

• Category: context model
• Status: W3C recommendation
• Date of last change in the activity: 5 Dec 2008
• Acronym & Name of proposed standard: Device Description Repository Simple API
• Short description of purpose (gap filled): simple API for access to device description repositories (DDR)
• Responsible person & partner: Jo Rabin, dotMobi
• Involved projects from this unit: MyMobileWeb
• URL(s): [7]

[edit] OCCI

• Category: Infrastructure Management
• Status: Recommendation (OGF)
• Date of last change in the activity: April 2011
• Acronym & Name of proposed standard: OCCI, Open Cloud Computing Interface
• Short description of purpose (gap filled): provide common API to cloud infrastructure resources
• Responsible person & partner: Andy Edmonds, Intel; Thijs Metsch, Sun
• Involved projects from this unit: SLA@SOI, RESERVOIR, CONTRAIL, mosaIC, VISIONCLOUD
• URL(s): [8]

[edit] OVF Open Virtualisation Format

• Category: Infrastructure Management
• Status: Standard (DMTF)
• Date of last change in the activity: 12 January 2010
• Acronym & Name of proposed standard: OVF, Open Virtualisation Format
• Short description of purpose (gap filled): Address current limitations of standard OVF when applied to federated cloud environments
• Responsible person & partner:
• Involved projects from this unit: RESERVOIR
• URL(s): [9]

[edit] SoaML

• Category: Service model
• Status: OMG standard
• Date of last change in the activity: Dec-2009
• Acronym & Name of proposed standard: SoaML, Service oriented architecture Modeling Language
• Short description of purpose (gap filled): SoaML describes a UML profile and metamodel for the design of services within a service-oriented architecture.
• Responsible person & partner: Arne Berre, SINTEF
• Involved projects from this unit: SHAPE
• URL(s): OMG Adopted Specification, FTF Beta 2 : [10]