discontinued / server · Files

REC-ws-fragment-20111213 78.9 KB
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 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Fragment (WS-Fragment)</title><style type="text/css">
code           { font-family: monospace; }

div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }

ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }


div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css" /></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title"></a>Web Services Fragment (WS-Fragment)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 13 December 2011</h2><dl><dt>This version:</dt><dd>
   <a href="http://www.w3.org/TR/2011/REC-ws-fragment-20111213">http://www.w3.org/TR/2011/REC-ws-fragment-20111213
   </a>
  </dd><dt>Latest version:</dt><dd>
    <a href="http://www.w3.org/TR/ws-fragment">http://www.w3.org/TR/ws-fragment
   </a>
  </dd><dt>Previous version:</dt><dd>
    <a href="http://www.w3.org/TR/2011/PR-ws-fragment-20110927">http://www.w3.org/TR/2011/PR-ws-fragment-20110927
    </a>
  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p>Please refer to the <a href="http://www.w3.org/2002/ws/ra/errata/ws-fragment-20111213-errata"><strong>errata</strong></a> for this document, which may
      include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-fragment"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
    This specification extends the WS-Transfer <a href="#WsTransfer">[WS-Transfer]</a>
    specification to enable clients to retrieve and manipulate parts or
    fragments of a WS-Transfer enabled resource without needing to include 
    the entire XML representation in a message exchange.
   </p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>
	    This section describes the status of this document at the time 
	    of its publication. Other documents may supersede this document.
	    A list of current W3C publications and the latest revision of 
	    this technical report can be found in the 
	    <a href="http://www.w3.org/TR/">W3C technical reports index</a>
	    at http://www.w3.org/TR/.
	  </em></p><p>
	  This is the 13 December 2011 Recommendation of the <em>Web Services Fragment (WS-Fragment)</em> specification.
          It has been produced by the
          <a href="http://www.w3.org/2002/ws/ra/">Web
          Services Resource Access Working Group</a> (WG), which is part of the
          <a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
          Activity</a>.
        </p><p>
          The public is encouraged to send comments to the Working Group's public mailing list
          <a href="mailto:public-ws-resource-access-comments@w3.org">
          public-ws-resource-access-comments@w3.org</a>
          mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/">public
          archive</a>). See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage guidelines</a>.
        </p><p>No changes were made as a result of the Proposed Recommendation phase (see also the <a href="http://www.w3.org/2002/ws/ra/test/scenario.html">test scenario</a> and the <a href="http://www.w3.org/2002/ws/ra/test/testResults.html">implementation report</a>).</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>
	  This document was produced by a group operating under the 
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 
	  February 2004 W3C Patent Policy</a>. W3C maintains a 
	  <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/43088/status">public 
	  list of any patent disclosures</a> made in connection with the 
	  deliverables of the group; that page also includes instructions for 
	  disclosing a patent. An individual who has actual knowledge of a 
	  patent which the individual believes contains 
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential 
	  Claim(s)</a> must disclose the information in accordance with 
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 
	  6 of the W3C Patent Policy</a>.
	</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
2 <a href="#intro">Introduction</a><br />
&nbsp;&nbsp;&nbsp;2.1 <a href="#reqs">Requirements</a><br />
3 <a href="#Notations_and_Terminology">Terminology and Notation</a><br />
&nbsp;&nbsp;&nbsp;3.1 <a href="#conven">Notational Conventions</a><br />
&nbsp;&nbsp;&nbsp;3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br />
&nbsp;&nbsp;&nbsp;3.3 <a href="#terminology">Terminology</a><br />
&nbsp;&nbsp;&nbsp;3.4 <a href="#compliance">Compliance</a><br />
&nbsp;&nbsp;&nbsp;3.5 <a href="#namespaces">XML Namespaces</a><br />
4 <a href="#fragments">Fragment WS-Transfer Dialect</a><br />
&nbsp;&nbsp;&nbsp;4.1 <a href="#IdResSubset">Identification of a Resource Subset</a><br />
&nbsp;&nbsp;&nbsp;4.2 <a href="#FragSer">Fragment Serialization</a><br />
&nbsp;&nbsp;&nbsp;4.3 <a href="#Get">Get</a><br />
&nbsp;&nbsp;&nbsp;4.4 <a href="#Put">Put</a><br />
&nbsp;&nbsp;&nbsp;4.5 <a href="#Delete">Delete</a><br />
&nbsp;&nbsp;&nbsp;4.6 <a href="#Create">Create</a><br />
5 <a href="#idp1578688">Examples</a><br />
&nbsp;&nbsp;&nbsp;5.1 <a href="#idp1579344">Examples</a><br />
6 <a href="#QName">QName Expression Language</a><br />
7 <a href="#XPath10">XPath 1.0 Expression Language</a><br />
8 <a href="#XPath20">XPath 2.0 Expression Language</a><br />
9 <a href="#Faults">Faults</a><br />
&nbsp;&nbsp;&nbsp;9.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br />
&nbsp;&nbsp;&nbsp;9.2 <a href="#InvalidExpression">InvalidExpression</a><br />
&nbsp;&nbsp;&nbsp;9.3 <a href="#UnsupportedMode">UnsupportedMode</a><br />
10 <a href="#metadata">WS-Fragment Metadata</a><br />
&nbsp;&nbsp;&nbsp;10.1 <a href="#idp1682688">Fragment Assertion</a><br />
11 <a href="#acks">Acknowledgements</a><br />
12 <a href="#refs">References</a><br />
&nbsp;&nbsp;&nbsp;12.1 <a href="#idp1699968">Normative References</a><br />
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br />
B <a href="#changelog">Change Log</a><br />
</p></div><hr /><div class="body"><div class="div1">
<h2><a name="composable" id="composable"></a>1 Composable Architecture</h2><p>
    By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
    <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
    extensibility models, the Web service
    specifications (WS-*) are designed to be composed with each other
    to provide a rich set of tools for the Web
    services environment. This specification specifically relies on
    other Web service specifications to provide secure, reliable,
    and/or transacted message delivery and to express Web service and
    client policy.
   </p></div><div class="div1">
<h2><a name="intro" id="intro"></a>2 Introduction</h2><p>
    This specification extends the WS-Transfer specification and defines
    a mechanism that allows clients to retrieve and manipulate subsets
    (parts or fragments)
    of a WS-Transfer enabled resource without needing to include the entire
    XML representation in a message exchange.
   </p><p>
    This specification defines a fragment transfer mechanism, an
    extension framework for defining expression languages, and a set of
    expression languages.
   </p><p>
    The fragment transfer mechanism is defined as an extension to 
    WS-Transfer.  This
    involves defining a WS-Transfer Dialect and corresponding XML elements
    that go into the SOAP Body of the Get and Put
    WS-Transfer operations. 
    This fragment transfer mechanism is designed so that it can be used 
    with any number of
    expression languages to indentify a subset of the resource the
    operation is to operate on.
   </p><p>
    While other specifications can define other expression languages,
    it is RECOMMENDED that those languages
    reuse the fragment transfer framework that this specification defines.
   </p><div class="div2">
