| 1 |
#?SuikaWiki/0.9
|
| 2 |
[1] '''Resource and Representation Typing in HTTP [INS[HTTP における資源及び表現型付け]]'''
|
| 3 |
-Internet Draft
|
| 4 |
-Document: draft-palmer-resrep-type-00.txt
|
| 5 |
-Expires: September 1, 2002
|
| 6 |
-Sean B. Palmer
|
| 7 |
-March 2001
|
| 8 |
|
| 9 |
*Status Of This Memo
|
| 10 |
>This document is an Internet-Draft and is in full conformance with
|
| 11 |
all provisions of Section 10 of RFC2026.
|
| 12 |
>Internet-Drafts are working documents of the Internet Engineering
|
| 13 |
Task Force (IETF), its areas, and its working groups. Note that
|
| 14 |
other groups may also distribute working documents as Internet-
|
| 15 |
Drafts.
|
| 16 |
>Internet-Drafts are draft documents valid for a maximum of six months
|
| 17 |
and may be updated, replaced, or obsoleted by other documents at any
|
| 18 |
time. It is inappropriate to use Internet-Drafts as reference
|
| 19 |
material or to cite them other than as "work in progress."
|
| 20 |
>The list of current Internet-Drafts can be accessed at
|
| 21 |
http://www.ietf.org/ietf/1id-abstracts.txt
|
| 22 |
The list of Internet-Draft Shadow Directories can be accessed at
|
| 23 |
http://www.ietf.org/shadow.html.
|
| 24 |
>This Internet-draft will expire on September 1, 2002.
|
| 25 |
>Copyright Notice Copyright (C) The Internet Society (2001). All
|
| 26 |
Rights Reserved. [INS[(ママ)]]
|
| 27 |
|
| 28 |
*Abstract
|
| 29 |
>This document defines the "Repr-Type" and "Resource-Type" HTTP
|
| 30 |
entity-header field names, to provide URIs that identify the
|
| 31 |
generic type (class membership) of representations and their
|
| 32 |
original source resources respectively.
|
| 33 |
|
| 34 |
この文書は、 [[HTTP]]
|
| 35 |
[[実体頭欄]]名
|
| 36 |
[CODE(HTTP)[[[Repr-Type]]
|
| 37 |
及び [CODE(HTTP)[[[Resource-Type]]]]
|
| 38 |
を定義します。
|
| 39 |
これらは、表現の一般的な型 (class
|
| 40 |
membership) とその元の典拠資源をそれぞれ識別する
|
| 41 |
URI を提供します。
|
| 42 |
|
| 43 |
*1. Introduction
|
| 44 |
>Providing a resource type along with an HTTP response is useful,
|
| 45 |
since there may be no other way to identify the resource type within
|
| 46 |
the domain of the HTTP message. For example, HTML pages do not give
|
| 47 |
a machine processable type for the resource that they are
|
| 48 |
representations of.
|
| 49 |
|
| 50 |
資源の型を HTTP 応答と共に提供することは有用です。
|
| 51 |
なぜなら、 HTTP メッセージの範囲内で資源の型を識別する方法は他にはおそらくないからです。
|
| 52 |
たとえば、 [[HTML]]
|
| 53 |
頁はその表現している資源の機械が処理可能な型を与えません。
|
| 54 |
|
| 55 |
>Meanwhile, using MIME types to identify content types is
|
| 56 |
architecturally inadvisable due to the centralization around the
|
| 57 |
IANA - URIs should identify all important things on the Web, and
|
| 58 |
content types are no exception. (Note that the current set of MIME
|
| 59 |
types can have URIs, and those can be used in the Repr-Type header).
|
| 60 |
|
| 61 |
他方、 [[MIME型]]を使って[[内容型]]を識別することは、
|
| 62 |
[[IANA]] で中央管理されているので構造的には不適当です。
|
| 63 |
[[URI]] は [[Web]]
|
| 64 |
のすべての重要なものを識別でき、
|
| 65 |
内容型も例外ではありません。
|
| 66 |
(現在の MIME 型の集合は URI
|
| 67 |
を持ち得て、これらは
|
| 68 |
[CODE(HTTP)[[[Repr-Type]]]]
|
| 69 |
頭で使用し得ることに注意。)
|
| 70 |
|
| 71 |
>In fact, the content type idiom is isomorphic with that of the
|
| 72 |
"Class" class in RDF Schema [RDFSchema].
|
| 73 |
|
| 74 |
実際、内容型慣用句は [[RDFSchema]]
|
| 75 |
の [CODE[[[Ckass]]]] class
|
| 76 |
と isomorphic です。
|
| 77 |
|
| 78 |
>>RDF classes can be defined to represent almost anything, such as
|
| 79 |
Web pages, people, document types, databases or abstract concepts. [INS[<http://www.w3.org/TR/2000/CR-rdf-schema-20000327/#s2.2.3>]]
|
| 80 |
|
| 81 |
RDF class は、 [[Web頁]],
|
| 82 |
人物, 文書型, データベース,
|
| 83 |
抽象概念などほとんどなんでも表現するように定義できます。
|
| 84 |
|
| 85 |
>Repr-Type values are generally restricted to content type classes,
|
| 86 |
whereas the Resource-Type value have no such restriction, according
|
| 87 |
to the definition of resource in RFC 2396.
|
| 88 |
|
| 89 |
[CODE(HTTP)[Repr-Type]] 値は通常内容型
|
| 90 |
class に制限されます。
|
| 91 |
[CODE(HTTP)[Resource-Type]]
|
| 92 |
値は、 [[RFC2396]]
|
| 93 |
の[[資源]]の定義に従ってそうした制限はありません。
|
| 94 |
|
| 95 |
*2. Entity-Header Productions
|
| 96 |
**2.1 Syntax
|
| 97 |
>Here is an ABNF for the proposed entity-headers:-
|
| 98 |
|
| 99 |
これは提案する実態頭の [[ABNF]]
|
| 100 |
です:
|
| 101 |
|
| 102 |
>
|
| 103 |
- ResourceType = "Resource-Type" ":" 1#URIview
|
| 104 |
- ReprType = "Repr-Type" ":" 1#URIview
|
| 105 |
>
|
| 106 |
- URIview = absoluteURI [ "#" fragment ] ; from [RFC2396]
|
| 107 |
|
| 108 |
>The <absoluteURI>, and <fragment> components are imported from
|
| 109 |
[RFC2396].
|
| 110 |
|
| 111 |
[CODE(ABNF)[[[absoluteURI]]]],
|
| 112 |
[CODE(ABNF)[[[fragment]]]]
|
| 113 |
は RFC 2396 から輸入しました。
|
| 114 |
|
| 115 |
>Two examples of syntactically valid ResourceType productions (i.e.
|
| 116 |
"Resource-Type" HTTP headers) are:-
|
| 117 |
|
| 118 |
構文的に妥当な
|
| 119 |
[CODE[ResourceType]] 生成物
|
| 120 |
(すなわち
|
| 121 |
[CODE(HTTP)[Resource-Type]]
|
| 122 |
HTTP 頭) の2つの例は:
|
| 123 |
|
| 124 |
>
|
| 125 |
- Resource-Type: http://xmlns.com/foaf/0.1/Person
|
| 126 |
- Resource-Type: http://www.w3.org/2000/10/swap/pim/doc#Work
|
| 127 |
|
| 128 |
>Two examples of syntactically valid ReprType productions (i.e.
|
| 129 |
"Repr-Type" HTTP headers) are:-
|
| 130 |
|
| 131 |
構文的に妥当な
|
| 132 |
[CODE[ReprType]] 生成物
|
| 133 |
(すなわち
|
| 134 |
[CODE(HTTP)[Repr-Type]]
|
| 135 |
HTTP 頭) の2つの例は:
|
| 136 |
|
| 137 |
>
|
| 138 |
- Repr-Type: http://www.w3.org/2000/10/swap/log#N3Document
|
| 139 |
- Repr-Type: http://www.iana.org/assignments/media-types/text/html
|
| 140 |
|
| 141 |
**2.2 Equality and Character Parsing of Header Values
|
| 142 |
>Header values are to be compared on a character for character (case
|
| 143 |
sensitive) basis. Due to internationalization issues, escaped
|
| 144 |
unicode characters are allowed in the URI header values. You must
|
| 145 |
use the following escaping procedure:-
|
| 146 |
|
| 147 |
頭値は文字ごとに
|
| 148 |
(大文字・小文字を区別して)
|
| 149 |
比較します。
|
| 150 |
国際化の問題から、 escape
|
| 151 |
した [[unicode]] 文字は URI
|
| 152 |
頭値中で認められます。
|
| 153 |
次の escape 手続きを踏まなければなりません。
|
| 154 |
|
| 155 |
>
|
| 156 |
=Each disallowed character is converted to UTF-8 (as defined in
|
| 157 |
[RFC2279]) as one or more bytes.
|
| 158 |
=Any bytes corresponding to a disallowed character are escaped
|
| 159 |
with the URI escaping mechanism (that is, converted to %HH,
|
| 160 |
where HH is the hexadecimal notation of the byte value).
|
| 161 |
=The original character is replaced by the resulting character
|
| 162 |
sequence.
|
| 163 |
|
| 164 |
=各禁止文字は [[UTF-8]]
|
| 165 |
の1つ以上のバイト列に変換します。
|
| 166 |
=禁止文字に対応するバイト列を
|
| 167 |
URI escape 機構により escape
|
| 168 |
します。 (すなわち、
|
| 169 |
[CODE(URI)[%[VAR[HH]]]]
|
| 170 |
に変換します。ここで、 [VAR[HH]]
|
| 171 |
はバイト値の16進記法です。
|
| 172 |
=元の文字を結果の文字列で置換します。
|
| 173 |
|
| 174 |
*3. General Use Considerations
|
| 175 |
>It is perfectly legal and sensible for either of the defined
|
| 176 |
entity-headers to occur more than once; if they do, then processors
|
| 177 |
should take the intersection of the given classes. For example, a
|
| 178 |
Resource Type may be both Vehicle and a Car. A Representation Type
|
| 179 |
may be both an XML document, and a canonicalized XML document.
|
| 180 |
|
| 181 |
定義された実体頭を複数回出現させることはまったく合法であって意味のあることです。
|
| 182 |
そうした場合、処理系は与えられた
|
| 183 |
class の相互作用と取るべきです。
|
| 184 |
たとえば、資源型は Vehicle
|
| 185 |
及び車の双方かもしれません。
|
| 186 |
表現型は XML 文書と正規化 XML
|
| 187 |
文書の双方かもしれません。
|
| 188 |
|
| 189 |
>Note that if the Repr-Type (and possibly Content-Type) headers
|
| 190 |
conflict semantically, then all of the Repr-Type headers (or just
|
| 191 |
those that conflict with Content-Type, if present) should be
|
| 192 |
abandoned.
|
| 193 |
|
| 194 |
[CODE(HTTP)[Repr-Type]]
|
| 195 |
(及びもしかすると [CODE(HTTP)[[[Content-Type]]]])
|
| 196 |
頭が意味的に衝突する場合は、
|
| 197 |
すべての [CODE(HTTP)[Repr-Type]]
|
| 198 |
頭 (あるいは [CODE(HTTP)[Content-Type]]
|
| 199 |
と衝突する場合は単にそれと衝突するもの)
|
| 200 |
は捨てるべきです。
|
| 201 |
|
| 202 |
*4. Security Considerations
|
| 203 |
>Implementors should take heed of section 15.1.1 of [RFC2616]. There
|
| 204 |
may be other security considerations that have not yet been raised.
|
| 205 |
|
| 206 |
実装者は [[RFC2616]] の
|
| 207 |
15.1.1 節に注意するべきです。
|
| 208 |
まだ起こっていない他の安全上の注意点もあるかもしれません。
|
| 209 |
|
| 210 |
>The relevant security issues associated with each Repr-Type value
|
| 211 |
should obviously be taken into consideration when handling the
|
| 212 |
entity-body.
|
| 213 |
|
| 214 |
各 [CODE(HTTP)[Repr-Type]]
|
| 215 |
値に関連付けられた関係する安全上の問題は[[実体本体]]を取り扱うときには十分考慮に入れるべきです。
|
| 216 |
|
| 217 |
*5. Further Information
|
| 218 |
>Further information on the headers defined by this document is
|
| 219 |
available at <http://purl.org/net/resreptype>
|
| 220 |
|
| 221 |
この文書の定義する頭についての詳しい情報は
|
| 222 |
<http://purl.org/net/resreptype>
|
| 223 |
から入手可能です。
|
| 224 |
|
| 225 |
*6. Acknowledgements
|
| 226 |
>Many thanks to Mark Baker, Tim Berners-Lee, Jonathan Borden, Sandro
|
| 227 |
Hawke, Mark Nottingham, and Aaron Swartz for the discussions and
|
| 228 |
inspiration that led to this document.
|
| 229 |
|
| 230 |
>Many thanks also to Daniel Biddle and Aaron Swartz for their help in
|
| 231 |
preparing this document.
|
| 232 |
|
| 233 |
*References
|
| 234 |
|
| 235 |
[RDFSchema] Dan Brickley, R. V. Guha (2000). Resource Description
|
| 236 |
Framework (RDF) Schema Specification 1.0. W3C Candidate
|
| 237 |
Recommendation.
|
| 238 |
http://www.w3.org/TR/2000/CR-rdf-schema-20000327/
|
| 239 |
|
| 240 |
[RFC2279] F. Yergeau (1998). UTF-8, a transformation format of
|
| 241 |
ISO 10646.
|
| 242 |
http://www.ietf.org/rfc/rfc2279.txt
|
| 243 |
|
| 244 |
[RFC2396] T. Berners-Lee, R. Fielding, L. Masinter (1998). Uniform
|
| 245 |
Resource Identifiers (URI): Generic Syntax.
|
| 246 |
http://www.ietf.org/rfc/rfc2279.txt
|
| 247 |
|
| 248 |
[RFC2616] T. Berners-Lee, R. Fielding, H. Frystyk, J. Gettys, P.
|
| 249 |
Leach, L. Masinter, J. Mogul (1999). Hypertext Transfer
|
| 250 |
Protocol -- HTTP/1.1.
|
| 251 |
http://www.ietf.org/rfc/rfc2616.txt
|
| 252 |
* License
|
| 253 |
[[RFCのライセンス]]
|
| 254 |
*メモ |
Parent Directory
| 
Revision Log