[oslc-ArchMgmt] Current OSLC AM Topics

[Ian Green1]

Hi Jim,
I like the idea of a predefined query.   Couple of comments:

        - is what you propose adequate to replace the CALM filters defined 
on jazz.net? (does it need to be?)
        - how about delegated UI that allow new predefined queries to be 
created?

The suggested design makes a clear separation between predefined queries 
and "simple" query, and does not treat oslc:QueryParameters as OSLC 
Defined Resources.  Might there be a benefit to bringing these together? 

For example, the resource that is POSTed to execute a query could be 
described by an OSLC Resource Shape rather than the way the 
oslc:PredefinedQuery element describes the parameters with 
oslc:predefinedQueryParameter.  A delegated UI could be used to make new 
predefined query resources - the required and optional parameters of such 
a newly created predefined query resource would be discoverable using OSLC 
Shape Resources. 

Whilst the OSLC query capability admits POST (for url-encoded simple 
syntax and for other non-OSLC query languages) there is nothing in 
oslc:QueryCapability to describe the kinds of things that can be POSTed 
(unlike creation factories).  Addressing this might provide a uniform way 
of treating predefined queries and simple queries, with OSLC shapes being 
used to describe the parameters of those predefined queries.

-ian

ian.green at uk.ibm.com (Ian Green1/UK/IBM at IBMGB)
Chief Software Architect, Requirements Definition and Management
IBM Rational



From:   Daniel Berg/Raleigh/IBM at IBMUS
To:     James Conallen/Philadelphia/IBM at IBMUS
Cc:     Ahmed Oraby/Ottawa/IBM at IBMCA, Alan Yeung/Ottawa/IBM at IBMCA, Alanna 
Zito/Ottawa/IBM at IBMCA, Andrew J Berner/Dallas/IBM at IBMUS, 
Brenda.Ellis at ngc.com, Clyde D Icuspit/Cambridge/IBM at IBMUS, Daniel 
Berg/Raleigh/IBM at IBMUS, Daniel Leroux/Ottawa/IBM at IBMCA, David M 
Johnson/Raleigh/IBM at IBMUS, derry.t.davis at accenture.com, Eldad 
Palachi/Haifa/IBM at IBMIL, Ian Green1/UK/IBM at IBMGB, Jim 
Amsden/Raleigh/IBM at IBMUS, Jin Li/Toronto/IBM at IBMCA, John 
Crouchley/UK/IBM at IBMGB, jonathan.harclerode at accenture.com, Lars 
Jenzer/Switzerland/IBM at IBMCH, Mahmoud Oraby/Ottawa/IBM at IBMCA, Martin 
Owen/UK/IBM at IBMGB, Nir Mashkif/Haifa/IBM at IBMIL, Peter Yee/New 
York/IBM at IBMUS, rmaksimchuk at projectpragmatics.com, Sandeep 
Kohli/India/IBM at IBMIN, Scott Bosworth/Raleigh/IBM at IBMUS, Scott 
Cowan/Ottawa/IBM at IBMCA, srinivasan.renganathan at citi.com, Steve K 
Speicher/Raleigh/IBM at IBMUS, Thomas Piccoli/New York/IBM at IBMUS, Vishwanath 
Ramaswamy/Ottawa/IBM at IBMCA, oslc-am at open-services.net
Date:   20/01/2011 14:31
Subject:        Current OSLC AM Topics


Hi Jim,

Thanks for taking the time for writing up the proposals. Here is my 
initial feedback. 

(Sorry for duplicate mailings for those on the oslc-am mailing list.)

Common Architecture Resource Types
        •       I agree with the need to register and discover available 
resource types from a service provider. 
        •       If we wanted to link the type to a Business Glosary term 
would we use an External Reference URI? I know this is a specific IBM 
usage but I would like to see that it is supported by the interface API.
        •       Do we went to restrict the "Generalizes" relationship to 
the UML domain? I would think that Generalizes could be used outside of 
the UML domain.
        •       Another common relationship type "Source" or "Derived" to 
link to another resource which the described resource is derived.
        ⁃      We use "Realized" a bit but if we have Source or Derived 
this could serve the purpose as well.


Composite Contexts
I understand the need for a composite context but I wonder if we could 
simplify the solution. For example can we drop the Composite Context 
Manager? I'm thinking that a Service Provider can provide a context (or 
many). What if any context could reference the context from other service 
providers? That would mean a context could be a composite as well. I would 
also expect that a Service Provider could query other providers to 
determine which contexts a given contextUri was referenced.
Thoughts?

Predefined Queries
I like the concept. Shouldn't the PredefinedQueryParameter support a 
default value?
In the example where the client POSTs a predefined query I do not see the 
query uri. I only see parameter values. Am I missing something?

Link Type Hints
I like the proposal because it is likely that the number of LinkTypes can 
and will grow over time. If we do not provide a mechanism to 
filter/prioritize link types we will run into a usability problem. With 
the hints clients can do a number of interesting things such as filter the 
number of links based on the source selection as well as target. The 
client may choose to present messages to the user for suspect links based 
on the type used for the source or target as part of an analysis report. 
There are many other applications for the hints as well. Of course users 
may always use a link with source or target types that are outside of the 
hints.

Regards,
Daniel Berg 
STSM | Master Inventor, IBM Rational Software
Collaborative Architecture Management | Deployment Planning & Automation
1-919-486-0047 | T/L 526-0047 | Cell: 1-919-637-8570
Rational Software Architecture community
"Everything should be made as simple as possible, but not simpler."  - 
Albert Einstein 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-am_open-services.net/attachments/20110202/65dac461/attachment-0003.html>