Re: [id-cloud] Member submissions of use cases and requirements

[Anil Saldhana <Anil.Saldhana@redhat.com>]

Hi all,
   few members wanted the template for the submissions.  This thread has 
the related discussion.

Regards,
Anil

On 05/26/2010 01:45 PM, Anil Saldhana wrote:
> Hi all,
>   at least one member asked about overlapping use cases with other 
> member submissions'.
>
> In my view, it is important to make your submissions without 
> evaluating the level of  duplicity/overlap with other submissions.
>
> Thoughts,comments and critic welcome.
>
> Regards,
> Anil
>
> On 05/06/2010 11:06 AM, Mary McRae wrote:
>> It seems more prudent to me to take the time to know that your 
>> proposal falls within the scope rather than taking up TC time to 
>> figure it out. The Charter is published and the Scope defines what 
>> can and cannot be done by the TC. Potential members review that 
>> Charter and Scope to determine whether they are willing to 
>> participate or not and evaluate what claims they might have around 
>> that scope. Encouraging people to disregard the scope - no matter to 
>> what degree - is a slippery slope and will likely result in 
>> protracted debates and end up delaying, rather than speeding up, 
>> progress. Not to mention a violation of the spirit of the TC Process.
>>
>> Regards,
>>
>> Mary
>>
>>
>>
>> On May 6, 2010, at 11:20 AM, Anil Saldhana wrote:
>>
>>> Hi Mary,
>>>
>>> Ok and Ok.
>>>
>>> The submissions are just raw materials for now. I am sure that the 
>>> members will vet their submission for IPR/confidential aspects.  But 
>>> I would prefer (request) the members to make the submission rather 
>>> than ponder over parts of their submission fall within scope or not. 
>>> That will save us time in discussions and merging exercise.
>>>
>>> Regards,
>>> Anil
>>>
>>> On 05/06/2010 10:07 AM, Mary McRae wrote:
>>>> Hi Anil,
>>>>
>>>> Just a couple of comments on your proposed submission guidelines:
>>>>
>>>> 2.  At OASIS, each member of a TC acts as an individual. You can't 
>>>> restrict individuals from the same company to act as a group.
>>>>
>>>> 4. I think many companies will want to ensure that any submissions 
>>>> made fall within the scope of the TC for IPR reasons prior to 
>>>> making those submissions. Certainly if someone is unclear, they can 
>>>> ask the question to see whether the other members feel it would be 
>>>> in scope or not.
>>>>
>>>> Regards,
>>>>
>>>> Mary
>>>>
>>>>
>>>> Mary P McRae
>>>> Director, Standards Development
>>>> Technical Committee Administrator
>>>> OASIS: Advancing open standards for the information society
>>>> email: mary.mcrae@oasis-open.org
>>>> web: www.oasis-open.org
>>>> twitter: @fiberartisan  #oasisopen
>>>> phone: 1.603.232.9090
>>>>
>>>> Standards are like parachutes: they work best when they're open.
>>>>
>>>>
>>>>
>>>> On May 5, 2010, at 11:11 PM, Anil Saldhana wrote:
>>>>
>>>>
>>>>> Hi all,
>>>>>     it is time to get started with the TC business as we get close 
>>>>> to the second meeting.  The first step is to solicit and collect 
>>>>> member submissions on use cases and requirements.
>>>>>
>>>>> Submission Guidelines:
>>>>> ---------------------------------
>>>>> 1) Please create separate email threads for each submission (do 
>>>>> not reply to someone else's submission with your own submission). 
>>>>> This is because the archives will be cleaner.  You can comment on 
>>>>> someone's submission by replying to that thread. You can also 
>>>>> refine your own submission by replying to your own thread.
>>>>> 2) One submission from a company/member. Please coordinate among 
>>>>> your colleagues from the same company.  Individual members are 
>>>>> free to submit their own submissions.
>>>>> 3) Please clean your submissions off proprietary or confidential 
>>>>> information. This is public work.
>>>>> 4) Please do not evaluate whether your content matches the TC 
>>>>> charter or not. It is important for you to submit the information. 
>>>>> The TC will evaluate your submission and decide if any of the 
>>>>> content is out of scope.
>>>>> 5) Level of detail is dependent on your comfort level. If 
>>>>> additional information is needed, the TC will request it from you 
>>>>> in the future.
>>>>>
>>>>> Submission Objectives:
>>>>> ---------------------------------
>>>>> * The TC is looking at use cases and requirements to start the work.
>>>>> * The TC will discuss the submissions and then the spec editors 
>>>>> will collate the submissions (based on TC feedback).
>>>>>
>>>>>
>>>>> Submission Format:
>>>>> ---------------------------
>>>>> This is open for discussion. Please suggest alternative formats.
>>>>>
>>>>> Potential format is the following:
>>>>> Name of the member (s):
>>>>> Affiliation:
>>>>> Use Cases:
>>>>> Requirements:
>>>>> Best Practices:
>>>>> Other Information:
>>>>>
>>>>>
>>>>> Note:  The TC will not only benefit from your submissions of use 
>>>>> cases and requirements for Identity In The Cloud, but also it will 
>>>>> be useful to hear your pain points/grievances in the field (good 
>>>>> for Other Information).
>>>>>
>>>>>
>>>>> Regards,
>>>>> Anil&   Tony