Scott, I think these are recommendations, e.g. An OSLC domain specification SHOULD use the following standard properties instead of defining new properties that satisfy the same requirements.
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: Scott Bosworth <[email protected]> To: [email protected] Date: 04/23/2010 10:28 AM Subject: [oslc-core] OSLC Common Properties Sent by: [email protected] Hi, was helping out on the QM V2 domain specification (which is aligning with Core guidelines). I wondered what the intention is for the OSLC Common properties in Appendix A of the Core? Are these required properties for every OSLC-defined resource? Are they a catalog of oft-used properties? Why are things like dc:identifier, dc:name, dc:type, dc:subject not listed? I'm assuming that the intent is encourage some uniformity (and to avoid arbitrary differences) across OSLC-defined resources by listing and describing properties in a catalog and recommending that domain spec authors consult the catalog before defining a domain specific property. If so, should we expand the list in Appendix A or break it out into a separate Common Property catalog topic? I've started to see other examples emerge - like the Comments property/resource in the CM workgroup that could easily be generalized as a Common OSLC property. Likewise, I think the coming set of common link properties could fit in here. What is the process for deciding if something is Common? Thoughts? Scott Scott Bosworth | IBM Rational CTO Team | [email protected] | 919.486.2197(w) | 919.244.3387(m) | 919.254.5271(f) _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