<h3><a name="reqs" id="reqs"></a>2.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>
       Provide an extension mechanism to WS-Transfer that allows for
       subsets (parts or fragments) of a resource to be retrieved or modified.
      </p></li><li><p>
       Provide an extension framework for defining expression languages.
      </p></li><li><p>
       Provide a set of expression languages that implementations
       can leverage.
      </p></li></ul></div></div><div class="div1">
<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"></a>3 Terminology and Notation</h2><div class="div2">
<h3><a name="conven" id="conven"></a>3.1 Notational Conventions</h3><p>
     The keywords "MUST", "MUST NOT",
     "REQUIRED", "SHALL", "SHALL NOT",
     "SHOULD", "SHOULD NOT", "RECOMMENDED",
     "MAY", and "OPTIONAL" in this document are to be
     interpreted as described in RFC 2119 
     <a href="#RFC2119">[RFC 2119]</a>.
    </p><p>
     This specification uses the following syntax to define outlines for 
     messages:
    </p><ul><li><p>
       The syntax appears as an XML instance, but values in italics
       indicate data types instead of literal values.
      </p></li><li><p>
       Characters are appended to elements and attributes to indicate
       cardinality:
      </p><ul><li><p> "?" (0 or 1) </p></li><li><p> "*" (0 or more) </p></li><li><p> "+" (1 or more) </p></li></ul></li><li><p>
       The character "|" is used to indicate a choice between
       alternatives.
      </p></li><li><p>
       The characters "(" and ")" are used to
       indicate that contained items are to be treated as a group with 
       respect to cardinality or choice.
      </p></li><li><p>
       The characters "[" and "]" are used to call
       out references and property names.
      </p></li><li><p>
       Ellipsis (i.e. "...") indicate points of extensibility.
      </p></li><li><p>
       XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used 
       to indicate the namespace of the element being defined.
      </p></li></ul><p>
     In addition to Message Information Header properties
     <a href="#AddrCore">[WS-Addressing]</a>,
     this specification uses the following properties to define messages:
    </p><dl><dt class="label"> <b>[Headers]</b> </dt><dd><p> Unordered message headers. </p></dd><dt class="label"> <b>[Action]</b> </dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"> <b>[Body]</b> </dt><dd><p> A message body. </p></dd></dl><p>
     These properties bind to a SOAP Envelope as follows:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
  &lt;s:Header&gt;
    <b>[Headers]</b>
    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
    ...
  &lt;/s:Header&gt;
  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     This specification can be used in terms of XML Information Set (Infoset)
     <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
     terminology. Valid Infoset for this specification is the one
     serializable in XML 1.0, hence the use of XML 1.0.
    </p><p>
     The term "generate" is used in relation to the various faults defined
     by this specification to imply that a fault is produced and no
     further processing SHOULD be performed. In these cases the fault
     SHOULD be transmitted. However, there might be reasons when a compliant
     implementation can choose not to transmit the fault - for example,
     security concerns - in these situations the service MAY choose
     not to transmit the fault.
    </p><p>
     In the outlines, <b>bold</b> text is used to indicate those parts
     of the message that are defined as part of this specification and 
     are extensions to the WS-Transfer messages.
    </p></div><div class="div2">
<h3><a name="extensions" id="extensions"></a>3.2 Considerations on the Use of Extensibility Points</h3><p>
     The elements defined in this specification MAY be extended at the
     points indicated by their outlines and schema. Implementations MAY
     add child elements and/or attributes at the indicated extension
     points but MUST NOT contradict the semantics of the parent and/or
     owner, respectively. If a receiver does not recognize an extension,
     the receiver SHOULD ignore that extension. Senders MAY indicate
     the presence of an extension that has to be understood through the use
     of a corresponding SOAP Header with a soap:mustUnderstand attribute
     with the value "1".
    </p><p>
     In cases where it is either desirable or necessary for the receiver
     of a request that has been extended to indicate that it has
     recognized and accepted the semantics associated with that extension,
     it is RECOMMENDED that the receiver add a corresponding extension
     to the response message.  The definition of an extension SHOULD clearly
     specify how the extension that appears in the response correlates
     with that in the corresponding request.
    </p><p>
     Extension elements and attributes MUST NOT use the Web Services
     Fragment namespace URI.
    </p></div><div class="div2">
<h3><a name="terminology" id="terminology"></a>3.3 Terminology</h3><dl><dt class="label">Expression</dt><dd><p>
        A Language specific set of tokens that resolves to a location
        in a resource that contains a subset of the resource.
       </p></dd><dt class="label">Fragment</dt><dd><p>
        A subset of a resource.
       </p></dd></dl></div><div class="div2">
