|Re: Missing nesting capabilities of ServiceProviders [message #1703011 is a reply to message #1702405]
||Mon, 27 July 2015 22:23
| Jim Ruehlin
Registered: July 2009
IMO, service provider catalogs were invented to avoid enforcing a data partitioning style, not to force implementors to create a particular partitioning.|
Keep in mind that OSLC does not define what an artifact container is (other than a box that contains some kind of artifacts). A container could be a development project, a database of some kind, a collection of folders, an alphabetized list of tests, etc. An artifact container is just an abstract representation of a top-level grouping element that lifecycle tools usually need to implement so the abstractions in their applications make sense.
So artifact containers might or might not contain other types of containers - OSLC doesn't define this. However, a service provider could provide a service that returns a catalog of other containers, such as folders. So OSLC allows for this type of hierarchy, but it doesn't demand it or restrict it.
This question is more oriented towards OSLC than Lyo. You might also want to pursue it on the OASIS OSLC Core TC mailing list.
- Jim Ruehlin
Powered by FUDForum
. Page generated in 0.01645 seconds