[oslc-core] Fw: Call for Participation: OSLC Lifecycle Integration Core (OSLC Core) Technical Committee
Steve K Speicher
sspeiche at us.ibm.com
Mon Oct 14 10:26:11 EDT 2013
Please see forwarded call for participation in the OSLC-Core TC. Details
on joining below.
Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->
http://open-services.net
----- Forwarded by Steve Speicher on 10/14/2013 10:22 AM -----
OASIS members & interested parties,
A new OASIS technical committee is being formed. The OSLC Lifecycle
Integration Core (OSLC Core) Technical Committee has been proposed by the
members of OASIS listed in the charter below. The TC name, statement of
purpose, scope, list of deliverables, audience, IPR mode and language
specified in the proposal will constitute the TC's official charter.
Submissions of technology for consideration by the TC, and the beginning
of technical discussions, may occur no sooner than the TC's first meeting.
The eligibility requirements for becoming a participant in the TC at the
first meeting are:
(a) you must be an employee or designee of an OASIS member organization or
an individual member of OASIS, and
(b) you must join the Technical Committee, which members may do by using
the Roster "join group: link on the TC's web page at [a].
To be considered a voting member at the first meeting:
(a) you must join the Technical Committee at least 7 days prior to the
first meeting (on or before 05 November 2013); and
(b) you must attend the first meeting of the TC, at the time and date
fixed below (12 November 2013).
Participants also may join the TC at a later time. OASIS and the TC
welcomes all interested parties.
Non-OASIS members who wish to participate may contact us about joining
OASIS [b]. In addition, the public may access the information resources
maintained for each TC: a mail list archive, document repository and
public comments facility, which will be linked from the TC's public home
page at [c].
Please feel free to forward this announcement to any other appropriate
lists. OASIS is an open standards organization; we encourage your
participation.
----------
[a] https://www.oasis-open.org/apps/org/workgroup/oslc-core/
[b] See http://www.oasis-open.org/join/
[c] http://www.oasis-open.org/committees/oslc-core/
--- Charter of TC
(1)(a) Name of the TC
OASIS OSLC Lifecycle Integration Core (OSLC Core) Technical Committee
(1)(b) Statement of Purpose
With strong demand for better support of integrated system and software
processes, enterprises want products from different vendors, open source
projects and their own homegrown components to work together. This level
of integration, however, can become quite challenging and unmanageable. In
order to support integration between a heterogeneous set of products and
components from various sources, there is a need for an architecture that
is minimalist, loosely coupled, and standardized. The OSLC (Open Services
for Lifecycle Collaboration) initiative applies World Wide Web and Linked
Data principles, such as those defined in the W3C Linked Data Platform
(LDP), to create a cohesive set of specifications that can enable
products, services and other distributed network resources to interoperate
successfully.
OSLC is motivated by domain scenarios such as change management,
requirement management, and quality management, as well as by cross-domain
scenarios such as Application Lifecycle Management (ALM), Product
Lifecycle Management (PLM), and Integrated Service Management (ISM). Each
domain and cross-domain area may have its own technical committee or
working groups and/or specifications.
The OSLC Lifecycle Integration Core TC is responsible for specifications
that expand W3C LDP concepts, as needed, to enable integration. It defines
the essential technical elements of OSLC specifications and offers
guidance on common concerns for creating, updating, retrieving, and
linking to lifecycle resources based on W3C LDP [1]. The OSLC Core TC
builds on community-developed best practices and on the work of other OSLC
MS-affiliated TCs. It should develop technical specifications, create best
practices documents and formulate design principles that can be leveraged
by other OSLC MS-affiliated TCs to enable them to focus on domain-specific
concerns.
(1)(c) Scope
The OASIS OSLC Lifecycle Integration Core TC defines the essential
technical elements of OSLC specifications and offers guidance on common
concerns for creating, updating, retrieving, and linking to lifecycle
resources based on W3C LDP. The OASIS OSLC Core TC will accept as input
the OSLC MS Steering Committee approved versions of the OSLC Core 3.0
specifications from open-services.net and targeted for development at
OASIS as indicated here:
http://open-services.net/wiki/core/Specification-3.0/#Specifications
Here are the key responsibilities of the OSLC Lifecycle Integration Core
TC:
1) Expand on LDP concepts, as needed, to meet this list of integration
capabilities
a) Accessing resources
b) Resource creation
c) Resource shapes for creation
d) Resource shapes for validation
e) Filter/query long collections of resources
f) Enable web-based delegated user interface dialogs for creating and
selecting resources
g) Leverage web-based user interface components for getting a preview of
a resource
h) Protection of resources through recommendations for identification,
authentication, access control, and delegation of access
i) Consistency in error responses
j) Common definition and usage of vocabulary terms.
k) Recommended resource representations
2) Add additional technical elements as required to support current and
future scenarios from OSLC User Groups, OSLC MS-affiliated TCs,
Subcommittees and the OSLC Member Section Steering Committee
3) Support technical coordination activities:
a) Review and recommend OSLC MS-affiliated domain specifications
b) Lead development in, contribute to, review, and endorse best
practices and guidance materials for implementers, scenario writers, and
specification developers. E.g. vocabularies, test suites, templates,
reference implementations, etc.
c) Develop and prioritize cross-cutting scenarios that affect either
OSLC Core TC specifications or OSLC MS-affiliated TC domain
specifications.
(1)(d) Deliverables
The OASIS OSLC Lifecycle Integration Core TC is expected to produce within
24 months of the first meeting:
1) Scenarios: these will guide the priorities and specification contents
within the TC
a) Also a prioritized list of scenarios both developed by the OSLC
Lifecycle Integration Core TC and contributed from OSLC User Groups, OSLC
MS-affiliated TCs, Subcommittees and the OSLC MS Steering Committee.
2) Specifications: Based on the scenarios, specifications will be
developed to address cross-domain technical requirements, and set rules by
which OSLC MS-affiliated domain TC specifications can leverage, and
possibly extend the OSLC Core TC specifications. The specifications will
provide terminology and rules for defining resource vocabularies in terms
of the property names and value-types, and will recommend various resource
representations.
a) These deliverables may constitute a collection of specifications, one
per capability or a single specification covering a collection of
capabilities
b) Additional specifications may be introduced over time to satisfy
capabilities needed by supported scenarios
3) Supporting and enabling material, produced in collaboration with other
OSLC MS-affiliated TCs as appropriate or on an as-needed basis to support
broad adoption including:
a) Guidance – informative, non-normative material covering topics such
as implementation, resource design, and specification development
b) Best Practices – publication of various best (and worst) practices to
aid in the implementation of specifications and interoperable solutions.
4) Terminology: a common set of terms intended to be used across OSLC
MS-affiliated TCs
5) Vocabulary: in support of specifications, a set of machine and human
processable vocabularies, including tools and best practices
6) Test suites: provide description test suites (perhaps manual) to
illustrate how implementations of specifications should comply with the
specification. OSLC Lifecycle Integration Core TC may identify suitable a
third party automated test suite, such as an open source suite from
Eclipse Lyo.
The OASIS OSLC Lifecycle Integration Core TC plans to revise and expand
its specifications over time, to enable functionality called for by
revisions in, and expansions of, the motivational scenarios. This means
that new specifications that cover new capabilities may be introduced as
scenarios are refined on to support new capabilities. In all cases the
OSLC Lifecycle Integration Core TC will produce specifications that are
generally applicable and domain neutral.
Maintenance
Once the TC has completed work on a specific deliverable (whether
“complete” means it has become an OASIS Standard, or simply a Committee
Specification is left to the TC’s discretion), the TC will provide
maintenance for that deliverable. The purpose of maintenance is to provide
minor revisions to previously adopted deliverables to clarify ambiguities,
inconsistencies and obvious errors. Maintenance is not intended to enhance
a deliverable or to extend its functionality. In addition to maintenance,
the TC may choose to create new versions of specifications that support
additional capabilities as needed by scenarios.
(1)(e) IPR Mode
This TC will operate under the “RF (Royalty Free) on Limited Terms” IPR
mode as defined in the OASIS Intellectual Property Rights (IPR) Policy.
(1)(f) Anticipated audience of the work
The OSLC Lifecycle Integration Core TC will produce specifications that
are applicable to two types of interest groups:
1) Developers of OSLC specifications, including those produced by OSLC
MS-affiliated TCs and other standards groups
2) End users of Specifications, including implementers (software vendors,
open source projects, and developers of custom business software)
The work should be of interest to anyone involved with integration of
tools.
(1)(g) Language
The OSLC Lifecycle Integration Core TC will conduct its business in
English. The TC may elect to form subcommittees that produce localized
documentation of the TC's work in additional languages.
(2) Non-normative information
(2)(a) Identification of similar or related work
1) W3C Linked Data Platform, referenced here:
http://www.w3.org/2012/ldp/wiki/Main_Page
2) OSLC Steering Committee approved versions of the OSLC Core
specifications from open-services.net targeted for OASIS as indicated
here:
http://open-services.net/wiki/core/Specification-3.0/#Specifications
(2)(b) Date, Time and Location of the first meeting
The first meeting will be held through teleconference on 10:00 AM-12:00PM
(EST) Nov. 12, 2013 and IBM will sponsor this call.
(2)(c) Ongoing meeting schedule
The TC intends to meet by teleconference every two weeks. Sponsorship for
these meetings will be rotated through the OASIS Organizational Members
represented on the TC.
(2)(d) The names, electronic mail addresses, and membership affiliations
of co-proposers
1) Andreas Eberhart, andreas.eberhart at fluidops.com, fluid Operations OASIS
member
2) Arnaud Le Hors, lehors at us.ibm.com, IBM OASIS member
3) Axel Reichwein, axel.reichwein at koneksys.com, OASIS individual member
4) David Green, david.green at tasktop.com, Tasktop OASIS member
5) Jad El-Khoury, jad at kth.se, KTH OASIS member
6) Ludmila Ohlsson, ludmila.ohlsson at ericsson.com, Ericsson OASIS member
7) Peter Haase, peter.haase at fluidops.com, fluid Operations OASIS member
8) Prasad Yendluri, Prasad.Yendluri at softwareag.com, Software AG OASIS
member
(2)(e) Statements of Support
I, Carolina Canales <carolina.canales at ericsson.com>, as OASIS primary
representative of Ericsson organization, confirm our support for this
charter and endorse our proposers listed above as named co-proposers.
I, Dave Ings, <ings at ca.ibm.com>, as OASIS primary representative of IBM
organization, confirm our support for this charter and endorse our
proposers listed above as named co-proposers.
I, David Green <david.green at tasktop.com>, as OASIS primary representative
of Tasktop organization, confirm our support for this charter and endorse
our proposers listed above as named co-proposers.
I, Irina Schmidt, irina.schmidt at fluidops.com, as OASIS primary
representative of fluid Operations organization, confirm our support for
this charter and endorse our proposers listed above as named co-proposers.
I, Martin Törngren <martint at kth.se>, as OASIS primary representative of
KTH organization, confirm our support for this charter and endorse our
proposers listed as named co-proposers.
I, Prasad Yendluri <Prasad.Yendluri at softwareag.com>, as OASIS primary
representative of Software AG organization, confirm our support for this
charter and endorse our proposers listed above as named co-proposers.
(2)(f) TC Convener
The TC Convener for the first meeting will be Steve Speicher,
sspeiche at us.ibm.com, IBM OASIS member.
(2)(g) Affiliation to Member Section
The OASIS OSLC Lifecycle Integration Core Technical Committee intends to
be affiliated with the OASIS OSLC Member Section (MS):
http://www.oasis-oslc.org/
(2)(h) List of anticipated contributions
The OASIS OSLC Lifecycle Integration Core TC will accept as input from the
OSLC Steering Committee approved versions of the OSLC Core 3.0
specifications from open-services.net targeted for OASIS as indicated
here:
http://open-services.net/wiki/core/Specification-3.0/#Specifications
References
[1] Linked Data Platform 1.0 (Draft)
http://www.w3.org/TR/ldp/
[2] Open Services for Lifecycle Collaboration (OSLC)
http://open-services.net
[3] Open Services for Lifecycle Collaboration Core Specification Version
2.0 (Final)
http://open-services.net/bin/view/Main/OslcCoreSpecification
[4] Open Services for Lifecycle Collaboration Core Specification Version
3.0 (Draft)
http://open-services.net/wiki/core/Specification-3.0/
[5] Eclipse Lyo
http://eclipse.org/lyo
[6] OASIS IPR Policy
https://www.oasis-open.org/policies-guidelines/ipr
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
More information about the Oslc-Core
mailing list