ANTACID Protocol Appendix D. ARS Top-Level DTD From: http://www.ietf.org/internet-drafts/draft-schwartz-antacid-protocol-00.txt %ARSC; %ARSC; %ARS; %ARSC; %ARSE; %ARSC; %ARS; %ARSE; Appendix E. ars-c DTD Appendix F. ars-s DTD Appendix G. ars-e DTD Appendix H. ARS Topology Configuration DTD Appendix I. Current Encodings and Registration Procedures ARS encodings are defined as MIME [11] Content-Type "application/ars", with the single parameter "encoding_name" naming which encoding is being used (e.g., DataWithOps). ars-e is NOT a MIME Content Transfer Encoding, since it is not application- independent. As is the case with MIME primary types, encodings being used privately (that is, between peers that understand the encoding by mutual prior arrangement) must be given names that begin with "X-" to indicate the encodings' non-standard status and to avoid a potential conflict with a future official name. Following the "X-" must be a URI [5] that identifies the encoding uniquely (for example, X- http://xml.resource.org/encodings/mysqlRaw.html). This URI should refer to a document that describes the encoding (whether formally or informally), but the existence of a document is not required. The only requirement is that the URI must provide a globally unique identification of the encoding, to prevent clashes in the name space of privately defined encodings. ARS Encodings are afforded official status when they have been registered with the Internet Assigned Numbers Authority (IANA), using the template provided below. The currently defined ARS encodings are also listed below, for convenience. Note that ARS references the encoding_name within the ContentEncodingsSupported and UpdateGroup elements, without the MIME "Content-Type:" syntax. I.1 Currently Defined Encodings