An Introduction to the ACAP Dataset Model
draft-ietf-acap-dataset-model-01
| Document | Type |
Expired Internet-Draft
(acap WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ryan Troll | ||
| Last updated | 1999-03-29 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | anonymous%20IMAP%3A%20cyrus.andrew.cmu.edu%3Aarchive.ietf-acap | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
The ACAP [ACAP] Dataset Model is very extensible, and allows applications to easily share options and information. With this extensibility comes a complexity that an application designer must fully understand in order to interoperate while using ACAP. This document will help the reader understand and visualize the ACAP hierarchy, come to a better understanding of how to design and access ACAP datasets, and understand the relationship between attributes, entries, datasets, and dataset classes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)