This is an archive of an inactive wiki and cannot be modified.

This is one of the possible Use Cases.

1. Abstract

Examining consistency between policy & preference pairs is becoming a common task for every kind of web transactions. Rules are useful for describing and exchanging complex policies and preferences.

2. Status

Proposed by MinsuJang

3. Links to Related Use Cases

4. Relationship to OWL/RDF Compatibility

5. Examples of Rule Platforms Supporting this Use Case

6. Benefits of Interchange

7. Requirements on the RIF

8. Breakdown

8.1. Actors and their Goals

8.2. Main Sequence

  1. Data Owner writes up or obtains a preference profile from Preference Publisher, publishes its data along with the preference profile to Service Provider.

  2. Data User writes up her own set of policies or obtains ready-made one from Policy Publisher.

  3. Data User tries to access the data of her interest via Service Provider by sending data request messages along with her policies.

  4. Service Provider calculates the commitment between the policies from Data User and the preferences from Data Owner, and provides the requested data if the commitment is positive.

9. Narratives

9.1. Accessing Location Information

Policy-Preference computing can occur in any controlled data access scenario. One representative setting is the scenario of serving location information as described as follows:

The actors are:

And the narrative is:

10. Commentary

I find preferences and policies everywhere on the web, e.g. P3P, CC/PP, location based service frameworks etc. Interchangeable rules will become an essential tool for formally describing and processing policies and preferences.