OASIS Rights Language TC

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200203/msg00001.html

At the first meeting of the Rights Language TC on 21 May 2002 the TC approved a clarified charter, as minuted at http://www.oasis-open.org/committees/rights/documents/rltc/minutes/RLTC%20Minutes%2020020521.doc

The charter was further clarified at a meeting on 12 September 2002, as minuted at http://www.oasis-open.org/committees/rights/documents/rltc/minutes/RLTC%20%20Minutes%2020020912.doc

The charter for this TC is as follows.

Name

OASIS Rights Language Technical Committee.

Statement of Purpose

The purpose of the Rights Language TC is to:

  1. Define the industry standard for a rights language that supports a wide variety of business models and has an architecture that provides the flexibility to address the needs of the diverse communities that have recognized the need for a rights language. The language needs to be:
    • Comprehensive: Capable of expressing simple and complex rights
    • Generic: Capable of describing rights for any type of digital content or service
    • Precise: Communicates precise meaning to all components of the system
    • Interoperable: Comprehends it is part of an integrated system
    • Agnostic: To platform, media type or format
  2. Use XrML as the basis in defining the industry standard rights language in order to maximize continuity with ongoing standards efforts. This TC welcomes the contribution of other requirements, specifications or ideas related to rights languages for consideration in making additions or subtractions to enhance the language.
  3. Define a governance and language extension development process that maintains and evolves the language while minimizing the negative impact of change on all stakeholders.
  4. Define the relationship with other complementary standards efforts within OASIS (e.g. SAML). Liaison with standards bodies external to OASIS that are working on complementary technologies (e.g. security, PKI, web services).
  5. Define relationship and establish liaisons with standards bodies that have identified the need for a rights language. This activity will promote the maintenance of a Core architecture that provides the basis for interoperability across different content domains as well as broader applicability of the tools and applications that create and consume rights expressions.

List of Deliverables

  1. To release the rights language Schema with supporting implementation information.
  2. To develop and execute governance process for managing the continuing improvements to the language.
  3. To provide liaisons to other complementary standards bodies.
  4. Policies defining the creation of extensions to the language.
  5. Policies defining the creation of subsets of the language.
  6. Policies addressing mapping to other specifications.
  7. Definition of conformance criteria.
  8. Definition of common methods for integration of the rights language with other standards, for example
    • metadata standards,
    • content/service identification standards,
    • content referencing standards,
    • authentication,
    • authorization,
    • crypto and PKI standards, and
    • web services.

The deliverables will be accomplished in 3 Phases:

Phase 1: Requirements Gathering and TC Structure Development (estimate 3 months)

  • Enhance language specification taking requirements from other standards initiatives, government and regulatory bodies, and content/web service value chain participants such as end users, content/web service owners, technology providers, and service providers.
  • Develop Governance Process for management of the language.

Phase 2: Language Development & Initial Language Release (estimate 3 months)

  • Develop use cases and scenarios.
  • Develop integration models to other standards initiatives.
  • Develop sample value chain models employing various features of the language.
  • Develop/release working draft of the language for review.
  • Release the language with supporting implementation information and guides based on feedback.

Phase 3: Evergreen Process - ongoing

  • Develop/execute process for continuous improvement of the language based upon guidelines developed in Phase 1.
  • Continue to provide liaisons to complementary standards initiatives.

 

TOP OF PAGE