this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

A_ALTERNATIVE_IDAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_alternative_idAPI.

A_ALTERNATIVE_IDDB describes a a_alternative_id in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_alternative_idDB.

A_ALTERNATIVE_IDDBResponse provides response swagger:response a_alternative_idDBResponse.

A_ALTERNATIVE_IDPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ALTERNATIVE_IDWOP is a A_ALTERNATIVE_ID without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_boolean_refAPI.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFDB describes a a_attribute_definition_boolean_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_boolean_refDB.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFDBResponse provides response swagger:response a_attribute_definition_boolean_refDBResponse.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFWOP is a A_ATTRIBUTE_DEFINITION_BOOLEAN_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_DATE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_date_refAPI.

A_ATTRIBUTE_DEFINITION_DATE_REFDB describes a a_attribute_definition_date_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_date_refDB.

A_ATTRIBUTE_DEFINITION_DATE_REFDBResponse provides response swagger:response a_attribute_definition_date_refDBResponse.

A_ATTRIBUTE_DEFINITION_DATE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_DATE_REFWOP is a A_ATTRIBUTE_DEFINITION_DATE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_enumeration_refAPI.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFDB describes a a_attribute_definition_enumeration_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_enumeration_refDB.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFDBResponse provides response swagger:response a_attribute_definition_enumeration_refDBResponse.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFWOP is a A_ATTRIBUTE_DEFINITION_ENUMERATION_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_INTEGER_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_integer_refAPI.

A_ATTRIBUTE_DEFINITION_INTEGER_REFDB describes a a_attribute_definition_integer_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_integer_refDB.

A_ATTRIBUTE_DEFINITION_INTEGER_REFDBResponse provides response swagger:response a_attribute_definition_integer_refDBResponse.

A_ATTRIBUTE_DEFINITION_INTEGER_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_INTEGER_REFWOP is a A_ATTRIBUTE_DEFINITION_INTEGER_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_REAL_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_real_refAPI.

A_ATTRIBUTE_DEFINITION_REAL_REFDB describes a a_attribute_definition_real_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_real_refDB.

A_ATTRIBUTE_DEFINITION_REAL_REFDBResponse provides response swagger:response a_attribute_definition_real_refDBResponse.

A_ATTRIBUTE_DEFINITION_REAL_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_REAL_REFWOP is a A_ATTRIBUTE_DEFINITION_REAL_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_STRING_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_string_refAPI.

A_ATTRIBUTE_DEFINITION_STRING_REFDB describes a a_attribute_definition_string_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_string_refDB.

A_ATTRIBUTE_DEFINITION_STRING_REFDBResponse provides response swagger:response a_attribute_definition_string_refDBResponse.

A_ATTRIBUTE_DEFINITION_STRING_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_STRING_REFWOP is a A_ATTRIBUTE_DEFINITION_STRING_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_DEFINITION_XHTML_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_definition_xhtml_refAPI.

A_ATTRIBUTE_DEFINITION_XHTML_REFDB describes a a_attribute_definition_xhtml_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_definition_xhtml_refDB.

A_ATTRIBUTE_DEFINITION_XHTML_REFDBResponse provides response swagger:response a_attribute_definition_xhtml_refDBResponse.

A_ATTRIBUTE_DEFINITION_XHTML_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_DEFINITION_XHTML_REFWOP is a A_ATTRIBUTE_DEFINITION_XHTML_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_booleanAPI.

A_ATTRIBUTE_VALUE_BOOLEANDB describes a a_attribute_value_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_booleanDB.

A_ATTRIBUTE_VALUE_BOOLEANDBResponse provides response swagger:response a_attribute_value_booleanDBResponse.

A_ATTRIBUTE_VALUE_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_BOOLEANWOP is a A_ATTRIBUTE_VALUE_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_dateAPI.

A_ATTRIBUTE_VALUE_DATEDB describes a a_attribute_value_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_dateDB.

A_ATTRIBUTE_VALUE_DATEDBResponse provides response swagger:response a_attribute_value_dateDBResponse.

A_ATTRIBUTE_VALUE_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_DATEWOP is a A_ATTRIBUTE_VALUE_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_enumerationAPI.

A_ATTRIBUTE_VALUE_ENUMERATIONDB describes a a_attribute_value_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_enumerationDB.

A_ATTRIBUTE_VALUE_ENUMERATIONDBResponse provides response swagger:response a_attribute_value_enumerationDBResponse.

A_ATTRIBUTE_VALUE_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_ENUMERATIONWOP is a A_ATTRIBUTE_VALUE_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_integerAPI.

A_ATTRIBUTE_VALUE_INTEGERDB describes a a_attribute_value_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_integerDB.

A_ATTRIBUTE_VALUE_INTEGERDBResponse provides response swagger:response a_attribute_value_integerDBResponse.

A_ATTRIBUTE_VALUE_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_INTEGERWOP is a A_ATTRIBUTE_VALUE_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_realAPI.

A_ATTRIBUTE_VALUE_REALDB describes a a_attribute_value_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_realDB.

A_ATTRIBUTE_VALUE_REALDBResponse provides response swagger:response a_attribute_value_realDBResponse.

A_ATTRIBUTE_VALUE_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_REALWOP is a A_ATTRIBUTE_VALUE_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_stringAPI.

A_ATTRIBUTE_VALUE_STRINGDB describes a a_attribute_value_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_stringDB.

