Source: https://iptc.org/std/RightsML/2.0/RightsML_2.0-specification.html
Timestamp: 2019-05-21 12:33:57
Document Index: 243219710

Matched Legal Cases: ['arty\n8', 'arty\n8', 'arty\n8', 'arty\n8', 'arty\n8', 'arty\n8', 'arty\n8', 'arty\n8', 'arty\n9']

IPTC RightsML Standard 2.0
IPTC Rights Expressions Working Group
version 2.0.2, 2018-08-06
IPTC RightsML Specification History
Specification Document Revision History
Other RightsML Documents
IPTC RightsML Introduction
2. RightsML as ODRL Profile
3. Specification templates
IPTC RightsML specifications
4. Namespaces and Identifiers
5. Actions for Rules
5.1. Accept Tracking
5.2. Aggregate
5.3. Annotate
5.4. Anonymize
5.5. Archive
5.6. Attribute
5.7. Compensate
5.8. Concurrent Use
5.10. Derive
5.11. Digitize
5.12. Display
5.13. Distribute
5.14. Ensure Exclusivity
5.15. Execute
5.16. Extract
5.17. Give
5.18. Grant Use
5.19. Include
5.20. Index
5.22. Modify
5.23. Move
5.24. Next Policy
5.25. Obtain Consent
5.26. Play
5.27. Present
5.28. Print
5.29. Reproduce
5.30. Review Policy
5.31. Sell
5.32. Stream
5.33. Synchronize
5.34. Text-to-Speech
5.35. Transform
5.36. Translate
5.37. Watermark
6. LeftOperands for Constraints
6.1. Absolute Asset Position
6.2. Absolute Asset Size
6.3. Absolute Spatial Asset Position
6.4. Absolute Temporal Asset Position
6.5. Asset Percentage
6.6. Count
6.7. Datetime
6.8. Delay Period
6.9. Delivery Channel
6.10. Elapsed Time
6.11. Event
6.12. File Format
6.13. Geospatial Coordinates
6.14. Geospatial Named Area
6.15. Industry Context
6.16. Language
6.17. Media Context
6.18. Metered Time
6.19. Payment Amount
6.20. Product Context
6.21. Purpose
6.22. Recipient
6.23. Recurring Time Interval
6.24. Relative Asset Position
6.25. Relative Asset Size
6.26. Relative Spatial Asset Position
6.27. Relative Temporal Asset Position
6.28. Rendition Resolution
6.29. System Device
6.30. UnitOfCount
6.31. Version
6.32. Virtual IT Communication Location
6.33. Compensation Value
7. RightOperands for Constraints
7.1. Policy Usage Time
8. Functional Roles of Parties
8.1. Attributed Party
8.2. Compensated Party
8.3. Compensating Party
8.4. Consented Party
8.5. Consenting Party
8.6. Informed Party
8.7. Informing Party
8.8. Tracked Party
8.9. Tracking Party
9. Relationships with Assets
10. Other standards
Copyright © 2018 by IPTC, the International Press Telecommunications Council - https://iptc.org. All Rights Reserved.
The IPTC RightsML Standard document is published under the Creative Commons Attribution 4.0 license - see the full license agreement at http://creativecommons.org/licenses/by/4.0/. By obtaining, using and/or copying this document, you (the licensee) agree that you have read, understood, and will comply with the terms and conditions of the license.
This project intends to use materials that are either in the public domain or are available by the permission for their respective copyright holders. All materials of this IPTC standard covered by copyright shall be licensable at no charge.
This document is the result of a team effort by members of the International Press Telecommunications Council since 2012 with input and assistance from other contributors.
Development and maintenance of RightsML was done by these persons (ordered by surname): Vincent Baby (Thomson Reuters), Linda Burman (L.Burman), Dave Compton (Thomson Reuters), Chris Eisenberg (Getty Images), Christ Hugh-Jones (Fingerpost), Stuart Myles (AP), Andy Read (BBC), Michael Steidl (IPTC).
This document specifies terms for the RightsML standard.
This document is a specification that may be revised to fix errata. Any changes will be indicated by a new document revision number. Any changes to the specification will be reflected by a change of the version of the standard.
This document is under the governance of the IPTC Rights Expressions Working Group of the IPTC Standards Committee.
This specification document was endorsed by IPTC members and may be updated, replaced or made obsolete by other documents at any time.
Public comments should be posted at this forum http://dev.iptc.org/Forum-3
Author/revised by
Rights Expressions WG/M Steidl
Link to ODRL profile file added
A generic introduction with a focus on the business features of RightsML is available on the IPTC main website at https://iptc.org/standards/rightsml/.
Guidelines and examples are available in the RightsML chapter of the IPTC Developer Site at http://dev.iptc.org/RightsML
RightsML is a Rights Expresson Language for the media industry. With RightsML, every single piece of content, a media asset, released by a news provider or publisher can be annotated with machine-readable instructions that spell out the particular permissions and restrictions for this media asset.
IPTC had decided not to create a Rights Expression Language completely on its own but to select an existing standard and extend it by requirements coming from the media industry. From the first version of RightsML on this standard builds on ODRL, the Open Digital Rights Language. As ODRL has evolved over time RightsML has aligned to ODRL changes. After the approval of ODRL as Recommendation by W3C in early 2018 the RightsML specification was synchonized with it.
RightsML versions 2.0 and later are based on the ODRL 2.2 Recommendation [ODRL22] (see Other standards) and comply with its specification of a Profile.
The RightsML standard …​
includes the full specification of the ODRL Information Model with the ODRL Core Vocabulary
defines an ODRL Profile which extends the ODRL Core Vocabulary by Actions for Rules, LeftOperands and RightsOperands for Constraints, functional roles of Parties and relationships of Assets. Many of these terms are available as members of the ODRL Common Vocabulary but must be adopted by a Profile to become valid in an ODRL Policy. Use the corresponding JSON-LD file at https://iptc.org/std/RightsML/odrl-profile/rightsml.jsonld
provides an OWL Ontology document for this profile (as required by the ODRL 2.2 Recommendation) at http://www.iptc.org/std/RightsML/2.0/RightsML_2.0-ontology.ttl
The specification of a RightsML property is shown in a generic table form using the following template.
Specification Table Template
What is specified by this row
A free-text defining the semantics of the specified concept
The name of the specified concept in English. This is semantically the same as the Label of the W3C Vocabulary
A URI as the globally unique identifier of the specified concept.
Any notes that apply to the end user of the specified concept.
This section extends the ODRL Recommendation [ODRL22] (see Other standards) by terms required by the media industry.
W3C ODRL Namespace
RightsML vocabulary
http://iptc.org/std/RightsML/2011-10-07/
RightsML ODRL Profile
https://iptc.org/std/RightsML/odrl-profile/
For the class Action (http://www.w3.org/ns/odrl/2/Action), used with Rules, these instances are defined.
Preserve a persistent copy of an asset so that it can be retrieved over a significant period of time.
http://iptc.org/std/RightsML/2011-10-07/archive
It may be bounded (i.e. have an end-date or end-time) or unbounded.
Preferred use as a Duty. May link to an Asset with the attribution information. May link to a Party with the role “attributedParty” function.
Preferred use as a Duty. The compensation may use different types of things with a value: (i) the thing is expressed by the value (term) of the Constraint name; (b) the value is expressed by operator, rightOperand, dataType and unit. Typically the assignee will compensate the assigner, but other compensation party roles may be used.
If used as a Duty, the assigner should be explicitly indicated as the party that is ensuring the exclusivity of the Rule.
For example, machine executable code or scripts used for running a visual display.
For example, to include a link to the Asset in a search engine.
Used as a duty, it may link to a Party with the role 'informedParty' function.
Used as a Duty to ensure that the Assigner or a another Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role “consentingParty” function.
To make duplicate copies of the Asset in any material form.
Used as a duty when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information.
For the class LeftOperand (http://www.w3.org/ns/odrl/2/LeftOperand), used with Constraints, these instances are defined.
Broader LeftOperand
Use with Actions including the target Asset in a larger media stream. The fragment part of a Media Fragment URI (https://www.w3.org/TR/media-frags/) may be used for the right operand. See the Left Operand realativeTemporalPosition. Example: The MP3 music file must be positioned between second 192 and 250 of the temporal length of a stream.
The date (and optional time and timezone) of exercising the action of the Rule. Right operand value MUST be an xsd:date or xsd:dateTime as defined by [xmlschema11-2].
The use of Timezone information is strongly recommended. The Rule may be exercised before (with operator lt/lteq) or after (with operator gt/gteq) the date(time) defined by the Right operand. Example: dateTime gteq 2017-12-31T06:00Z means the Rule can only be exercised after (and including) 6:00AM on the 31st Decemeber 2017 UTC time.
A time delay period prior to exercising the action of the Rule. The point in time triggering this period MAY be defined by another temporal Constraint combined by a Logical Constraint (utilising the odrl:andSequence operand). Right operand value MUST be an xsd:duration as defined by [xmlschema11-2].
Only the eq, gt, gteq operators SHOULD be used. Example: delayPeriod eq P60M indicates a delay of 60 Minutes before exercising the action.
A continuous elapsed time period which may be used for exercising of the action of the Rule. Right operand value MUST be an xsd:duration as defined by [xmlschema11-2].
Only the eq, lt, lteq operators SHOULD be used. See also Metered Time. Example: elpasedTime eq P60M indicates a total elapsed time of 60 Minutes.
Events are temporal periods of time, and operators can be used to signal before (lt), during (eq) or after (gt) the event. Example: May be taken during the “FIFA World Cup 2020” only.
The default values are the altitude of earth’s surface at this location and the WGS 84 datum.
A code value for the area and source of the code must be presented in the Right Operand. Example: the [iso3166] Country Codes or the Getty Thesaurus of Geographic Name
Example: the asset can only be translated into Greek. Must use [bcp47] codes for language values.
An accumulated amount of one to many metered time periods which were used for exercising the action of the Rule. Right operand value MUST be an xsd:duration as defined by [xmlschema11-2].
Only the eq, lt, lteq operators SHOULD be used. See also Elapsed Time. Example: meteredTime lteq P60M indicates an accumulated period of 60 Minutes or less.
A recurring period of time before the next execution of the action of the Rule. Right operand value MUST be an xsd:duration as defined by [xmlschema11-2].
Only the eq operator SHOULD be used. Example: timeInterval eq P7D indicates a recurring 7 day period.
See also Absolute Temporal Asset Position. Example: The MP3 music file must be positioned between the positions at 33% and 48% of the temporal length of a stream.
UnitOfCount
Note: Typically used with Duties to indicate the unit entity to be counted of the Action. Example: A duty to compensate and a unitOfCount constraint of 'perUser' would indicate that the compensation may be multiplied by the 'number of users'.
The value of a compensation expressed as a monetary amount. Right operand value MUST be an xsd:decimal.
http://iptc.org/std/RightsML/2011-10-07/compensationValue
May be used for other compensations than payments, e.g. barter agreements.
For the class RightOperand (http://www.w3.org/ns/odrl/2/RightOperand), used with Constraints, this instance is defined.
Policy Usage Time
This can be used to express constraints with a LeftOperand relative to the time the rule is exercised. Operators indicate before (lt, lteq), during (eq) or after (gt, gteq) the usage of the rule. Example: event lt policyUsage expresses that the identified event must have happened before the action of the rule is exercised.
For the function property (http://www.w3.org/ns/odrl/2/function) expressing relationships with Parties, these additonal sub-properties are defined.
For the relation property (http://www.w3.org/ns/odrl/2/relation), expressing relationships with Assets, this additonal sub-property is defined.
ODRL22
W3C Recommendation https://www.w3.org/TR/odrl-model and https://www.w3.org/TR/odrl-vocab
What showed an error
How the error was fixed