|
8 | 8 | <!ENTITY rfc3339 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3339.xml">
|
9 | 9 | <!ENTITY rfc2045 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2045.xml">
|
10 | 10 | <!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
|
11 |
| -<!ENTITY rfc2396 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2396.xml"> |
12 | 11 | <!ENTITY iddiscovery SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.hammer-discovery.xml">
|
13 | 12 | <!ENTITY uritemplate SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.gregorio-uritemplate.xml">
|
14 | 13 | <!ENTITY linkheader SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.nottingham-http-link-header.xml">
|
@@ -825,89 +824,17 @@ GET /Resource/
|
825 | 824 | resolving fragment identifiers in URIs within the instance
|
826 | 825 | representations. This applies to the instance object URIs and all
|
827 | 826 | children of the instance object's URIs. The default fragment resolution
|
828 |
| - protocol is "slash-delimited", which is defined below. Other fragment |
| 827 | + protocol is "json-pointer", which is defined below. Other fragment |
829 | 828 | resolution protocols MAY be used, but are not defined in this document.
|
830 | 829 | </t>
|
831 | 830 |
|
832 | 831 | <t>
|
833 |
| - The fragment identifier is based on <xref target="RFC2396">RFC 2396, Sec 5</xref>, and defines the |
| 832 | + The fragment identifier is based on <xref target="RFC3986">RFC 3986, Sec 5</xref>, and defines the |
834 | 833 | mechanism for resolving references to entities within a document.
|
835 | 834 | </t>
|
836 | 835 |
|
837 |
| - <section title="slash-delimited fragment resolution"> |
838 |
| - <t> |
839 |
| - With the slash-delimited fragment resolution protocol, the fragment |
840 |
| - identifier is interpreted as a series of property reference tokens that start with and |
841 |
| - are delimited by the "/" character (\x2F). Each property reference token |
842 |
| - is a series of unreserved or escaped URI characters. Each property |
843 |
| - reference token SHOULD be interpreted, starting from the beginning of |
844 |
| - the fragment identifier, as a path reference in the target JSON |
845 |
| - structure. The final target value of the fragment can be determined by |
846 |
| - starting with the root of the JSON structure from the representation of |
847 |
| - the resource identified by the pre-fragment URI. If the target is a JSON |
848 |
| - object, then the new target is the value of the property with the name |
849 |
| - identified by the next property reference token in the fragment. If the |
850 |
| - target is a JSON array, then the target is determined by finding the |
851 |
| - item in array the array with the index defined by the next property |
852 |
| - reference token (which MUST be a number). The target is successively |
853 |
| - updated for each property reference token, until the entire fragment has |
854 |
| - been traversed. |
855 |
| - </t> |
856 |
| - |
857 |
| - <t> |
858 |
| - Property names SHOULD be URI-encoded. In particular, any "/" in a |
859 |
| - property name MUST be encoded to avoid being interpreted as a property |
860 |
| - delimiter. |
861 |
| - </t> |
862 |
| - |
863 |
| - <t> |
864 |
| - <figure> |
865 |
| - <preamble>For example, for the following JSON representation:</preamble> |
866 |
| - <artwork> |
867 |
| -<![CDATA[ |
868 |
| -{ |
869 |
| - "foo": { |
870 |
| - "anArray": [{ |
871 |
| - "prop": 44 |
872 |
| - }], |
873 |
| - "another prop": { |
874 |
| - "baz": "A string" |
875 |
| - } |
876 |
| - } |
877 |
| -} |
878 |
| -]]> |
879 |
| - </artwork> |
880 |
| - </figure> |
881 |
| - |
882 |
| - <figure> |
883 |
| - <preamble>The following fragment identifiers would be resolved:</preamble> |
884 |
| - <artwork> |
885 |
| -<![CDATA[ |
886 |
| -fragment identifier resolution |
887 |
| -------------------- ---------- |
888 |
| -# self, the root of the resource itself |
889 |
| -#/foo the object referred to by the foo property |
890 |
| -#/foo/another%20prop the object referred to by the "another prop" |
891 |
| - property of the object referred to by the |
892 |
| - "foo" property |
893 |
| -#/foo/another%20prop/baz the string referred to by the value of "baz" |
894 |
| - property of the "another prop" property of |
895 |
| - the object referred to by the "foo" property |
896 |
| -#/foo/anArray/0 the first object in the "anArray" array |
897 |
| -]]> |
898 |
| - </artwork> |
899 |
| - </figure> |
900 |
| - </t> |
901 |
| - </section> |
902 |
| - |
903 |
| - <section title="dot-delimited fragment resolution"> |
904 |
| - <t> |
905 |
| - The dot-delimited fragment resolution protocol is the same as |
906 |
| - slash-delimited fragment resolution protocol except that the "." character |
907 |
| - (\x2E) is used as the delimiter between property names (instead of "/") and |
908 |
| - the path does not need to start with a ".". For example, #.foo and #foo are a valid fragment |
909 |
| - identifiers for referencing the value of the foo propery. |
910 |
| - </t> |
| 836 | + <section title="json-pointer fragment resolution"> |
| 837 | + <t>The "json-pointer" fragment resolution protocol uses a <xref target="json-pointer">JSON Pointer</xref> to resolve fragment identifiers in URIs within instance representations.</t> |
911 | 838 | </section>
|
912 | 839 | </section>
|
913 | 840 |
|
@@ -1037,10 +964,21 @@ Content-Type: application/json; profile=/schema-for-this-data
|
1037 | 964 | <references title="Normative References">
|
1038 | 965 | &rfc2045;
|
1039 | 966 | &rfc2119;
|
1040 |
| - &rfc2396; |
1041 | 967 | &rfc3339;
|
1042 | 968 | &rfc3986;
|
1043 | 969 | &rfc4287;
|
| 970 | + <reference anchor="json-pointer" target="http://tools.ietf.org/html/draft-pbryan-zyp-json-pointer-02"> |
| 971 | + <front> |
| 972 | + <title>JSON Pointer</title> |
| 973 | + <author initials="P." surname="Bryan"> |
| 974 | + <organization>ForgeRock US, Inc.</organization> |
| 975 | + </author> |
| 976 | + <author initials="K." surname="Zyp"> |
| 977 | + <organization>SitePen (USA)</organization> |
| 978 | + </author> |
| 979 | + <date year="2011" month="October" /> |
| 980 | + </front> |
| 981 | + </reference> |
1044 | 982 | </references>
|
1045 | 983 | <references title="Informative References">
|
1046 | 984 | &rfc2616;
|
|
0 commit comments