Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/odrl issues and pull requests

#63 - odrl:inheritFrom too generic to work for supply chains, add odrl:import and odrl:reference

Issue - State: closed - Opened by joshcornejo 2 months ago - 6 comments
Labels: New Feature, Implementation Best Practices

#62 - Section 2.6

Issue - State: closed - Opened by joshcornejo 5 months ago - 1 comment

#61 - How to represent in the "state of the world" the executed Actions

Issue - State: open - Opened by fornaran 5 months ago - 2 comments
Labels: New Feature, Formal Semantics

#60 - Refinement V Constraint

Issue - State: open - Opened by riannella 6 months ago - 4 comments
Labels: Implementation Best Practices

#59 - odrl:payAmount (possible for 3.0?)

Issue - State: open - Opened by joshcornejo 6 months ago - 4 comments
Labels: Implementation Best Practices

#58 - ODRL Profile: Big Data (various issues & comments)

Issue - State: open - Opened by joshcornejo 6 months ago
Labels: Data Spaces

#57 - W3C TPAC 2024 - Community Group meetings

Issue - State: open - Opened by riannella 6 months ago - 4 comments
Labels: W3C

#56 - Policy state

Issue - State: open - Opened by joshcornejo 6 months ago
Labels: Implementation Best Practices

#55 - odrl:collate (suitable for 3.0)

Issue - State: open - Opened by joshcornejo 6 months ago - 2 comments
Labels: Implementation Best Practices, Community Vocabulary

#54 - odrl:action

Issue - State: open - Opened by joshcornejo 6 months ago - 2 comments
Labels: Implementation Best Practices

#53 - odrl:function

Issue - State: open - Opened by joshcornejo 6 months ago
Labels: Implementation Best Practices

#52 - odrl:target

Issue - State: open - Opened by joshcornejo 6 months ago - 5 comments
Labels: Implementation Best Practices

#50 - Request to add some state diagrams explaining states in ODRL formal semantics

Issue - State: closed - Opened by ksridhar 7 months ago - 2 comments
Labels: Formal Semantics

#49 - propose template for meetings

Pull Request - State: closed - Opened by besteves4 8 months ago

#48 - Broken links

Issue - State: closed - Opened by vroddon 9 months ago - 1 comment
Labels: Editorial, Website

#47 - Keep meeting notes in the repository

Issue - State: closed - Opened by besteves4 9 months ago - 5 comments
Labels: bug, New Feature

#46 - Align with the work of DPVCG

Issue - State: open - Opened by besteves4 9 months ago
Labels: W3C, Align

#45 - Problem in Example 7

Issue - State: closed - Opened by vroddon 9 months ago - 2 comments
Labels: Implementation Best Practices

#44 - Example 2-2 in JSON-LD missing

Issue - State: closed - Opened by vroddon 9 months ago - 2 comments
Labels: Implementation Best Practices

#43 - ODRL Community Vocabulary

Issue - State: open - Opened by riannella 9 months ago - 3 comments
Labels: Community Vocabulary

#42 - Refine refinements

Issue - State: closed - Opened by joshcornejo 9 months ago - 3 comments
Labels: W3C

#41 - Feedback on 'ODRL V2.2 Profile Best Practices'

Issue - State: closed - Opened by YassirSellami 9 months ago - 2 comments
Labels: Profile Best Practices

#40 - Wrong naming of the ``neq`` operator

Issue - State: closed - Opened by IcarusCoding 9 months ago - 1 comment

#38 - Invalid json-ld syntax in EXAMPLE 29

Issue - State: closed - Opened by ksridhar 10 months ago - 1 comment

#37 - A typo error in Example Use Case of EXAMPLE 21

Issue - State: closed - Opened by ksridhar 10 months ago - 1 comment

#36 - A typo error in section 2.6 Rule Class

Issue - State: closed - Opened by ksridhar 10 months ago - 1 comment

#35 - Create asset Action not present in ODRL

Issue - State: open - Opened by woutslabbinck 10 months ago - 6 comments
Labels: Community Vocabulary

#34 - Add Participate section to README.md

Pull Request - State: closed - Opened by bact 11 months ago

#33 - Fix some typos and punctuation

Pull Request - State: closed - Opened by JensPiegsa about 1 year ago - 1 comment
Labels: Editorial

#32 - Objects requiring licenses or constraining effective licenses?

Issue - State: closed - Opened by bobwyman over 1 year ago - 2 comments

#31 - fixed minor typo: rhat -> that

