We expect that OSLC domain specifications will specify Resource Shapes for some resources. How will we provide these shapes and can providers extend them? Consider these two question:
1) Should we make OSLC defined shapes available at open-services.net or do we expect that providers will each provide these shapes as part of their implementation? My opinion: we should do both. Make shapes available on open-services.net and recommend that allow providers to provide them as well. 2) If we allow implementations to provide the specified shapes, what are the requirements? What changes are implementations allowed to make? Can they add new "custom" properties? I have two opinions on this one: a) Implementation must provide the OSLC Defined Resource shapes verbatim with no changes and no additional properties. Resource Shape Extensibility is a new feature not in the spec and we shouldn't add new features during convergence. b) Implementations must not remove or add any properties to an OSLC defined resource shape, but may add new custom properties. To prevent conflicts, for custom properties, implementations should define entirely new properties in an entirely implementation-specific namespace. Thanks, - Dave
