This is resending the following e-mail due to transmission error
(I fixed two e-mail addresses of Kamimura-san and Kishinoue-san).
Mikio
From:
Mikio Aoyama
Sent: Saturday, February 22, 2014 12:09 AM
To:
Sean Kennedy
Cc:
Carol Geyer ; Dave Ings ;
; ; -kishinoue
;
; Robin Cover ; Yabuta Kazuo ; ??????? ; Chet Ensign
Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
Hi Chet, Sean, and all:
Today, the PROMCODE consortium had a regular steering committee meeting, and
decided the name of TC as Sean suggested:
OASIS OSLC Lifecycle Integration for Project Management of
Contracted Delivery (OSLC PROMCODE)
TC
Chet, please find the revised charter attached.
If you have any concerns, please let me know.
Regards,
Mikio
From:
Sean Kennedy
Sent: Friday, February 21, 2014 4:47 AM
To:
Mikio Aoyama
Cc:
Carol Geyer ; Dave Ings ;
; ; -kishinoue
;
; Robin Cover ; Yabuta Kazuo ; ??????? ; Chet Ensign
Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
Aoyama-san:
I also prefer the second choice.
In talking to Chet on a separate thread, he reminded me that there is also an explanatory sentence that shows up in the list of TCs and on the TC webpage. Examples, see:
https://www.oasis-open.org/committees/
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oslc-core
This gives a way for us to still get Software Supply Chains in front of people wondering what the TC is about.
Best regards,
Sean Kennedy
OSLC Community Development Leader
for IBM Rational
Operations Coordinator
for the OSLC Steering Committee
Phone:
+1-905-413-4385
8200
Warden Ave
Fax:
+1-905-413-4850
Markham, Ontario L6G 1C7
Email:
D1/R0A/8200/MKM
LinkedIn:
http://www.linkedin.com/in/seanpk
Canada
OSLC:
Lifecycle
integration inspired by the web
http://open-services.net
Eclipse Lyo:
Enabling tool integration with OSLC
http://eclipse.org/lyo
There is nothing more powerful than an idea whose time has
come.
--
Victor Hugo
Chet Ensign ---2014/02/20 02:33:52 PM---Thanks Mikio. I'll watch for your update. /chet
From:
Chet Ensign <>
To:
Mikio Aoyama <>,
Cc:
Sean Kennedy/Toronto/IBM@IBMCA, Carol Geyer <>, Dave Ings/Toronto/IBM@IBMCA, , , Tsutomu Kamimura <>, , , Robin Cover <>, Yabuta Kazuo <>, ??????? <>
Date:
2014/02/20 02:33 PM
Subject:
Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
Thanks Mikio. I'll watch for your update.
/chet
On Thu, Feb 20, 2014 at 12:03 PM, Mikio Aoyama <
> wrote:
Hi Sean and
Chet:
I personally prefer:
2.
OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
(OSLC PROMCODE)
TC (97 chars)
since
PROMCODE is an abbreviation of
“ Project Management of Contracted
Delivery”.
I will come back to you
tomorrow.
Regards,
Mikio
From:
Sean Kennedy
Sent:
Friday, February
21, 2014 1:41 AM
To:
Chet
Ensign
Cc:
Carol Geyer
;
Dave Ings
;
;
;
Tsutomu
Kamimura
;
Mikio Aoyama
;
;
;
Robin
Cover
;
Yabuta Kazuo
;
???????
Subject:
Re: We have
encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes
from the PROMCODE convener call
Hi Chet,
I'm checking with the
Steering Committee about dropping the OSLC Lifecycle Integration words as
this is something that they wanted all affiliated TCs to have. (It's
surprising that the vendor couldn't simply instruct you to update the database
schema to increase that limit ... *shrug*)
For now, I've got a
pair of suggestions that keep those words by dropping others: 1. OASIS OSLC
Lifecycle Integration for Project Management of Software Supply Chains
(OSLC-PROMCODE)
TC (100 chars) 2. OASIS OSLC Lifecycle Integration for
Project Management of Contracted Delivery (OSLC-PROMCODE)
TC (97
chars)
Best regards,
Sean Kennedy
OSLC Community Development Leader
for IBM Rational
Operations Coordinator
for the OSLC Steering Committee
Phone:
+1-905-413-4385
8200
Warden Ave
Fax:
+1-905-413-4850
Markham, Ontario L6G 1C7
Email:
D1/R0A/8200/MKM
LinkedIn:
http://www.linkedin.com/in/seanpk
Canada
OSLC:
Lifecycle integration
inspired by the web
http://open-services.net
Eclipse
Lyo:
Enabling tool
integration with OSLC
http://eclipse.org/lyo
There is
nothing more powerful than an idea whose time has come.
--
Victor Hugo
Chet Ensign ---2014/02/20 11:14:52
AM---Mikio, Sean and all - We have run into a technical limitation in our
system that requires me to
From:
Chet Ensign <
>
To:
Mikio Aoyama
<
>,
Cc:
Tsutomu Kamimura
<
>, Yabuta Kazuo <
>,
, ??????? <
>, Dave Ings/Toronto/IBM@IBMCA,
,
, Sean Kennedy/Toronto/IBM@IBMCA, Carol Geyer <
>, Robin Cover <
>,
Date:
2014/02/20 11:14 AM
Subject:
We have
encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes
from the PROMCODE convener call
Mikio, Sean and all -
We have run into a technical limitation in our
system that requires me to ask for a change to the PROMCODE charter.
We just learned, in setting up the website for
the TC, that we are restricted to a 100 character limit to the name of the TC.
We have checked with the vendor of our software and we’re told that this is a
hard limit in the system and cannot be changed.
Unfortunately, we now find that the name as we
all agreed to it is 23 characters over the 100 limit and will have to be
shortened. (Specifically, OASIS OSLC Lifecycle Integration for Project
Management of Contracted Delivery for Software Supply C^^hain (OSLC PROMCODE)
TC)
The decision on the name is up to all of you
of course. We worked to see what options we could come up with and here are
two suggestions we can offer:
- OASIS OSLC Project Management of Contracted
Delivery for Software Supply Chain (PROMCODE)
TC (92
characters)
- OASIS Project Management of Contracted
Delivery for Software Supply Chain (OSLC PROMCODE)
TC (91 characters)
Please note that we need to keep “OASIS” at
the start of the name and “TC” at the end. We don’t absolutely need to have
the parenthetical abbreviation included. You can also abbreviate some of the
words if you like (e.g. ‘PM’ instead of ‘Project Management’). We didn't want
to make any assumptions on what abbreviations might or might not work for you.
Again, please accept my apologies for hitting
this problem at this late stage of the process. We have simply never hit this
limit before and it took us by surprise.
If you would let us know what name you all
decide to use, we’ll proceed with getting everything set up for the Call for
Participation.
Best regards,
/chet
On Wed, Feb 19, 2014 at 3:40 AM, Mikio
Aoyama <
> wrote:
Hi Chet and
folks: Thank you for accepting the revised charter. Attached
please find a plain text format of the charter. I hope this complies your
request. Best Regards, Mikio
From:
Chet
Ensign
Sent:
Wednesday, February 19, 2014 7:16 AM
To:
Mikio
Aoyama
Cc:
Tsutomu
Kamimura
;
Yabuta Kazuo
;
;
???????
;
Dave Ings
;
;
;
Sean
Kennedy
;
Carol Geyer
;
Robin
Cover
;
Subject:
Re:
[oasis-charter-discuss] Re: Notes from the PROMCODE convener
call
Mikio, this looks fine. Can you
do one last thing for me? Accept all your changes so that the form of the
document is final, then save it as a plain text file (not a .doc format
file) and send that to me as the final, formal submission. I will then get
that loaded to the TC web site and prepare the call for participation.
Thanks very much,
/chet
On Tue, Feb 18, 2014
at 11:49 AM, Mikio Aoyama <
> wrote:
Hi Chet and
PROMCODE team: Thank you for your follow-up minutes on the agenda
for OASIS OSLC-PROMCODE TC. Attached please find the revised “final
version” of TC charter which reflects two comments. I hope this version
meets all the requirements to PROMCODE TC. Best Regards, Mikio
From:
Chet
Ensign
Sent:
Saturday, February 15, 2014 12:00 AM
To:
Mikio
Aoyama
;
Tsutomu Kamimura
;
Yabuta
Kazuo
;
;
???????
;
Dave
Ings
;
;
;
Sean
Kennedy
;
Carol Geyer
;
Robin
Cover
Cc:
Subject:
Notes from the PROMCODE convener call
Proposers of the PROMCODE Technical
Committee,
Following the close of the call for comment
period on your proposed charter, the convener call was held yesterday, 14
February 2014, 10:00 am JST, 13 February 2014, 8:00 pm US EDT. Dr. Mikio
Aoyama, the convener, Sean Kennedy from the OSLC Member Section and Chet
Ensign from OASIS were in attendance.
We noted that two comments were received on
the draft charter: a request that a link to the existing PROMCODE
specification that will be contributed be provided in the charter and a
recommendation to change the proposed TC name to align with the pattern
being used by the other TCs affiliated with the OSLC Member Section. Dr.
Aoyama said that the proposers will make these changes. He has provided a
comment resolution log for these comments to OASIS.
We reviewed the next steps for starting the
Technical Committee and the upcoming schedule:
- Submission of the final version of the
charter: no later than Wednesday, 19 February, 2014
- OASIS issues the Call for Participation: no
later than Sunday, 23 February, 2014
- OASIS issues a reminder of the upcoming
deadline to join the TC and be eligible for voting rights at the first
meeting: Monday, 10 March, 2014
- OASIS issues the call for nominations for
chair: Monday, 10 March, 2014
- Last day to join the TC in time to have
voting rights at the first meeting: Tuesday, 18 March, 2014
- OASIS issues the list of members eligible
to vote at the first meeting: Wednesday, 19 March, 2014
- First meeting of the TC: Tuesday, 25 March
2014
We reviewed the resources that will be
available to the TC when the Call for Participation is issued: the
internal and public web pages, the email listserv, the roster, calendar
and document repository. I covered the additional capabilities that the TC
can request after the initial meeting: a wiki, JIRA project and SVN
version control repository.
We discussed steps that OASIS will take to
publicize the TC and solicit additional participants. Sean mentioned that
the Member Section has been running webcasts on OSLC work and that
PROMCODE will be included in an upcoming one on the 19th of February. We
discussed that it would be useful if the Call for Participation were
available at that time.
We then closed the meeting. Please let me
know if you have any questions about any of the above or about the
upcoming steps.
--
/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
Check
your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and
support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS
on: LinkedIn:
http://linkd.in/OASISopen
Twitter:
http://twitter.com/OASISopen
Facebook:
http://facebook.com/oasis.open
---------------------------------------------------------------------
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
--
/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
Check
your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support
is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen
Twitter:
http://twitter.com/OASISopen
Facebook:
http://facebook.com/oasis.open
---------------------------------------------------------------------
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
--
/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
Check your work using the Support Request Submission
Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support
is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen
Twitter:
http://twitter.com/OASISopen
Facebook:
http://facebook.com/oasis.open
--
/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
Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen
Twitter:
http://twitter.com/OASISopen
Facebook:
http://facebook.com/oasis.open
OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE)
TC Charter (1) (a) The name of the TC OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE)
Technical Committee (1) (b) Statement of Purpose Global software delivery is commonplace today. With ever increasing pressure, such as faster delivery, competitive cost, and skill availability, it is becoming common for software delivery to be done by collaboration of multiple organizations forming a chain of carriers and suppliers. Resembling the traditional manufacturing industry supply chain, this trend of software delivery is often called a Software Supply Chain (SSC). The SSC is a new paradigm of software delivery, where carriers and suppliers work together. Effective collaboration between an SSC acquirer and supplier requires activities to be managed and information to be shared across organizational boundaries. The management of software deliverycan be highly challenging due to the diversity of the development process, method, tools and platforms used by organizations participating in the supply chain. As a result, both the information shared and the management used are usually unique to each organization. Typically, manual operations are performed in exchanging proprietary information and in coordinating activities; resulting in inefficient, error-prone and inflexible operations. As the number of organizations involved in software delivery increases, the need for more systematic and standards-based information sharing and coordination becomes critical. PROMCODE (PROject Management of COntracted Delivery for software supply chains) is a set of specifications to exchange project management information across organizational boundaries [1]. PROMCODE leverages OSLC specifications [2, 3, 4] and defines a set of resources and links as abstraction of information used in many real projects in SSC. PROMCODE was initially developed by six leading IT companies and a university in Japan who subsequently validated PROMCODE use in each organization's project environment. The OASIS OSLC PROMCODE TC intends to build on this work to create an open standard specification of a model and information used for project management in SSC. The initiative calls for broad participation from anyone interested in the topic so that the resulting specification will be widely applicable to the global community. (1) (c) Scope The OSLC PROMCODE TC defines technical elements and guidelines for project management of Software Supply Chains. The OSLC PROMCODE TC will examine the work done by the PROMCODE consortium on exchanging project management information [1], and will modify/extend the work so that it fits the needs of the global community. The OSLC PROMCODE TC will work to: 1) Define a model of project management information for SSC. A model should describe a minimum set of information and relationships commonly used by carriers and suppliers to manage software delivery. 2) Define a set of resources and their relationships following the OSLC framework as defined by the OSLC Core TC. 3) Create additional technical elements as required to support current and future scenarios for OSLC User Groups, OSLC MS-affiliated TCs, Subcommittees and the OSLC Member Section Steering Committee. 4) Leverage existing work, such as existing OSLC specifications, as much as possible. If gaps are identified, the OSLC PROMCODE TC will attempt to resolve them with other affiliated TCs prior to defining new concepts within PROMCODE. (1) (d) Deliverables The OSLC PROMCODE TC is expected to produce within 24 months after the first meeting: 1) Scenarios: a set of scenarios illustrating user stories in the project management for SSC. 2) Specifications: Based on the scenarios, a set of specifications will be developed to address technical requirements for project management for SSC.The set of 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. 3) Supporting and enabling material 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 good practices to aid in the implementation of specifications and interoperable solutions. 4) Terminology: a common set of terms intended to be used by the OSLC PROMCODE TC. 5) Vocabulary: in support of specifications, a set of vocabularies, including tools and best practices, that can be processed either by machine or manually. The OSLC PROMCODE 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 new specifications that cover additionalcapabilities may be introduced as scenarios are refined to support new capabilities. Maintenance Once the OSLC PROMCODE 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 OSLC PROMCODE 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 PROMCODE TC will produce a set of specifications that are applicable to two types of interest groups: 1) End users of the specifications, including implementers (software suppliers, open source project teams, and developers of custom business software) 2) Developers of OSLC specifications, including those produced by OSLC MS-affiliated TCs and other standards groups The work should be of interest to anyone involved with integration of project management tools. (1) (g) Language The OSLC PROMCODE 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 A substantial amount of work has been done on the exchange of project management data and tool integration for the software supply chain. The following lists some of the highly visible initiatives. 1) The PROMCODE Interface Specification developed by the PROMCODE Consortium: http://www.promcode.org/en/specifications/PROMCODE-Interface-Specification-140217L.pdf
2) OASIS OSLC Lifecycle Integration Core (OSLC Core) https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oslc-core#resources 3) OSLC Steering Committee approved specifications from open-services.net including OSLC Change Management Specification Version 2.0: http://open-services.net/bin/view/Main/CmSpecificationV2 4) World Wide Web Consortium (W3C)
Linked Data Platform (LDP) http://www.w3.org/2012/ldp/charter 5) Eclipse Lyo, a reference implementation of OSLC http://eclipse.org/lyo
(2) (b) Date, Time and Location of the first meeting The first meeting will be held by teleconference at 8:00 p.m. on March, 25, 2014 (Eastern Daylight Time) or 9:00 a.m. on March 26, 2014 (Japanese Standard Time). Nanzan University will sponsor this call. (2) (c) Ongoing meeting schedule The OSLC PROMCODE TC intends to meet by teleconference every month (2) (d) The names, electronic mail addresses, and membership affiliations of co-proposers 1) Mikio Aoyama, , Nanzan University 2) Tsutomu Kamimura, , IBM Corp. 3) Kazuo Yabuta, , Fujitsu Limited 4) Nobuhiko Kishinoue, , NEC Corporation 5) Hiroyuki Yoshida, , Fujitsu Limited
(2) (e) Statements of Support I, Mikio Aoyama, , as OASIS primary representative for Nanzan University, confirm our support for this charter and endorse our proposers listed above as named co-proposers. I, Dave Ings, , as OASIS primary representative for IBM Corp., confirm our support for this charter and endorse our proposers listed above as named co-proposers. I, Hiroshi Yoshida, , as OASIS primary representative for Fujitsu Limited, confirm our support for this charter and endorse our proposers listed above as named co-proposers. I, Keiko Matsunaga, , as OASIS primary representative for NEC Corporation, confirm our support for this charter and endorse our proposers listed above as named co-proposers. (2) (f) TC Convener The OSLC PROMCODE TC Convener will be Dr. Mikio Aoyama (), Nanzan University. (2) (g) Member Section Affiliation The OSLC PROMCODE TC intends to request affiliation with the OSLC Member Section. (2)(h) List of Contributions of Existing Technical Work PROMCODE Interface Specification (Draft) http://www.promcode.org/en/specifications/PROMCODE-Interface-Specification-140217L.pdf
