idnits 2.17.1
draft-snell-atompub-bidi-01.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** It looks like you're using RFC 3978 boilerplate. You should update this
to the boilerplate described in the IETF Trust License Policy document
(see https://trustee.ietf.org/license-info), which is required now.
-- Found old boilerplate from RFC 3978, Section 5.1 on line 14.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 247.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 224.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 231.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 237.
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to RFC
4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== No 'Intended status' indicated for this document; assuming Proposed
Standard
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (September 2006) is 6432 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
-- Possible downref: Non-RFC (?) normative reference: ref. 'UNI9'
-- Possible downref: Non-RFC (?) normative reference: ref. 'UNICODE'
Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 9 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 Network Working Group J. Snell
3 Internet-Draft September 2006
4 Expires: March 5, 2007
6 Atom Bidirectional Attribute
7 draft-snell-atompub-bidi-01.txt
9 Status of this Memo
11 By submitting this Internet-Draft, each author represents that any
12 applicable patent or other IPR claims of which he or she is aware
13 have been or will be disclosed, and any of which he or she becomes
14 aware will be disclosed, in accordance with Section 6 of BCP 79.
16 Internet-Drafts are working documents of the Internet Engineering
17 Task Force (IETF), its areas, and its working groups. Note that
18 other groups may also distribute working documents as Internet-
19 Drafts.
21 Internet-Drafts are draft documents valid for a maximum of six months
22 and may be updated, replaced, or obsoleted by other documents at any
23 time. It is inappropriate to use Internet-Drafts as reference
24 material or to cite them other than as "work in progress."
26 The list of current Internet-Drafts can be accessed at
27 http://www.ietf.org/ietf/1id-abstracts.txt.
29 The list of Internet-Draft Shadow Directories can be accessed at
30 http://www.ietf.org/shadow.html.
32 This Internet-Draft will expire on March 5, 2007.
34 Copyright Notice
36 Copyright (C) The Internet Society (2006).
38 Abstract
40 This document updates the Atom Syndication Format by adding a new
41 attribute that may be used to indicate the base directionality of
42 directionally-neutral characters.
44 Table of Contents
46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
47 1.1. Namespace . . . . . . . . . . . . . . . . . . . . . . . . . 3
48 1.2. Notational Conventions . . . . . . . . . . . . . . . . . . 3
49 2. The "dir" Attribute . . . . . . . . . . . . . . . . . . . . . . 3
50 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
51 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
52 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
53 5.1. Normative References . . . . . . . . . . . . . . . . . . . 5
54 5.2. Informative References . . . . . . . . . . . . . . . . . . 6
55 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 6
56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
57 Intellectual Property and Copyright Statements . . . . . . . . . . 8
59 1. Introduction
61 This document updates the Atom Syndication Format [RFC4287] by adding
62 a new 'dir' attribute that can be used to define the base
63 directionality of directionally-neutral characters contained within
64 an Atom document.
66 1.1. Namespace
68 The XML Namespaces URI [W3C.REC-xml-names-19990114] for the Atom
69 Syndication Format is:
70 http://www.w3.org/2005/Atom
72 1.2. Notational Conventions
74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
76 document are to be interpreted as described in BCP 14, [RFC2119].
78 The Atom Syndication Format [RFC4287] is specified using terms from
79 the XML Infoset [W3C.REC-xml-infoset-20040204]. This specification
80 uses a shorthand form for two commons terms: The phrase "Information
81 Item" is omitted when naming Element and Attribute Information Items.
82 Therefore, when this specification uses the term "element," it is
83 referring to an Element Information Item in Infoset terms. Likewise,
84 when it uses the term "attribute," it is referring to an Attribute
85 Information Item.
87 Portions this specification are illustrated with fragments of a non-
88 normative RELAX NG Compact schema [RELAXNG]. However, the text of
89 this specification provides the sole definition of conformance.
91 2. The "dir" Attribute
93 The "dir" attribute specifies the base direction of directionally-
94 neutral text [UNICODE]. Possible values for the attribute are "ltr"
95 and "rtl" indicating "left-to-right" and "right-to-left"
96 respectively, "lro" and "rlo" indicating explicit "left-to-right" and
97 "right-to-left" overrides, or an empty string indicating that no
98 base-direction is specified. If the "dir" attribute is not
99 specified, the value is assumed to be an empty string. The attribute
100 can appear anywhere in an Atom document, except where it is
101 explicitly forbidden.
103 atomCommonAttributes =
104 attribute xml:base { atomUri }?,
105 attribute xml:lang { atomLanguageTag }?,
106 attribute dir { "ltr" | "rtl" | "lro" | "rlo" | "" }?,
107 undefinedAttribute*
109 The direction specified by "dir" applies to elements and attributes
110 whose values are specified as being "Language-Sensitive" as defined
111 by Section 2 of [RFC4287]. The attribute is inherited by descendent
112 elements and may be overridden.
114 Example atom:feed with right-to-left directionality
116
117
118 ٹٺٻ
119 ...
120
122 If an Atom document contains any right-to-left characters, the
123 Unicode Bidirectional Algorithm [UNI9] MUST be used to render that
124 text. Because consumers of Atom documents vary broadly in the way
125 they display text, the "ltr" and "rtl" values do not necessarily open
126 an additional level of embedding with respect to the bidirectional
127 algorithm. Consuming applications that render bidirectional text are
128 responsible for determining the appropriate level of embedding.
130 The "lro" and "rlo" values override the inherent directionality of
131 characters as defined by [UNICODE]. When used, affected text MUST be
132 rendered as if preceded by either Unicode character U+202D (left-to-
133 right override) or U+202E (right-to-left override) and followed by
134 U+202C (pop directional formatting).
136 When Atom Text Constructs or the atom:content elements contain
137 bidirectional text and the type attribute is set to either "html" or
138 "xhtml", the bidirectional markup mechanisms specific to each format
139 SHOULD be used. The value of the "dir" attribute does define the
140 base directionality of Language-Sensitive text within Text Constructs
141 and atom:content elements regardless of the value of the type
142 attribute.
144 Example atom:feed with bidirectional XHTML:
146
147
148
149
152
153 ...
154
156 The Unicode bidirectional control characters MAY also be used within
157 attributes and element values to indicate the directionality of text.
158 Implementers are reminded that unexpected results could occur when
159 using both the "dir" attribute and the Unicode control characters
160 within a single document.
162 3. Security Considerations
164 The security considerations discussed in [RFC4287] Section 8 apply.
166 4. IANA Considerations
168 No IANA actions are required by this document.
170 5. References
172 5.1. Normative References
174 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
175 Requirement Levels", BCP 14, RFC 2119, March 1997.
177 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
178 Syndication Format", RFC 4287, December 2005.
180 [UNI9] Davis, M., "The Bidirectional Algorithm", March 2004.
182 [UNICODE] International Organization for Standardization, "ISO/IEC
183 10646:2003: Information Technology - Universal Multiple-
184 Octet Coded Character Set (UCS)", December 2003.
186 [W3C.REC-xml-infoset-20040204]
187 Cowan, J. and R. Tobin, "XML Information Set (Second
188 Edition)", World Wide Web Consortium Recommendation REC-
189 xml-infoset-20040204, February 2004,
190 .
192 [W3C.REC-xml-names-19990114]
193 Layman, A., Bray, T., and D. Hollander, "Namespaces in
194 XML", World Wide Web Consortium Recommendation REC-xml-
195 names-19990114, January 1999,
196 .
198 5.2. Informative References
200 [RELAXNG] Clark, J., "RELAX NG Compact Syntax", December 2001, .
204 Appendix A. Acknowledgements
206 TBD
208 Author's Address
210 James M Snell
212 Email: jasnell@gmail.com
213 URI: http://www.snellspace.com
215 Intellectual Property Statement
217 The IETF takes no position regarding the validity or scope of any
218 Intellectual Property Rights or other rights that might be claimed to
219 pertain to the implementation or use of the technology described in
220 this document or the extent to which any license under such rights
221 might or might not be available; nor does it represent that it has
222 made any independent effort to identify any such rights. Information
223 on the procedures with respect to rights in RFC documents can be
224 found in BCP 78 and BCP 79.
226 Copies of IPR disclosures made to the IETF Secretariat and any
227 assurances of licenses to be made available, or the result of an
228 attempt made to obtain a general license or permission for the use of
229 such proprietary rights by implementers or users of this
230 specification can be obtained from the IETF on-line IPR repository at
231 http://www.ietf.org/ipr.
233 The IETF invites any interested party to bring to its attention any
234 copyrights, patents or patent applications, or other proprietary
235 rights that may cover technology that may be required to implement
236 this standard. Please address the information to the IETF at
237 ietf-ipr@ietf.org.
239 Disclaimer of Validity
241 This document and the information contained herein are provided on an
242 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
243 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
244 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
245 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
246 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
247 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
249 Copyright Statement
251 Copyright (C) The Internet Society (2006). This document is subject
252 to the rights, licenses and restrictions contained in BCP 78, and
253 except as set forth therein, the authors retain all their rights.
255 Acknowledgment
257 Funding for the RFC Editor function is currently provided by the
258 Internet Society.