Composing Presence Information
draft-schulzrinne-simple-composition-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Henning Schulzrinne | ||
| Last updated | 2006-06-29 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Composition creates a presence document from multiple components published by one or more sources. This document identifies sources of information that a compositor might draw on presence composition and describes steps for composition. The composing function can be complex, so we intentionally restrict the discussion to cases that are likely to be common across many users of presence systems. We present an XML format for specifying a composition policy, based on our discussion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)