I've added a section to the guidance document [1] to show an example and
walk through the NOT rule in more detail.

[1]
http://open-services.net/wiki/reconciliation/OSLC-Reconciliation-Guidance-for-Implementers/#Interpreting-the-NOT-operator

Thanks ! T

Tuan Dang
Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common
Data Model
Internet: [email protected]
phone: (919) 224-1242 T/L 687-1242




From:   Steve K Speicher/Raleigh/IBM
To:     Tuan Dang/Raleigh/IBM@IBMUS,
Cc:     [email protected]
Date:   03/01/2013 12:50 PM
Subject:        Re: [Oslc-recon] Comments on Recon spec


+1 on 6a

+0 on 6b.  I read the terminology and studied the section.  It was not
obvious to me.  Maybe this is primer material, maybe you add an informative
example to the section for newbie's like me.

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->
http://open-services.net

"Oslc-Recon" <[email protected]> wrote on 02/26/2013
04:44:32 PM:

> From: Tuan Dang/Raleigh/IBM@IBMUS
> To: [email protected]
> Date: 02/26/2013 04:45 PM
> Subject: Re: [Oslc-recon] Comments on Recon spec
> Sent by: "Oslc-Recon" <[email protected]>
>
> >6) #ComputerSystem / Additional Requirements
> >6a) 2nd bullet, crtv_hostid should be crtv:hostid  (replace the '_' with

> ':').  vmid missing namespace prefix too?
>
> typos fixed
>
> >6b) Are bullets 1 & 2 just telling me I need a crtv:hostid ?  what the
> positive and negative of vmid? Likewise for bullets 3&4, do I need vmid?

> Some additional >explanation/samples may help here (directly or
referenced).
>
> the use of NOT is defined in the terminlogy section [1]
> If you have a resource R1(hostid=a,vmid=11) and a resource R2
(hostid=a,vmid
> is not set), you cannot reconcile them based
> on the rule (hostid, NOT vmid) since R1 has vmid set. Furthermore, you
> cannot reconcile them based  on the rule (hostid,vmid) since
> R2 does not have vmid set.
> So, although R1 and R2 have hostid in common, they cannot be reconciled
as
> we cannot apply any of the rules listed.
>
>
>
> [1] http://open-services.net/wiki/reconciliation/OSLC-Reconciliation-
> Specification-Version-2.0/#Terminology
>
> Thanks ! T
>
> Tuan Dang
> Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common
Data Model
> Internet: [email protected]
> phone: (919) 224-1242 T/L
687-1242_______________________________________________
> Oslc-Recon mailing list
> [email protected]
> http://open-services.net/mailman/listinfo/oslc-recon_open-services.net

Reply via email to