1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
|
<pre>Internet Engineering Task Force (IETF) J. Snell
Request for Comments: 6721 September 2012
Category: Standards Track
ISSN: 2070-1721
<span class="h1">The Atom "deleted-entry" Element</span>
Abstract
This specification adds mechanisms to the Atom Syndication Format
that publishers of Atom Feed and Entry documents can use to
explicitly identify Atom entries that have been removed.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6721">http://www.rfc-editor.org/info/rfc6721</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Snell Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Notational Conventions ..........................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. The at:deleted-entry Element ....................................<a href="#page-2">2</a>
<a href="#section-4">4</a>. Deleted Entry Document ..........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Digital Signatures ..............................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. Encryption ......................................................<a href="#page-7">7</a>
<a href="#section-7">7</a>. Security Considerations .........................................<a href="#page-7">7</a>
<a href="#section-8">8</a>. IANA Considerations .............................................<a href="#page-8">8</a>
<a href="#section-9">9</a>. Acknowledgements ................................................<a href="#page-9">9</a>
<a href="#section-10">10</a>. Normative References ...........................................<a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Atom [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>] is an XML-based document format that describes lists
of related information known as "feeds". Feeds are composed of a
number of items known as "entries", each with an extensible set of
attached metadata. The primary use case that Atom addresses is the
syndication of Web content, such as weblogs and news headlines to Web
sites as well as directly to user agents.
In the base Atom format, when an entry is removed from a feed but a
consumer has already received and processed that entry, perhaps
adding it to a local cache or display, there is no mechanism for
determining that the entry has been removed. This specification adds
a mechanism to the Atom Syndication Format that publishers of Atom
Feed and Entry documents can use to explicitly identify Atom entries
that have been removed. Atom consumers can use that information to
adjust such things as their document cache and user interfaces.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Notational Conventions</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
This specification uses XML Namespaces [<a href="#ref-W3C.REC-xml-names-19990114">W3C.REC-xml-names-19990114</a>]
to uniquely identify XML element names. It uses the following
namespace prefix for the indicated namespace URI:
"at": "<a href="http://purl.org/atompub/tombstones/1.0">http://purl.org/atompub/tombstones/1.0</a>"
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The at:deleted-entry Element</span>
The at:deleted-entry element represents an Atom Entry that has been
removed.
<span class="grey">Snell Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
deletedEntry =
element at:deleted-entry {
atomCommonAttributes,
attribute ref { atomUri },
attribute when { atomDateConstruct },
( element at:by { atomPersonConstruct }?
& element at:comment { atomTextConstruct }?
& element atom:link { atomLink }*
& element atom:source { atomSource }?
& anyElement* )
}
The at:deleted-entry element MUST contain a "ref" attribute whose
value specifies the value of the atom:id of the entry that has been
removed.
The at:deleted-entry element MUST contain a "when" attribute whose
value is an [<a href="./rfc3339" title=""Date and Time on the Internet: Timestamps"">RFC3339</a>] "date-time", specifying the instant the entry
was removed. An uppercase "T" character MUST be used to separate
date and time, and an uppercase "Z" character MUST be present in the
absence of a numeric time zone offset.
The at:deleted-entry element MAY contain one at:by element used to
identify the entity that removed the entry. The at:by element is an
Atom Person Construct as defined by <a href="./rfc4287#section-3.2">Section 3.2 of [RFC4287]</a>.
The at:deleted-entry element MAY contain one at:comment element whose
value provides additional, language-sensitive information about the
deletion operation. The atom:comment element is an Atom Text
Construct as defined by <a href="./rfc4287#section-3.1">Section 3.1 of [RFC4287]</a>.
The at:deleted-entry element MAY contain any number of atom:link
elements as specified by <a href="./rfc4287#section-4.2.7">Section 4.2.7 of [RFC4287]</a>.
The at:deleted-entry element MAY contain one atom:source element as
defined by <a href="./rfc4287#section-4.2.11">Section 4.2.11 of [RFC4287]</a>. Within the context of an at:
deleted-entry element, the atom:source element is intended to allow
the aggregation of at:deleted-entry elements from different feeds
while retaining information about an at:deleted-entry's source Feed.
When an at:deleted-entry element appears in a Feed document other
than its source feed or when an at:deleted-entry element that has a
source Feed document is used in the context of a Deleted Entry
Document, it MUST contain an atom:source element.
An Atom feed MAY contain any number of at:deleted-entry elements, but
MUST NOT contain more than one with the same combination of ref and
when attribute values.
<span class="grey">Snell Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
<feed xmlns="http://www.w3.org/2005/Atom"
xmlns:at="http://purl.org/atompub/tombstones/1.0">
...
<!-- Minimal deleted-entry -->
<at:deleted-entry
ref="tag:example.org,2005:/entries/1"
when="2005-11-29T12:11:12Z"/>
<!-- Extended deleted-entry -->
<at:deleted-entry
ref="tag:example.org,2005:/entries/2"
when="2005-11-29T12:11:12Z">
<at:by>
<name>John Doe</name>
<email>jdoe@example.org</email>
</at:by>
<at:comment>Removed comment spam</at:comment>
</at:deleted-entry>
...
</feed>
An Atom feed MAY contain atom:entry elements and at:deleted-entry
elements sharing the same atom:id value. In such cases, the
implication is that the particular atom:entry has either been
published to the feed and then subsequently removed, or that a
previously removed entry has been republished to the feed following a
previous deletion. To determine which condition applies, the
Processor needs to compare the value of the at:deleted-entry
element's when attribute to the value of the corresponding atom:entry
element's atom:updated value:
o If the when attribute specifies a value equal to or more recent
than that specified by the atom:updated element, the atom:entry is
assumed to have been published and then subsequently removed.
Processors SHOULD ignore the older atom:entry element.
o If the when attribute specifies a value older than that specified
by the atom:updated element, the atom:entry is assumed to have
been republished to the feed following a prior removal.
Processors SHOULD ignore the older at:deleted-entry element.
Publishers of feeds containing at:deleted-entry elements should note
that the at:deleted-entry element is advisory in nature only, and it
may be ignored by Atom Processors. The presence of an at:deleted-
entry element does not guarantee that the atom:entry to which it is
referring will no longer be available. For example, if an entry was
published to a feed document that was published and processed
yesterday by an aggregator application, and then is subsequently
<span class="grey">Snell Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
deleted today with a corresponding at:deleted-entry element added to
the feed as a signal that the entry was deleted, there is no
guarantee that the aggregator application will pay any attention to
the at:deleted-entry element during subsequent processing operations.
Elements and attributes from any XML vocabulary MAY be used within an
at:deleted-entry element. Processors encountering such markup MUST
NOT stop processing or signal an error. It might be the case that
the Processor is able to process the foreign markup correctly and
does so. When unknown markup is encountered as a child of at:
deleted-entry, Processors MAY bypass the markup and any textual
content but MUST NOT change their behavior as a result of the
markup's presence.
This specification allows the use of Internationalized Resource
Identifiers (IRIs) [<a href="./rfc3987" title=""Internationalized Resource Identifiers (IRIs)"">RFC3987</a>] in precisely the same manner specified
in <a href="./rfc4287#section-2">Section 2 of [RFC4287]</a>.
Any element defined by this specification MAY have an xml:base
attribute [<a href="#ref-W3C.REC-xmlbase-20010627">W3C.REC-xmlbase-20010627</a>]. When xml:base is used, it
serves the function described in <a href="./rfc3986#section-5.1.1">Section 5.1.1 of [RFC3986]</a>,
establishing the base URI (or IRI) for resolving any relative
references found within the effective scope of the xml:base
attribute.
Any element defined by this specification MAY have an xml:lang
attribute, whose content indicates the natural language for the
element and its descendents. Requirements regarding the content and
interpretation of xml:lang are specified in XML 1.0
[<a href="#ref-W3C.REC-xml-20040204">W3C.REC-xml-20040204</a>], Section 2.12.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Deleted Entry Document</span>
A "Deleted Entry Document" represents exactly one at:deleted-entry
element outside the context of an Atom feed. Its root is the at:
deleted-entry element.
namespace at = "<a href="http://purl.org/atompub/tombstones/1.0">http://purl.org/atompub/tombstones/1.0</a>"
start = at:deleted-entry
Deleted Entry Documents are specified in terms of the XML Information
Set, serialized as XML 1.0 [<a href="#ref-W3C.REC-xml-20040204">W3C.REC-xml-20040204</a>] and identified with
the "application/atomdeleted+xml" media type. Deleted Entry
Documents MUST be well-formed XML. This specification does not
define a DTD for Deleted Entry Documents, and hence does not require
them to be valid (in the sense used by XML).
<span class="grey">Snell Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Digital Signatures</span>
The at:deleted-entry element MAY have an Enveloped Signature, as
described by XML-Signature and Syntax Processing
[<a href="#ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>].
Processors MUST NOT reject an at:deleted-entry containing such a
signature because they are not capable of verifying it; they MUST
continue processing and MAY inform the user of their failure to
validate the signature.
In other words, the presence of an element with the namespace URI
"<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>" and a local name of "Signature"
as a child of the document element MUST NOT cause a Processor to fail
merely because of its presence.
Section 6.5.1 of [<a href="#ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>] requires support for
Canonical XML [<a href="#ref-W3C.REC-xml-c14n-20010315">W3C.REC-xml-c14n-20010315</a>]. However, many
implementers do not use it because signed XML documents enclosed in
other XML documents have their signatures broken. Thus, Processors
that verify signed at:deleted-entry elements MUST be able to
canonicalize with the exclusive XML canonicalization method
identified by the URI "<a href="http://www.w3.org/2001/10/xml-exc-c14n#">http://www.w3.org/2001/10/xml-exc-c14n#</a>", as
specified in Exclusive XML Canonicalization
[<a href="#ref-W3C.REC-xml-exc-c14n-20020718">W3C.REC-xml-exc-c14n-20020718</a>].
Intermediaries such as aggregators may need to add an atom:source
element to an at:deleted-entry that does not contain its own atom:
source element. If such an entry is signed, the addition will break
the signature. Thus, a publisher of individually signed at:deleted-
entry's should strongly consider adding an atom:source element to
those elements before signing them. Implementers should also be
aware of the issues concerning the use of markup in the "xml:"
namespace as it interacts with canonicalization.
Section 4.4.2 of [<a href="#ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>] requires support for
Digital Signature Algorithm (DSA) signatures and recommends support
for RSA signatures. However, because of the much greater popularity
in the market of RSA versus DSA, Atom Processors that verify signed
Atom Documents MUST be able to verify RSA signatures; they do not
need be able to verify DSA signatures. Due to security issues that
can arise if the keying material for the message authentication code
(MAC) is not handled properly, Atom Documents SHOULD NOT use MACs for
signatures.
<span class="grey">Snell Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Encryption</span>
The root of a Deleted Entry Document (the at:deleted-entry element)
MAY be encrypted using the mechanisms described by XML Encryption
Syntax and Processing [<a href="#ref-W3C.REC-xmlenc-core-20021210">W3C.REC-xmlenc-core-20021210</a>].
Section 5.1 of [<a href="#ref-W3C.REC-xmlenc-core-20021210">W3C.REC-xmlenc-core-20021210</a>] requires support of
TripleDES, AES-128, and AES-256. Processors that decrypt Deleted
Entry Documents MUST be able to decrypt with AES-128 in Cipher Block
Chaining (CBC) mode.
Encryption based on [<a href="#ref-W3C.REC-xmlenc-core-20021210">W3C.REC-xmlenc-core-20021210</a>] does not ensure
integrity of the original document. There are known cryptographic
attacks in which someone who cannot decrypt a message can still
change bits in a way in which part or all the decrypted message makes
sense but has a different meaning. Thus, Processors that decrypt
Deleted Entry Documents SHOULD check the integrity of the decrypted
document by verifying the hash in the signature (if any) in the
document, or by verifying a hash of the document within the document
(if any).
When a Deleted Entry Document is to be both signed and encrypted, it
is generally a good idea to first sign the document and then encrypt
the signed document. This provides integrity to the base document
while encrypting all the information, including the identity of the
entity that signed the document. Note that if MACs are used for
authentication, the order MUST be that the document is signed and
then encrypted, and not the other way around. Further, if MACs are
used along with a symmetric encryption algorithm, the same key SHOULD
NOT be used in the generation of the MAC and the encryption.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
As specified in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>], Atom Processors should be aware of the
potential for spoofing attacks in which an attacker publishes atom:
entry or atom:deleted-entry elements using the same atom:id values as
entries from other Atom feeds. An attacker may attempt to trick an
application into believing that a given entry has either been removed
from or added to a feed. To mitigate this issue, Atom Processors are
advised to ignore at:deleted-entry elements referencing entries that
have not previously appeared within the containing Feed document and
should take steps to verify the origin of the Atom feed before
considering the entries to be removed.
The at:deleted-entry element can be encrypted and signed using
[<a href="#ref-W3C.REC-xmlenc-core-20021210">W3C.REC-xmlenc-core-20021210</a>] and [<a href="#ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>],
respectively, and is subject to the security considerations implied
by their use.
<span class="grey">Snell Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
Digital signatures provide authentication and message integrity with
proof of origin. Encryption provides data confidentiality.
An application supporting the use of digitally signed atom:entry and
at:deleted-entry elements should be aware of the potential issues
that could arise if an at:deleted-entry element that indicates the
deletion of an atom:entry element has been signed using a different
key than what was used to sign the atom:entry, or if an unsigned at:
deleted-entry is used to indicate the deletion of a signed atom:
entry. Either case can potentially indicate a form of spoofing
attack. Processors must take steps to verify the validity of the at:
deleted-entry element.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
A Deleted Entry Document, when serialized as XML 1.0, can be
identified with the following media type:
Type name: application
Subtype name: atomdeleted+xml
Required parameters: None
Optional parameters: "charset": This parameter has semantics
identical to the charset parameter of the "application/xml" media
type as specified in [<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Encoding considerations: Identical to those of "application/xml"
as described in <a href="./rfc3023#section-3.2">[RFC3023], Section 3.2</a>.
Security considerations: As defined in this specification. In
addition, as this media type uses the "+xml" convention, it shares
the same security considerations as described in <a href="./rfc3023#section-10">[RFC3023],
Section 10</a>.
Interoperability considerations: There are no known
interoperability issues.
Published specification: This specification.
Applications that use this media type: Undefined. As an extension
to the Atom Syndication Format ([<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]), this specification may
be used within any application that uses the Atom Format.
<span class="grey">Snell Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
Additional information:
Magic number(s): As specified for "application/xml" in
<a href="./rfc3023#section-3.2">[RFC3023], Section 3.2</a>
File extension(s): .atomdeleted
Macintosh file type code(s): TEXT
Person & email address to contact for further information: James M
Snell <jasnell@us.ibm.com>
Intended usage: COMMON
Restrictions on usage: None.
Author: James M Snell <jasnell@us.ibm.com>
Change controller: IESG
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
The author gratefully acknowledges the feedback from the members of
the Atom Publishing Format and Protocol working group during the
development of this specification.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", <a href="./rfc3023">RFC 3023</a>, January 2001.
[<a id="ref-RFC3339">RFC3339</a>] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", <a href="./rfc3339">RFC 3339</a>, July 2002.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC3987">RFC3987</a>] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, January 2005.
[<a id="ref-RFC4287">RFC4287</a>] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
Syndication Format", <a href="./rfc4287">RFC 4287</a>, December 2005.
<span class="grey">Snell Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6721">RFC 6721</a> Atom deleted-entry September 2012</span>
[<a id="ref-W3C.REC-xml-20040204">W3C.REC-xml-20040204</a>]
Yergeau, F., Maler, E., Sperberg-McQueen, C., Paoli, J.,
and T. Bray, "Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium FirstEdition REC-xml-
20040204, February 2004,
<<a href="http://www.w3.org/TR/2004/REC-xml-20040204">http://www.w3.org/TR/2004/REC-xml-20040204</a>>.
[<a id="ref-W3C.REC-xml-c14n-20010315">W3C.REC-xml-c14n-20010315</a>]
Boyer, J., "Canonical XML Version 1.0", World Wide Web
Consortium Recommendation REC-xml-c14n-20010315,
March 2001,
<<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</a>>.
[<a id="ref-W3C.REC-xml-exc-c14n-20020718">W3C.REC-xml-exc-c14n-20020718</a>]
Reagle, J., 3rd, D., and J. Boyer, "Exclusive XML
Canonicalization Version 1.0", World Wide Web Consortium
Recommendation REC-xml-exc-c14n-20020718, July 2002,
<<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718</a>>.
[<a id="ref-W3C.REC-xml-names-19990114">W3C.REC-xml-names-19990114</a>]
Hollander, D., Bray, T., and A. Layman, "Namespaces in
XML", World Wide Web Consortium FirstEdition REC-xml-
names-19990114, January 1999,
<<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">http://www.w3.org/TR/1999/REC-xml-names-19990114</a>>.
[<a id="ref-W3C.REC-xmlbase-20010627">W3C.REC-xmlbase-20010627</a>]
Marsh, J., "XML Base", World Wide Web Consortium
FirstEdition REC-xmlbase-20010627, June 2001,
<<a href="http://www.w3.org/TR/2001/REC-xmlbase-20010627">http://www.w3.org/TR/2001/REC-xmlbase-20010627</a>>.
[<a id="ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>]
Solo, D., Reagle, J., and D. Eastlake, "XML-Signature
Syntax and Processing", World Wide Web Consortium
FirstEdition REC-xmldsig-core-20020212, February 2002,
<<a href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212</a>>.
[<a id="ref-W3C.REC-xmlenc-core-20021210">W3C.REC-xmlenc-core-20021210</a>]
Eastlake, D. and J. Reagle, "XML Encryption Syntax and
Processing", World Wide Web Consortium Recommendation REC-
xmlenc-core-20021210, December 2002,
<<a href="http://www.w3.org/TR/2002/REC-xmlenc-core-20021210">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210</a>>.
Author's Address
James M Snell
EMail: jasnell@us.ibm.com
URI: <a href="http://ibm.com">http://ibm.com</a>
Snell Standards Track [Page 10]
</pre>
|
