/[pub]/suikawiki/sw4data/ids/2/181.txt
Suika

Contents of /suikawiki/sw4data/ids/2/181.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (hide annotations) (download)
Wed Nov 12 16:52:54 2008 UTC (16 years ago) by wakaba
Branch: MAIN
CVS Tags: before-graph-20090923, suika-20100509
File MIME type: text/plain
converted from SuikaWiki3 <http://suika.fam.cx/gate/cvs/suikawiki/wikidata/page/5246432033393032.txt>

1 wakaba 1.1
2     '''The "application/soap+xml" media type'''
3     - Network Working Group
4     - Request for Comments: 3902
5     - Category: Informational
6     - M. Baker
7     - Independent
8     - M. Nottingham
9     - BEA Systems
10     - September 2004
11    
12    
13     * Status of this Memo
14    
15     > This memo provides information for the Internet community. It does
16     not specify an Internet standard of any kind. Distribution of this
17     memo is unlimited.
18    
19    
20     * Copyright Notice
21    
22     > Copyright (C) The Internet Society (2004).
23    
24    
25     * Abstract
26    
27     > This document defines the "application/soap+xml" media type which can
28     be used to describe SOAP 1.2 messages serialized as XML 1.0.
29    
30     この文書は XML 1.0 で直列化した SOAP 1.2 メッセージを記述するために使用できる
31     [CODE(MIME)[application/soap+xml]] 媒体型を定義します。
32    
33    
34     * 1. Introduction
35    
36     > SOAP version 1.2 (SOAP) is a lightweight protocol intended for
37     exchange of structured information between peers in a decentralized,
38     distributed environment. It defines an extensible messaging
39     framework that contains a message construct based on XML technologies
40     that can be exchanged over a variety of underlying protocols.
41    
42     SOAP 1.2 版 (SOAP) は脱集中分散環境の同輩間の構造化情報の交換のための軽量プロトコルです。
43     SOAP は様々なプロトコルの上で交換できる XML
44     技術を基にしたメッセージ構造を含む、拡張可能なメッセージ付けの枠組みを定義しています。
45    
46     > This specification defines the media type "application/soap+xml"
47     which can be used to identify SOAP 1.2 message envelopes that have
48     been serialized with XML 1.0. Such serializations are useful as the
49     basis of "wire formats" for SOAP 1.2 Protocol Binding Specifications
50     [W3C.REC-soap12-part1-20030624], or in other situations where an XML
51     serialization of a SOAP envelope is required.
52    
53     この仕様書は XML 1.0 で直列化した SOAP 1.2 メッセージ封筒を識別するために使うことができる
54     [DFN[[CODE(MIME)[[[application/soap+xml]]]]]] 媒体型を定義します。
55     XML 1.0 直列化形は、 SOAP 1.2 プロトコル束縛仕様書の[Q[[RUBYB[通信] [wire]]形]]の基礎として、
56     あるいはその他 SOAP 封筒の XML 直列化が必要な状況で有用です。
57    
58     > The "application/soap+xml" media type explicitly identifies SOAP 1.2
59     message envelopes that have been serialised with XML 1.0; message
60     envelopes with a different SOAP namespace version or using another
61     XML serialisation MUST NOT use it.
62    
63     [CODE(MIME)[application/soap+xml]] 媒体型は明示的に SOAP 1.2
64     メッセージ封筒を XML 1.0 で直列化したものを識別します。
65     異なる SOAP 名前空間版や他の XML 直列化を使ったメッセージ封筒は、
66     この媒体型を使っては'''なりません'''。
67    
68     > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
69     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
70     document are to be interpreted as described in [RFC2119].
71    
72    
73     * 2. Registration
74    
75     >
76     :MIME media type name:application
77     :MIME subtype name:soap+xml
78     :Required parameters:none
79     :Optional parameters:
80    
81     >
82     :"charset":This parameter has identical semantics to the charset
83     parameter of the "application/xml" media type as specified in
84     RFC 3023 [RFC3023].
85     :"action":This optional parameter can be used to specify the URI
86     that identifies the intent of the message. In SOAP 1.2, it
87     serves a similar purpose as the SOAPAction HTTP header field
88     did in SOAP 1.1. Namely, its value identifies the intent of the message.
89    
90     :[CODE(MIME)[[[charset]]]]:[[RFC 3023]] で規定されている
91     [CODE(MIME)[[[application/xml]]]] 媒体型の [CODE(MIME)[[[charset]]]]
92     引数と同じ意味を持つ引数です。
93     :[CODE(MIME)[[[action]]]]:メッセージの意図を識別する URI
94     を指定するために使うことができる省略可能な引数です。
95     SOAP 1.2 では SOAP 1.1 の [CODE(HTTP)[[[SOAPAction]]]] HTTP
96     頭欄と同様の目的で使います。つまり、値はメッセージの意図を識別します。
97    
98     > The value of the action parameter is an absolute URI-reference
99     as defined by RFC 2396 [RFC2396], which MUST be non-empty.
100     SOAP places no restrictions on the specificity of the URI or
101     that it is resolvable. Although the purpose of the action
102     parameter is to indicate the intent of the SOAP message there
103     is no mechanism for automatically computing the value based on
104     the SOAP envelope. In other words, the value has to be
105     determined out of band. It is recommended that the same value
106     be used to identify sets of message types that are logically
107     connected in some manner, for example part of the same
108     "service". It is strongly RECOMMENDED that the URI be globally
109     unique and stable over time.
110    
111     [CODE(MIME)[[[action]]]] 引数の値は [[RFC 2396]] で定義された絶対
112     URI 参照で、空以外でなければ'''なりません'''。 SOAP
113     はこの URI の特異性やこの URI が解決可能かどうかについて何の制限も課しません。
114     [CODE(MIME)[action]] 引数の目的は SOAP メッセージの意図を示すことですが、
115     SOAP 封筒を基にして自動的に値を計算する仕組みはありません。
116     言い換えれば、この値は外部で決定しなければなりません。ある方法で論理的に接続されたメッセージ型の集合、
117     例えば同じ[Q[サービス]]の一部を識別するために同じ値を使うことを推奨します。
118     URI は大域的に固有であって、時をこえて安定であることを強く'''推奨'''します。
119    
120     > Use of the action parameter is OPTIONAL. SOAP Receivers MAY
121     use it as a hint to optimize processing, but SHOULD NOT require
122     its presence in order to operate.
123    
124     [CODE(MIME)[action]] 引数の使用は'''任意選択'''です。 SOAP
125     受信者は処理を最適化するヒントとして使っても'''構いません'''が、
126     処理のためにこの引数が存在していることを必要とする'''べきではありません'''。
127    
128     >
129     :Encoding considerations:Identical to those of "application/xml" as
130     described in RFC 3023 [RFC3023], section 3.2, as applied to the
131     SOAP envelope infoset.
132    
133     [[RFC 3023]] 3.2節で [CODE(MIME)[application/xml]] について説明されていることが
134     SOAP 封筒情報集合にも適用されます。
135    
136     >
137     :Security considerations:Because SOAP can carry application defined
138     data whose semantics is independent from that of any MIME wrapper
139     (or context within which the MIME wrapper is used), one should not
140     expect to be able to understand the semantics of the SOAP message
141     based on the semantics of the MIME wrapper alone. Therefore,
142     whenever using the "application/soap+xml" media type, it is
143     strongly RECOMMENDED that the security implications of the context
144     within which the SOAP message is used is fully understood. The
145     security implications are likely to involve both the specific SOAP
146     binding to an underlying protocol as well as the application-defined
147     semantics of the data carried in the SOAP message (though
148     one must be careful when doing this, as discussed in SOAP 1.2 Part
149     1 [W3C.REC-soap12-part1-20030624], section Binding to
150     Application-Specific Protocols).
151    
152     SOAP はその意味が MIME [RUBYB[覆い子] [wrapper]]のもの
153     (や MIME 覆い子が使用されている文脈) から独立した応用定義のデータを伝達できますから、
154     MIME 覆い子だけの意味に基づいて SOAP メッセージの意味を理解できると期待するべきではありません。
155     従って、 [CODE(MIME)[application/soap+xml]] 媒体型を使う時は常に SOAP
156     メッセージが使われている文脈による安全性への影響を完全に理解することを強く'''推奨'''します。
157     安全性への影響は特定の下位プロトコルへの束縛にも、
158     SOAP メッセージで伝達されるデータの意味にも関わります。
159    
160     > Also, see SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], the
161     entire section Security Considerations.
162    
163     また、 SOAP 1.2 第1部の安全性に関してもご覧下さい。
164    
165     > In addition, as this media type uses the "+xml" convention, it
166     shares the same security considerations as described in RFC 3023
167     [RFC3023], section 10.
168    
169     加えて、この媒体型は [CODE(MIME)[+xml]] 記法を使っていますから、
170     [[RFC 3023]] 10章で説明されている安全性についての考察も該当します。
171    
172     > The action parameter is not a security mechanism, and SHOULD NOT
173     be used for authentication. If the action parameter is used to
174     make decisions (e.g., dispatch, filtering), it is RECOMMENDED that
175     the basis for such decisions should be confirmed by examining the
176     SOAP Envelope.
177    
178     [CODE(MIME)[action]] 引数は安全のための仕組みではなく、
179     認証のために使用する'''べきではありません'''。決定
180     (例えば発射、濾過) のために [CODE(MIME)[action]]
181     引数を使う場合は、その決定の基礎は SOAP 封筒の検査によって確認することを'''推奨'''します。
182    
183     >
184     :Interoperability considerations:There are no known interoperability issues.
185     :Published specification:SOAP 1.2 Part 1
186     [W3C.REC-soap12-part1-20030624] and SOAP 1.2 Part 2
187     [W3C.REC-soap12-part2-20030624].
188     :Applications which use this media type:Various SOAP 1.2 conformant
189     toolkits use this media type.
190     :Additional information:
191     [PRE[
192     File extension: SOAP messages are not required or expected to be
193     stored as files.
194     Fragment identifiers: Identical to that of "application/xml" as
195     described in RFC 3023 [RFC3023], section 5.
196     Base URI: As specified in RFC 3023 [RFC3023], section 6. Also see
197     SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Use of
198     URIs in SOAP.
199     Macintosh File Type code: TEXT
200     Person and email address to contact for further information:
201     World Wide Web Consortium <web-human@w3.org>
202     Intended usage: COMMON
203     Author/Change controller: The SOAP 1.2 specification set is a work
204     product of the World Wide Web Consortium's XML Protocol Working
205     Group. The W3C has change control over these specifications.
206     ]PRE]
207    
208    
209    
210     * 3. Security Considerations
211    
212     > See the "Security Considerations" section of the registration
213     template found in Section 2.
214    
215    
216     * 4. Normative References
217    
218     [PRE[
219     [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
220     Requirement Levels", BCP 14, RFC 2119, March 1997.
221     ]PRE]
222    
223     [PRE[
224     [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
225     Resource Identifiers (URI): Generic Syntax", RFC 2396,
226     August 1998.
227     ]PRE]
228    
229     [PRE[
230     [RFC3023] Murata, M., St.Laurent, S., and D. Kohn, "XML Media
231     Types", RFC 3023, January 2001.
232     ]PRE]
233    
234     [PRE[
235     [W3C.REC-soap12-part1-20030624]
236     Hadley, M., Mendelsohn, N., Moreau, J., Nielsen, H., and
237     M. Gudgin, "SOAP Version 1.2 Part 1: Messaging
238     Framework", W3C REC REC-soap12-part1-20030624, June 2003.
239     ]PRE]
240    
241     [PRE[
242     [W3C.REC-soap12-part2-20030624]
243     Moreau, J., Nielsen, H., Gudgin, M., Hadley, M., and N.
244     Mendelsohn, "SOAP Version 1.2 Part 2: Adjuncts", W3C REC
245     REC-soap12-part2-20030624, June 2003.
246     ]PRE]
247    
248    
249     * 5. Authors' Addresses
250    
251     [PRE[
252     Mark A. Baker
253     Independent
254     37 Charles St.
255     Ottawa, Ontario K1M 1R3
256     CA
257     ]PRE]
258    
259     [PRE[
260     EMail: distobj@acm.org
261     ]PRE]
262    
263     [PRE[
264     Mark Nottingham
265     BEA Systems
266     235 Montgomery St., Level 15
267     San Francisco, CA 94010
268     US
269     ]PRE]
270    
271     [PRE[
272     EMail: mnot@pobox.com
273     ]PRE]
274    
275    
276     * 6. Full Copyright Statement
277    
278     [PRE[
279     Copyright (C) The Internet Society (2004).
280     ]PRE]
281    
282     [PRE[
283     This document is subject to the rights, licenses and restrictions
284     contained in BCP 78, and at www.rfc-editor.org, and except as set
285     forth therein, the authors retain all their rights.
286     ]PRE]
287    
288     [PRE[
289     This document and the information contained herein are provided on an
290     "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
291     REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
292     INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
293     IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
294     THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
295     WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
296     ]PRE]
297    
298    
299     * Intellectual Property
300    
301     [PRE[
302     The IETF takes no position regarding the validity or scope of any
303     Intellectual Property Rights or other rights that might be claimed to
304     pertain to the implementation or use of the technology described in
305     this document or the extent to which any license under such rights
306     might or might not be available; nor does it represent that it has
307     made any independent effort to identify any such rights. Information
308     on the ISOC's procedures with respect to rights in ISOC Documents can
309     be found in BCP 78 and BCP 79.
310     ]PRE]
311    
312     [PRE[
313     Copies of IPR disclosures made to the IETF Secretariat and any
314     assurances of licenses to be made available, or the result of an
315     attempt made to obtain a general license or permission for the use of
316     such proprietary rights by implementers or users of this
317     specification can be obtained from the IETF on-line IPR repository at
318     http://www.ietf.org/ipr.
319     ]PRE]
320    
321     [PRE[
322     The IETF invites any interested party to bring to its attention any
323     copyrights, patents or patent applications, or other proprietary
324     rights that may cover technology that may be required to implement
325     this standard. Please address the information to the IETF at ietf-
326     ipr@ietf.org.
327     ]PRE]
328    
329    
330     * Acknowledgement
331    
332     [PRE[
333     Funding for the RFC Editor function is currently provided by the
334     Internet Society.
335     ]PRE]
336    
337    
338     * メモ
339    
340     [1]
341     This is gonsalez music site - <a href="http://www.gonsalez.info/72802.html">best music site in da world</a>.
342     ([[David]] [kalimurzino@rambler.ru])
343    
344     [2]
345     This is Agape blog site - <a href="http://www.agapeblogx.com/72802.html">Interesting blog</a>.
346     ([[David]] [kalimuino@gmail.com])
347    
348     [3]
349     vufv3G <a href="http://cgrxxawjbscu.com/">cgrxxawjbscu</a>, [url=http://kcojuinbffom.com/]kcojuinbffom[/url], [link=http://tsumndaudngq.com/]tsumndaudngq[/link], http://npbvcldiszmr.com/
350     ([[cbsibkt]] [fhnric@utrvmt.com] [WEAK[2007-09-14 20:32:53 +00:00]])
351    

admin@suikawiki.org
ViewVC Help
Powered by ViewVC 1.1.24