We use the following schemas for our implementation of EPP:

• epp-1.0.xsd. This is one of the two standard base EPP schemas.
• eppcom-1.0.xsd. This is one of the two standard base EPP schemas.
• nom-domain-2.1.xsd. This is our custom schema for domain objects.
• nom-account-2.0.xsd. This is our custom schema for account objects.
• nom-contact-2.0.xsd. This is our custom schema for contact objects.
• host-1.0.xsd. This is a standard EPP schema.
• nom-notifications-2.1.xsd. This is our custom schema used for notifications.
• nom-abuse-feed-1.0.xsd. This is our custom schema used for the nominet abuse feed.
• std-warning-1.1.xsd.  This is used to encode warnings referring to the EPP standard host schema.
• nom-common-1.1.xsd. This is our custom schema containing definitions used by our other schemas.
• secDNS-1.1.xsd. This is a standard EPP schema
  

You can download this version 2.1.1 schema bundle in either TGZ or ZIP format.

Note that the schemas used when logging into the system must all be part of the same schema bundle.
For example if nom-notifications-2.1.xsd is used from the 2.1.1 schema bundle then nom-domain-2.1.xsd must be used - the attempt to login will fail if nom-domain-2.0.xsd is used instead.

---

Changelog

• 06 Sep 2011: updated nom-notifications schema to nom-notifications-2.1 (initially only available on the EPP Testbed)
  
• 07 Feb 2011: added secDNS-1.1 to add support for DNSSEC.  Also created a new 2.1 schema bundle; the only difference is to add nom-domain-2.1.xsd which makes DNSSEC data available to EPP List commands.  It is still possible to use nom-domain-2.0 for other DNSSEC operations.
  
• 04 June 2010: added warning to std-warning-1.1.xsd: "registrar account forked"
• 11 May 2010: Addition of registrarAccountForkedType to std-warnings-1.1.xsd
• 09 March 2010: bugfix to nom-domain-2.0 to allow renew-not-required field to be cleared
• 20 January 2010: added nom-abuse-feed-1.0 to version 2.0 schema bundles
  
• 20 January 2010: bugfix to nom-domain-2.0 to allow empty resellers field
• 04 December 2009: bugfix to nom-account-2.0.xsd to remove admin contact type

We use the following schemas for our implementation of EPP reseller management operations: 

• epp-1.0.xsd. This is one of the two standard base EPP schemas.
• eppcom-1.0.xsd. This is one of the two standard base EPP schemas.
• nom-reseller-1.0.xsd. This is our custom schema for reseller objects.

You can download this schema bundle in either TGZ or ZIP format.
Note that the nom-reseller schema cannot be mixed with Nominet EPP or Standard EPP schemas when logging into the system.


We use the following schemas for our implementation of EPP tag list:

• epp-1.0.xsd. This is one of the two standard base EPP schemas.
• eppcom-1.0.xsd. This is one of the two standard base EPP schemas.
• nom-tag-1.0.xsd. This is our custom schema for tag objects.

You can download this schema bundle in either TGZ or ZIP format.
Note that the nom-tag schema cannot be mixed with Nominet EPP or Standard EPP schemas when logging into the system.

We use the following schemas for our implementation of the EPP DNSSEC Signing Service:

• epp-1.0.xsd. This is one of the two standard base EPP schemas.
• eppcom-1.0.xsd. This is one of the two standard base EPP schemas.
• nom-dss-1.0.xsd. This is our custom schema for the DNSSEC Signing Service.
• secDNS-1.1.xsd. This is a standard EPP schema.

You can download this schema bundle in either TGZ or ZIP format.
Note that the nom-dss schema cannot be mixed with Nominet EPP or Standard EPP schemas when logging into the system.

---

Note: All nom-domain-1.x, nom-account-1.x, nom-contact-1.x and nom-ns schemas are deprecated.

Last updated: 13 Oct 2011