[oslc-core] programmatic selection of creation factories

[Arthur Ryman]

Dave,

Thx for the clarification.

IMHO, I think it's simpler if you associate one type with a creation URL. 
However, since we need to allow a diversity of designs, the oslc:shape 
property is multi-valued and each Shape resource should have a description 
and an oslc:describes property that specifies the type.

You asked "How does a client select a shape?" Unless there is something 
more to your question, I'd say:

A human client can read the dc:title or dc:description property.
A programmatic client can check the oslc:describes property.



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
Twitter | Facebook | YouTube







From:
Dave <snoopdave at gmail.com>
To:
oslc-core at open-services.net
Cc:
John_Wiegand at us.ibm.com
Date:
06/01/2010 02:55 PM
Subject:
Re: [oslc-core] programmatic selection of creation factories
Sent by:
oslc-core-bounces at open-services.net



On Tue, Jun 1, 2010 at 2:14 PM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> I don't understand your statement: "Also, a Resource Shapes does not
> indicate which type it describes."
>
> The spec has a property on Resource Shape, oslc:describes, that 
identifies
> the rdf:type of the resource [1]. It seems the text has been edited, but
> the diagram shows it, and it is present in the examples [2]

Yes, you are correct and I made a mistake. I removed the
oslc:describes property without properly raising an issue on the
issues page. Somebody pointed out that shapes should not be tied to
types, which I thought was consensus, I dropped that property and then
forgot to raise/document it with an issue.

I just added it back, but I do wonder: do we really want to tie
resource types to shapes?

Back to the topic at hand...

With oslc:describes, there is a way to enable clients to
programmatically select a Creation Factory and a Query Capability.

But perhaps we are not quite there yet. Once a Creation Factory is
selected, a client would then have to select a Resource Shape. There
could be multiple Resource Shapes that describe any one OSLC defined
resource type, e.g. Task, Defect, Issue and Story shapes for a Change
Request. How does a client select a shape?

- Dave

_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net