[Oslc-pm] Proposal to Finalize a Subset of the OSLC EMS 1.0 Vocabulary

[Arthur Ryman]

Julie,

Done.

Regards, 
___________________________________________________________________________ 

Arthur Ryman 

DE, Chief Architect, Reporting &
Portfolio and Strategy Management
IBM Software, Rational 

Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) 





From:   Julianne Bielski/Raleigh/IBM at IBMUS
To:     Arthur Ryman <ryman at ca.ibm.com>, 
Cc:     community at open-services.net, oslc-metrics at open-services.net, 
oslc-pm at open-services.net, "Oslc-Pm" <oslc-pm-bounces at open-services.net>
Date:   03/27/2013 03:33 PM
Subject:        Re: [Oslc-pm] Proposal to Finalize a Subset of the OSLC 
EMS 1.0 Vocabulary


Hi Arthur,

Please add ems:Metric to the subset, and then it's complete for our 
purposes.


-- Regards,

Julianne Bielski, STSM
ITM Core Chief Architect
Tivoli, IBM Software Group
tel: (919) 224-1170      (T/L) 687-1170
e-mail: bielsk at us.ibm.com

"All growth is a leap in the dark, a spontaneous unpremeditated act 
without benefit of experience." ? Henry Miller




From:   Arthur Ryman <ryman at ca.ibm.com>
To:     oslc-metrics at open-services.net, 
Cc:     community at open-services.net, oslc-pm at open-services.net
Date:   03/15/2013 01:22 PM
Subject:        [Oslc-pm] Proposal to Finalize a Subset of the OSLC EMS 
1.0     Vocabulary
Sent by:        "Oslc-Pm" <oslc-pm-bounces at open-services.net>



The OSLC Performance Monitoring 2.0 specification [1] depends on a subset 
of the OSLC EMS 1.0 vocabulary [2], which is currently in the Convergence 
phase. The use of these vocabulary terms by OSLC Performance Monitoring 
2.0 provides us with enough implementation experience to recommend that we 

finalize the used subset. The remainder of the vocabulary will remain in 
the Convergence phase until we get similar implementation experience.

Based on discussions with Steve Speicher, we've decided to maintain a 
single namespace for OSLC EMS 1.0, and to allow its terms to be at various 

phases of approval. This approach follows the way that the FOAF vocabulary 

is managed. [3] In FOAF, each term has a "Status", which is a value such 
as "testing", or "stable". FOAF uses the vocabulary vs: "
http://www.w3.org/2003/06/sw-vocab-status/ns#" and the property 
vs:term_status="testing". [4]

I'll use the standard OSLC lifecycle phases: "Scope", "Draft", "Converge", 

"Finalize", and "Final" as the values for vs:term_status. [5]

I have created a wiki page that lists the proposed subset. [6] 

I will also be adding indicators to the OSLC EMS 1.0 vocabulary document 
to clearly define the approval status of each term.  All terms except the 
requested subset will be marked as "Converge". The requested subset will 
be marked as "Finalize". 
Please reply to this list with your comments, concerns, and feedback.

[1] 
http://open-services.net/wiki/performance-monitoring/OSLC-Performance-Monitoring-Specification-Version-2.0/

[2] 
http://open-services.net/wiki/estimation-and-measurement/OSLC-Estimation-and-Measurement-Vocabulary/

[3] http://xmlns.com/foaf/spec/
[4] http://www.w3.org/2003/06/sw-vocab-status/note
[5] http://open-services.net/specifications/
[6] 
http://open-services.net/wiki/estimation-and-measurement/Finalization-of-Vocabulary-Terms-Used-by-OSLC-Performance-Monitoring-2.0/


Regards, 
___________________________________________________________________________ 


Arthur Ryman 

DE, Chief Architect, Reporting &
Portfolio and Strategy Management
IBM Software, Rational 

Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) 



_______________________________________________
Oslc-Pm mailing list
Oslc-Pm at open-services.net
http://open-services.net/mailman/listinfo/oslc-pm_open-services.net