Contributions > Service Genres > Rate 1.1 Login
  Minimize

 
      Minimize
Name
 
  • Name: Rate
  • Alternate Name: Assign rating
Rationale
 

This Service Genre has been developed from multiple projects and outlines the functionalities and behaviours required of ratings services. Services of this Genre allow users to assign a subjective assessment to a data item within a collection, without altering the underlying data.

Classification
 
Domain(s) [ ] Learning & Teaching [ ] Research
[ ] Libraries
[ ] Administration
[ ] IT Services
[X] Common
Maturity [ ] Immature [X] Mature
Development Scale [ ] Isolated [X] Ubiquitous
Status [X] Approved [ ] Placeholder
[ ] Unapproved
[ ] Superseded
[ ] Withdrawn
Confidence Level [ ] High [X] Medium [ ] Low
Version
 
  • e-Framework Service Genre Version: v1.1
Version History
 
Version Date Author Description Organisation / Project
v1.1
2007-02-28  Phil Nicholls
Draft approved by eFIG
JISC
Description
 

This Service Genre describes the assignment of a subjective evaluation as a property of an object. For example, an object is reviewed, and a value from a range of ratings is applied. Ratings are typically numbers, with higher numbers indicating a more generous subjective evaluation. (E.g. A website which rates cinema films may give a particular film a rating of "4 stars").

The original object MAY be modified by the Rating service. The Rating MAY be applied to a proxy of the object. The Rating MAY be applied as metadata. Ratings can be applied from any subjective scale; common examples include confidence or popularity.

The data used to make up the set from which ratings are drawn (the Rating Set) MUST be finite, and MUST be ordered. If neither of these conditions are met, a rating has not been applied (perhaps an annotation or classification has been instead). Ratings SHOULD be attached as a distinct property of an object. (E.g. The property could be "satisfaction" and the allowed Ratings could be "1", "2", "3").

Ratings MAY be made anonymously. Ratings MAY be accompanied by a comment.

As defined the Rate Service Genre is not access controlled. Any client may attempt to contact a Rate service end point. There are no authentication controls. The service end point is responsible for determining which individual objects can be rated and which clients can assign ratings to existing objects.

Functionality
 

The Rate Service Genre supports functions that enable the assignment and alteration of ratings, and calculation of average rating for an object.

  • Assign Rating - allows a requester to assign rating data to an existing object. The data assigned MAY include a "comment", but SHOULD include a metric representing the 'value' of the property being rated. Rating Services SHOULD store the rating permanently within the context of the object that has been rated.
  • Alter Rating - allows a requester to edit an existing rating on an object.
  • Delete Rating - allows a requester to remove an existing rating from an object.
  • Calculate Average - calculates an average rating from all applied ratings to an object. Rating services may offer different types of averages (modal, median, mean).

No other functionality is defined. The functionality that is defined MAY be extended.

Usage Scenarios
 

 

Applicability
 

Ratings SHOULD be used when an ordered bounded value is to be assigned to an object.

Ratings MAY be applied to collections of objects as well individual objects.

Ratings SHOULD NOT be used if an unbounded value is to be assigned to an object. Annotation SHOULD be used instead.

Ratings SHOULD NOT be used if an unordered value is to be assigned to an object. Classify SHOULD be used instead.

Requests & Behaviours
 

Requests SHOULD be implemented to enable all functionality.

Assign Rating SHALL meet the following conditions:

  • The Request SHOULD specify:
    • The target object to be rated
    • The Property against which the rating is to be applied
    • A value from the Rating Set to be applied
  • The Request MAY Specify:
    • A comment to be applied to the rating
    • The author of the Rating

Alter Rating SHALL meet the following conditions:

  • The Request SHOULD specify:
    • The target Property to be altered
    • A new value from the Rating Set which is to be the new rating
  • The Request MAY specify:
    • A comment to be applied to the new Rating
    • The author of the new rating

Delete Rating SHALL meet the following conditions:

  • The Request SHOULD specify the target Property to be deleted

Calculate Average SHALL meet the following conditions:

  • The Request SHOULD specify:
    • The target object for which an average rating is to be calculated
    • The Property for which the average rating is to be calculated
  • The Request MAY specify the type of average to be calculated
  • The Response SHOULD specify the calculated average rating for the target object

Responses SHOULD:

  • Indicate any error conditions (such as the Rating not being accepted)
Use & Interactions
 

Individual Service Expressions SHOULD provide models showing how clients interact with service interfaces.

Structure
 

 

Applicable Standards
 

None

Design Decisions and Tradeoffs
 

Authorisation SHOULD be considered when specialising this Service Genre. Specifically, whether owners of the original object are authorised to delete and edit Ratings. Additionally, Service Expressions should consider whether Ratings can be modified by other Raters.

Management of the Ratings set SHOULD be specified by the Service Expression or SUM which incorporates Rating.

The management of which objects can be rated SHOULD be considered by the Service Expression or SUM which incorporates Rating.

Implementation Guidance and Dependencies

 
Known Uses
 

 

Related Service Usage Models (SUMs)
 

 

Related CORE SUMs
 

 


Intellectual Property Rights: This document is governed by the e-Framework Intellectual Property Rights Statement [http://www.e-framework.org/Default.aspx?tabid=738]. © Copyright, JISC, DEST & e-Framework Partners 2007. This document may be used under the Creative Commons Attribution-ShareAlike 2.5 Australia License [http://creativecommons.org/licenses/by-sa/2.5/au/].


The words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC 2119].

The Service Genre description uses e-Framework Service Genre description elements as of 2006-12-09, updated to include draft e-Framework service classifications. Other terms, e.g., client, provider, and resource, are used as defined in the e-Framework.

 
    Minimize
Unless otherwise noted material from the e-Framework website can be downloaded for your own use under a Creative Commons Attribution-ShareAlike 2.5 Australia License
CreativeCommons-by-sa.png
 
Thursday, August 21, 2008
Copyright e-Framework Partners 2006 - 2008

Terms and Conditions

Privacy Statement