A_ATTRIBUTE_VALUE_STRINGDBResponse provides response swagger:response a_attribute_value_stringDBResponse.

A_ATTRIBUTE_VALUE_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_STRINGWOP is a A_ATTRIBUTE_VALUE_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_XHTML_1API is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_xhtml_1API.

A_ATTRIBUTE_VALUE_XHTML_1DB describes a a_attribute_value_xhtml_1 in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_xhtml_1DB.

A_ATTRIBUTE_VALUE_XHTML_1DBResponse provides response swagger:response a_attribute_value_xhtml_1DBResponse.

A_ATTRIBUTE_VALUE_XHTML_1PointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_XHTML_1WOP is a A_ATTRIBUTE_VALUE_XHTML_1 without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ATTRIBUTE_VALUE_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_attribute_value_xhtmlAPI.

A_ATTRIBUTE_VALUE_XHTMLDB describes a a_attribute_value_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_attribute_value_xhtmlDB.

A_ATTRIBUTE_VALUE_XHTMLDBResponse provides response swagger:response a_attribute_value_xhtmlDBResponse.

A_ATTRIBUTE_VALUE_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ATTRIBUTE_VALUE_XHTMLWOP is a A_ATTRIBUTE_VALUE_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_CHILDRENAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_childrenAPI.

A_CHILDRENDB describes a a_children in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_childrenDB.

A_CHILDRENDBResponse provides response swagger:response a_childrenDBResponse.

A_CHILDRENPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_CHILDRENWOP is a A_CHILDREN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_CORE_CONTENTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_core_contentAPI.

A_CORE_CONTENTDB describes a a_core_content in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_core_contentDB.

A_CORE_CONTENTDBResponse provides response swagger:response a_core_contentDBResponse.

A_CORE_CONTENTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_CORE_CONTENTWOP is a A_CORE_CONTENT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_BOOLEAN_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_boolean_refAPI.

A_DATATYPE_DEFINITION_BOOLEAN_REFDB describes a a_datatype_definition_boolean_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_boolean_refDB.

A_DATATYPE_DEFINITION_BOOLEAN_REFDBResponse provides response swagger:response a_datatype_definition_boolean_refDBResponse.

A_DATATYPE_DEFINITION_BOOLEAN_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_BOOLEAN_REFWOP is a A_DATATYPE_DEFINITION_BOOLEAN_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_DATE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_date_refAPI.

A_DATATYPE_DEFINITION_DATE_REFDB describes a a_datatype_definition_date_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_date_refDB.

A_DATATYPE_DEFINITION_DATE_REFDBResponse provides response swagger:response a_datatype_definition_date_refDBResponse.

A_DATATYPE_DEFINITION_DATE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_DATE_REFWOP is a A_DATATYPE_DEFINITION_DATE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_ENUMERATION_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_enumeration_refAPI.

A_DATATYPE_DEFINITION_ENUMERATION_REFDB describes a a_datatype_definition_enumeration_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_enumeration_refDB.

A_DATATYPE_DEFINITION_ENUMERATION_REFDBResponse provides response swagger:response a_datatype_definition_enumeration_refDBResponse.

A_DATATYPE_DEFINITION_ENUMERATION_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_ENUMERATION_REFWOP is a A_DATATYPE_DEFINITION_ENUMERATION_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_INTEGER_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_integer_refAPI.

A_DATATYPE_DEFINITION_INTEGER_REFDB describes a a_datatype_definition_integer_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_integer_refDB.

A_DATATYPE_DEFINITION_INTEGER_REFDBResponse provides response swagger:response a_datatype_definition_integer_refDBResponse.

A_DATATYPE_DEFINITION_INTEGER_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_INTEGER_REFWOP is a A_DATATYPE_DEFINITION_INTEGER_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_REAL_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_real_refAPI.

A_DATATYPE_DEFINITION_REAL_REFDB describes a a_datatype_definition_real_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_real_refDB.

A_DATATYPE_DEFINITION_REAL_REFDBResponse provides response swagger:response a_datatype_definition_real_refDBResponse.

A_DATATYPE_DEFINITION_REAL_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_REAL_REFWOP is a A_DATATYPE_DEFINITION_REAL_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_STRING_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_string_refAPI.

A_DATATYPE_DEFINITION_STRING_REFDB describes a a_datatype_definition_string_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_string_refDB.

A_DATATYPE_DEFINITION_STRING_REFDBResponse provides response swagger:response a_datatype_definition_string_refDBResponse.

A_DATATYPE_DEFINITION_STRING_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_STRING_REFWOP is a A_DATATYPE_DEFINITION_STRING_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPE_DEFINITION_XHTML_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatype_definition_xhtml_refAPI.

A_DATATYPE_DEFINITION_XHTML_REFDB describes a a_datatype_definition_xhtml_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatype_definition_xhtml_refDB.

A_DATATYPE_DEFINITION_XHTML_REFDBResponse provides response swagger:response a_datatype_definition_xhtml_refDBResponse.

A_DATATYPE_DEFINITION_XHTML_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPE_DEFINITION_XHTML_REFWOP is a A_DATATYPE_DEFINITION_XHTML_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_DATATYPESAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_datatypesAPI.

A_DATATYPESDB describes a a_datatypes in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_datatypesDB.

A_DATATYPESDBResponse provides response swagger:response a_datatypesDBResponse.

A_DATATYPESPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_DATATYPESWOP is a A_DATATYPES without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_EDITABLE_ATTSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_editable_attsAPI.

