Data relationships

The AR System C API contains structures that store both simple and complex information. Structures that store simple information, (such as the type of value or the product of an arithmetic operation) serve as building blocks for complex structures.

This section contains data structure diagrams that explain these hierarchical relationships. The diagrams also identify which structures or groups of structures AR System uses to manipulate objects.

The following image explains the data relationship notation:


 

Related topic

Developing-an-API-program

Zero or one

221_DevAPI_DataStruct1.PNG

For example

A person might have no high school diploma (optional relationship) or a maximum of one high school diploma 221_DataStructIcon2.png.

Conversely, a high school diploma must belong to one and only one person 221_DataStructIcon1.png.





Zero or more

221_DevAPI_DataStruct2.PNG

For example

A person might have no credit card (optional relationship) or any number of credit cards 221_DataStructIcon3.png.

Conversely, a credit card must belong to one and only one person 221_DataStructIcon1.png.


One only

221_DevAPI_DataStruct3.PNG

For example

 A person must have one and only one birth date (required relationship) 221_DataStructIcon1.png.

Conversely, a birth date must belong to at least one person and might belong to any number of people221_DataStructIcon4.png


One or more

221_DevAPI_DataStruct4.PNG

For example

A person must have at least one name (required relationship) and might have any number of names 221_DataStructIcon4.png.

Conversely, a name might belong to no person or any number of people 221_DataStructIcon3.png.

For all data structure diagrams in this section, lack of notation indicates only one relationship.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*