<<O>> Difference Topic ChangeProposalUseCases (r1.9 - 25 Sep 2009 - LucMoreau)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 60 to 60

-- LucMoreau - 24 Jun 2009

Added:

>
>

Outcome

Unanimity we want use cases: Yes: 7/No: 0.

In all likelihood, the use cases need to be collected in a separate document. Most importantly, we need to contribute use cases!

<<O>> Difference Topic ChangeProposalUseCases (r1.8 - 23 Sep 2009 - PaoloMissier)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 56 to 56

Jan Van den Bussche, yes, this is essential

Added:

>
>

PaoloMissier, yes -- but as others said, this is best placed in a primer document, a companion to the core

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.7 - 23 Sep 2009 - JanVanDenBussche)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 54 to 54

NataliaKwasnikowska, yes

Added:

>
>

Jan Van den Bussche, yes, this is essential

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.6 - 23 Sep 2009 - NataliaKwasnikowska)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 52 to 52

Luc Moreau, yes, many specifications refer to a (possibly separate) set of use cases. It would be very useful to have it to justify our design decisions. This would make opm v1.1 more compelling to a broader community.

Added:

>
>

NataliaKwasnikowska, yes

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.5 - 22 Sep 2009 - LucMoreau)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 50 to 50

Paul Groth, yes, but I agree with Simon that these should be in a primer document.

Added:

>
>

Luc Moreau, yes, many specifications refer to a (possibly separate) set of use cases. It would be very useful to have it to justify our design decisions. This would make opm v1.1 more compelling to a broader community.

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.4 - 22 Sep 2009 - PaulGroth)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 48 to 48

Joe Futrelle, yes

Added:

>
>

Paul Groth, yes, but I agree with Simon that these should be in a primer document.

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.3 - 22 Sep 2009 - JoeFutrelle)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 47 to 46

Simon Miles - yes, it is important for people to understand why OPM is useful and guide them in using it, though I don't know whether it is most helpful to include in the core spec or a separate primer document

Added:

>
>

Joe Futrelle, yes

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.2 - 22 Sep 2009 - SimonMiles)

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Line: 45 to 45

Vote

Changed:

<
<

>
>

Simon Miles - yes, it is important for people to understand why OPM is useful and guide them in using it, though I don't know whether it is most helpful to include in the core spec or a separate primer document

-- LucMoreau - 24 Jun 2009

<<O>> Difference Topic ChangeProposalUseCases (r1.1 - 24 Jun 2009 - LucMoreau)

Line: 1 to 1

Added:

>
>

META TOPICPARENT	WorkInProgressV1pt1

OPM Use cases

Luc Moreau, June 24.

Subject

All specs, but specifically OPM v1.01

Background

To understand motivations of OPM, a series of Use cases would be useful.

Problem addressed

Currently, use cases have not been made explicit.

Proposed solution

Add a section on use cases.

Rationale for the solution

It's common practice in standardization activities to enumerate the use cases intended to be supported by a spec.

Comments

Community is invited to provide comments on proposals and submit possible use cases.

comment 1

include authors

Vote

-- LucMoreau - 24 Jun 2009