Dave, Nice summary. Very useful. I suggest you sort it be compliance level, i.e. group all the MUSTs, then the SHOULDs, then the MAYs. Then people can see the mimimum amout of work required.
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 <[email protected]> To: oslc-core <[email protected]> Date: 06/02/2010 04:06 PM Subject: [oslc-core] Core spec feature requirements matrix Sent by: [email protected] One suggestion for making it easier to understand the OSLC Core spec, what it requires and how OSLC domain specs extend it by adding or tightening requirements is to provide a matrix with features on one axis and requirement level(?) on the other. Here's my first attempt at such a matrix: https://spreadsheets.google.com/pub?key=0AmuMBlP1tnN6dEZfRkR4OHJUTnpUMklDRWYzc0JfekE&hl=en&output=html I'm not sure yet how a domain spec would use this to indicate how the Core spec applied, or what the columns should be. Feedback is welcome... Thanks, - Dave _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
