Names and descriptions of impact analysis direction properties are misleading

XMLWordPrintable

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

      Change the terms and the descriptions:

      <http://open-services.net/ns/core#ImpactFollowsLink> a rdf:Description;
      rdfs:comment "The property represents a dependency from subject to object." ;

      <http://open-services.net/ns/core#ImpactOppositeLink>
      rdfs:comment "The property represents a dependency from object to subject." ;

      <http://open-services.net/ns/core#SymmetricImpact> a rdf:Description;
      rdfs:comment "The property represents a dependency from both subject to object and object to subject" ;

      <http://open-services.net/ns/core#NoImpact>
      rdfs:comment "The property does not represent a dependency.";

      Show
      Change the terms and the descriptions: < http://open-services.net/ns/core#ImpactFollowsLink > a rdf:Description; rdfs:comment "The property represents a dependency from subject to object." ; < http://open-services.net/ns/core#ImpactOppositeLink > rdfs:comment "The property represents a dependency from object to subject." ; < http://open-services.net/ns/core#SymmetricImpact > a rdf:Description; rdfs:comment "The property represents a dependency from both subject to object and object to subject" ; < http://open-services.net/ns/core#NoImpact > rdfs:comment "The property does not represent a dependency.";

      The OSLC Core 3.0 vocabulary includes the terms defined in the Vocabulary Annotation Vocabulary (an addendum at http://open-services.net/wiki/core/Vocabulary-Annotation-Vocabulary/) from OSLC 2.0 days - though these terms were not published as part of OSLC 2.0 Core.

      However, two of the terms proposed for impact analysis have misleading names, and very misleading descriptions in the proposed Core 3.0 vocabulary:

      <http://open-services.net/ns/core#UpstreamImpact>
      rdfs:comment "Subject resources, indicated by triples of the subject property, have an upstream impact from the object resource." ;

      Impact is always felt downstream, as per the definition of these terms as described at http://open-services.net/wiki/core/Vocabulary-Annotation-Vocabulary/. What this term is trying to describe is that the link is pointing upstream, and so impact analysis should consider impact to flow in the opposite direction of the link. For this reason, both the original name and the 3.0 description are misleading.

            Assignee:
            Nick Crossley (Inactive)
            Reporter:
            Nick Crossley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: