+1 on all points, though I'd rather see us utilize scenarios that are not contrived (e.g. blog) but that are more relevant to lifecycle integration...Scott
[email protected] wrote on 12/01/2010 03:18:18 PM: > From: Arthur Ryman <[email protected]> > To: Steve K Speicher/Raleigh/IBM@IBMUS > Cc: oslc-core <[email protected]>, oslc-core-bounces@open- > services.net > Date: 12/01/2010 03:31 PM > Subject: Re: [oslc-core] OSLC Primer straw-man outline > Sent by: [email protected] > > IMHO, the primary purpose of a Primer should be to teach people how to use > the specifications, without having to read the specifications in detail. > This means that the Primer should be very pragmatic and have lots of > realistic examples. Ideally, the Primer should progressively reveal more > detail, starting with a simple example and building on it, showing how > each feature of the specification is motivated by some real-world > requirement. > Ideally, the Primer should use a consistent, unifying, realistic scenario > as the basis for the examples - no foo's or bar's. The Core spec currently > uses a Blog scenario. That could be elaborated. > The Primer I most frequently use is the XML Schema Primer. Notice the > absence of generalities and the abundance of concrete examples. > Lengthy general information should not be in the Primer. It should be in > other documents, e.g. Guides or Overviews. > > Regards, > ___________________________________________________________________________ > > Arthur Ryman, PhD, DE > > Chief Architect, Project and Portfolio Management > IBM Software, Rational > Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063 > Scott Bosworth | IBM Rational CTO Team | [email protected] | 919.486.2197 (w) | 919.244.3387(m) | 919.254.5271(f)
