[Oslc-recon] requirement that a provider MUST provide an oslc:serviceProvider property for its resources

[Tuan Dang]

Hi John,

So we want to report if a resource is/is not monitored.

Let's say there's a reconciled resource R .  This is a collection of 
reconcilable resources {(R1 from SP1), (R2 from SP2), etc... }. We can 
then say if there
is no Rx from Spx that services a monitoring domain in that collection 
then R is not monitored and gets added to the report.

Is that enough to require that resources have a reference to their SP ?

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 at IBMUS
To:     oslc-recon at open-services.net, 
Date:   02/21/2013 08:51 AM
Subject:        Re: [Oslc-recon] requirement that a provider MUST provide 
an oslc:serviceProvider property for its resources
Sent by:        "Oslc-Recon" <oslc-recon-bounces at open-services.net>



> The scenario ( http://open-services.net/wiki/reconciliation/
> Scenario-Coverage-Report/ ) calls for reporting on the delta between 
> monitored resources and discovered resources. 
> 
> We'd be able to determine if a reconciled resource has a 
> reconcilable resource from a monitoring SP and a reconcilable 
> resource from a discoverySP 

You're way smarter than me.  I've been on the emails leading up to this 
and I have no idea what you're saying. 
I really wish I didn't have a standing conflict Wed mornings.  Will be 
nice after March 15 when I get at least half of the hour back for Recon 
calls so real-time rather than email becomes practical. 
Best Regards, John

Voice US 845-435-9470  BluePages 
Tivoli OSLC Lead - Show me the Scenario 
_______________________________________________
Oslc-Recon mailing list
Oslc-Recon at open-services.net
http://open-services.net/mailman/listinfo/oslc-recon_open-services.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-recon_open-services.net/attachments/20130221/6d18efaa/attachment-0003.html>