assurance - Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19
Subject: Assurance
List archive
- From: "Cantor, Scott" <>
- To: "" <>
- Subject: Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19
- Date: Mon, 19 Sep 2011 22:21:16 +0000
- Accept-language: en-US
On 9/19/11 5:08 PM, "Ann West"
<>
wrote:
>
>To help migrate services into a common framework, we should define a null
>assurance value, so that empty requests are not the common case.
>Requiring "ordinary" as class would get folks going and at least
>asserting something. Campuses could also assert several assurance values
>upon the SP request---the order of the values matter in the process given
>the first one that matches is triggerable.
That was more of a "could" than "should". It was just a suggestion, but is
a lot of work to end up saying "I'm telling you nothing useful".
-- Scott
- [Assurance] Assurance InterOp: Notes/AIs from 9/19, Ann West, 09/19/2011
- Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Cantor, Scott, 09/19/2011
- RE: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Curry, Warren, 09/20/2011
- Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Cantor, Scott, 09/20/2011
- RE: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Curry, Warren, 09/20/2011
- Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Cantor, Scott, 09/20/2011
- RE: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Curry, Warren, 09/20/2011
- Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Jim Basney, 09/19/2011
- Re: [Assurance] Assurance InterOp: Notes/AIs from 9/19, Cantor, Scott, 09/19/2011
Archive powered by MHonArc 2.6.16.