RE: Common feature sets: scenarios, term
[email protected] (Reynolds Franklin NRC/Boston)
| Newsgroups | gmane.ietf.medfree |
|---|---|
| Organization | Nokia Telecommunications |
| Message-ID | <[email protected]> |
>Scenarios: >---------- > >(S1) [per W3C CC/PP paper] providing a shorthand mechanism to capture the >common characteristics of some identifiable device or system, which may >then be augmented by additional information. If such a feature set is >considered an appropriate unit for caching, this can reduce the need to >transfer *all* characteristics, only those that are different from some >baseline set. > >(S2) [per <draft-ietf-fax-feature-schema-05>, Appendix B] providing a means >to indicate standard feature sets. > >(S3) Providing an expression of corporate policy with respect to >media capabilities. > >(S4) Consider a web server offering several variants of a resource, each >having several features in common and a relatively small number of key >differences. It is desirable that the common features can be described >just once, and the variants can simply describe their differences from that >common set. > Practically speaking, I don't think I understand (S3). Why would anyone want to provide a corporate policy with respect to media capabilities? What would be a reasonable example of such a policy? Franklin Reynolds Nokia Research Center