[oslc-core] OSLC Primer straw-man outline

[Andrew J Berner]

+1 for Scott's comment (so I guess I amend my previous vote to +0.75 for
Arthur's?)....a scenario that is not only about lifecycle integration, but
has at least some of the relational complexity that people will actually
face (and as Arthur very smartly says, has this complexity revealed in
layers as the primer goes along) would be great.  I know that "blog" was
probably used to be neutral to any particular OSLC spec....I don't think
that's necessary.  If we use, say, testing (which nicely has the
complexity), then anyone can translate what they learn to requirements,
modeling, change management or whatever (as they could, in fairness, with
"blog", but a lifecycle example will show better why the issues were
addressed and how they were addressed without anything artificial).

Andy Berner
Lead Architect, ISV Technical Enablement and Strategy
IBM Rational Business Development
972 561-6599
ajberner at us.ibm.com

Ready for IBM Rational software partner program -
http://www.ibm.com/isv/rational/readyfor.html

oslc-core-bounces at open-services.net wrote on 12/01/2010 03:16:45 PM:

> [image removed]
>
> Re: [oslc-core] OSLC Primer straw-man outline
>
> Scott Bosworth
>
> to:
>
> oslc-core
>
> 12/01/2010 03:17 PM
>
> Sent by:
>
> oslc-core-bounces at open-services.net
>
> +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
>
>
> oslc-core-bounces at open-services.net wrote on 12/01/2010 03:18:18 PM:
>
> > From: Arthur Ryman <ryman at ca.ibm.com>
> > To: Steve K Speicher/Raleigh/IBM at IBMUS
> > Cc: oslc-core <oslc-core at open-services.net>, oslc-core-bounces at open-
> > services.net
> > Date: 12/01/2010 03:31 PM
> > Subject: Re: [oslc-core] OSLC Primer straw-man outline
> > Sent by: oslc-core-bounces at open-services.net
> >
> > 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 | bosworth at us.ibm.com | 919.
> 486.2197(w) | 919.244.3387(m) | 919.254.5271(f)
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net