A_EDITABLE_ATTSDB describes a a_editable_atts in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_editable_attsDB.

A_EDITABLE_ATTSDBResponse provides response swagger:response a_editable_attsDBResponse.

A_EDITABLE_ATTSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_EDITABLE_ATTSWOP is a A_EDITABLE_ATTS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ENUM_VALUE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_enum_value_refAPI.

A_ENUM_VALUE_REFDB describes a a_enum_value_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_enum_value_refDB.

A_ENUM_VALUE_REFDBResponse provides response swagger:response a_enum_value_refDBResponse.

A_ENUM_VALUE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_ENUM_VALUE_REFWOP is a A_ENUM_VALUE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_OBJECTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_objectAPI.

A_OBJECTDB describes a a_object in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_objectDB.

A_OBJECTDBResponse provides response swagger:response a_objectDBResponse.

A_OBJECTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_OBJECTWOP is a A_OBJECT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_PROPERTIESAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_propertiesAPI.

A_PROPERTIESDB describes a a_properties in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_propertiesDB.

A_PROPERTIESDBResponse provides response swagger:response a_propertiesDBResponse.

A_PROPERTIESPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_PROPERTIESWOP is a A_PROPERTIES without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_RELATION_GROUP_TYPE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_relation_group_type_refAPI.

A_RELATION_GROUP_TYPE_REFDB describes a a_relation_group_type_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_relation_group_type_refDB.

A_RELATION_GROUP_TYPE_REFDBResponse provides response swagger:response a_relation_group_type_refDBResponse.

A_RELATION_GROUP_TYPE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_RELATION_GROUP_TYPE_REFWOP is a A_RELATION_GROUP_TYPE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SOURCE_1API is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_source_1API.

A_SOURCE_1DB describes a a_source_1 in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_source_1DB.

A_SOURCE_1DBResponse provides response swagger:response a_source_1DBResponse.

A_SOURCE_1PointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SOURCE_1WOP is a A_SOURCE_1 without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SOURCE_SPECIFICATION_1API is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_source_specification_1API.

A_SOURCE_SPECIFICATION_1DB describes a a_source_specification_1 in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_source_specification_1DB.

A_SOURCE_SPECIFICATION_1DBResponse provides response swagger:response a_source_specification_1DBResponse.

A_SOURCE_SPECIFICATION_1PointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SOURCE_SPECIFICATION_1WOP is a A_SOURCE_SPECIFICATION_1 without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_ATTRIBUTESAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_attributesAPI.

A_SPEC_ATTRIBUTESDB describes a a_spec_attributes in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_attributesDB.

A_SPEC_ATTRIBUTESDBResponse provides response swagger:response a_spec_attributesDBResponse.

A_SPEC_ATTRIBUTESPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_ATTRIBUTESWOP is a A_SPEC_ATTRIBUTES without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_OBJECT_TYPE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_object_type_refAPI.

A_SPEC_OBJECT_TYPE_REFDB describes a a_spec_object_type_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_object_type_refDB.

A_SPEC_OBJECT_TYPE_REFDBResponse provides response swagger:response a_spec_object_type_refDBResponse.

A_SPEC_OBJECT_TYPE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_OBJECT_TYPE_REFWOP is a A_SPEC_OBJECT_TYPE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_OBJECTSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_objectsAPI.

A_SPEC_OBJECTSDB describes a a_spec_objects in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_objectsDB.

A_SPEC_OBJECTSDBResponse provides response swagger:response a_spec_objectsDBResponse.

A_SPEC_OBJECTSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_OBJECTSWOP is a A_SPEC_OBJECTS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_RELATION_GROUPSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_relation_groupsAPI.

A_SPEC_RELATION_GROUPSDB describes a a_spec_relation_groups in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_relation_groupsDB.

A_SPEC_RELATION_GROUPSDBResponse provides response swagger:response a_spec_relation_groupsDBResponse.

A_SPEC_RELATION_GROUPSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_RELATION_GROUPSWOP is a A_SPEC_RELATION_GROUPS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_RELATION_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_relation_refAPI.

A_SPEC_RELATION_REFDB describes a a_spec_relation_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_relation_refDB.

A_SPEC_RELATION_REFDBResponse provides response swagger:response a_spec_relation_refDBResponse.

A_SPEC_RELATION_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_RELATION_REFWOP is a A_SPEC_RELATION_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_RELATION_TYPE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_relation_type_refAPI.

A_SPEC_RELATION_TYPE_REFDB describes a a_spec_relation_type_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_relation_type_refDB.

A_SPEC_RELATION_TYPE_REFDBResponse provides response swagger:response a_spec_relation_type_refDBResponse.

A_SPEC_RELATION_TYPE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_RELATION_TYPE_REFWOP is a A_SPEC_RELATION_TYPE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_RELATIONSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_relationsAPI.

A_SPEC_RELATIONSDB describes a a_spec_relations in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_relationsDB.

A_SPEC_RELATIONSDBResponse provides response swagger:response a_spec_relationsDBResponse.

A_SPEC_RELATIONSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_RELATIONSWOP is a A_SPEC_RELATIONS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPEC_TYPESAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_spec_typesAPI.

A_SPEC_TYPESDB describes a a_spec_types in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_spec_typesDB.

A_SPEC_TYPESDBResponse provides response swagger:response a_spec_typesDBResponse.

A_SPEC_TYPESPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPEC_TYPESWOP is a A_SPEC_TYPES without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPECIFICATION_TYPE_REFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_specification_type_refAPI.

A_SPECIFICATION_TYPE_REFDB describes a a_specification_type_ref in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_specification_type_refDB.

A_SPECIFICATION_TYPE_REFDBResponse provides response swagger:response a_specification_type_refDBResponse.

A_SPECIFICATION_TYPE_REFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPECIFICATION_TYPE_REFWOP is a A_SPECIFICATION_TYPE_REF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPECIFICATIONSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_specificationsAPI.

A_SPECIFICATIONSDB describes a a_specifications in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_specificationsDB.

A_SPECIFICATIONSDBResponse provides response swagger:response a_specificationsDBResponse.

A_SPECIFICATIONSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPECIFICATIONSWOP is a A_SPECIFICATIONS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_SPECIFIED_VALUESAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_specified_valuesAPI.

A_SPECIFIED_VALUESDB describes a a_specified_values in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_specified_valuesDB.

A_SPECIFIED_VALUESDBResponse provides response swagger:response a_specified_valuesDBResponse.

A_SPECIFIED_VALUESPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_SPECIFIED_VALUESWOP is a A_SPECIFIED_VALUES without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_THE_HEADERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_the_headerAPI.

A_THE_HEADERDB describes a a_the_header in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_the_headerDB.

A_THE_HEADERDBResponse provides response swagger:response a_the_headerDBResponse.

A_THE_HEADERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_THE_HEADERWOP is a A_THE_HEADER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_TOOL_EXTENSIONSAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model a_tool_extensionsAPI.

A_TOOL_EXTENSIONSDB describes a a_tool_extensions in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model a_tool_extensionsDB.

A_TOOL_EXTENSIONSDBResponse provides response swagger:response a_tool_extensionsDBResponse.

A_TOOL_EXTENSIONSPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

A_TOOL_EXTENSIONSWOP is a A_TOOL_EXTENSIONS without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ALTERNATIVE_IDAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model alternative_idAPI.

ALTERNATIVE_IDDB describes a alternative_id in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model alternative_idDB.

ALTERNATIVE_IDDBResponse provides response swagger:response alternative_idDBResponse.

ALTERNATIVE_IDPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ALTERNATIVE_IDWOP is a ALTERNATIVE_ID without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_booleanAPI.

ATTRIBUTE_DEFINITION_BOOLEANDB describes a attribute_definition_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_booleanDB.

ATTRIBUTE_DEFINITION_BOOLEANDBResponse provides response swagger:response attribute_definition_booleanDBResponse.

ATTRIBUTE_DEFINITION_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_BOOLEANWOP is a ATTRIBUTE_DEFINITION_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_dateAPI.

ATTRIBUTE_DEFINITION_DATEDB describes a attribute_definition_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_dateDB.

ATTRIBUTE_DEFINITION_DATEDBResponse provides response swagger:response attribute_definition_dateDBResponse.

ATTRIBUTE_DEFINITION_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_DATEWOP is a ATTRIBUTE_DEFINITION_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_enumerationAPI.

ATTRIBUTE_DEFINITION_ENUMERATIONDB describes a attribute_definition_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_enumerationDB.

ATTRIBUTE_DEFINITION_ENUMERATIONDBResponse provides response swagger:response attribute_definition_enumerationDBResponse.

ATTRIBUTE_DEFINITION_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_ENUMERATIONWOP is a ATTRIBUTE_DEFINITION_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_integerAPI.

ATTRIBUTE_DEFINITION_INTEGERDB describes a attribute_definition_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_integerDB.

ATTRIBUTE_DEFINITION_INTEGERDBResponse provides response swagger:response attribute_definition_integerDBResponse.

ATTRIBUTE_DEFINITION_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_INTEGERWOP is a ATTRIBUTE_DEFINITION_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_realAPI.

ATTRIBUTE_DEFINITION_REALDB describes a attribute_definition_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_realDB.

ATTRIBUTE_DEFINITION_REALDBResponse provides response swagger:response attribute_definition_realDBResponse.

ATTRIBUTE_DEFINITION_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_REALWOP is a ATTRIBUTE_DEFINITION_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_stringAPI.

ATTRIBUTE_DEFINITION_STRINGDB describes a attribute_definition_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_stringDB.

ATTRIBUTE_DEFINITION_STRINGDBResponse provides response swagger:response attribute_definition_stringDBResponse.

ATTRIBUTE_DEFINITION_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_STRINGWOP is a ATTRIBUTE_DEFINITION_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_xhtmlAPI.

ATTRIBUTE_DEFINITION_XHTMLDB describes a attribute_definition_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_xhtmlDB.

ATTRIBUTE_DEFINITION_XHTMLDBResponse provides response swagger:response attribute_definition_xhtmlDBResponse.

ATTRIBUTE_DEFINITION_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_XHTMLWOP is a ATTRIBUTE_DEFINITION_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_booleanAPI.

ATTRIBUTE_VALUE_BOOLEANDB describes a attribute_value_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_booleanDB.

ATTRIBUTE_VALUE_BOOLEANDBResponse provides response swagger:response attribute_value_booleanDBResponse.

ATTRIBUTE_VALUE_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_BOOLEANWOP is a ATTRIBUTE_VALUE_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_dateAPI.

ATTRIBUTE_VALUE_DATEDB describes a attribute_value_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_dateDB.