Pull Request - State: closed - Opened by DavidFichtmueller almost 2 years ago

#30 - JSON-LD context incorrectly maps odrl:uid to @id

Issue - State: closed - Opened by matthieubosquet about 2 years ago - 3 comments
Labels: New Feature, W3C

#28 - Usage of `odrl:eq` and `odrl:isA` operators and missing operator for subclasses

Issue - State: open - Opened by besteves4 about 2 years ago - 6 comments
Labels: Community Vocabulary

#27 - Add negation operator

Issue - State: open - Opened by besteves4 about 2 years ago - 7 comments
Labels: Community Vocabulary

#26 - Incorrect Usage of uid/@id in Implementation Best Practices

Issue - State: closed - Opened by sebbader about 2 years ago - 4 comments
Labels: Implementation Best Practices

#25 - Typo on ODRL Implementation Best Practices

Issue - State: closed - Opened by lolostar about 2 years ago - 2 comments

#24 - add access control scenario to ODRL formal semantics document

Pull Request - State: closed - Opened by besteves4 about 2 years ago - 1 comment

#23 - Semantics for overlapping Permissions

Issue - State: closed - Opened by Jimflip about 2 years ago - 4 comments

#22 - Problem with the odrl.jsonld context file and CORS

Issue - State: closed - Opened by dlongley over 2 years ago - 8 comments

#21 - Expressing preferred policies or templates

Issue - State: open - Opened by csarven over 2 years ago - 6 comments
Labels: Community Vocabulary

#20 - Small typo in the json-ld context

Issue - State: closed - Opened by markwilkinson over 2 years ago - 1 comment

#19 - Diffference between Distribute and GrantUse

Issue - State: closed - Opened by Jimflip almost 3 years ago - 7 comments

#18 - Hosting of mapped licenses

Issue - State: closed - Opened by riannella about 3 years ago - 3 comments

#17 - Publication of ODRL Profiles

Issue - State: closed - Opened by riannella about 3 years ago - 3 comments
Labels: Website

#16 - ODRL Temporal Profile TIME modelling is invalid + other suggestions

Issue - State: open - Opened by nicholascar over 3 years ago - 5 comments
Labels: Temporal Profile

#15 - Added temporal policies

Pull Request - State: closed - Opened by benedictDD over 3 years ago

#14 - Access and License Indicators (ALI)

Issue - State: closed - Opened by vroddon over 3 years ago - 5 comments
Labels: Industry

#13 - Fix respec config

Pull Request - State: closed - Opened by dontcallmedom almost 4 years ago

#12 - Discovery of an ODRL resource

Issue - State: closed - Opened by csarven almost 4 years ago - 13 comments
Labels: New Feature

#11 - Erratum

Issue - State: closed - Opened by vroddon almost 4 years ago - 1 comment
Labels: Editorial

#10 - Creating Rule subclasses being a Permission, Prohibition or Duty

Issue - State: closed - Opened by nitmws over 4 years ago - 3 comments
Labels: Profile

#9 - Inconsistencies around prohibition, prohibition and obligation in a Policy

Issue - State: closed - Opened by nitmws almost 5 years ago - 2 comments
Labels: bug, Profile

#8 - Guidelines for what a Policy or a Rule subclass may define

Issue - State: closed - Opened by nitmws over 5 years ago
Labels: Profile, Best Practices

#7 - How to define terms of a profile in a machine-readable way?

Issue - State: closed - Opened by nitmws over 6 years ago - 26 comments
Labels: Profile, Developers

#6 - W3C ODRL Recommendations errata maintenance

Issue - State: open - Opened by riannella over 6 years ago - 4 comments
Labels: W3C

#5 - Update the CG Home Page

Issue - State: closed - Opened by riannella over 6 years ago - 6 comments
Labels: Website

#4 - REQUEST for preliminary review: Verifiable Credentials Data Model 1.0

Issue - State: closed - Opened by riannella over 6 years ago - 4 comments
Labels: W3C

#3 - W3C ODRL Use Case note

Issue - State: closed - Opened by riannella over 6 years ago - 2 comments
Labels: W3C

#2 - Use Cases for Best Practices guide?

Issue - State: closed - Opened by aisaac over 6 years ago - 5 comments
Labels: Implementation Best Practices

#1 - ODRL Best Practices document needs corrections and add-ons

Issue - State: closed - Opened by nitmws over 6 years ago - 3 comments
Labels: Editorial, Implementation Best Practices