DokuWiki

XML structures can be challenging to document in a manner that is simple and easy to read or understand. This said, this document is intended to outline the characteristics of the most frequently used XML nodes and properties in the CeRTNA Standard XML structures.

The CeRTNA Standard XML consists of 3 major structures, a REQUEST_GROUP, a RESPONSE_GROUP, and a PRIA_DOCUMENT structure. The PRIA_DOCUMENT structure is 'included' (common) across both the REQUEST_GROUP and the RESPONSE_GROUP structures.

The REQUEST_GROUP, with its embedded PRIA_DOCUMENT nodes represents what is delivered by the Submitter and the RESPONSE_GROUP, with its embedded PRIA_DOCUMENT nodes represents what is returned by the County Recorder.

The PRIA_DOCUMENT nodes contained in the RESPONSE_GROUP returned by the County Recorder will contain either recording information or reject information, depending on the action taken by the County Recorder.

Additional information associated with CeRTNA recommendations and/or best practices for CeRTNA System Integrators can be found in the CeRTNA System Integrators Guide.

The following tables provide information describing, historically, the most commonly used nodes and properties:

The Req column will use one of the following codes.

• R = Required
• O = Optional
• P = Required if Parent node is present.

Note: In the table below, some space characters were used to accommodate visual formatting. Be aware that there are actually no space characters in the XML node or property names.

|

In summary, this page is not intended to imply that the only XML elements that an integrator should plan for are ‘the most common’ but rather, to help integrators understand what elements we are seeing supplied by various submitters today.

Any element that is part of the CeRTNA Standardized XML structure is valid for supplying data. What submitters and integrators need to keep in mind is that every county is different and the communication that has been supplied to date is that counties prefer to index the documents within their backend applications. This said, the CeRTNA ERDS Portal, passes in a very limited amount of information that a county might use for indexing, such as the Document Type and the Number Of Pages. On the other hand, agent submitters or government agencies might pass in GRANTOR/GRANTEE information too, since they often create XML payloads programmatically.

Just because GRANTOR/GRANTEE information is supplied, it does not mean a County Integrator must use it. That is a decision for each county and its software vendor. This said, if a submitter supplies GRANTOR/GRANTEE information (as an example), then an integrator should return that data in their Response payload, regardless of whether they use it in their application.

This document is not intended to dictate policy. A Polices & Procedures Committee is in place for that very function. What this document is intended to do is to provide the best guidance it can with regard to what the individual data elements mean, which ones are required, and which ones we are seeing being used at the time of this writing.