ATTRIBUTE_VALUE_DATEDBResponse provides response swagger:response attribute_value_dateDBResponse.

ATTRIBUTE_VALUE_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_DATEWOP is a ATTRIBUTE_VALUE_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_enumerationAPI.

ATTRIBUTE_VALUE_ENUMERATIONDB describes a attribute_value_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_enumerationDB.

ATTRIBUTE_VALUE_ENUMERATIONDBResponse provides response swagger:response attribute_value_enumerationDBResponse.

ATTRIBUTE_VALUE_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_ENUMERATIONWOP is a ATTRIBUTE_VALUE_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_integerAPI.

ATTRIBUTE_VALUE_INTEGERDB describes a attribute_value_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_integerDB.

ATTRIBUTE_VALUE_INTEGERDBResponse provides response swagger:response attribute_value_integerDBResponse.

ATTRIBUTE_VALUE_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_INTEGERWOP is a ATTRIBUTE_VALUE_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_realAPI.

ATTRIBUTE_VALUE_REALDB describes a attribute_value_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_realDB.

ATTRIBUTE_VALUE_REALDBResponse provides response swagger:response attribute_value_realDBResponse.

ATTRIBUTE_VALUE_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_REALWOP is a ATTRIBUTE_VALUE_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_stringAPI.

ATTRIBUTE_VALUE_STRINGDB describes a attribute_value_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_stringDB.

ATTRIBUTE_VALUE_STRINGDBResponse provides response swagger:response attribute_value_stringDBResponse.

ATTRIBUTE_VALUE_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_STRINGWOP is a ATTRIBUTE_VALUE_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_xhtmlAPI.

ATTRIBUTE_VALUE_XHTMLDB describes a attribute_value_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_xhtmlDB.

ATTRIBUTE_VALUE_XHTMLDBResponse provides response swagger:response attribute_value_xhtmlDBResponse.

ATTRIBUTE_VALUE_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_XHTMLWOP is a ATTRIBUTE_VALUE_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

BackRepoStruct supports callback functions.

DATATYPE_DEFINITION_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_booleanAPI.

DATATYPE_DEFINITION_BOOLEANDB describes a datatype_definition_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_booleanDB.

DATATYPE_DEFINITION_BOOLEANDBResponse provides response swagger:response datatype_definition_booleanDBResponse.

DATATYPE_DEFINITION_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_BOOLEANWOP is a DATATYPE_DEFINITION_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_dateAPI.

DATATYPE_DEFINITION_DATEDB describes a datatype_definition_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_dateDB.

DATATYPE_DEFINITION_DATEDBResponse provides response swagger:response datatype_definition_dateDBResponse.

DATATYPE_DEFINITION_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_DATEWOP is a DATATYPE_DEFINITION_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_enumerationAPI.

DATATYPE_DEFINITION_ENUMERATIONDB describes a datatype_definition_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_enumerationDB.

DATATYPE_DEFINITION_ENUMERATIONDBResponse provides response swagger:response datatype_definition_enumerationDBResponse.

DATATYPE_DEFINITION_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_ENUMERATIONWOP is a DATATYPE_DEFINITION_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_integerAPI.

DATATYPE_DEFINITION_INTEGERDB describes a datatype_definition_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_integerDB.

DATATYPE_DEFINITION_INTEGERDBResponse provides response swagger:response datatype_definition_integerDBResponse.

DATATYPE_DEFINITION_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_INTEGERWOP is a DATATYPE_DEFINITION_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_realAPI.

DATATYPE_DEFINITION_REALDB describes a datatype_definition_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_realDB.

DATATYPE_DEFINITION_REALDBResponse provides response swagger:response datatype_definition_realDBResponse.

DATATYPE_DEFINITION_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_REALWOP is a DATATYPE_DEFINITION_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_stringAPI.

DATATYPE_DEFINITION_STRINGDB describes a datatype_definition_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_stringDB.

DATATYPE_DEFINITION_STRINGDBResponse provides response swagger:response datatype_definition_stringDBResponse.

DATATYPE_DEFINITION_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_STRINGWOP is a DATATYPE_DEFINITION_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_xhtmlAPI.

DATATYPE_DEFINITION_XHTMLDB describes a datatype_definition_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_xhtmlDB.

DATATYPE_DEFINITION_XHTMLDBResponse provides response swagger:response datatype_definition_xhtmlDBResponse.

DATATYPE_DEFINITION_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_XHTMLWOP is a DATATYPE_DEFINITION_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

EMBEDDED_VALUEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model embedded_valueAPI.

EMBEDDED_VALUEDB describes a embedded_value in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model embedded_valueDB.

EMBEDDED_VALUEDBResponse provides response swagger:response embedded_valueDBResponse.

EMBEDDED_VALUEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

EMBEDDED_VALUEWOP is a EMBEDDED_VALUE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ENUM_VALUEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model enum_valueAPI.

ENUM_VALUEDB describes a enum_value in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model enum_valueDB.

ENUM_VALUEDBResponse provides response swagger:response enum_valueDBResponse.

ENUM_VALUEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ENUM_VALUEWOP is a ENUM_VALUE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

RELATION_GROUP_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model relation_group_typeAPI.

RELATION_GROUP_TYPEDB describes a relation_group_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model relation_group_typeDB.

RELATION_GROUP_TYPEDBResponse provides response swagger:response relation_group_typeDBResponse.

