ISSUE-12: Make asserting flexible values more flexible

Make asserting flexible values more flexible

State:
CLOSED
Product:
ODRL Version 2.0 XML Encoding (Public)
Raised by:
Michael Steidl
Opened on:
2012-06-20
Description:
As the example 4.6 of the XML Encoding page of the ODRL specs (http://www.w3.org/community/odrl/two/xml/) shows the concrete value of a license fee has to be expressed as Asset.
As licensing fees a) are flexible and b) a very large amount of them exist IPTC members raised the business requirement to have a more flexible way for expressing such literal values in ODRL.
We could think about adding attributes like @valuetype, @value and @valueunit to the asset element and to define some indicator (e.g. a special @relation value) for this use case.

Thank you for considering

Michael
Related Actions Items:
Related emails:
  1. ODRL Teleconference NOTES (from ri@semanticidentity.com on 2013-04-11)
  2. Updating Specs (from ri@semanticidentity.com on 2013-01-22)
  3. RE: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from mdirector@iptc.org on 2012-11-13)
  4. Re: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from ri@semanticidentity.com on 2012-11-13)
  5. RE: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from mdirector@iptc.org on 2012-11-09)
  6. Re: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from ri@semanticidentity.com on 2012-07-05)
  7. RE: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from mdirector@iptc.org on 2012-07-02)
  8. Re: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from ri@semanticidentity.com on 2012-07-01)
  9. odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ] (from sysbot+tracker@w3.org on 2012-06-20)

Related notes:

Agreed to add two new attributes to constraint element.
- rOpDataType
- rOpUnit

However, cannot be used for payments

Renato Iannella, 6 Oct 2012, 04:47:36

- Current Drafts for Model/Vocab/XML have been updated for Constraint Changes and new License term
- [RI] to add links to show HTML-diffs between documents
- Question - need to discuss how we version the specs and maintain updates over time (eg look at UBL)

Renato Iannella, 26 Jun 2013, 12:02:29

Display change log ATOM feed


Renato Iannella <r@iannel.la>, Víctor Rodríguez-Doncel <vrodriguez@fi.upm.es>, Michael W Steidl <mwsteidl@newsit.biz>, David Filip <david.filip@adaptcentre.ie>, Chairs, Dominique Hazaël-Massieux <dom@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 12.html,v 1.1 2019/11/08 09:44:54 carcone Exp $