SNIP_ADAPTIVE_CAN_FIGURE_Figure_5_6

Figure 5.6: Modeling of the REST elements [TPS_MANI_01125] Properties of REST elements can either be primitive or have array semantics⌈ The properties of REST elements can either be primitive or have array semantics. There is no support for the creation of structures nor is the nesting of property definitions with array semantics supported. This aspect is already clarified by the model ( RestArrayPropertyDef directly aggregates RestPrimitivePropertyDef) and does not need to be expressed by a written constraint.⌋(RS_MANI_00033) Class RestPrimitivePropertyDef (abstract) Package M2::AUTOSART emplates::AdaptivePlatform::ApplicationDesign::PortInterface::REST Note This meta-class acts as an abstract base class for the definition of primitive properties of elements of a REST service. Tags: atp.Status=draft Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement , Identifiable, MultilanguageReferrable, Referrable, RestAbstractPropertyDef Subclasses RestAbstractNumericalPropertyDef , RestBooleanPropertyDef, RestObjectRef, Rest StringPropertyDef Attribute Type Mul. Kind Note – – – – – Table 5.12: RestPrimitivePropertyDef 222 of 602 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification