Uploaded image for project: 'OASIS OSLC Lifecycle Integration Core (OSLC Core) TC'
  1. OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
  2. OSLCCORE-48

Allow ResourceShapes to extend other ResourceShapes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      One possible solution to this requirement is to recognize that property constraints can be reused in different ResourceShapes. So the only thing that needs to be copied down to create a ResourceShape for a subclass is the list of properties for that ResourceShape. The property constraints don't need to be redefined with a different namespace unless they are actually overridden in the subclass.

      Another possibility is to extend ResoureShape with a new oslc:extendsShape property that supports constraint chaining or inherited constraints (depending on whether this is viewed as class or object inheritance).

      Show
      One possible solution to this requirement is to recognize that property constraints can be reused in different ResourceShapes. So the only thing that needs to be copied down to create a ResourceShape for a subclass is the list of properties for that ResourceShape. The property constraints don't need to be redefined with a different namespace unless they are actually overridden in the subclass. Another possibility is to extend ResoureShape with a new oslc:extendsShape property that supports constraint chaining or inherited constraints (depending on whether this is viewed as class or object inheritance).

      Description

      Many of the existing OSLC domain vocabularies are fairly simple, defining a relatively small number of RDFS classes, and rarely (if ever) use subClassOf. As a result an instance of a domain class can have an oslc:instanceShape that references a simple ResourceShape.

      However, some vocabularies, such as those derived from UML, SysML, PLE, etc. may have much richer vocabularies that have deep inheritance hierarchies. Although it is possible to create A ResourceShape for each subclass, this would result in a very large number of repeated properties as the properties inherited from superclasses would need to be copied down into the ResourceShape for each subclass in order to fully specify the resource shape.

      I is therefore desirable to have some means of "inheriting" constraints from some other ResourceShape(s), or extend a ResourceShape with constraints defined in some other shape - a chain of constraints like prototypes in JavaScript.

        Attachments

          Activity

            People

            • Assignee:
              jamsden James Amsden
              Reporter:
              jamsden James Amsden
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: