[Oslc-steeringcommittee] 15-day Public Review for Product Life Cycle Support V1.0
Steve K Speicher
sspeiche at us.ibm.com
Fri Sep 6 16:47:09 EDT 2013
Hi Mark,
To quote a wise man (I'm not sure who made the quote) "The great thing
about standards is that there are so many to choose from". I haven't run
into this work before and its name alone caught my attention. I
definitely think it makes sense for the StC to consider, or maybe just
someone within the PLCS TC, to invite some OSLC people for a discussion
and knowledge sharing. PLCS takes an approach to define a large common
information model and then allow profiling it for certain purposes. It
also defines some data exchange spec (DEX). I have only had time to dig a
few inches into PLCS. Though the 1.4 MB OWL file has me a bit
intimidated, hopefully it isn't that bad. I hope to be able to spend a
little more time on it.
Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->
http://open-services.net
From: "Schulte, Mark D" <mark.d.schulte at boeing.com>
To: Steve K Speicher/Raleigh/IBM at IBMUS
Cc: "oslc-steeringcommittee at open-services.net"
<oslc-steeringcommittee at open-services.net>
Date: 09/05/2013 11:31 AM
Subject: RE: [Oslc-steeringcommittee] 15-day Public Review for
Product Life Cycle Support V1.0
From my standpoint, having become engaged with the StC has helped me be
more aware of related standards work (as with the TestIF interface std at
the OMG) which seem to have parallel or overlapping interest in the areas
of linking data and related work with data exchange. I am not entirely
sure yet how the StC views that but it would seem to me that when we run
into those kinds of things we should try to ascertain whether they are
doing something which conflicts or relates or parallels our own
specifications that are in work, and if so, at a minimum exchange
information with those thought leaders on the OSLC approach and
specifications being developed.
For example, having a particular interface for defining XML std data for
exchanging test information between tools as well as an OSLC Quality spec
for defining test-related linked data queries, would seem to signal a
couple of things. Vendors have to support multiple ways to exchange or
link data between tools to cover the bases. And as a user of tools in a
systems or software engineering toolchain, I don’t want to find that some
of my preferred tools support exchange of data with one std
(import/export) while other tools do not, but instead support an OSLC
interface. Essentially, multiple conflicting but related standards don’t
really help my long term integration problems.
Of course, I realize that we can’t get alignments in this area any time
soon and I know we don’t have the resources to engage and work all of the
parallel efforts that may come up, but I think engaging as much as we can
with these other organizations will help at least increase awareness and
perhaps help us understand any gaps in what we are doing.
Steve,
With respect to this one in particular, since it was within OASIS already,
I just thought maybe someone already knew something about and could
provide an overview and comment on whether it was related to our work or
really covering something totally different.
Thanks,
Mark
From: Steve K Speicher [mailto:sspeiche at us.ibm.com]
Sent: Monday, August 26, 2013 8:18 AM
To: Schulte, Mark D
Cc: oslc-steeringcommittee at open-services.net
Subject: Re: [Oslc-steeringcommittee] 15-day Public Review for Product
Life Cycle Support V1.0
Hi Mark and all,
I have been doing some learning on this but had a question on
clarification on what is expected from me:
- Are you looking for a summary or this effort?
- Perhaps stated a different way, what level of understanding do the
Steering Committee members have about this effort?
- I'd be interested to hear any thoughts on synergies, please send to me
and I can consolidate into a report.
Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->
http://open-services.net
From: "Schulte, Mark D" <mark.d.schulte at boeing.com>
To: "oslc-steeringcommittee at open-services.net" <
oslc-steeringcommittee at open-services.net>
Date: 08/14/2013 07:19 AM
Subject: [Oslc-steeringcommittee] 15-day Public Review for Product
Life Cycle Support V1.0
Sent by: "Oslc-steeringcommittee" <
oslc-steeringcommittee-bounces at open-services.net>
I was just curious as to whether others had seen this.
The OASIS Product Life Cycle Support (PLCS) TC (which I know nothing
about) sent out information on a review last week that sounded like it
would have some relationship to the same things we are doing here with
OSLC, although perhaps that is not quite the case. Is this a concern?
“to establish structured data exchange and sharing capabilities for use by
industry to support complex engineered assets throughout their total life
cycle. The OASIS Product Life Cycle Support (PLCS) standard is defined by
Data Exchange Specifications (DEX) that are based upon ISO 10303 (STEP)
Application Protocol 239 Product Life Cycle Support. This draft includes
the PLCS library, templates, derived SysML and XML models and associated
reference data.”
Is there any synergy needed between this effort and the OSLC work?
Mark D. Schulte, Associate Technical Fellow
Systems, Software, PLM & ESML Engineering
Boeing Defense Systems
The Boeing Company
mark.d.schulte at boeing.com
Office: +1 314-777-7331
----- Message from Chet Ensign <chet.ensign at oasis-open.org> on Mon, 5 Aug
2013 22:09:54 +0000 -----
To:
"tc-announce at lists.oasis-open.org" <tc-announce at lists.oasis-open.org>, "
members at lists.oasis-open.org" <members at lists.oasis-open.org>, "
plcs at lists.oasis-open.org" <plcs at lists.oasis-open.org>
Subject:
[members] 15-day Public Review for Product Life Cycle Support V1.0
The OASIS Product Life Cycle Support (PLCS) TC members [1] have produced
an updated Committee Specification Draft (CSD) and submitted this
specification for 15-day public review:
Product Life Cycle Support Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
19 July 2013
Specification Overview:
The purpose of the OASIS Product Life Cycle Support (PLCS) standard is to
establish structured data exchange and sharing capabilities for use by
industry to support complex engineered assets throughout their total life
cycle. The OASIS Product Life Cycle Support (PLCS) standard is defined by
Data Exchange Specifications (DEX) that are based upon ISO 10303 (STEP)
Application Protocol 239 Product Life Cycle Support. This draft includes
the PLCS library, templates, derived SysML and XML models and associated
reference data.
Please note that this Committee Specification Draft is a highly
interlinked collection of HTML documents. The navigation links on the top
and in the left column provide accesss to the components of the draft. The
link to Help on the navigation links includes an explanation of the
organization of the material. The Help topic "PLCSlib navigation" explains
how to use the interface.
TC Description:
The TC is currently developing templates for deployment of the ISO
10303-239 standard, together with associated SysML and XML models to
facilitate implementation. It is intended that the work be adopted by ISO.
Public Review Period:
The public review starts 6 August 2013 at 00:00 GMT and ends 21 August
2013 at 23:59 GMT. The specification was previously submitted for public
review [2].
This is an open invitation to comment. OASIS solicits feedback from
potential users, developers and others, whether OASIS members or not, for
the sake of improving the interoperability and quality of its technical
work.
Due to the complex structure of the material, the TC requests that, when
making a comment, you prefix the comment with a label identifying the
artifact against which the comment is made:
- For comments against the PLCS Platform Specific Model: EXPRESS
information model, use "(plcs-psm.exp)."
- For comments against the PLCS Platform Specific Model: SysML information
model, use "(plcs-psm.xmi)."
- For comments against the XML Schema, use "(plcs-psm.xsd)."
- For comments against the Schematron, use "(plcs-psm.sch)."
- For comments against the PLCS Platform Specific Model: OWL Reference
Data, use "(plcs-psm-en.owl)."
- For comments against the PLCS OWL Reference Data, use
"(plcs-rdl-en.owl)."
- For comments against a template, use "Template: <template name>."
The members of the TC thank reviewers in advance for helping to make the
comments traceable.
URIs:
The prose specification document and related files are available here:
HTML (Authoritative):
http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd02/plcslib-v1.0-csprd02.html
PDF (Cover pages only with links to specification):
http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd02/plcslib-v1.0-csprd02.pdf
ZIP distribution files (complete):
For your convenience, OASIS provides a complete package of the prose
specification and related files in a ZIP distribution file. You can
download the ZIP file here:
http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd02/plcslib-v1.0-csprd02.zip
Additional information about this specification and the PLCS TC may be
found on the TC's public home page located at:
http://www.oasis-open.org/committees/plcs/
Comments may be submitted to the TC by any person through the use of the
OASIS TC Comment Facility which can be accessed by following the
instructions at "Send A Comment" at the top of the TC public home page, or
directly at:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=plcs
Feedback submitted by TC non-members for this work and for other work of
this TC is publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/plcs-comment/
All comments submitted to OASIS are subject to the OASIS Feedback License,
which ensures that the feedback you provide carries the same obligations
at least as the obligations of the TC members. In connection with this
public review of "Product Life Cycle Support Version 1.0", we call your
attention to the OASIS IPR Policy [3] applicable especially [4] to the
work of this technical committee. All members of the TC should be familiar
with this document, which may create obligations regarding the disclosure
and availability of a member's patent, copyright, trademark and license
rights that read on an approved OASIS specification. OASIS invites any
persons who know of any such claims to disclose these if they may be
essential to the implementation of the above specification, so that notice
of them may be posted to the notice page for this TC's work.
========== Additional references:
[1] OASIS Product Life Cycle Support (PLCS) TC
https://www.oasis-open.org/committees/plcs
[2] Previous public reviews:
30-day public review, 27 March 2013:
https://lists.oasis-open.org/archives/tc-announce/201303/msg00007.html
Comment resolution log:
http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd01/plcs-plcslib-v1.0-csprd01-issues.xls
[3] https://www.oasis-open.org/policies-guidelines/ipr
[4] http://www.oasis-open.org/committees/plcs/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms Mode
/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
---------------------------------------------------------------------
This email list is used solely by OASIS for official consortium
communications.
Opt-out requests may be sent to member-services at oasis-open.org, however,
all members are strongly encouraged to maintain a subscription to this
list.
_______________________________________________
Oslc-steeringcommittee mailing list
Oslc-steeringcommittee at open-services.net
http://open-services.net/mailman/listinfo/oslc-steeringcommittee_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130906/1abf2007/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 4317 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130906/1abf2007/attachment.gif>
More information about the Oslc-steeringcommittee
mailing list