module ietf-yang-patch {

    yang-version 1.1;

    namespace
      "urn:ietf:params:xml:ns:yang:ietf-yang-patch";

    prefix ypatch;

    import ietf-restconf {
      prefix rc;
    }

    organization
      "IETF NETCONF (Network Configuration) Working Group";

    contact
      "WG Web:   <http://tools.ietf.org/wg/netconf/>
WG List:  <mailto:netconf@ietf.org>

Author:   Andy Bierman
	  <mailto:andy@yumaworks.com>

Author:   Martin Bjorklund
	  <mailto:mbj@tail-f.com>

Author:   Kent Watsen
	  <mailto:kwatsen@juniper.net>";

    description
      "This module contains conceptual YANG specifications
for the YANG Patch and YANG Patch Status data structures.

Note that the YANG definitions within this module do not
represent configuration data of any kind.
The YANG grouping statements provide a normative syntax
for XML and JSON message encoding purposes.

Copyright (c) 2017 IETF Trust and the persons identified as
authors of the code.  All rights reserved.

Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC 8072; see
the RFC itself for full legal notices.";

    revision "2017-02-22" {
      description "Initial revision.";
      reference
        "RFC 8072: YANG Patch Media Type.";

    }

    rc:yang-data "yang-patch";
    rc:yang-data "yang-patch-status";

    typedef target-resource-offset {
      type string;
      description
        "Contains a data resource identifier string representing
a sub-resource within the target resource.
The document root for this expression is the
target resource that is specified in the
protocol operation (e.g., the URI for the PATCH request).

This string is encoded according the same rules as
a data resource identifier in a RESTCONF Request URI.";
      reference
        "RFC 8040, Section 3.5.3.";

    }
  }  // module ietf-yang-patch