RELATION_GROUP_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

RELATION_GROUP_TYPEWOP is a RELATION_GROUP_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

RELATION_GROUPAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model relation_groupAPI.

RELATION_GROUPDB describes a relation_group in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model relation_groupDB.

RELATION_GROUPDBResponse provides response swagger:response relation_groupDBResponse.

RELATION_GROUPPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

RELATION_GROUPWOP is a RELATION_GROUP without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_CONTENTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_contentAPI.

REQ_IF_CONTENTDB describes a req_if_content in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_contentDB.

REQ_IF_CONTENTDBResponse provides response swagger:response req_if_contentDBResponse.

REQ_IF_CONTENTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_CONTENTWOP is a REQ_IF_CONTENT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_HEADERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_headerAPI.

REQ_IF_HEADERDB describes a req_if_header in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_headerDB.

REQ_IF_HEADERDBResponse provides response swagger:response req_if_headerDBResponse.

REQ_IF_HEADERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_HEADERWOP is a REQ_IF_HEADER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_TOOL_EXTENSIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_tool_extensionAPI.

REQ_IF_TOOL_EXTENSIONDB describes a req_if_tool_extension in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_tool_extensionDB.

REQ_IF_TOOL_EXTENSIONDBResponse provides response swagger:response req_if_tool_extensionDBResponse.

REQ_IF_TOOL_EXTENSIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_TOOL_EXTENSIONWOP is a REQ_IF_TOOL_EXTENSION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_ifAPI.

REQ_IFDB describes a req_if in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_ifDB.

REQ_IFDBResponse provides response swagger:response req_ifDBResponse.

REQ_IFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IFWOP is a REQ_IF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_HIERARCHYAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_hierarchyAPI.

SPEC_HIERARCHYDB describes a spec_hierarchy in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_hierarchyDB.

SPEC_HIERARCHYDBResponse provides response swagger:response spec_hierarchyDBResponse.

SPEC_HIERARCHYPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_HIERARCHYWOP is a SPEC_HIERARCHY without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_OBJECT_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_object_typeAPI.

SPEC_OBJECT_TYPEDB describes a spec_object_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_object_typeDB.

SPEC_OBJECT_TYPEDBResponse provides response swagger:response spec_object_typeDBResponse.

SPEC_OBJECT_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_OBJECT_TYPEWOP is a SPEC_OBJECT_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_OBJECTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_objectAPI.

SPEC_OBJECTDB describes a spec_object in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_objectDB.

SPEC_OBJECTDBResponse provides response swagger:response spec_objectDBResponse.

SPEC_OBJECTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_OBJECTWOP is a SPEC_OBJECT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_RELATION_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_relation_typeAPI.

SPEC_RELATION_TYPEDB describes a spec_relation_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_relation_typeDB.

SPEC_RELATION_TYPEDBResponse provides response swagger:response spec_relation_typeDBResponse.

SPEC_RELATION_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_RELATION_TYPEWOP is a SPEC_RELATION_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_RELATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_relationAPI.

SPEC_RELATIONDB describes a spec_relation in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_relationDB.

SPEC_RELATIONDBResponse provides response swagger:response spec_relationDBResponse.

SPEC_RELATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_RELATIONWOP is a SPEC_RELATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPECIFICATION_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model specification_typeAPI.

SPECIFICATION_TYPEDB describes a specification_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model specification_typeDB.

SPECIFICATION_TYPEDBResponse provides response swagger:response specification_typeDBResponse.

SPECIFICATION_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPECIFICATION_TYPEWOP is a SPECIFICATION_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPECIFICATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model specificationAPI.

SPECIFICATIONDB describes a specification in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model specificationDB.

SPECIFICATIONDBResponse provides response swagger:response specificationDBResponse.

SPECIFICATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPECIFICATIONWOP is a SPECIFICATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

XHTML_CONTENTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_contentAPI.

XHTML_CONTENTDB describes a xhtml_content in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_contentDB.

XHTML_CONTENTDBResponse provides response swagger:response xhtml_contentDBResponse.

XHTML_CONTENTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

XHTML_CONTENTWOP is a XHTML_CONTENT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

A_ALTERNATIVE_IDDBs arrays a_alternative_idDBs swagger:response a_alternative_idDBsResponse.

A_ATTRIBUTE_DEFINITION_BOOLEAN_REFDBs arrays a_attribute_definition_boolean_refDBs swagger:response a_attribute_definition_boolean_refDBsResponse.

A_ATTRIBUTE_DEFINITION_DATE_REFDBs arrays a_attribute_definition_date_refDBs swagger:response a_attribute_definition_date_refDBsResponse.

A_ATTRIBUTE_DEFINITION_ENUMERATION_REFDBs arrays a_attribute_definition_enumeration_refDBs swagger:response a_attribute_definition_enumeration_refDBsResponse.

A_ATTRIBUTE_DEFINITION_INTEGER_REFDBs arrays a_attribute_definition_integer_refDBs swagger:response a_attribute_definition_integer_refDBsResponse.

A_ATTRIBUTE_DEFINITION_REAL_REFDBs arrays a_attribute_definition_real_refDBs swagger:response a_attribute_definition_real_refDBsResponse.

A_ATTRIBUTE_DEFINITION_STRING_REFDBs arrays a_attribute_definition_string_refDBs swagger:response a_attribute_definition_string_refDBsResponse.

