Permissions and Obligations Expression Working Group - Activity in 2017
No matches.
GitHub
w3c/poe
-
2 issues opened.
-
Dc:license vocabulary hijacking? w3c/poe#286, by @iherman.
-
Informative references to schema, vcard, & foaf w3c/poe#285, by @iherman.
-
-
3 issues closed.
-
Split LeftOperands into constraints and refinements w3c/poe#282.
-
ODRL Validation/Validation issues w3c/poe#261.
-
-
7 issues received 33 new comments.
-
Dc:license vocabulary hijacking? w3c/poe#286 (19 comments by @benedictws, @iherman, @nitmws, @riannella, @simonstey, @vroddon)
-
Add reference to original ODRL requirements w3c/poe#65 (3 comments by @riannella, @simonstey, @vroddon)
-
Review definitions of LeftOperands in the Common Vocab w3c/poe#284 (3 comments by @nitmws, @riannella)
-
GitHub
w3c/poe
-
4 issues opened.
-
Review definitions of LeftOperands in the Common Vocab w3c/poe#284, by @nitmws.
-
Add version number to the titles of the specs w3c/poe#283, by @riannella.
-
Split LeftOperands into constraints and refinements w3c/poe#282, by @riannella.
-
Update Example 14 w3c/poe#281, by @riannella.
-
-
2 issues closed.
-
Add version number to the titles of the specs w3c/poe#283.
-
Update Example 14 w3c/poe#281.
-
-
4 issues received 19 new comments.
-
Review definitions of LeftOperands in the Common Vocab w3c/poe#284 (5 comments by @nitmws, @riannella)
GitHub
w3c/poe
-
4 issues opened.
-
On requiring mutually disjoint sets of policy/rule types w3c/poe#280, by @simonstey.
-
JSON-LD serialization of rightOperand values w3c/poe#279, by @simonstey.
-
IM: Constraint and Logical Constraint do not have a uid property w3c/poe#278, by @nitmws.
-
Error in the ODRL JSON-LD context resource w3c/poe#277, by @nitmws.
-
-
14 issues closed.
-
fix for examples in 3.3 ODRL Profile Mechanism w3c/poe#271.
-
Conflict - invalid case w3c/poe#270.
-
Harmonize 2.6.7 Remedy property with Prohibition w3c/poe#274.
-
the assignee(s) of the Duty MUST satisfy the Duty. w3c/poe#269.
-
fixing selected examples w3c/poe#268.
-
XML Schema issues w3c/poe#276.
-
JSON-LD serialization of rightOperand values w3c/poe#279.
-
inconsistent requirements wrt. profile definitions w3c/poe#272.
-
Unsatisfiable consequence example w3c/poe#275.
-
Error in the ODRL JSON-LD context resource w3c/poe#277.
-
-
14 issues received 79 new comments.
-
IM: Constraint and Logical Constraint do not have a uid property w3c/poe#278 (20 comments by @iherman, @nitmws, @riannella, @simonstey)
-
Harmonise how a Duty with consequences should be evaluated w3c/poe#267 (15 comments by @iherman, @nitmws, @riannella, @simonstey)
-
JSON-LD serialization of rightOperand values w3c/poe#279 (6 comments by @iherman, @riannella, @simonstey, @vroddon)
-
the assignee(s) of the Duty MUST satisfy the Duty. w3c/poe#269 (5 comments by @riannella, @simonstey, @vroddon)
-
On requiring mutually disjoint sets of policy/rule types w3c/poe#280 (4 comments by @riannella, @vroddon)
-
Common Vocabulary Concepts/Terms used/referenced in Core Vocabulary Section w3c/poe#273 (4 comments by @nitmws, @riannella)
-
TR publications
-
2 documents published.
-
ODRL Information Model published as a Candidate Recommendation Snapshot. History of ODRL Information Model
-
ODRL Vocabulary & Expression published as a Candidate Recommendation Snapshot. History of ODRL Vocabulary & Expression
-
GitHub
w3c/poe
-
43 issues opened.
-
XML Schema issues w3c/poe#276, by @nitmws.
-
Unsatisfiable consequence example w3c/poe#275, by @simonstey.
-
Harmonize 2.6.7 Remedy property with Prohibition w3c/poe#274, by @nitmws.
-
inconsistent requirements wrt. profile definitions w3c/poe#272, by @simonstey.
-
fix for examples in 3.3 ODRL Profile Mechanism w3c/poe#271, by @simonstey.
-
Conflict - invalid case w3c/poe#270, by @riannella.
-
the assignee(s) of the Duty MUST satisfy the Duty. w3c/poe#269, by @simonstey.
-
fixing selected examples w3c/poe#268, by @simonstey.
-
Harmonise how a Duty with consequences should be evaluated w3c/poe#267, by @nitmws.
-
obligation is missing in odrl.jsonld w3c/poe#265, by @nitmws.
-
CR IM: JSON of examples 20, 16, 17, 25 wrong w3c/poe#264, by @nitmws.
-
Problem in JSON-LD? w3c/poe#263, by @vroddon.
-
ODRL Validation/Validation issues w3c/poe#261, by @nitmws.
-
ODRL Validation questions w3c/poe#259, by @vroddon.
-
source of a *Collection (and also Asset/Party?) w3c/poe#258, by @nitmws.
-
IM diagrams issues w3c/poe#257, by @nitmws.
-
Wording and RDF semantics: Collection - List - Sequence ... w3c/poe#256, by @nitmws.
-
Cardinality of odrl:rightOperand w3c/poe#255, by @simonstey.
-
Review of Evaluator Truth Tables (of 5 September) w3c/poe#254, by @nitmws.
-
How much infererence for validation? w3c/poe#253, by @vroddon.
-
Mild contradictions in IM wrt validation w3c/poe#252, by @vroddon.
-
Profiles and @context in JSON-LD - 5.2 in Vocab needs update w3c/poe#251, by @nitmws.
-
Wording in Logical Constraints w3c/poe#250, by @vroddon.
-
Diagram missing arrows w3c/poe#249, by @vroddon.
-
Validation: profiles and new terms w3c/poe#248, by @vroddon.
-
Validation: OWL consistency w3c/poe#247, by @vroddon.
-
Small ammendment: Offer is normative w3c/poe#246, by @vroddon.
-
What exactly is stated by Non-/Active? w3c/poe#245, by @nitmws.
-
CR Exit Criteria w3c/poe#244, by @riannella.
-
ODRL Validator w3c/poe#242, by @vroddon.
-
use of @value for action constraints w3c/poe#241, by @simonstey.
-
Not-/Active Rules, evaluation, Policy inheritance and conflicts w3c/poe#240, by @nitmws.
-
Assigner/Assignee at the policy level w3c/poe#239, by @vroddon.
-
Confusing wording w3c/poe#238, by @vroddon.
-
Validator/validation/valid-related terminology w3c/poe#237, by @nitmws.
-
One redundancy in the spec w3c/poe#235, by @vroddon.
-
rightOperand property: IM and Vocab not in sync w3c/poe#231, by @nitmws.
-
Missing type of a Constraint's unit property w3c/poe#230, by @nitmws.
-
Misleading statements about failure properties w3c/poe#229, by @simonstey.
-
Fixed constraint at policy level w3c/poe#228, by @riannella.
-
-
44 issues closed.
-
Validator/validation/valid-related terminology w3c/poe#237.
-
obligation is missing in odrl.jsonld w3c/poe#265.
-
CR IM: JSON of examples 20, 16, 17, 25 wrong w3c/poe#264.
-
Problem in JSON-LD? w3c/poe#263.
-
ODRL Validation questions w3c/poe#259.
-
IM diagrams issues w3c/poe#257.
-
On 2.6.8 Rule Active State Processing w3c/poe#226.
-
source of a *Collection (and also Asset/Party?) w3c/poe#258.
-
Cardinality of odrl:rightOperand w3c/poe#255.
-
ODRL Validator w3c/poe#242.
-
How much infererence for validation? w3c/poe#253.
-
What exactly is stated by Non-/Active? w3c/poe#245.
-
Review of Evaluator Truth Tables (of 5 September) w3c/poe#254.
-
Mild contradictions in IM wrt validation w3c/poe#252.
-
CR Exit Criteria w3c/poe#244.
-
Validation: OWL consistency w3c/poe#247.
-
Validation: profiles and new terms w3c/poe#248.
-
Diagram missing arrows w3c/poe#249.
-
Wording in Logical Constraints w3c/poe#250.
-
One redundancy in the spec w3c/poe#235.
-
Assigner/Assignee at the policy level w3c/poe#239.
-
Fixed constraint at policy level w3c/poe#228.
-
Misleading statements about failure properties w3c/poe#229.
-
Missing type of a Constraint's unit property w3c/poe#230.
-
rightOperand property: IM and Vocab not in sync w3c/poe#231.
-
Reviews of ODRL IM - Editor's Draft 3 August 2017 w3c/poe#215.
-
How Rules become Active w3c/poe#221.
-
The foggy effective/in-effect terminology w3c/poe#225.
-
use of @value for action constraints w3c/poe#241.
-
Small ammendment: Offer is normative w3c/poe#246.
-
Confusing wording w3c/poe#238.
-
ambiguous semantics of duty constraints w3c/poe#211.
-
Logic w3c/poe#236.
-
Definition of ODRL w3c/poe#219.
-
wording of cardinality restrictions w3c/poe#218.
-
Duty->Consequence w3c/poe#209.
-
ODRL Evaluator review - IM of 11 August 2017 w3c/poe#217.
-
-
3 issues reopened.
-
Validator/validation/valid-related terminology w3c/poe#237, by @simonstey.
-
Cardinality of odrl:rightOperand w3c/poe#255, by @nitmws.
-
ambiguous semantics of duty constraints w3c/poe#211, by @vroddon.
-
-
40 issues received 181 new comments.
-
Wording and RDF semantics: Collection - List - Sequence ... w3c/poe#256 (17 comments by @iherman, @nitmws, @riannella, @simonstey, @vroddon)
-
use of @value for action constraints w3c/poe#241 (14 comments by @iherman, @nitmws, @riannella, @simonstey, @vroddon)
-
Validator/validation/valid-related terminology w3c/poe#237 (8 comments by @nitmws, @riannella, @simonstey)
-
Harmonise how a Duty with consequences should be evaluated w3c/poe#267 (6 comments by @nitmws, @riannella, @simonstey)
-
ODRL Validation/Validation issues w3c/poe#261 (6 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
source of a *Collection (and also Asset/Party?) w3c/poe#258 (4 comments by @iherman, @nitmws, @riannella)
-
adding disclaimer to http://www.w3.org/TR/odrl w3c/poe#224 (4 comments by @iherman, @philarcher, @riannella)
-
rightOperand property: IM and Vocab not in sync w3c/poe#231 (3 comments by @iherman, @riannella, @vroddon)
-
Not-/Active Rules, evaluation, Policy inheritance and conflicts w3c/poe#240 (1 comment by @riannella)
-
Use of plural in the definition of classes and properties in the Vocab w3c/poe#232 (1 comment by @riannella)
-
6 pull requests opened.
-
Draft announcement texts w3c/poe#266, by @iherman.
-
Improvement on the /ns content w3c/poe#260, by @iherman.
-
Modified the config files as a preparation to CR w3c/poe#243, by @iherman.
-
Update contact in w3c.json w3c/poe#234, by @dontcallmedom.
-
-
6 pull requests merged.
-
Draft announcement texts w3c/poe#266.
-
Improvement on the /ns content w3c/poe#260.
-
Modified the config files as a preparation to CR w3c/poe#243.
-
Update contact in w3c.json w3c/poe#234.
-
CR admin w3c/poe#233.
-
-
4 pull requests received 8 new comments.
GitHub
w3c/poe
-
13 issues opened.
-
Setting a value related to the leftOperand of a constraint w3c/poe#227, by @nitmws.
-
On 2.6.8 Rule Active State Processing w3c/poe#226, by @simonstey.
-
The foggy effective/in-effect terminology w3c/poe#225, by @nitmws.
-
adding disclaimer to http://www.w3.org/TR/odrl w3c/poe#224, by @simonstey.
-
How to evaluate the results of Permission, Prohibition and Duty w3c/poe#223, by @nitmws.
-
Which property of type Duty has a consequence property? w3c/poe#222, by @nitmws.
-
How Rules become Active w3c/poe#221, by @nitmws.
-
IM - simple typos w3c/poe#220, by @nitmws.
-
Definition of ODRL w3c/poe#219, by @vroddon.
-
wording of cardinality restrictions w3c/poe#218, by @simonstey.
-
ODRL Evaluator review - IM of 11 August 2017 w3c/poe#217, by @nitmws.
-
Reviews of ODRL Vocabulary ... - Editor's Draft 3 August 2017 w3c/poe#216, by @nitmws.
-
Reviews of ODRL IM - Editor's Draft 3 August 2017 w3c/poe#215, by @nitmws.
-
-
28 issues closed.
-
IM - simple typos w3c/poe#220.
-
Role of the ODRL Common Vocabulary and of Profiles w3c/poe#210.
-
Define Atomic and Compound Constraint as subclasses w3c/poe#206.
-
Auto Script Bugs w3c/poe#186.
-
ODRL Latest Version Redirects w3c/poe#91.
-
Accessibility w3c/poe#114.
-
Duplicates in Vocabulary w3c/poe#199.
-
Constraint Narrative w3c/poe#203.
-
Modelling duty/obligation w3c/poe#191.
-
Model clarifications w3c/poe#162.
-
ODRL Processor & Test Suite w3c/poe#86.
-
Naming of elements/properties w3c/poe#165.
-
Vocab clarifications w3c/poe#164.
-
XML Schema design w3c/poe#197.
-
Use of cardinality restrictions in the ontology? w3c/poe#198.
-
Range of RightOperand w3c/poe#208.
-
1 issue reopened.
-
ambiguous semantics of duty constraints w3c/poe#211, by @simonstey.
-
-
26 issues received 170 new comments.
-
Reviews of ODRL IM - Editor's Draft 3 August 2017 w3c/poe#215 (41 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
ambiguous semantics of duty constraints w3c/poe#211 (17 comments by @nitmws, @riannella, @simonstey)
-
wording of cardinality restrictions w3c/poe#218 (14 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
How to evaluate the results of Permission, Prohibition and Duty w3c/poe#223 (7 comments by @nitmws, @riannella, @simonstey)
-
Which property of type Duty has a consequence property? w3c/poe#222 (5 comments by @nitmws, @riannella)
-
Reviews of ODRL Vocabulary ... - Editor's Draft 3 August 2017 w3c/poe#216 (5 comments by @nitmws, @riannella)
-
Does the JSON-LD serialization distinguish human-readable and machine-readable strings for DC terms? w3c/poe#213 (1 comment by @riannella)
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (1 comment by @riannella)
-
Compatibility with common patterns for linking assets to policies w3c/poe#184 (1 comment by @riannella)
-
Participants
-
1 participant left.
-
Phil Archer (W3C) left.
-
GitHub
w3c/poe
-
7 issues opened.
-
Can policy metadata be serialized in the XML encoding w3c/poe#214, by @riannella.
-
I18N Review: does Policy Metadata need Unicode normalization w3c/poe#212, by @riannella.
-
ambiguous semantics of duty constraints w3c/poe#211, by @simonstey.
-
Role of the ODRL Common Vocabulary and of Profiles w3c/poe#210, by @nitmws.
-
Duty->Consequence w3c/poe#209, by @riannella.
-
Range of RightOperand w3c/poe#208, by @riannella.
-
-
9 issues closed.
-
IM wording for classes and their relationships w3c/poe#200.
-
Single vs. Collection of Asset and Party unclear w3c/poe#195.
-
revising vocabulary definitions w3c/poe#74.
-
Checking the dynamic use of partOf w3c/poe#196.
-
Evaluation of Constraints of a Rule inconsistent w3c/poe#193.
-
assigneeTo and assignerTo inverse properties? w3c/poe#190.
-
not all contraint operators are logical operators w3c/poe#194.
-
ODRL Ontology: formal definition and design issues w3c/poe#188.
-
Requirements of Agreement Policies w3c/poe#187.
-
-
1 issue reopened.
-
20 issues received 119 new comments.
-
Role of the ODRL Common Vocabulary and of Profiles w3c/poe#210 (19 comments by @nitmws, @riannella, @simonstey)
-
Define Atomic and Compound Constraint as subclasses w3c/poe#206 (18 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
IM: upgrade Short-cut Instances of Classes in Policy Rule Composition to a section w3c/poe#202 (11 comments by @nitmws, @riannella, @simonstey)
-
Specifications of includedIn and implies need improvements w3c/poe#192 (6 comments by @riannella, @vroddon)
-
What's the immutable core of ODRL that cannot be changed by Profiles? w3c/poe#173 (4 comments by @larsgsvensson, @riannella)
-
Remove inheritAllowed functionality & single inheritance restriction w3c/poe#204 (3 comments by @benedictws, @riannella)
-
Compatibility with common patterns for linking assets to policies w3c/poe#184 (2 comments by @aisaac)
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (1 comment by @simonstey)
-
Relation to other standard frameworks for expressing rights statements w3c/poe#158 (1 comment by @riannella)
-
-
1 pull request merged.
-
Initial stab at definition of an ODRL Evaluator w3c/poe#207.
-
Participants
-
1 participant joined.
-
Linda Burman (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Fraunhofer Gesellschaft joined.
-
GitHub
w3c/poe
-
19 issues opened.
-
Define Atomic and Compound Constraint as subclasses w3c/poe#206, by @nitmws.
-
EXAMPLE 19 makes no sense w3c/poe#205, by @simonstey.
-
Constraint Narrative w3c/poe#203, by @simonstey.
-
Note on Policy Inference w3c/poe#201, by @nitmws.
-
IM wording for classes and their relationships w3c/poe#200, by @nitmws.
-
Duplicates in Vocabulary w3c/poe#199, by @simonstey.
-
Use of cardinality restrictions in the ontology? w3c/poe#198, by @nitmws.
-
XML Schema design w3c/poe#197, by @nitmws.
-
Checking the dynamic use of partOf w3c/poe#196, by @nitmws.
-
Single vs. Collection of Asset and Party unclear w3c/poe#195, by @nitmws.
-
not all contraint operators are logical operators w3c/poe#194, by @simonstey.
-
Evaluation of Constraints of a Rule inconsistent w3c/poe#193, by @nitmws.
-
Specifications of includedIn and implies need improvements w3c/poe#192, by @nitmws.
-
Modelling duty/obligation w3c/poe#191, by @fornaran.
-
assigneeTo and assignerTo inverse properties? w3c/poe#190, by @riannella.
-
ODRL Ontology in non-perfect state w3c/poe#189, by @vroddon.
-
ODRL Ontology: formal definition and design issues w3c/poe#188, by @nitmws.
-
-
35 issues closed.
-
EXAMPLE 19 makes no sense w3c/poe#205.
-
@uid vs @id w3c/poe#111.
-
Vocab feedback w3c/poe#185.
-
whats's the rationale behind uids? w3c/poe#174.
-
Mechanism for specifying constraints w3c/poe#161.
-
Vocab Editorial w3c/poe#166.
-
Definitions of Atomic Constraint Operators w3c/poe#180.
-
Model Comments/Feedback (PhilA) w3c/poe#181.
-
Remove Scope - replace with Constraint w3c/poe#183.
-
Difference between Policy Types and Rule Types w3c/poe#154.
-
Vocab terms "to an audience" w3c/poe#101.
-
Support JSON-LD w3c/poe#46.
-
what is the authoritative 'formal' definition? w3c/poe#124.
-
What properties are used with which classes? w3c/poe#128.
-
What does Policy merge means (model document) w3c/poe#130.
-
XML encoding: qcodes and qnames w3c/poe#151.
-
consistency of definitions w3c/poe#171.
-
Use of "agent" in the definition of "Party" w3c/poe#143.
-
Note on Duty w3c/poe#149.
-
Action names to be used w3c/poe#145.
-
Synchronize (addition to vocab) w3c/poe#123.
-
Should vs must in some odrl:LeftOperand w3c/poe#150.
-
JSON-LD Encoding w3c/poe#153.
-
Vocab Time examples w3c/poe#118.
-
1.4 Terminology w3c/poe#119.
-
ODRL Ontology in non-perfect state w3c/poe#189.
-
Undefined Actions - deprecate? w3c/poe#139.
-
odrl:use w3c/poe#140.
-
Systematic labeling of normative vs. informative w3c/poe#155.
-
ODRL Profiles & RFC2119 w3c/poe#172.
-
-
5 issues reopened.
-
Model clarifications w3c/poe#162, by @simonstey.
-
revising vocabulary definitions w3c/poe#74, by @simonstey.
-
whats's the rationale behind uids? w3c/poe#174, by @riannella.
-
42 issues received 349 new comments.
-
Compatibility with common patterns for linking assets to policies w3c/poe#184 (34 comments by @aisaac, @nitmws, @riannella, @simonstey, @vroddon)
-
ODRL Ontology: formal definition and design issues w3c/poe#188 (25 comments by @larsgsvensson, @nitmws, @riannella, @simonstey, @vroddon)
-
What's the immutable core of ODRL that cannot be changed by Profiles? w3c/poe#173 (23 comments by @iherman, @larsgsvensson, @nitmws, @philarcher, @riannella, @simonstey, @vroddon)
-
Model clarifications w3c/poe#162 (22 comments by @aisaac, @nitmws, @riannella, @simonstey, @vroddon)
-
Requirements of Agreement Policies w3c/poe#187 (20 comments by @larsgsvensson, @nitmws, @riannella, @vroddon)
-
Use of cardinality restrictions in the ontology? w3c/poe#198 (18 comments by @iherman, @nitmws, @riannella, @simonstey)
-
Relation to other standard frameworks for expressing rights statements w3c/poe#158 (13 comments by @aisaac, @larsgsvensson, @riannella, @simonstey, @vroddon)
-
Evaluation of Constraints of a Rule inconsistent w3c/poe#193 (12 comments by @nitmws, @riannella, @simonstey)
-
Specifications of includedIn and implies need improvements w3c/poe#192 (11 comments by @nitmws, @riannella, @vroddon)
-
IM: upgrade Short-cut Instances of Classes in Policy Rule Composition to a section w3c/poe#202 (9 comments by @nitmws, @riannella, @simonstey)
-
assigneeTo and assignerTo inverse properties? w3c/poe#190 (9 comments by @nitmws, @riannella, @simonstey)
-
Possible extensions of the (SKOS) concept schemes defined in POE w3c/poe#160 (8 comments by @aisaac, @riannella)
-
Single vs. Collection of Asset and Party unclear w3c/poe#195 (6 comments by @nitmws, @riannella, @simonstey)
-
Define Atomic and Compound Constraint as subclasses w3c/poe#206 (3 comments by @benedictws, @riannella)
-
Remove inheritAllowed functionality & single inheritance restriction w3c/poe#204 (2 comments by @riannella, @simonstey)
-
Normative and non-normative parties, actions, leftOperands, operators ... w3c/poe#182 (2 comments by @riannella, @vroddon)
-
-
1 pull request opened.
-
Initial stab at definition of an ODRL Evaluator w3c/poe#207, by @philarcher.
-
GitHub
w3c/poe
-
29 issues opened.
-
Requirements of Agreement Policies w3c/poe#187, by @simonstey.
-
Auto Script Bugs w3c/poe#186, by @riannella.
-
Vocab feedback w3c/poe#185, by @riannella.
-
Compatibility with common patterns for linking assets to policies w3c/poe#184, by @aisaac.
-
Remove Scope - replace with Constraint w3c/poe#183, by @riannella.
-
Model Comments/Feedback (PhilA) w3c/poe#181, by @riannella.
-
Definitions of Atomic Constraint Operators w3c/poe#180, by @nitmws.
-
Actions (Permission/Prohibition and Duty) - editorial issues w3c/poe#178, by @nitmws.
-
Policy Composition & Vocab w3c/poe#177, by @simonstey.
-
invalid examples w3c/poe#176, by @simonstey.
-
whats's the rationale behind uids? w3c/poe#174, by @simonstey.
-
ODRL Profiles & RFC2119 w3c/poe#172, by @simonstey.
-
consistency of definitions w3c/poe#171, by @simonstey.
-
A Party MUST have the function role fulfilled by a Party w3c/poe#170, by @simonstey.
-
Vocab Editorial w3c/poe#166, by @riannella.
-
Naming of elements/properties w3c/poe#165, by @riannella.
-
Vocab clarifications w3c/poe#164, by @riannella.
-
Model editorial w3c/poe#163, by @riannella.
-
Model clarifications w3c/poe#162, by @riannella.
-
Mechanism for specifying constraints w3c/poe#161, by @riannella.
-
Question about Data Quality Vocabulary case w3c/poe#159, by @riannella.
-
Europeana/DPLA use case w3c/poe#157, by @riannella.
-
General feedback on POE Use Cases w3c/poe#156, by @riannella.
-
-
22 issues closed.
-
Question about Data Quality Vocabulary case w3c/poe#159.
-
RDF/OWL encoding w3c/poe#152.
-
Editorial style w3c/poe#85.
-
invalid examples w3c/poe#176.
-
Cardinality of Permission in Policy w3c/poe#144.
-
Actions for Prohibitions and Duties w3c/poe#148.
-
Text for note on Target w3c/poe#147.
-
Example used for "scope" w3c/poe#142.
-
Processing of dc:isReplacedBy w3c/poe#141.
-
Usage permissions for Ticket w3c/poe#146.
-
Policy Conflict - Deprecate? w3c/poe#138.
-
Model editorial w3c/poe#163.
-
Policy Composition & Vocab w3c/poe#177.
-
Differences between constraint terms w3c/poe#117.
-
URI or IRI? (Model) w3c/poe#133.
-
Add sameAs/subClassOf w3c/poe#83.
-
(Editorial) use 'code' for URL-s in the text w3c/poe#132.
-
Asset references (Model document) w3c/poe#134.
-
What is an ODRL Processor? (Model document) w3c/poe#131.
-
Definition of relations (model) w3c/poe#135.
-
-
16 issues reopened.
-
invalid examples w3c/poe#176, by @riannella.
-
Policy Composition & Vocab w3c/poe#177, by @simonstey.
-
Processing of dc:isReplacedBy w3c/poe#141, by @riannella.
-
Example used for "scope" w3c/poe#142, by @riannella.
-
Cardinality of Permission in Policy w3c/poe#144, by @riannella.
-
Action names to be used w3c/poe#145, by @riannella.
-
Text for note on Target w3c/poe#147, by @riannella.
-
Actions for Prohibitions and Duties w3c/poe#148, by @riannella.
-
Naming of elements/properties w3c/poe#165, by @riannella.
-
Model editorial w3c/poe#163, by @riannella.
-
Model clarifications w3c/poe#162, by @riannella.
-
Vocab Editorial w3c/poe#166, by @simonstey.
-
what is the authoritative 'formal' definition? w3c/poe#124, by @simonstey.
-
1.4 Terminology w3c/poe#119, by @simonstey.
-
revising vocabulary definitions w3c/poe#74, by @simonstey.
-
@uid vs @id w3c/poe#111, by @simonstey.
-
-
58 issues received 261 new comments.
-
Difference between Policy Types and Rule Types w3c/poe#154 (20 comments by @iherman, @riannella, @simonstey, @vroddon)
-
Compatibility with common patterns for linking assets to policies w3c/poe#184 (14 comments by @aisaac, @riannella, @simonstey, @vroddon)
-
revising vocabulary definitions w3c/poe#74 (12 comments by @larsgsvensson, @riannella, @simonstey, @vroddon)
-
ODRL Profiles & RFC2119 w3c/poe#172 (12 comments by @iherman, @philarcher, @riannella, @simonstey, @vroddon)
-
Question about Data Quality Vocabulary case w3c/poe#159 (9 comments by @aisaac, @riannella, @simonstey)
-
What's the immutable core of ODRL that cannot be changed by Profiles? w3c/poe#173 (7 comments by @larsgsvensson, @philarcher, @riannella, @simonstey)
-
Use of "agent" in the definition of "Party" w3c/poe#143 (7 comments by @larsgsvensson, @riannella, @simonstey, @vroddon)
-
Normative and non-normative parties, actions, leftOperands, operators ... w3c/poe#182 (6 comments by @riannella, @vroddon)
-
What properties are used with which classes? w3c/poe#128 (6 comments by @larsgsvensson, @riannella, @simonstey)
-
Possible extensions of the (SKOS) concept schemes defined in POE w3c/poe#160 (5 comments by @aisaac, @riannella)
-
Actions for Prohibitions and Duties w3c/poe#148 (5 comments by @larsgsvensson, @riannella, @simonstey)
-
Actions (Permission/Prohibition and Duty) - editorial issues w3c/poe#178 (5 comments by @nitmws, @riannella, @vroddon)
-
Relation to other standard frameworks for expressing rights statements w3c/poe#158 (5 comments by @aisaac, @riannella)
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (3 comments by @riannella, @simonstey)
-
An Action is associated to the Asset with the action property in a Rule. w3c/poe#175 (2 comments by @riannella)
-
Constraint: specs of classes and of instances of LeftOperand - editorial issues w3c/poe#179 (1 comment by @riannella)
-
-
3 pull requests opened.
-
Adding third invalid example w3c/poe#169, by @philarcher.
-
Forgot the config file w3c/poe#168, by @philarcher.
-
Skeleton idea for test suite doc w3c/poe#167, by @philarcher.
-
-
3 pull requests merged.
-
Adding third invalid example w3c/poe#169.
-
Forgot the config file w3c/poe#168.
-
Skeleton idea for test suite doc w3c/poe#167.
-
GitHub
w3c/poe
-
32 issues opened.
-
Systematic labeling of normative vs. informative w3c/poe#155, by @iherman.
-
Difference between Policy Types and Rule Types w3c/poe#154, by @simonstey.
-
JSON-LD Encoding w3c/poe#153, by @riannella.
-
RDF/OWL encoding w3c/poe#152, by @riannella.
-
XML encoding: qcodes and qnames w3c/poe#151, by @riannella.
-
Should vs must in some odrl:LeftOperand w3c/poe#150, by @larsgsvensson.
-
Note on Duty w3c/poe#149, by @larsgsvensson.
-
Actions for Prohibitions and Duties w3c/poe#148, by @larsgsvensson.
-
Text for note on Target w3c/poe#147, by @larsgsvensson.
-
Usage permissions for Ticket w3c/poe#146, by @larsgsvensson.
-
Action names to be used w3c/poe#145, by @larsgsvensson.
-
Cardinality of Permission in Policy w3c/poe#144, by @larsgsvensson.
-
Use of "agent" in the definition of "Party" w3c/poe#143, by @larsgsvensson.
-
Example used for "scope" w3c/poe#142, by @larsgsvensson.
-
Processing of dc:isReplacedBy w3c/poe#141, by @larsgsvensson.
-
odrl:use w3c/poe#140, by @riannella.
-
Undefined Actions - deprecate? w3c/poe#139, by @riannella.
-
Policy Conflict - Deprecate? w3c/poe#138, by @riannella.
-
Let us not use P3P terms... w3c/poe#136, by @iherman.
-
Definition of relations (model) w3c/poe#135, by @iherman.
-
Asset references (Model document) w3c/poe#134, by @iherman.
-
URI or IRI? (Model) w3c/poe#133, by @iherman.
-
(Editorial) use 'code' for URL-s in the text w3c/poe#132, by @iherman.
-
What is an ODRL Processor? (Model document) w3c/poe#131, by @iherman.
-
What does Policy merge means (model document) w3c/poe#130, by @iherman.
-
What does 'information entity' means? (Model document) w3c/poe#129, by @iherman.
-
What properties are used with which classes? w3c/poe#128, by @iherman.
-
rearrange examples in example 7 w3c/poe#127, by @iherman.
-
Wrong examples (4 & 5) in the model document w3c/poe#126, by @iherman.
-
what is the authoritative 'formal' definition? w3c/poe#124, by @iherman.
-
Synchronize (addition to vocab) w3c/poe#123, by @riannella.
-
-
8 issues closed.
-
Let us not use P3P terms... w3c/poe#136.
-
JSON example - fix repeated properties w3c/poe#116.
-
rearrange examples in example 7 w3c/poe#127.
-
Wrong examples (4 & 5) in the model document w3c/poe#126.
-
On Duties and their Permissions w3c/poe#122.
-
Align vocab terms to the definitions in the IM w3c/poe#99.
-
Clarify inheritance and over-riden entities w3c/poe#22.
-
Ontology constraints/restrictions w3c/poe#26.
-
-
34 issues received 122 new comments.
-
What properties are used with which classes? w3c/poe#128 (23 comments by @iherman, @larsgsvensson, @riannella, @simonstey, @vroddon)
-
what is the authoritative 'formal' definition? w3c/poe#124 (6 comments by @iherman, @riannella, @simonstey)
-
Editorial: the formatting of the examples is not consistent (model) w3c/poe#137 (6 comments by @iherman, @riannella, @simonstey)
-
What does 'information entity' means? (Model document) w3c/poe#129 (4 comments by @iherman, @riannella, @simonstey)
-
What does Policy merge means (model document) w3c/poe#130 (4 comments by @iherman, @riannella, @simonstey)
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (1 comment by @riannella)
-
-
1 pull request opened.
-
Update index.html w3c/poe#125, by @iherman.
-
-
1 pull request merged.
-
Update index.html w3c/poe#125.
-
-
1 pull request received 1 new comment.
GitHub
w3c/poe
-
6 issues opened.
-
On Duties and their Permissions w3c/poe#122, by @simonstey.
-
3.3.2 (Party) Scope w3c/poe#120, by @simonstey.
-
1.4 Terminology w3c/poe#119, by @simonstey.
-
Vocab Time examples w3c/poe#118, by @riannella.
-
Differences between constraint terms w3c/poe#117, by @simonstey.
-
JSON example - fix repeated properties w3c/poe#116, by @riannella.
-
-
8 issues closed.
-
3.1.1 Policy Conflict w3c/poe#76.
-
3.1 Policy w3c/poe#96.
-
Additional party Roles w3c/poe#110.
-
Definition of odrl:delayPeriod w3c/poe#115.
-
3.3.2 (Party) Scope w3c/poe#120.
-
Add "stream" to Vocab w3c/poe#103.
-
-
5 issues reopened.
-
Clarify inheritance and over-riden entities w3c/poe#22, by @simonstey.
-
3.1 Policy w3c/poe#96, by @simonstey.
-
3.1.1 Policy Conflict w3c/poe#76, by @simonstey.
-
Clarify inheritance and over-riden entities w3c/poe#22, by @simonstey.
-
-
18 issues received 71 new comments.
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (10 comments by @riannella, @simonstey)
-
Differences between constraint terms w3c/poe#117 (8 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
Does every permission/prohibition need to have both an assignee & assigner? w3c/poe#113 (2 comments by @nitmws, @riannella)
-
-
1 pull request merged.
-
typo fixx w3c/poe#121.
-
TR publications
-
3 documents published.
-
ODRL Information Model published as a Working Draft. History of ODRL Information Model
-
ODRL Vocabulary & Expression published as a Working Draft. History of ODRL Vocabulary & Expression
-
POE Use Cases and Requirements published as a Working Draft. History of POE Use Cases and Requirements
-
GitHub
w3c/poe
-
16 issues opened.
-
Definition of odrl:delayPeriod w3c/poe#115, by @simonstey.
-
Accessibility w3c/poe#114, by @riannella.
-
@uid vs @id w3c/poe#111, by @simonstey.
-
Additional party Roles w3c/poe#110, by @riannella.
-
wrong wgPatentURI in InfoModel config.js w3c/poe#108, by @simonstey.
-
Making ODRL2.2 to be OWL DL w3c/poe#107, by @vroddon.
-
On the convenience of rdfs:Resource for the rdfs:Range w3c/poe#106, by @vroddon.
-
Undefined Actions w3c/poe#105, by @riannella.
-
Update each section's list of attributes w3c/poe#104, by @riannella.
-
Add "stream" to Vocab w3c/poe#103, by @riannella.
-
Definition of policy w3c/poe#102, by @vroddon.
-
Vocab terms "to an audience" w3c/poe#101, by @riannella.
-
:Asset owl:equivalentClass owl:Thing . w3c/poe#100, by @vroddon.
-
-
12 issues closed.
-
Undefined Actions w3c/poe#105.
-
Update each section's list of attributes w3c/poe#104.
-
Making ODRL2.2 to be OWL DL w3c/poe#107.
-
wrong wgPatentURI in InfoModel config.js w3c/poe#108.
-
Definition of policy w3c/poe#102.
-
isNeccessaryFor w3c/poe#98.
-
3. ODRL Information Model w3c/poe#95.
-
Normative and non-normative terms w3c/poe#64.
-
Improve Constraint definitions w3c/poe#67.
-
:Asset owl:equivalentClass owl:Thing . w3c/poe#100.
-
-
1 issue reopened.
-
Normative and non-normative terms w3c/poe#64, by @riannella.
-
-
19 issues received 104 new comments.
-
Support JSON-LD w3c/poe#46 (35 comments by @azaroth42, @gkellogg, @iherman, @riannella, @simonstey, @stuartmyles)
-
This specification doesn't appear to have any 'Privacy' or 'Security' considerations sections. w3c/poe#109 (5 comments by @iherman, @riannella, @simonstey)
-
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied? w3c/poe#112 (2 comments by @simonstey)
-
Constraint specs currently do not cover logic operation on constraints w3c/poe#94 (1 comment by @riannella)
-
GitHub
w3c/poe
-
14 issues opened.
-
Align vocab terms to the definitions in the IM w3c/poe#99, by @riannella.
-
isNeccessaryFor w3c/poe#98, by @riannella.
-
On prohibitions living alone w3c/poe#97, by @vroddon.
-
3.1 Policy w3c/poe#96, by @simonstey.
-
3. ODRL Information Model w3c/poe#95, by @simonstey.
-
normative vs non-normative vocabulary terms strategy? w3c/poe#93, by @nitmws.
-
Should hasRightOperandReference survive? w3c/poe#92, by @vroddon.
-
ODRL Latest Version Redirects w3c/poe#91, by @riannella.
-
XML Linking w3c/poe#90, by @riannella.
-
Renaming properties w3c/poe#89, by @vroddon.
-
Move Scenario Examples to Best Practices NOTE w3c/poe#88, by @riannella.
-
Use of the label Left Operand in the ontology/vocabulary w3c/poe#87, by @nitmws.
-
ODRL Processor & Test Suite w3c/poe#86, by @philarcher.
-
-
28 issues closed.
-
On prohibitions living alone w3c/poe#97.
-
Extended Relations w3c/poe#63.
-
Constraints on Constraints w3c/poe#62.
-
Consistency and cohesiveness of nomenclature w3c/poe#77.
-
1.4 Terminology w3c/poe#78.
-
Renaming properties w3c/poe#89.
-
Should hasRightOperandReference survive? w3c/poe#92.
-
Deprecation predicate w3c/poe#25.
-
Policy Versioning w3c/poe#48.
-
Add Constraint to Party and Asset w3c/poe#59.
-
Review definition of Constraint by ODRL ontology w3c/poe#84.
-
Add unit-of-count w3c/poe#58.
-
Inverse Target Link w3c/poe#61.
-
Support Multiple Actions w3c/poe#73.
-
Allow Asset/Party at the Policy level w3c/poe#82.
-
XML Linking w3c/poe#90.
-
rightOperand is a reference to a value w3c/poe#56.
-
Move Vocab short-name back to odrl-vocab w3c/poe#72.
-
Add license example w3c/poe#41.
-
Check Policy Types w3c/poe#39.
-
Update Constraint narrative w3c/poe#68.
-
3.1.2 Undefined Policy w3c/poe#75.
-
ODRL Profiles w3c/poe#49.
-
3.7 Action w3c/poe#79.
-
-
29 issues received 115 new comments.
-
Improve Constraint definitions w3c/poe#67 (33 comments by @nitmws, @riannella, @simonstey, @vroddon)
-
Review definition of Constraint by ODRL ontology w3c/poe#84 (11 comments by @iherman, @nitmws, @riannella, @vroddon)
-
Use of the label Left Operand in the ontology/vocabulary w3c/poe#87 (7 comments by @nitmws, @riannella, @vroddon)
-
Constraint specs currently do not cover logic operation on constraints w3c/poe#94 (6 comments by @nitmws, @riannella)
-
normative vs non-normative vocabulary terms strategy? w3c/poe#93 (2 comments by @nitmws, @riannella)
-