As per Relevance of the word copyright, we have this rfc below:
Network Working Group G.
Request for Comments: 2738 Content
Updates: 2533 December 1999
Category: Standards
Corrections to "A Syntax for Describing Media Feature Sets
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
In RFC 2533, "A Syntax for Describing Media Feature Sets",
expression format is presented for describing media
capabilities using simple media feature tags
This memo contains two corrections to that specification: one
an error in the formal syntax specification, and the other fixes
error in the rules for reducing feature comparison predicates
Table of
1. Introduction ............................................2
1.1 Terminology and document conventions 2
1.2 Discussion of this document 2
2. Correction to feature expression syntax .................3
3. Correction to feature set matching reduction rules ......3
4. Security Considerations .................................4
5. References ..............................................4
6. Author's Address ........................................4
7. Full Copyright Statement ................................5
Klyne Standards Track [Page 1]
RFC 2738 Corrections to Syntax for Media Features December 1999
1.
In RFC 2533, "A Syntax for Describing Media Feature Sets" [1],
expression format is presented for describing media
capabilities using simple media feature tags. This provides a
for message handling agents to describe the media feature content
messages that they can handle. That memo also describes an
for finding the common capabilities expressed by two
feature expressions
This memo contains two corrections to that specification: one
an error in the formal syntax specification, and the other fixes
error in the feature set matching algorithm, in the rules
reducing feature comparison predicates
The first of these corrections affects the normative content of
2533; the second affects non-normative content
1.1 Terminology and document
This specification uses syntax notation and conventions described
RFC 2234, "Augmented BNF for Syntax Specifications: ABNF" [2].
NOTE: Comments like this provide additional
information about the rationale behind this document.
information is not needed for building a
implementation, but may help those who wish to understand
design in greater depth
1.2 Discussion of this
Discussion of this document should take place on the
negotiation and media feature registration mailing list hosted by
Internet Mail Consortium (IMC).
Please send comments regarding this document to
ietf-medfree@imc.
To subscribe to this list, send a message with the body 'subscribe
to "ietf-medfree-request@imc.org".
To see what has gone on before you subscribed, please see the
list archive at
http://www.imc.org/ietf-medfree
Klyne Standards Track [Page 2]
RFC 2738 Corrections to Syntax for Media Features December 1999
2. Correction to feature expression
In section 4.1, RFC 2533 defines the syntax for a "set" expression
follows
set = attr "=" "[" setentry *( "," setentry ) "]"
setentry = value "/"
The production for 'setentry' should read
setentry = value /
That is: the '/' character is not a character literal, but
two alternative forms for 'setentry'. This corrected syntax
the set expression examples given in section 4.2.5 of RFC 2533,
as
( width=[3,4,6..17/2] )
3. Correction to feature set matching reduction
In section 5.8.2, "Rules for simplifying unordered values", RFC 2533
lists the following rewriting rules for simplifying feature
comparisons with unordered values
(LE f a) (LE f b) --> (LE f a), a=
FALSE,
(LE f a) (GE f b) --> FALSE, a!=
(LE f a) (NL f b) --> (LE f a) a!=
FALSE,
(LE f a) (NG f b) --> (LE f a), a!=
FALSE,
The second of these rules is incomplete, and should read
(LE f a) (GE f b) --> (LE f a), a=
FALSE,
NOTE: implementation experience with these rules
suggested a revised feaure set matching algorithm with
more useful set of simplification rules. Apart from
change noted above, the algorithm given in RFC 2533
been implemented and shown to work as intended, but
results generated are not always in the most
form. It is planned to test and publish a
algorithm at a future date
Klyne Standards Track [Page 3]
RFC 2738 Corrections to Syntax for Media Features December 1999
4. Security
Security considerations are discussed in RFC 2533 [1] and
documents
5.
[1] Klyne, G., "A Syntax for Describing Media Feature Sets",
2533, March 1999.
[2] Crocker, D. and P. Overell, "Augmented BNF for
Specifications: ABNF", RFC 2234, November 1997.
6. Author's
Graham
Content Technologies Ltd
1220
Arlington Business
Reading, RG7 4
United
Phone: +44 118 930 1300
Fax: +44 118 930 1301
EMail: GK@ACM.
Klyne Standards Track [Page 4]
RFC 2738 Corrections to Syntax for Media Features December 1999
7. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Klyne Standards Track [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
