TRS individuals Creation, Modification and Deletion have properties and should be classes

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: None
    • Hide

      Change trs:Creation, Modification, and Deletion to rdf:Class so they can have properties rdf:type, trs:changed, and trs:order.

      Show
      Change trs:Creation, Modification, and Deletion to rdf:Class so they can have properties rdf:type, trs:changed, and trs:order.

      Individuals trs:Creation, Modification, and Deletion should be classes (subtypeOf ChangeEvent ideally) since they have properties: type, changed and order.

      The TRS vocabulary didn’t include a ChangeEvent class. The ChangeLog trs:change property had range trs:Creation, Modification and Deletion which could be enumerations, classes or subclasses of ChangeEvent. They all have type, changed (resource) and order properties.

      I added a ChangeEvent shape that constrains ldp:DirectContainer.

            Assignee:
            James Amsden (Inactive)
            Reporter:
            James Amsden (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: