Additional domains

Jul 29, 2013 at 6:09 AM
Hi all,

As of right now OSLC4Net only comes with resource definitions for Change Management.
I'd be happy to do the grunt work of adding definitions from the other domains (to the same level), but first I'd like to know:
  1. Is it a goal of the project to provide these? Or is the Change Management stuff intended only for demo purposes?
  2. If the former, would it not make sense to move those properties that are listed in the specs as Core Common to an abstract class in Core.Model and have ChangeRequest, Requirement and the rest inherit from that?
Cheers,

/Uffe
Jul 30, 2013 at 5:31 AM
Actually, scratch number 2. It wouldn't make sense because the common properties are not common to all resources (or even to the "main" resources in the different specifications). Commonality between the resources is by choice, not by requirement, so an abstract base class is not viable.
Furthermore, the core specification appendix A, which lists the common properties, intentinally omits the occurs attribute, which means it wouldn't be possible to determine the nullability of the base class members.