<h3><a name="compliance" id="compliance"></a>3.4 Compliance</h3><p>
     An implementation is not compliant with this specification if it fails to
     satisfy one or more of the MUST or REQUIRED level requirements defined 
     herein.  A SOAP Node MUST NOT use the XML namespace identifier for this 
     specification (listed in <a href="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP 
     Envelopes unless it is compliant with this specification. 
    </p><p>
     Normative text within this specification takes precedence over the XML 
     Schema and WSDL descriptions, which in turn take precedence over 
     outlines, which in turn take precedence over examples. 
    </p><p>
     All messages defined by this specification MUST conform to the
     WS-Addressing specifications and be sent to a Web service that
     is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
    </p><p>
     Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
     MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
    </p><p>
     For any message defined by this specification, any OPTIONAL elements
     or attributes in the message MAY be used by senders of the message;
     however receivers of those messages MUST support those OPTIONAL
     elements and attributes, unless other behavior is explicitly defined
     by this specification.
    </p><p>
     Implementations are expected to support both UTF-8 and UTF-16 as
     described in XML 1.0.
    </p><p>
     Implementations of this specification MUST conform to the corrected
     version of WSDL as defined by the 'WSDL Correction' sections of WS-I
     Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
     <a href="#BP20">[BP20]</a>.
    </p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"></a>3.5 XML Namespaces</h3><p>
     The XML Namespace URI that MUST be used by implementations of this
     specification is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra">http://www.w3.org/2011/03/ws-fra</a></pre></div></div><p>
     <a href="#xmlnamespaces">Table 3-1</a> lists XML namespaces that are 
     used in this specification. The
     choice of any namespace prefix is arbitrary and not semantically
     significant.
    </p><a name="xmlnamespaces" id="xmlnamespaces"></a><table border="1" cellpadding="5"><caption>Table 3-1: 
      Prefixes and XML Namespaces used in this specification.
     </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsf </td><td>
        <a href="http://www.w3.org/2011/03/ws-fra">http://www.w3.org/2011/03/ws-fra</a>
       </td><td>
        This specification
       </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td>
        <a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>
       </td><td>
        <a href="#SOAP11">[SOAP11]</a>
       </td></tr><tr><td> s12 </td><td>
        <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>
       </td><td>
        <a href="#SOAP12">[SOAP12]</a>
       </td></tr><tr><td> wsa </td><td>
        <a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a>
       </td><td>
        <a href="#AddrCore">[WS-Addressing]</a>
       </td></tr><tr><td> wst </td><td>
        <a href="http://www.w3.org/2011/03/ws-tra">http://www.w3.org/2011/03/ws-tra</a>
       </td><td>
        <a href="#WsTransfer">[WS-Transfer]</a>
       </td></tr><tr><td> wsp </td><td>
        <a href="http://www.w3.org/ns/ws-policy">http://www.w3.org/ns/ws-policy</a>
       </td><td> <a href="#wspolicy">[WS-Policy]</a> </td></tr><tr><td> xs </td><td>
        <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>
       </td><td> 
        XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
       </td></tr></tbody></table><p>
     The working group intends to update the value of the Web Services
     Fragment namespace URI each time a new version of this document is
     published until such time that the document reaches Candidate
     Recommendation status. Once it has reached Candidate Recommendation
     status, the working group intends to maintain the value of the
     Web Services Fragment namespace URI that was assigned in the
     Candidate Recommendation unless significant changes are made that
     impact the implementation or break post-CR implementations of the
     specification. Also see
     <a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
      http://www.w3.org/2001/tag/doc/namespaceState.html
     </a> and
     <a href="http://www.w3.org/2005/07/13-nsuri">
      http://www.w3.org/2005/07/13-nsuri
     </a>.
    </p></div></div><div class="div1">
<h2><a name="fragments" id="fragments"></a>4 Fragment WS-Transfer Dialect</h2><p>
    This section defines the fragment transfer mechanism that the expression
    languages defined in subsequent sections will use. 
    The following sections define the expected behavior when the WS-Fragment
    Dialect is used in each of the WS-Transfer operations.
   </p><p>
    WS-Transfer defines what the expected behavior of a resource is 
    with respect to modifications of the resource that might result in
    an invalid state or if the client does not have the authority to
    perform such operations.  This specification only extends but does
    not modify the base WS-Transfer behavior.
   </p><div class="div2">
<h3><a name="IdResSubset" id="IdResSubset"></a>4.1 Identification of a Resource Subset</h3><p>
     The WS-Fragment Dialect is used to identify a portion of a resource 
     representation to update. The WS-Transfer Get and Put operations have 
     an Expression that allows a requester to specify which subset of the 
     resource is being modified. Except in the cases listed below, the 
     Expression MUST evaluate to a single node within the representation. 
     This avoids any issues that might occur due to updating multiple 
     portions of a resource within one invocation - in other words, 
     "batching" is prohibited. There are however a few special cases 
     that need to be taken into account:
    </p><ul><li><p>
       An Expression that evaluates to the root of the resource 
       representation might not result in any nodes being returned from the 
       Expression processor. For example, an XPath expression of "/" on an 
       empty resource would return an empty node-set.  However, to allow 
       for requesters to specify the root (implying the entire document), 
       Expression Languages (and supporting services) that wish to 
       support  this concept might need to make special allowances for this 
       situation. Each Expression Language would need to call out this 
       special expression.
      </p></li><li><p>
       While WS-Fragment doesn't support batching, there are times when 
       a requester might need to act upon an entire sequence of elements 
       (i.e. a list of elements of the same QName that are all siblings). 
       For example, a requester wanting to delete all children of an 
       element. Rather than requiring the requester to send a series of 
       WS-Transfer Put requests to delete each individual child element, 
       WS-Fragment allows for Expression Languages (and services) to 
       identify and act upon the sequence as one entity.
      </p></li></ul><p>
     If an Expression does evaluate to more than one node then, except for 
     the cases listed above, the implementation MUST process only the 
     first selected node.
    </p><p>
     For the purposes of this specification, attributes are treated as 
     single strings - multi-value attributes are not supported.
    </p></div><div class="div2">
<h3><a name="FragSer" id="FragSer"></a>4.2 Fragment Serialization</h3><p>
     When using the WS-Fragment Dialect, subsets of resource representations 
     are serialized into the Get response and Put request messages. To 
     ensure that the receiver of those messages can unambiguously parse the 
     data into the proper XML entities, this specification defines the 
     following rules for serializing XML fragments.
    </p><p>
     Expressions MUST evaluate to one of four possible types: a node-set, 
     a Boolean, a Number or a String. The latter three types are the 
     results of evaluating a computed expression. When they appear in a 
     message they are serialized by performing the following conversion and 
     then wrapping the result in the wsf:Value element: 
    </p><ul><li><p>Boolean - converted to an xs:boolean</p></li><li><p>Number - converted to an xs:double</p></li><li><p>String - converted to an xs:string</p></li></ul><p>
     A node-set is zero or more elements, attributes or text values of 
     elements. A node-set is serialized into XML by concatenating each 
     node and enclosing it in the wsf:Value wrapper XML element for which 
     schema validation is suppressed. Element nodes in a node-set are 
     serialized directly into their XML representation. For attributes 
     and text nodes in the node-set, a wrapper element is used to 
     enclose these values to distinguish them from other such nodes in 
     the serialized result. 
    </p><p>
     Attribute nodes in XPath are represented in the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>name="value"</pre></div></div><p>
     Serialization of an attribute node separates the name from
     the value using the following element:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="<em>xs:QName</em>"&gt;
(02)   <em>attribute value</em>
(03) &lt;/wsf:AttributeNode&gt;</pre></div></div><p>
     The following describes additional constraints on the outline 
     listed above:
    </p><dl><dt class="label"> wsf:AttributeNode </dt><dd><p>
        This element is used to serialize an attribute node in a
        node-set and MUST contain the value portion of the attribute node.
       </p></dd><dt class="label"> wsf:AttributeNode/@name </dt><dd><p>
        This attribute MUST be the qualified name of the attribute node.
       </p></dd></dl><p>
     Text nodes are serialized in the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;
(02)   <em>text value</em>
(03) &lt;/wsf:TextNode&gt;</pre></div></div><p>
     The following describes additional constraints on the
     outline listed above:
    </p><dl><dt class="label"> wsf:TextNode </dt><dd><p>
        This element is used to serialize a text node in a node-set
        and MUST contain the text value.
       </p></dd></dl><p>Given the following XML as an example document.</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a xmlns="example"&gt;
(02)   &lt;b&gt;1&lt;/b&gt;
(03)   &lt;c x="y"&gt;2&lt;/c&gt;
(04) &lt;/a&gt;</pre></div></div><p>
     The result of the XPath "/a/b | /a/b/text() | /a/c/@x" would
     be serialized as the following:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:Value&gt;
(02)   &lt;b&gt;1&lt;/b&gt;
(03)   &lt;wsf:TextNode&gt;1&lt;/wsf:TextNode&gt;
(04)   &lt;wsf:AttributeNode name="x"&gt;y&lt;/wsf:AttributeNode&gt;
(05) &lt;/wsf:Value&gt;</pre></div></div><p>The nodes in the node-set MAY be serialized in any order.</p><p>
     The namespace bindings are evaluated against any namespace
     declarations that are in scope where the expression appears within 
     the SOAP message.
     Note that the evaluation of expressions that rely on such context
     dependent bindings is fragile in the face of transformations that alter
     namespace prefixes. Such transformations might occur during the
     transmission, processing, storage, or retrieval of a request. Clients
     that wish to isolate expressions from the effects of any changes to the
     namespace prefixes in the containing SOAP message are advised to
     construct expressions in a manner that avoids the use of namespace
     prefixes. For example, use an expression such as
     "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
    </p></div><div class="div2">
<h3><a name="Get" id="Get"></a>4.3 Get</h3><p>
     To retrieve a subset of a resource
     a client MUST specify the WS-Fragment Dialect IRI in the wst:Get request.
    </p><p>
     The Get request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Get

<b>[Body]</b>
  &lt;wst:Get Dialect="<b>http://www.w3.org/2011/03/ws-fra</b>" ...&gt;
    <b>&lt;wsf:Expression Language="</b><em><b>xs:anyURI</b></em><b>"? ...&gt;
      </b><em><b>xs:any</b></em><b> *
    &lt;/wsf:Expression&gt;
    </b>
    <em>xs:any</em> *
  &lt;/wst:Get&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the outline
     listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Get@Dialect </dt><dd><p>
        This attribute MUST be set to http://www.w3.org/2011/03/ws-fra.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Get/wsf:Expression </dt><dd><p>
        This element identifies which fragment in the resource this 
        operation applies to. If the value of this element does not 
        conform to the syntax of the language specified in the Language 
        attribute, or is semantically invalid, a wsf:InvalidExpression 
        fault MUST be generated.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Get/wsf:Expression@Language </dt><dd><p>
        Implied value is "http://www.w3.org/2011/03/ws-fra/XPath10".
       </p><p>
        This OPTIONAL IRI indicates which expression language will be
        used to identify the subset of the resource this operation applies
        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
        does not support the specified Language.
       </p></dd></dl><p>
     If the resource accepts a Get request, it MUST reply with a response of
     the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/GetResponse

<b>[Body]</b>
  &lt;wst:GetResponse ...&gt;
    <b>&lt;wsf:Value ...&gt; </b><em><b>xs:any</b></em><b> * &lt;/wsf:Value&gt;
    </b><em>xs:any</em> *
  &lt;/wst:GetResponse&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the 
     outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:GetResponse/wsf:Value </dt><dd><p>
        This element encompasses the fragment response corresponding to the 
        wsf:Expression in the request and MUST contain the subset of the 
        resource identified by the wsf:Expression element in the
        corresponding Get request. If the
        Expression evaluates to a fragment with no value, then this
        element MAY be empty.
       </p></dd></dl><p>
     Other components of the outline above are not further constrained 
     by this specification.
    </p></div><div class="div2">
<h3><a name="Put" id="Put"></a>4.4 Put</h3><p>
     To update a subset of a resource a client MUST specify the WS-Fragment
     IRI in the wst:Put request.
    </p><p>
     The Put request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/Put

<b>[Body]</b>
  &lt;wst:Put Dialect="<b>http://www.w3.org/2011/03/ws-fra</b>" ...&gt;
    <b>&lt;wsf:Fragment ...&gt;
      &lt;wsf:Expression Language="</b><em><b>xs:anyURI</b></em><b>"? Mode="</b><em><b>xs:anyURI</b></em><b>"? ...&gt;
        </b><em><b>xs:any</b></em><b> *
      &lt;/wsf:Expression&gt; 
      &lt;wsf:Value ...&gt;
        </b><em><b>xs:any</b></em><b> *
      &lt;/wsf:Value&gt; ?
    &lt;/wsf:Fragment&gt;
    </b>
    <em>xs:any</em> *
  &lt;/wst:Put&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the outline
     listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wst:Put@Dialect </dt><dd><p>
        This attribute MUST be set to http://www.w3.org/2011/03/ws-fra.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment </dt><dd><p>
        This element contains an expression that identifies the location of
        a fragment in the resource and a value for the fragment. 
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression </dt><dd><p>
        This element identifies which fragment in the resource this operation 
        applies to. If the value of this element does not conform to the 
        syntax of the language specified in the Language attribute, or is 
        semantically invalid, a wsf:InvalidExpression fault MUST be generated.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Language </dt><dd><p>
        Implied value is "http://www.w3.org/2011/03/ws-fra/XPath10".
       </p><p>
        This OPTIONAL IRI indicates which expression language will be 
        used to identify the subset of the resource this operation applies
        to. A resource MUST generate a wsf:UnsupportedLanguage fault if it 
        does not support the specified Language.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode </dt><dd><p>
        This OPTIONAL attribute indicates the type of update to be 
        performed on this fragment.
        The implied value for this attribute is 
        "http://www.w3.org/2011/03/ws-fra/Modes/Replace". 
        A resource MUST generate a wsf:UnsupportedMode fault if the specified 
        Mode is not supported.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2011/03/ws-fra/Modes/Replace" </dt><dd><p>
        This Mode value indicates that the children of the Value element 
        MUST be added to the resource representation in place of the 
        fragment referenced by the children of the Expression element.
       </p><p>
        This Mode value has the net effect of doing a "delete" on the 
        referenced fragment, followed by an "insert" on the fragment's
        parent.
       </p><p>
        If the fragment is absent, or if the Expression evaluates to an 
        empty fragment, then the "delete" portion of the operation MUST 
        have no effect. If the implementation is schema aware 
        and it detects that the Expression is not valid per the schema then a 
        wsf:InvalidExpression fault MUST be generated.
       </p><p>
        When this Mode value is used the Value element MUST be present.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2011/03/ws-fra/Modes/Add" </dt><dd><p>
        This Mode value indicates that the children of the Value element 
        MUST be added to the resource representation relative to the 
        fragment referenced by the children of the Expression element.
       </p><p>
        If the Value element contains an attribute node then the attribute 
        MUST be added to the referenced element. If an attribute with 
        that name already exists then a wst:InvalidRepresentation fault 
        MUST be generated.
       </p><p>
        If the Value element contains a fragment that is not an 
        attribute node, the children of the Value element are added as 
        children to the referenced fragment.
       </p><p>
        When adding a child element and a child element of that QName 
        already exists, the new element MUST be added to the end of that 
        sequence of child elements. If the requester wants to ensure 
        that only a single instance of that child element is present 
        it can use the "Replace" instead.
       </p><p>
        While schema validation is not required of resource managers, 
        since resources are only allowed to have a single root element, 
        attempts to "Add" a second root element MUST generate a 
        wst:InvalidRepresentation fault.
       </p><p>
        When this Mode value is used the Value element MUST be present.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2011/03/ws-fra/Modes/InsertBefore" </dt><dd><p>
        This Mode value indicates that the children of the Value element 
        MUST be inserted immediately before (as a sibling to) the fragment 
        referenced by the children of the Expression element. Note, this 
        Mode MUST NOT be used for attributes.
       </p><p>
        If the implementation is schema aware and it detects that the 
        Expression does not reference a sequence then it MUST generate 
        a wst:InvalidRepresentation fault. 
       </p><p>
        When this Mode value is used the Value element MUST be present.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2011/03/ws-fra/Modes/InsertAfter" </dt><dd><p>
        This Mode value indicates that the children of the Value element 
        MUST be inserted immediately after (as a sibling to) the fragment 
        referenced by the children of the Expression element. Note, this 
        Mode MUST NOT be used for attributes.
       </p><p>
        If the implementation is schema aware and it detects that the 
        Expression does not reference a sequence then it MUST generate 
        a wst:InvalidRepresentation fault. 
       </p><p>
        When this Mode value is used the Value element MUST be present.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2011/03/ws-fra/Modes/Remove" </dt><dd><p>
        This Mode value indicates that the resource representation referenced 
        by the children of the Expression element MUST be deleted from the 
        resource representation.  If the target fragment is not present then 
        this operation MUST have no effect.
       </p><p>
        When this Mode value is used the Value element MUST NOT be present.
       </p></dd><dt class="label"> <b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Value </dt><dd><p>
        This OPTIONAL element contains the fragment resource representation
        to be added to the resource representation.
        If the contents of this element are invalid, a 
        wst:InvalidRepresentation fault MUST be generated.
       </p><p>
        Any optional values (element or attributes) within this subset that are 
        not specified in the Value element MUST be set to a resource-specific 
        default value.
       </p><p>
        The children of this element MUST be serialized according to the 
        rules defined in <a href="#FragSer"><b>4.2 Fragment Serialization</b></a>.
       </p></dd></dl><p>
     If the resource accepts a Put request, it MUST reply with a response of
     the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-tra/PutResponse

<b>[Body]</b>
  &lt;wst:PutResponse ...&gt;
    &lt;wst:Representation ...&gt;
      <em>xs:any</em> ?
    &lt;/wst:Representation ...&gt; ?
    <em>xs:any</em> *
  &lt;/wst:PutResponse&gt;</pre></div></div><p>
     There are no additional constraints beyond what WS-Transfer defines.
    </p><p>
     The following table elaborates on the expected behavior of a 
     WS-Fragment Put request using the XPath language.
    </p><p>
     Given a resource whose schema is defined as:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;a foo="xs:integer"? bar="xs:integer"? &gt;
  ( &lt;b&gt; &lt;c/&gt; &lt;/b&gt; * | &lt;c/&gt; ) 
&lt;/a&gt;</pre></div></div><p>
     Note: for the sake of clarity, some element names have a ' or " to 
     indicate that it is a different instance of that type of element.
    </p><table border="1"><tbody><tr><td>Initial Representation</td><td>@Mode</td><td>Expression</td><td>Value</td><td>Final Represenation</td></tr><tr><td></td><td>Add</td><td>/ or /*</td><td>&lt;a/&gt;</td><td>&lt;a/&gt;</td></tr><tr><td></td><td>Replace</td><td>/ or /*</td><td>&lt;a/&gt;</td><td>&lt;a/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Add</td><td>/ or /*</td><td>&lt;a'/&gt;</td><td>fault</td></tr><tr><td>&lt;a/&gt;</td><td>Replace</td><td>/a</td><td>&lt;a'/&gt;</td><td>&lt;a'/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Add</td><td>/a</td><td>&lt;wsf:AttributeNode name="foo"&gt;1&lt;/wsf:AttributeNode&gt;</td><td>&lt;a foo="1"/&gt;</td></tr><tr><td>&lt;a foo="1"/&gt;</td><td>Add</td><td>/a</td><td>&lt;wsf:AttributeNode name="foo"&gt;2&lt;/wsf:AttributeNode&gt;</td><td>fault</td></tr><tr><td>&lt;a foo="1"/&gt;</td><td>Replace</td><td>/a@foo</td><td>&lt;wsf:AttributeNode name="foo"&gt;2&lt;/wsf:AttributeNode&gt;</td><td>&lt;a foo="2"/&gt;</td></tr><tr><td>&lt;a foo="1"/&gt;</td><td>Replace</td><td>/a@foo</td><td>&lt;wsf:AttributeNode name="bar"&gt;2&lt;/wsf:AttributeNode&gt;</td><td>&lt;a bar="2"/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Replace</td><td>/a@foo</td><td>&lt;wsf:AttributeNode name="bar"&gt;2&lt;/wsf:AttributeNode&gt;</td><td>&lt;a bar="2"/&gt;</td></tr><tr><td>&lt;a foo="1"/&gt;</td><td>Remove</td><td>/a@foo</td><td></td><td>&lt;a/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Add</td><td>/a</td><td>&lt;b/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td><td>Add</td><td>/a</td><td>&lt;b'/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;b'/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td><td>Replace</td><td>/a/b</td><td>&lt;b'/&gt;</td><td>&lt;a&gt; &lt;b'/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Replace</td><td>/a/b</td><td>&lt;b/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>InsertAfter</td><td>/a/b or /a/b[last()]</td><td>&lt;b"/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;b"/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>InsertBefore</td><td>/a/b or /a/b[1]</td><td>&lt;b"/&gt;</td><td>&lt;a&gt; &lt;b"/&gt; &lt;b&gt; &lt;b'/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>Replace</td><td>/a/b</td><td>&lt;b"/&gt;</td><td>&lt;a&gt; &lt;b"/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>Replace</td><td>/a/b[1]</td><td>&lt;b"/&gt;</td><td>&lt;a&gt; &lt;b"/&gt; &lt;b'&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td><td>Remove</td><td>/a/b</td><td></td><td>&lt;a/&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>Remove</td><td>/a/b</td><td></td><td>&lt;a/&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>Remove</td><td>/a/b[1]</td><td></td><td>&lt;a&gt; &lt;b'&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a&gt; &lt;b/&gt; &lt;b'&gt; &lt;/a&gt;</td><td>Replace</td><td>/a/b</td><td>&lt;c/&gt;</td><td>&lt;a&gt; &lt;c&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>Replace</td><td>/ or /*</td><td>&lt;a'/&gt;</td><td>&lt;a'/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>InsertBefore</td><td>/ or /*</td><td>&lt;a'/&gt;</td><td>fault</td></tr><tr><td>&lt;a/&gt;</td><td>InsertAfter</td><td>/ or /*</td><td>&lt;a'/&gt;</td><td>fault</td></tr><tr><td></td><td>InsertBefore</td><td>/ or /*</td><td>&lt;a/&gt;</td><td>&lt;a/&gt;</td></tr><tr><td></td><td>InsertAfter</td><td>/ or /*</td><td>&lt;a/&gt;</td><td>&lt;a/&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>InsertBefore</td><td>/a/b</td><td>&lt;b/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td></tr><tr><td>&lt;a/&gt;</td><td>InsertAfter</td><td>/a/b</td><td>&lt;b/&gt;</td><td>&lt;a&gt; &lt;b/&gt; &lt;/a&gt;</td></tr></tbody></table></div><div class="div2">
<h3><a name="Delete" id="Delete"></a>4.5 Delete</h3><p>
     This specification does not extend the Delete operation defined in
     WS-Transfer.
    </p></div><div class="div2">
<h3><a name="Create" id="Create"></a>4.6 Create</h3><p>
     This specification does not extend the Create operation defined in
     WS-Transfer.
    </p></div></div><div class="div1">
<h2><a name="idp1578688" id="idp1578688"></a>5 Examples</h2><div class="div2">
<h3><a name="idp1579344" id="idp1579344"></a>5.1 Examples</h3><p>
     In the following examples, and Expression Language definitions,
     the following representation of a resource is used for
     informational purposes:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;ab:AddressBook xmlns:ab="http://example.com/address"&gt;
  &lt;ab:owner&gt;Me&lt;/owner&gt;
  &lt;ab:size&gt;2&lt;/size&gt;
  &lt;ab:contact&gt;
    &lt;ab:name&gt;Joe Brown&lt;/name&gt;
    &lt;ab:address&gt;123 Main Street&lt;/address&gt;
    &lt;ab:city&gt;AnyTown&lt;/city&gt;
    &lt;ab:state&gt;CA&lt;/state&gt;
    &lt;ab:zip&gt;90210&lt;/zip&gt;
    &lt;ab:email&gt;joe@example.com&lt;/email&gt;
  &lt;/ab:contact&gt;
  &lt;ab:contact&gt;
    &lt;ab:name&gt;Mary Smith&lt;/name&gt;
    &lt;ab:address&gt;345 South Pine&lt;/address&gt;
    &lt;ab:city&gt;AnyTown&lt;/city&gt;
    &lt;ab:state&gt;CA&lt;/state&gt;
    &lt;ab:zip&gt;90210&lt;/zip&gt;
    &lt;ab:email&gt;mary@example.com&lt;/email&gt;
  &lt;/ab:contact&gt;
&lt;/ab:AddressBook&gt;</pre></div></div><p>
     The following shows a sample SOAP envelope containing a Get 
     request:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope  
    xmlns:s="http://www.w3.org/2003/05/soap-envelope" 
    xmlns:wsa="http://www.w3.org/2005/08/addressing" 
    xmlns:ex="http://www.example.com/" &gt;
  &lt;s:Header&gt;
    &lt;wsa:To&gt;http://www.example.org/resourceABC&lt;/wsa:To&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/Get
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:00000000-0000-0000-C000-000000000046
    &lt;/wsa:MessageID&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:Get Dialect="http://www.w3.org/2011/03/ws-fra"&gt;
      &lt;wsf:Expression Language="http://www.w3.org/2011/03/ws-fra/QName"&gt;
        ab:contact
      &lt;/wsf:Expression&gt;
    &lt;/wst:Get&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     The following shows the corresponding response message:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope  
    xmlns:s="http://www.w3.org/2003/05/soap-envelope" 
    xmlns:wsa="http://www.w3.org/2005/08/addressing" 
    xmlns:ex="http://www.example.com/" &gt;
  &lt;s:Header&gt;
    &lt;wsa:Action&gt;
      http://www.w3.org/2011/03/ws-tra/GetResponse
    &lt;/wsa:Action&gt;
    &lt;wsa:MessageID&gt;
      urn:uuid:0000010e-0000-0000-C000-000000000047
    &lt;/wsa:MessageID&gt;
    &lt;wsa:RelatesTo&gt;
      urn:uuid:00000000-0000-0000-C000-000000000046
    &lt;/wsa:RelatesTo&gt;
  &lt;/s:Header&gt;
  &lt;s:Body&gt;
    &lt;wst:GetResponse&gt;
      &lt;wsf:Value&gt;
        &lt;ab:contact&gt;
          &lt;ab:name&gt;Joe Brown&lt;/name&gt;
          &lt;ab:address&gt;123 Main Street&lt;/address&gt;
          &lt;ab:city&gt;AnyTown&lt;/city&gt;
          &lt;ab:state&gt;CA&lt;/state&gt;
          &lt;ab:zip&gt;90210&lt;/zip&gt;
          &lt;ab:email&gt;joe@example.com&lt;/email&gt;
        &lt;/ab:contact&gt;
        &lt;ab:contact&gt;
          &lt;ab:name&gt;Mary Smith&lt;/name&gt;
          &lt;ab:address&gt;345 South Pine&lt;/address&gt;
          &lt;ab:city&gt;AnyTown&lt;/city&gt;
          &lt;ab:state&gt;CA&lt;/state&gt;
          &lt;ab:zip&gt;90210&lt;/zip&gt;
          &lt;ab:email&gt;mary@example.com&lt;/email&gt;
        &lt;/ab:contact&gt;
      &lt;/wsf:Value&gt;
    &lt;/wst:GetResponse&gt;
  &lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div></div></div><div class="div1">
<h2><a name="QName" id="QName"></a>6 QName Expression Language</h2><p>
    The QName expression language is a syntax for expressions that 
    uses a single QName to reference the immediate children of the root 
    element of 
    the resource representation.  The expression MUST evaluate to zero or 
    more elements, each including the element name, any attributes 
    and its entire content.
    This language can be implemented as a precise subset of the 
    XPath 1.0 <a href="#XPath1">[XPath1.0]</a> language.
   </p><p>
    The QName language MUST be indicated by using the IRI:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra/QName">http://www.w3.org/2011/03/ws-fra/QName</a></pre></div></div></div><div class="div1">
<h2><a name="XPath10" id="XPath10"></a>7 XPath 1.0 Expression Language</h2><p>
    The XPath 1.0 expression language uses an XPath to reference specific
    fragments of the resource representation. The XPath is logically 
    applied to the XML representation of the resource and the result of 
    the XPath is returned as the value for that expression. 
    This language is
    useful for resources with full XPath processing capability or which 
    need to support returning values computed from their resource 
    representation.
   </p><p>
    An XPath 1.0 expression is an expression whose context is:
   </p><ul><li><p>
      Context Node: the root element of the XML representation of the resource
     </p></li><li><p>Context Position: 1</p></li><li><p>Context Size: 1</p></li><li><p>Variable Binding: None</p></li><li><p>Function Libraries: Core function library</p></li><li><p>
      Namespace Declarations: Any namespace declarations in-scope where 
      the XPath expression appears
     </p></li></ul><p>
    The XPath 1.0 language can
    define references to any element, attribute or value in the resource
    representation and can also be used to compute values from the resource
    representation.
   </p><p>The XPath 1.0 language MUST be indicated by using the IRI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra/XPath10">http://www.w3.org/2011/03/ws-fra/XPath10</a></pre></div></div><p>
    Most of the examples assume the following XML sample acting
    as a "resource" document:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a&gt;
(02)   &lt;b&gt;
(03)     &lt;c d="30"&gt; 20 &lt;/c&gt;
(04)   &lt;/b&gt;
(05)   &lt;e&gt;
(06)     &lt;f/&gt;
(07)     &lt;f/&gt;
(08)   &lt;/e&gt;
(09) &lt;/a&gt;</pre></div></div><p>
    The context and document root node need
    clarification. The XPath 1.0 language assumes that the root is the root
    node of the resource document, not the SOAP envelope or any other wrapper
    element which might contain the resource.
   </p><p>
    Further, the default context is the root element and the
    context position is 1.
   </p><p>
    In view of this, the / operator selects the containing root,
    and the only valid operand which can follow it is the outermost element 
    of the resource:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a</pre></div></div><p>The following paths are equivalent:</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b
(02) b</pre></div></div><p>
    Note that because the context node is the root element, a
    relative path selects a matching child element.
   </p><p>
    The text() NodeTest MAY be applied as a final token to the
    selected element. This NodeTest selects any text nodes that are
    children of the selected element. If the element only contains text
    content, the return value will be a node-set containing a single text node.
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) b/c/text()</pre></div></div><p>
    The above expression would return a node-set containing a
    single text node with the value <em>20 </em>as its result. This text 
    node would then be serialized into the following XML representation:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;20&lt;/wsf:TextNode&gt;</pre></div></div><p>
    If accessed, attributes MUST be the final token in the path
    and they MAY be namespace-qualified or unqualified names, as needed:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c/@d</pre></div></div><p>
    The above expression would return a node-set containing a
    single attribute node with the value <em>d="30"</em> as its result. 
    This attribute node would then be serialized into the following XML
    representation:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="d"&gt;30&lt;/wsf:AttributeNode&gt;</pre></div></div><p>
    Selection of an element returns the element and its entire
    content. The path <em>/a/b </em>executed against the sample XML 
    returns a
    node-set containing a single element node which serializes directly:
   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;b&gt; &lt;c d="30"&gt; 20 &lt;/c&gt; &lt;/b&gt;</pre></div></div></div><div class="div1">
<h2><a name="XPath20" id="XPath20"></a>8 XPath 2.0 Expression Language</h2><p>
    The XPath 2.0 expression language is the same as the XPath 1.0
    expression language except it uses <a href="#XPath2">[XPath2.0]</a>
    as the expression language.
   </p><p>The XPath 2.0 language MUST be indicated by using the IRI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra/XPath20">http://www.w3.org/2011/03/ws-fra/XPath20</a></pre></div></div></div><div class="div1">
<h2><a name="Faults" id="Faults"></a>9 Faults</h2><p>
    All fault messages defined in this specification MUST be sent
    according to the rules and usage described in
    <a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
    Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
    The <b>[Action]</b> property below MUST be used for faults
    defined in this specification:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra/fault">http://www.w3.org/2011/03/ws-fra/fault</a></pre></div></div><p>
    The definitions of faults in this section use the following properties:
   </p><p>
    <b>[Code]</b> The fault code.<br />
    <b>[Subcode]</b> The fault subcode.<br />
    <b>[Reason]</b> The English language reason element.<br />
    <b>[Detail]</b> The detail element. If absent, no detail element 
    is defined for the fault.<br />
   </p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s12:Body&gt;
    &lt;s12:Fault&gt;
      &lt;s12:Code&gt;
        &lt;s12:Value&gt;<b>[Code]</b>&lt;/s12:Value&gt;
        &lt;s12:Subcode&gt;
          &lt;s12:Value&gt;<b>[Subcode]</b>&lt;/s12:Value&gt;
        &lt;/s12:Subcode&gt;
      &lt;/s12:Code&gt;
      &lt;s12:Reason&gt;
        &lt;s12:Text xml:lang="en"&gt;<b>[Reason]</b>&lt;/s12:Text&gt;
      &lt;/s12:Reason&gt;
      &lt;s12:Detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/s12:Detail&gt;
    &lt;/s12:Fault&gt;
  &lt;/s12:Body&gt;
&lt;/s12:Envelope&gt;</pre></div></div><p>The properties bind to a SOAP 1.1 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s11:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s11:Body&gt;
    &lt;s11:Fault&gt;
      &lt;faultcode&gt;<b>[Subcode]</b>&lt;/faultcode&gt;
      &lt;faultstring xml:lang="en"&gt;<b>[Reason]</b>&lt;/faultstring&gt;
      &lt;detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/detail&gt;
    &lt;/s11:Fault&gt;
  &lt;/s11:Body&gt;
&lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"></a>9.1 UnsupportedLanguage</h3><p>
     This fault MUST be generated when a service detects an unknown or
     unsupported Language 
     IRI in a request message. 
    </p><a name="Table3" id="Table3"></a><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wsf:UnsupportedLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
        The specified Language IRI is not supported.
       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Language IRI.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="InvalidExpression" id="InvalidExpression"></a>9.2 InvalidExpression</h3><p>
     This fault MUST be generated when a service determines that the Language
     expression specified in a request does not conform to the syntax
     of the language specified in the Language attribute or is semantically
     invalid.
    </p><a name="Table5" id="Table5"></a><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wsf:InvalidExpression</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
        The specified Language expression is invalid.
       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedMode" id="UnsupportedMode"></a>9.3 UnsupportedMode</h3><p>
     This fault MUST be generated when a service detects a Mode in a Put
     request that is not supported.
    </p><a name="Table6" id="Table6"></a><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wsf:UnsupportedMode</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
        The specified mode is not supported.
       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Mode.</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="metadata" id="metadata"></a>10 WS-Fragment Metadata</h2><p>
    An endpoint MAY indicate its support of WS-Fragment, or its features,
    by including the WS-Fragment FragmentAssertion Policy assertion within its 
    WSDL. By
    doing so the endpoint is indicating that the corresponding WS-Fragment
    features are supported by that endpoint.
   </p><div class="div2">
<h3><a name="idp1682688" id="idp1682688"></a>10.1 Fragment Assertion</h3><p>
     Services indicate their support for the WS-Fragment specification through 
     the use of the Web Services
     Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
     Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
    </p><p>
     This specification defines a policy assertion (wsf:FragmentAssertion).  
     The normative outline of this assertion is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsf:FragmentAssertion ...&gt;
  &lt;wsf:Language URI="<em>xs:anyURI</em> ...&gt; 
    <em>xs:any</em>*
  &lt;/wsf:Language&gt; * 
  <em>xs:any</em>*
&lt;/wsf:FragmentAssertion&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> /wsf:FragmentAssertion </dt><dd><p>
         This policy assertion has Endpoint Policy Subject. When present
         in a policy alternative, it indicates that the WS-Fragment
         protocol MUST be used when communicating with this endpoint. 
        </p></dd><dt class="label"> /wsf:FragmentAssertion/wsf:Language </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the 
         specified Language IRI.
        </p></dd><dt class="label"> /wsf:FragmentAssertion/wsf:Language/xs:any </dt><dd><p>
         This extensibility point allows for additional Language specific 
         metadata to be included within the policy assertion. Any metadata 
         that appears is scoped to the use of the specified Language URI.
        </p></dd><dt class="label"> /wsf:FragmentAssertion/xs:any </dt><dd><p>
         This extensibility point allows for additional WS-Fragment 
         specific metadata to be included within the policy assertion. 
         Any metadata that appears is scoped to the operations and features 
         of the WS-Fragment specification.
        </p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"></a>11 Acknowledgements</h2><p>
    This specification has been developed as a result of joint
    work with many individuals and teams, including: 
     Alessio Soldano (Red Hat),
     Ashok Malhotra (Oracle Corp.),
     Asir Vedamuthu (Microsoft Corp.),
     Bob Freund (Hitachi, Ltd.),
     Bob Natale (MITRE Corp.),
     David Snelling (Fujitsu, Ltd.),
     Doug Davis (IBM),
     Fred Maciel (Hitachi, Ltd.),
     Geoff Bullen (Microsoft Corp.),
     Gilbert Pilz (Oracle Corp.),
     Greg Carpenter (Microsoft Corp.),
     Jeff Mischkinsky (Oracle Corp.),
     Katy Warr (IBM),
     Li Li (Avaya Communications),
     Mark Little (Red Hat),
     Martin Chapman (Oracle Corp.),
     Paul Fremantle (WSO2),
     Paul Nolan (IBM),
     Prasad Yendluri (Software AG),
     Ram Jeyaraman (Microsoft Corp.),
     Sreedhara Narayanaswamy (CA),
     Sumeet Vij (Software AG),
     Tom Rutt (Fujitsu, Ltd.),
     Vikas Varma (Software AG),
     Wu Chou (Avaya Communications),
     Yves Lafon (W3C/ERCIM).
   </p></div><div class="div1">
<h2><a name="refs" id="refs"></a>12 References</h2><div class="div2">
<h3><a name="idp1699968" id="idp1699968"></a>12.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"></a>BP12</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 1.2
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"></a>BP20</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 2.0
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd>
       <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
        Key words for use in RFCs to Indicate Requirement Levels
       </cite></a>
       , S. Bradner, Author.
       Internet Engineering Task Force, March 1997.
      Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"></a>RFC 3987</dt><dd>
       <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
        Internationalized Resource Identifiers (IRIs)
       </cite></a>
       , M. Duerst and M. Suignard, Authors.
       Internet Engineering Task Force, January 2005.
      Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP11</dt><dd>
       <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
        W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
       </cite></a>
       , D. Box, et al, Editors.
       World Wide Web Consortium (W3C), 8 May 2000.
      Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"></a>SOAP12</dt><dd>
       <a href="http://www.w3.org/TR/soap12-part1/"><cite>
        W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
       </cite></a>
       , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
        Editors.
       World Wide Web Consortium (W3C), 27 April 2007.
      Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"></a>WS-Addressing</dt><dd>
       <a href="http://www.w3.org/TR/ws-addr-core"><cite>
        W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </cite></a>
       , M. Gudgin, M. Hadley, T. Rogers, Editors.
       World Wide Web Consortium (W3C), 9 May 2006.
      Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="WSABinding" id="WSABinding"></a>WS-Addressing 1.0 SOAP Binding</dt><dd>
       <a href="http://www.w3.org/TR/ws-addr-soap"><cite>
        W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
       </cite></a>
       , M. Gudgin, M. Hadley, T. Rogers, Editors.
       World Wide Web Consortium (W3C), 9 May 2006.
      Available at <a href="http://www.w3.org/TR/ws-addr-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
       <a href="http://www.w3.org/TR/ws-policy/"><cite>
        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
       </cite></a>
       , A. Vedamuthu, et al., Editors.
       World Wide Web Consortium (W3C), 4 September 2007.
      Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="wspolicyattach" id="wspolicyattach"></a>WS-Policy Attachment</dt><dd>
       <a href="http://www.w3.org/TR/ws-policy-attach"><cite>
        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
       </cite></a>
       , A. Vedamuthu, et al., Editors.
       World Wide Web Consortium (W3C), 4 September 2007.
      Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd><dt class="label"><a name="WsTransfer" id="WsTransfer"></a>WS-Transfer</dt><dd>
      <a href="http://www.w3.org/TR/ws-transfer"><cite>
       W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
      </cite></a>
      , D. Davis, et al., Editors.
      World Wide Web Consortium (W3C), 15 September 2009.
      Available at <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL11</dt><dd>
       <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
        W3C Note, "Web Services Description Language (WSDL) 1.1"
       </cite></a>
       , E. Christensen, et al., Editors.
       World Wide Web Consortium (W3C), 15 March 2001
      Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
       <a href="http://www.w3.org/TR/xml-infoset"><cite>
        W3C Recommendation, "XML Information Set (Second Edition)"
       </cite></a>
       , J. Cowan, R. Tobin, Editors.
       World Wide Web Consortium (W3C), 4 February 2004.
      Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XMLSchema - Part 1</dt><dd>
       <a href="http://www.w3.org/TR/xmlschema-1/"><cite>
        W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
       </cite></a>
       , H. Thompson, et al., Editors.
       World Wide Web Consortium (W3C), 28 October 2004.
      Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XMLSchema - Part 2</dt><dd>
       <a href="http://www.w3.org/TR/xmlschema-2/"><cite>
        W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
       </cite></a>
       , P. Biron, A. Malhotra, Editors.
       World Wide Web Consortium (W3C), 28 October 2004.
      Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd><dt class="label"><a name="XPath1" id="XPath1"></a>XPath1.0</dt><dd>
       <a href="http://www.w3.org/TR/xpath"><cite>
        W3C Recommendation, "XML Path Language (XPath) Version 1.0"
       </cite></a>
       , J. Clark, S. DeRose, Editors.
       World Wide Web Consortium (W3C), 16 November 1999.
      Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd><dt class="label"><a name="XPath2" id="XPath2"></a>XPath2.0</dt><dd>
       <a href="http://www.w3.org/TR/xpath20/"><cite>
        W3C Recommendation, "XML Path Language (XPath) 2.0"
       </cite></a>
       , A. Berglund, et al., Editors.
       World Wide Web Consortium (W3C), 23 January 2007.
      Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="Appendix_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"></a>A XML Schema</h2><p>
    A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
    <a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
    retrieved from the following address:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-fra/Fragment.xsd">http://www.w3.org/2011/03/ws-fra/fragment.xsd</a></pre></div></div><p>
    A non-normative copy of the XML schema is listed below for convenience.
   </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;xs:schema 
  targetNamespace='http://www.w3.org/2011/03/ws-fra'
  xmlns:tns='http://www.w3.org/2011/03/ws-fra'
  xmlns:xs='http://www.w3.org/2001/XMLSchema'
  elementFormDefault='qualified'
  blockDefault='#all' &gt;
 
  &lt;xs:complexType name='ExpressionType'&gt;
    &lt;xs:sequence&gt;
      &lt;xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:attribute name='Language' type='xs:anyURI' use='optional'/&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name='Expression' type='tns:ExpressionType'/&gt;

  &lt;xs:complexType name='ValueType'&gt;
    &lt;xs:sequence&gt;
      &lt;xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name='Value' type='tns:ValueType'/&gt;
  
  &lt;xs:element name='Fragment'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Expression' type='tns:ExpressionType'/&gt;
        &lt;xs:element name='Value' type='tns:ValueType' minOccurs='0'/&gt;
        &lt;xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Policy --&gt;
  &lt;xs:complexType name='URI'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:anyURI'&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:element name='FragmentAssertion'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Language' minOccurs='0' maxOccurs='unbounded'&gt;
          &lt;xs:complexType&gt;
            &lt;xs:sequence&gt;
              &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                          maxOccurs='0'/&gt;
            &lt;/xs:sequence&gt;
            &lt;xs:attribute name='URI' type='xs:anyURI' use='required' /&gt;
            &lt;xs:anyAttribute namespace="##other" processContents='lax'/&gt;
          &lt;/xs:complexType&gt;
        &lt;/xs:element&gt;
        &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                    maxOccurs='unbounded'/&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

&lt;/xs:schema&gt;</pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"></a>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/08/01 </td><td> DD </td><td> Initial draft </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7197">7197</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a>
      </td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a>
      </td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a>
      </td></tr><tr><td> 2009/09/30 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7088">7088</a>
      </td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7770">7770</a>
      </td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a>
      </td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6407">6407</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7969">7969</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a>
      </td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a>
      </td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8194">8194</a>
      </td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8195">8195</a>
      </td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8192">8192</a>
      </td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a>
      </td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8181">8181</a>
      </td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8257">8257</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8229">8229</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302">8302</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180">8180</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191">8191</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a>
      </td></tr><tr><td> 2010/02/10 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a>
      </td></tr><tr><td> 2010/02/10 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a>
      </td></tr><tr><td> 2010/03/02 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185">8185</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193">8193</a>
      </td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a>
      </td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9558">9558</a>
      </td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</a>
      </td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a>
      </td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a>
      </td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11724">11724</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11772">11772</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12042">12042</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a>
      </td></tr></tbody></table></div></div></body></html>