Steve/David, FYI, Roy Fielding asserts that one of the defining principles of REST API is that all interactions should be driven from links present in the representation of the resource, i.e. given a resource URL it should be possible to navigate from it to the service URL just by following links. [1] He has a lot of extreme opinions, but I like this one.
In the Estimation spec, every resource instance (Project, Scenario, Estimate, Baseline,..) has a link to its containing List resource (e.g. ProjectList, ..), which in term has a link to its Service resource. The Service resource links to all the List resources. Each List resource links to all of its member instance resource. Therefore, if you get any of these resources you can navigate to any other resource within the service. [1] http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven 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: Steve K Speicher <[email protected]> To: David M Johnson <[email protected]> Cc: [email protected] Date: 02/26/2010 04:13 PM Subject: [oslc-core] Signing up to look at service discovery Sent by: [email protected] Hi Dave, I spoke up at the end of last call but not sure you heard. I am offering to author some content around service discovery and description. In addition, I'll look into what some refer to as "inverse discovery", given a resource URL, how to get the service description for that service provider. I know a few domains have expressed a need for this. Let me know if you've already got this covered. Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