A_ATTRIBUTE_DEFINITION_XHTML_REFDBs arrays a_attribute_definition_xhtml_refDBs swagger:response a_attribute_definition_xhtml_refDBsResponse.

A_ATTRIBUTE_VALUE_BOOLEANDBs arrays a_attribute_value_booleanDBs swagger:response a_attribute_value_booleanDBsResponse.

A_ATTRIBUTE_VALUE_DATEDBs arrays a_attribute_value_dateDBs swagger:response a_attribute_value_dateDBsResponse.

A_ATTRIBUTE_VALUE_ENUMERATIONDBs arrays a_attribute_value_enumerationDBs swagger:response a_attribute_value_enumerationDBsResponse.

A_ATTRIBUTE_VALUE_INTEGERDBs arrays a_attribute_value_integerDBs swagger:response a_attribute_value_integerDBsResponse.

A_ATTRIBUTE_VALUE_REALDBs arrays a_attribute_value_realDBs swagger:response a_attribute_value_realDBsResponse.

A_ATTRIBUTE_VALUE_STRINGDBs arrays a_attribute_value_stringDBs swagger:response a_attribute_value_stringDBsResponse.

A_ATTRIBUTE_VALUE_XHTML_1DBs arrays a_attribute_value_xhtml_1DBs swagger:response a_attribute_value_xhtml_1DBsResponse.

A_ATTRIBUTE_VALUE_XHTMLDBs arrays a_attribute_value_xhtmlDBs swagger:response a_attribute_value_xhtmlDBsResponse.

A_CHILDRENDBs arrays a_childrenDBs swagger:response a_childrenDBsResponse.

A_CORE_CONTENTDBs arrays a_core_contentDBs swagger:response a_core_contentDBsResponse.

A_DATATYPE_DEFINITION_BOOLEAN_REFDBs arrays a_datatype_definition_boolean_refDBs swagger:response a_datatype_definition_boolean_refDBsResponse.

A_DATATYPE_DEFINITION_DATE_REFDBs arrays a_datatype_definition_date_refDBs swagger:response a_datatype_definition_date_refDBsResponse.

A_DATATYPE_DEFINITION_ENUMERATION_REFDBs arrays a_datatype_definition_enumeration_refDBs swagger:response a_datatype_definition_enumeration_refDBsResponse.

A_DATATYPE_DEFINITION_INTEGER_REFDBs arrays a_datatype_definition_integer_refDBs swagger:response a_datatype_definition_integer_refDBsResponse.

A_DATATYPE_DEFINITION_REAL_REFDBs arrays a_datatype_definition_real_refDBs swagger:response a_datatype_definition_real_refDBsResponse.

A_DATATYPE_DEFINITION_STRING_REFDBs arrays a_datatype_definition_string_refDBs swagger:response a_datatype_definition_string_refDBsResponse.

A_DATATYPE_DEFINITION_XHTML_REFDBs arrays a_datatype_definition_xhtml_refDBs swagger:response a_datatype_definition_xhtml_refDBsResponse.

A_DATATYPESDBs arrays a_datatypesDBs swagger:response a_datatypesDBsResponse.

A_EDITABLE_ATTSDBs arrays a_editable_attsDBs swagger:response a_editable_attsDBsResponse.

A_ENUM_VALUE_REFDBs arrays a_enum_value_refDBs swagger:response a_enum_value_refDBsResponse.

A_OBJECTDBs arrays a_objectDBs swagger:response a_objectDBsResponse.

A_PROPERTIESDBs arrays a_propertiesDBs swagger:response a_propertiesDBsResponse.

A_RELATION_GROUP_TYPE_REFDBs arrays a_relation_group_type_refDBs swagger:response a_relation_group_type_refDBsResponse.

A_SOURCE_1DBs arrays a_source_1DBs swagger:response a_source_1DBsResponse.

A_SOURCE_SPECIFICATION_1DBs arrays a_source_specification_1DBs swagger:response a_source_specification_1DBsResponse.

A_SPEC_ATTRIBUTESDBs arrays a_spec_attributesDBs swagger:response a_spec_attributesDBsResponse.

A_SPEC_OBJECT_TYPE_REFDBs arrays a_spec_object_type_refDBs swagger:response a_spec_object_type_refDBsResponse.

A_SPEC_OBJECTSDBs arrays a_spec_objectsDBs swagger:response a_spec_objectsDBsResponse.

A_SPEC_RELATION_GROUPSDBs arrays a_spec_relation_groupsDBs swagger:response a_spec_relation_groupsDBsResponse.

A_SPEC_RELATION_REFDBs arrays a_spec_relation_refDBs swagger:response a_spec_relation_refDBsResponse.

A_SPEC_RELATION_TYPE_REFDBs arrays a_spec_relation_type_refDBs swagger:response a_spec_relation_type_refDBsResponse.

A_SPEC_RELATIONSDBs arrays a_spec_relationsDBs swagger:response a_spec_relationsDBsResponse.

A_SPEC_TYPESDBs arrays a_spec_typesDBs swagger:response a_spec_typesDBsResponse.

A_SPECIFICATION_TYPE_REFDBs arrays a_specification_type_refDBs swagger:response a_specification_type_refDBsResponse.

A_SPECIFICATIONSDBs arrays a_specificationsDBs swagger:response a_specificationsDBsResponse.

A_SPECIFIED_VALUESDBs arrays a_specified_valuesDBs swagger:response a_specified_valuesDBsResponse.

