W3C home > Mailing lists > Public > public-poe-archives@w3.org > January 2017

[poe] Should hasRightOperandReference survive?

From: Víctor Rodríguez-Doncel via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Jan 2017 22:27:43 +0000
To: public-poe-archives@w3.org
Message-ID: <issues.opened-202258369-1484951262-sysbot+gh@w3.org>
vroddon has just created a new issue for https://github.com/w3c/poe:

== Should hasRightOperandReference survive? ==
I believe there was a redundant property. Since :hasRightOperand can 
have as range a :RightOperandReference, In such a case, I don't see 
the point of maintaining a property like :hasRightOperandReference.  I
 have commented the redundant property, to be deleted if I dont hear 
the contrary.

```
:hasRightOperand
        a rdf:Property ;
        rdfs:isDefinedBy odrl: ;
        rdfs:label "Has Right Operand"@en ;
        skos:definition "The operand applied to an instance of a 
constraint."@en ;
        rdfs:range [
                a owl:Class ;
                owl:unionOf ( :RightOperandReference xsd:any ) ;
        ] ;
        rdfs:domain :Constraint .

#:rightOperandReference
#       a rdf:Property ;
#       rdfs:isDefinedBy odrl: ;
#       rdfs:label "Has Right Operand Reference"@en ;
#       skos:definition "A reference to the operand applied to an 
instance of a constraint."@en ;
#       skos:note "Represents a URI that must be dereferenced to 
obtain the actual right operand value"@en ;
#       rdfs:domain :Constraint ;
#   skos:scopeNote "Non-Normative"@en .
```


Please view or discuss this issue at 
https://github.com/w3c/poe/issues/92 using your GitHub account
Received on Friday, 20 January 2017 22:27:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:46:59 UTC