RFC 7644 - System for Cross-domain Identity Management: Protocol. [Docs] [txt|pdf] [draft-ietf-scim-api] [Diff1] [Diff2] PROPOSED STANDARD Internet Engineering Task Force (IETF) P. Hunt, Ed. Request for Comments: 7644 Oracle Category: Standards Track K. Grizzle ISSN: 2070-1721 SailPoint M. RFC 7644 SCIM Protocol Specification September 2015 Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. RFC 7644 SCIM Protocol Specification September 2015 3.12. 1. The SCIM protocol is an application-level HTTP-based protocol for provisioning and managing identity data on the web and in cross-domain environments such as enterprise-to-cloud service providers or inter-cloud scenarios. 1.1.
This document is intended to serve as a guide to SCIM protocol usage for both SCIM HTTP service providers and HTTP clients who may provision information to service providers or retrieve information from them. RFC 7644 SCIM Protocol Specification September 2015 1.2. 1.3. RFC 7644 SCIM Protocol Specification September 2015 2. 2.1. 2.2.
Draft-ietf-appsawg-uri-get-off-my-lawn-02 - URI Design and Ownership. [Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] Versions: (draft-nottingham-uri-get-off-my-lawn) 00 01 02 03 04 05 appsawg M. Nottingham Internet-Draft April 3, 2014 Updates: 3986 (if approved) Intended status: BCP Expires: October 5, 2014 Abstract RFC3986 Section 3.1 defines URI syntax as "a federated and extensible naming system my further restrict the syntax and semantics of identifiers using that scheme. " In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing standards that mandate particular forms of URI substructure is inappropriate, because the effectively usurps ownership.
This document is intended to prevent this practice (sometimes called "URI Squatting") in standards, but updating RFC3986 to indicate where it is acceptable. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 1. RFC 5988 - Web Linking. [Docs] [txt|pdf] [draft-nottingham-...] [Diff1] [Diff2] [Errata] PROPOSED STANDARD Errata Exist Internet Engineering Task Force (IETF) M. Nottingham Request for Comments: 5988 October 2010 Updates: 4287 Category: Standards Track ISSN: 2070-1721 Abstract This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).
RFC 5988 Web Linking October 2010 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. RFC 5988 Web Linking October 2010 1. 2. RFC 5988 Web Linking October 2010 3. RFC 5988 Web Linking October 2010 4. In the simplest case, a link relation type identifies the semantics of a link. 4.1. 4.2. 5. 5.1. 5.2. 5.3. RFC 6901 - JavaScript Object Notation (JSON) Pointer. [Docs] [txt|pdf] [draft-ietf-appsaw...] [Diff1] [Diff2] [Errata] PROPOSED STANDARD Errata Exist Internet Engineering Task Force (IETF) P. Bryan, Ed. Request for Comments: 6901 Salesforce.com Category: Standards Track K. Zyp ISSN: 2070-1721 SitePen (USA) M. RFC 6901 JSON Pointer April 2013 Table of Contents 1. 1.
This specification defines JSON Pointer, a string syntax for identifying a specific value within a JavaScript Object Notation (JSON) document [RFC4627]. 2. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. A JSON Pointer is a Unicode string (see [RFC4627], Section 3) containing a sequence of zero or more reference tokens, each prefixed by a '/' (%x2F) character. 4. Evaluation of a JSON Pointer begins with a reference to the root value of a JSON document and completes with a reference to some value within the document. 5. 6. 7. 8.
Rfc-ref. Appsawg-json-patch-07 - JSON Patch. [Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] Versions: (draft-pbryan-json-patch) 00 01 02 03 04 05 06 07 08 09 10 RFC 6902 Applications Area Working Group P. Bryan, Ed. Internet-Draft Salesforce.com Intended status: Informational M. Nottingham, Ed. Expires: June 8, 2013 Akamai December 5, 2012 Abstract JSON Patch defines the media type "application/json-patch", a JSON document structure for expressing a sequence of operations to apply to a JSON document. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Draft JSON Patch December 2012 Table of Contents 1. Internet-Draft JSON Patch December 2012 1.
JavaScript Object Notation (JSON) [RFC4627] is a common format for the exchange and storage of structured data. 2. 3. Internet-Draft JSON Patch December 2012 4. 4.1. add 4.2. remove 4.3. replace The "replace" operation replaces the value at the target location with a new value. 4.4. move 4.5. copy 5.