[Oslc-pm] Use of pm:availabilityStatus

[Julianne Bielski]

I updated the spec with this text.


-- 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:	Tuan Dang/Raleigh/IBM at IBMUS
To:	oslc-pm at open-services.net,
Date:	02/20/2013 09:27 AM
Subject:	Re: [Oslc-pm] Use of pm:availabilityStatus
Sent by:	"Oslc-Pm" <oslc-pm-bounces at open-services.net>



Hi John,
understood.
I like the way you described it.

Can we edit the spec to add this text ?

Thanks ! T

Tuan Dang
Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common
Data Model
Internet: tdang at us.ibm.com
phone: (919) 224-1242 T/L 687-1242




From:        John Arwe/Poughkeepsie/IBM
To:        Tuan Dang/Raleigh/IBM at IBMUS,
Cc:        oslc-pm at open-services.net, "Oslc-Pm"
<oslc-pm-bounces at open-services.net>
Date:        02/19/2013 06:05 PM
Subject:        Re: [Oslc-pm] Use of pm:availabilityStatus


The resource shape governs occurrence constraints w/in PM.   It says 0:*
pm:availabilityStatus
The intent of the cited text is:


- if you have >= 1 pm:availabilityStatus predicate, then


-- all objects must be non-conflicting .... typically some are refinements
of others; the singleton case is trivially non-conflicting.


-- at least one of them must be from the PM vocab ... so clients knowing
ONLY the PM spec are "guaranteed" to find at least one value useful


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario





From:        Tuan Dang/Raleigh/IBM at IBMUS
To:        oslc-pm at open-services.net,
Date:        02/19/2013 03:46 PM
Subject:        [Oslc-pm] Use of pm:availabilityStatus
Sent by:        "Oslc-Pm" <oslc-pm-bounces at open-services.net>



Hi all,

From the spec:
OSLC Performance Monitoring service providers can identify the
availabilityStatus using references to property values in the OSLC
Performance Monitoring vocabulary or to property values that are not in the
Performance Monitoring vocabulary (i.e. in the service provider’s own
vocabulary). It is expected that the availabilityStatus values will be URI
references to property values, but inline resources defining the
availabilityStatus property values are also valid. Performance Monitoring
service providers MUST use at least one availabilityStatus (Performance
Monitoring Record) defined in the OSLC Performance Monitoring vocabulary in
addition to any availabilityStatus values not in the Performance Monitoring
vocabulary.

The additional property values for pm:availabilityStatus are:

URI        Description
http://open-services.net/ns/perfmon#NotRunning        Not running in its
host environment
http://open-services.net/ns/perfmon#Running        Running in its host
environment
http://open-services.net/ns/perfmon#Unknown        Unknown

=======

I think what we're saying here is that providers can define their own URIs
for the status and that a resource should always have at least 2
pm:availabilityStatus ,
one of which is set to #Running/#NotRunning/#Unknown.
Am I reading this correctly ?

Thanks ! T

Tuan Dang
Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common
Data Model
Internet: tdang at us.ibm.com
phone: (919) 224-1242 T/L 687-1242
_______________________________________________
Oslc-Pm mailing list
Oslc-Pm at open-services.net
http://open-services.net/mailman/listinfo/oslc-pm_open-services.net
_______________________________________________
Oslc-Pm mailing list
Oslc-Pm at open-services.net
http://open-services.net/mailman/listinfo/oslc-pm_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20130401/ed6ed8c0/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20130401/ed6ed8c0/attachment.gif>