Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consistency and cohesiveness of nomenclature #77

Closed
simonstey opened this issue Dec 2, 2016 · 0 comments
Closed

Consistency and cohesiveness of nomenclature #77

simonstey opened this issue Dec 2, 2016 · 0 comments
Assignees
@sereAbi @riannella
Labels
Editorial To Be Closed
Milestone
Information Model

Comments

@simonstey
Copy link
Contributor

Throughout the entire spec. almost every ODRL concept/term is formatted and/or named differently.

For example (the same hold for any other concept as well) :
Policy -> (p|P)olicy, Policy, ODRL (p|P)olicy, ODRL Policy expression, (c|Child) (p|P)olicy, ...

  1. if differences in formatting/naming should imply differences in semantics, they need to be made explicit
  2. otherwise, they need to be aligned with each other
@simonstey simonstey added this to the Information Model milestone Dec 2, 2016
sereAbi added a commit that referenced this issue Jan 23, 2017
@sereAbi
Update nomenclature - Issue #77
657b0ff
sereAbi added a commit that referenced this issue Jan 23, 2017
@sereAbi
Nomenclature - Issue #77
2a872da
sereAbi added a commit that referenced this issue Jan 23, 2017
@sereAbi
Nomenclature - Issue #77
d30d126
sereAbi added a commit that referenced this issue Jan 23, 2017
@sereAbi
Nomenclature - Issue #77
b058a79
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sereAbi sereAbi

@riannella riannella

Labels
Editorial To Be Closed
Projects
None yet
Milestone
Information Model
Development

No branches or pull requests
3 participants
@sereAbi @simonstey @riannella