A_THE_HEADERDBs arrays a_the_headerDBs swagger:response a_the_headerDBsResponse.

A_TOOL_EXTENSIONSDBs arrays a_tool_extensionsDBs swagger:response a_tool_extensionsDBsResponse.

ALTERNATIVE_IDDBs arrays alternative_idDBs swagger:response alternative_idDBsResponse.

ATTRIBUTE_DEFINITION_BOOLEANDBs arrays attribute_definition_booleanDBs swagger:response attribute_definition_booleanDBsResponse.

ATTRIBUTE_DEFINITION_DATEDBs arrays attribute_definition_dateDBs swagger:response attribute_definition_dateDBsResponse.

ATTRIBUTE_DEFINITION_ENUMERATIONDBs arrays attribute_definition_enumerationDBs swagger:response attribute_definition_enumerationDBsResponse.

ATTRIBUTE_DEFINITION_INTEGERDBs arrays attribute_definition_integerDBs swagger:response attribute_definition_integerDBsResponse.

ATTRIBUTE_DEFINITION_REALDBs arrays attribute_definition_realDBs swagger:response attribute_definition_realDBsResponse.

ATTRIBUTE_DEFINITION_STRINGDBs arrays attribute_definition_stringDBs swagger:response attribute_definition_stringDBsResponse.

ATTRIBUTE_DEFINITION_XHTMLDBs arrays attribute_definition_xhtmlDBs swagger:response attribute_definition_xhtmlDBsResponse.

ATTRIBUTE_VALUE_BOOLEANDBs arrays attribute_value_booleanDBs swagger:response attribute_value_booleanDBsResponse.

ATTRIBUTE_VALUE_DATEDBs arrays attribute_value_dateDBs swagger:response attribute_value_dateDBsResponse.

ATTRIBUTE_VALUE_ENUMERATIONDBs arrays attribute_value_enumerationDBs swagger:response attribute_value_enumerationDBsResponse.

ATTRIBUTE_VALUE_INTEGERDBs arrays attribute_value_integerDBs swagger:response attribute_value_integerDBsResponse.

ATTRIBUTE_VALUE_REALDBs arrays attribute_value_realDBs swagger:response attribute_value_realDBsResponse.

ATTRIBUTE_VALUE_STRINGDBs arrays attribute_value_stringDBs swagger:response attribute_value_stringDBsResponse.

ATTRIBUTE_VALUE_XHTMLDBs arrays attribute_value_xhtmlDBs swagger:response attribute_value_xhtmlDBsResponse.

DATATYPE_DEFINITION_BOOLEANDBs arrays datatype_definition_booleanDBs swagger:response datatype_definition_booleanDBsResponse.

DATATYPE_DEFINITION_DATEDBs arrays datatype_definition_dateDBs swagger:response datatype_definition_dateDBsResponse.

DATATYPE_DEFINITION_ENUMERATIONDBs arrays datatype_definition_enumerationDBs swagger:response datatype_definition_enumerationDBsResponse.

DATATYPE_DEFINITION_INTEGERDBs arrays datatype_definition_integerDBs swagger:response datatype_definition_integerDBsResponse.

DATATYPE_DEFINITION_REALDBs arrays datatype_definition_realDBs swagger:response datatype_definition_realDBsResponse.

DATATYPE_DEFINITION_STRINGDBs arrays datatype_definition_stringDBs swagger:response datatype_definition_stringDBsResponse.

DATATYPE_DEFINITION_XHTMLDBs arrays datatype_definition_xhtmlDBs swagger:response datatype_definition_xhtmlDBsResponse.

EMBEDDED_VALUEDBs arrays embedded_valueDBs swagger:response embedded_valueDBsResponse.

ENUM_VALUEDBs arrays enum_valueDBs swagger:response enum_valueDBsResponse.

RELATION_GROUP_TYPEDBs arrays relation_group_typeDBs swagger:response relation_group_typeDBsResponse.

RELATION_GROUPDBs arrays relation_groupDBs swagger:response relation_groupDBsResponse.

REQ_IF_CONTENTDBs arrays req_if_contentDBs swagger:response req_if_contentDBsResponse.

REQ_IF_HEADERDBs arrays req_if_headerDBs swagger:response req_if_headerDBsResponse.

REQ_IF_TOOL_EXTENSIONDBs arrays req_if_tool_extensionDBs swagger:response req_if_tool_extensionDBsResponse.

REQ_IFDBs arrays req_ifDBs swagger:response req_ifDBsResponse.

SPEC_HIERARCHYDBs arrays spec_hierarchyDBs swagger:response spec_hierarchyDBsResponse.

SPEC_OBJECT_TYPEDBs arrays spec_object_typeDBs swagger:response spec_object_typeDBsResponse.

SPEC_OBJECTDBs arrays spec_objectDBs swagger:response spec_objectDBsResponse.

SPEC_RELATION_TYPEDBs arrays spec_relation_typeDBs swagger:response spec_relation_typeDBsResponse.

SPEC_RELATIONDBs arrays spec_relationDBs swagger:response spec_relationDBsResponse.

SPECIFICATION_TYPEDBs arrays specification_typeDBs swagger:response specification_typeDBsResponse.

SPECIFICATIONDBs arrays specificationDBs swagger:response specificationDBsResponse.

XHTML_CONTENTDBs arrays xhtml_contentDBs swagger:response xhtml_contentDBsResponse.