From 038360011682b95ba81c645f44102f2b051a0f71 Mon Sep 17 00:00:00 2001 From: D024504 Date: Thu, 12 Sep 2024 17:13:01 +0200 Subject: [PATCH 1/3] Undeprecate `Common.SecondaryKey` --- vocabularies/Common.json | 6 +- vocabularies/Common.md | 384 +++++++++++++++++++-------------------- vocabularies/Common.xml | 13 +- 3 files changed, 199 insertions(+), 204 deletions(-) diff --git a/vocabularies/Common.json b/vocabularies/Common.json index 548852c0..57e01e94 100644 --- a/vocabularies/Common.json +++ b/vocabularies/Common.json @@ -172,10 +172,8 @@ "$Collection": true, "$Type": "Edm.PropertyPath", "$AppliesTo": ["EntityType"], - "@Core.Revisions": [ - { "Kind": "Deprecated", "Description": "Use term `AlternateKeys` from the OASIS Core vocabulary instead" } - ], - "@Core.Description": "The listed properties form a secondary key. Multiple secondary keys are possible using different qualifiers." + "@Core.Description": "The listed properties form a secondary key", + "@Core.LongDescription": "Multiple secondary keys are possible using different qualifiers.\n Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys),\n secondary keys cannot be used to address an entity in a resource path." }, "MinOccurs": { "$Kind": "Term", diff --git a/vocabularies/Common.md b/vocabularies/Common.md index c2469172..1ec2390a 100644 --- a/vocabularies/Common.md +++ b/vocabularies/Common.md @@ -27,90 +27,90 @@ Term|Type|Description [IsUnit](Common.xml#L205)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Annotated property or parameter is a unit of measure [UnitSpecificScale](Common.xml#L209)|PrimitiveType|The number of fractional decimal digits of a currency amount or measured quantity
The annotated property contains a currency code or unit of measure, and the annotation value specifies the default scale of numeric values with that currency code or unit of measure. Can be used in e.g. a list of available currency codes or units of measure, or a list of measuring devices to specify the number of fractional digits captured by that device. [UnitSpecificPrecision](Common.xml#L214) *([Experimental](Common.md#Experimental))*|PrimitiveType|The number of significant decimal digits of a currency amount or measured quantity
The annotated property contains a currency code or unit of measure, and the annotation value specifies the default precision of numeric values with that currency code or unit of measure. Can be used in e.g. a list of available currency codes or units of measure, or a list of measuring devices to specify the number of significant digits captured by that device. -[SecondaryKey](Common.xml#L220) *(Deprecated)*|\[PropertyPath\]|Use term `AlternateKeys` from the OASIS Core vocabulary instead -[MinOccurs](Common.xml#L232)|Int64|The annotated set or collection contains at least this number of items -[MaxOccurs](Common.xml#L236)|Int64|The annotated set or collection contains at most this number of items -[AssociationEntity](Common.xml#L240)|\[NavigationPropertyPath\]|Entity representing an n:m association with attributes -[DerivedNavigation](Common.xml#L247)|NavigationPropertyPath|Shortcut for a multi-segment navigation, contains the long path with all its segments -[Masked](Common.xml#L253) *(Deprecated)*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Use terms `MaskedValue` instead -[MaskedValue](Common.xml#L268) *([Experimental](Common.md#Experimental))*|String?|Property contains sensitive data that is by default not transferred
By default a masked property is excluded from responses and instead an instance annotation with this term is sent, containing a masked value that can be rendered by user interfaces. -[RevealOnDemand](Common.xml#L277) *([Experimental](Common.md#Experimental))*|Boolean|Unmasked data for this property can be requested with custom query option `masked-values=false` -[SemanticObject](Common.xml#L283)|String?|Name of the Semantic Object represented as this entity type or identified by this property -[SemanticObjectMapping](Common.xml#L286)|\[[SemanticObjectMappingType](#SemanticObjectMappingType)\]|Maps properties of the annotated entity type or sibling properties of the annotated property to properties of the Semantic Object
This allows "renaming" of properties in the current context to match property names of the Semantic Object, e.g. `SenderPartyID` to `PartyID`. Only properties explicitly listed in the mapping are renamed, all other properties are available for intent-based navigation with their "local" name. -[SemanticObjectUnavailableActions](Common.xml#L299)|\[String\]|List of actions that are not available in the current state of the instance of the Semantic Object -[IsInstanceAnnotation](Common.xml#L303)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Term can also be used as instance annotation; AppliesTo of this term specifies where it can be applied -[FilterExpressionRestrictions](Common.xml#L333) *(Deprecated)*|\[[FilterExpressionRestrictionType](#FilterExpressionRestrictionType)\]|Use term Capabilities.FilterRestrictions instead -[FieldControl](Common.xml#L376)|[FieldControlType?](#FieldControlType)|Control state of a property, parameter, or the media stream of a media entity
This term can be used for static field control, providing an enumeration member value in $metadata, as well as dynamically, providing a `Path` expression.
In the dynamic case the property referenced by the `Path` expression MUST be of type `Edm.Byte` to accommodate OData V2 services as well as V4 infrastructures that don't support enumeration types. -[ExceptionCategory](Common.xml#L433) *([Experimental](Common.md#Experimental))*|String|A machine-readable exception category -[Application](Common.xml#L438) *([Experimental](Common.md#Experimental))*|[ApplicationType](#ApplicationType)|... -[Timestamp](Common.xml#L458) *([Experimental](Common.md#Experimental))*|DateTimeOffset|... -[TransactionId](Common.xml#L463) *([Experimental](Common.md#Experimental))*|String|... -[ErrorResolution](Common.xml#L468) *([Experimental](Common.md#Experimental))*|[ErrorResolutionType](#ErrorResolutionType)|Hints for resolving this error -[Messages](Common.xml#L486)|\[ComplexType\]|Collection of end-user messages

The name of the message type is service-specific, its structure components are identified by naming convention, following the names of the OData error response structure.

The minimum structure is

-[additionalTargets](Common.xml#L502) *([Experimental](Common.md#Experimental))*|\[String\]|Additional targets for the message
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response -[longtextUrl](Common.xml#L508)|URL|Location of the message long text
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response -[numericSeverity](Common.xml#L514)|[NumericMessageSeverityType](#NumericMessageSeverityType)|Classifies an end-user message as info, success, warning, or error
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response -[MaximumNumericMessageSeverity](Common.xml#L519) *([Experimental](Common.md#Experimental))*|[NumericMessageSeverityType?](#NumericMessageSeverityType)|The maximum severity of all end-user messages attached to an entity, null if no messages are attached
This metadata annotation can be applied to entity types that are also annotated with term [`Common.Messages`](#Messages) -[IsActionCritical](Common.xml#L548)|Boolean|Criticality of the function or action to enforce a warning or similar before it's executed -[Attributes](Common.xml#L552)|\[PropertyPath\]|Attributes related to this property, which may occur in denormalized entity types -[RelatedRecursiveHierarchy](Common.xml#L556)|AnnotationPath|A recursive hierarchy related to this property. The annotation path must end in Aggregation.RecursiveHierarchy. -[Interval](Common.xml#L560)|[IntervalType](#IntervalType)|An interval with lower and upper boundaries described by two properties -[ResultContext](Common.xml#L583)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated entity type has one or more containment navigation properties. An instance of the annotated entity type provides the context required for determining the target entity sets reached by these containment navigation properties. -[SAPObjectNodeType](Common.xml#L591) *([Experimental](Common.md#Experimental))*|[SAPObjectNodeTypeType](#SAPObjectNodeTypeType)|The SAP Object Node Type represented by the annotated entity type
SAP Object Node Types define the structure of SAP Object Types, which are a generalization of Business Object, Technical Object, Configuration Object, and Analytical Object. -[Composition](Common.xml#L607) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated navigation property represents a logical composition, even though it is non-containment
The entities related via this navigation property have an existential dependency on their composition parent. The entity set of the composition parent MUST contain a NavigationPropertyBinding for this navigation property. -[SAPObjectNodeTypeReference](Common.xml#L616) *([Experimental](Common.md#Experimental))*|String|The entity referenced by the annotated property has the [`SAPObjectNodeType`](#SAPObjectNodeType) with this name
The entity containing the property and the entity referenced by it will in general have different SAP Object Node Types. -[IsNaturalPerson](Common.xml#L624)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated entity type (e.g. `Employee`) or annotation (e.g. `IsImageUrl`) represents a natural person -[ValueList](Common.xml#L630)|[ValueListType](#ValueListType)|Specifies how to get a list of acceptable values for a property or parameter
The value list can be based on user input that is passed in the value list request. The value list can be used for type-ahead and classical pick lists. -[ValueListRelevantQualifiers](Common.xml#L704)|\[[SimpleIdentifier](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)\]|List of qualifiers of relevant ValueList annotations
The value of this annotation is a dynamic expression for calculating the qualifiers of relevant value lists depending on the values of one or more other properties. -[ValueListWithFixedValues](Common.xml#L709)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|If specified as true, there's only one value list mapping and its value list consists of a small number of fixed values
Can be annotated with: -[ValueListShowValuesImmediately](Common.xml#L718) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|A value list with a very small number of fixed values, can decide to show all values immediately -[ValueListForValidation](Common.xml#L723)|String|Contains the qualifier of the ValueList or ValueListMapping that should be used for validation
An empty string identifies the ValueList or ValueListMapping without a qualifier. -[ValueListReferences](Common.xml#L728)|\[URL\]|A list of URLs of CSDL documents containing value list mappings for this parameter or property -[ValueListMapping](Common.xml#L733)|[ValueListMappingType](#ValueListMappingType)|Specifies the mapping between data service properties and value list properties
The value list can be filtered based on user input. It can be used for type-ahead and classical pick lists. There may be many alternative mappings with different qualifiers. -[IsCalendarYear](Common.xml#L845)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a year number as string following the logical pattern (-?)YYYY(Y*) consisting of an optional minus sign for years B.C. followed by at least four digits. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3}) -[IsCalendarHalfyear](Common.xml#L854)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a halfyear number as string following the logical pattern H consisting of a single digit. The string matches the regex pattern [1-2] -[IsCalendarQuarter](Common.xml#L863)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar quarter number as string following the logical pattern Q consisting of a single digit. The string matches the regex pattern [1-4] -[IsCalendarMonth](Common.xml#L872)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar month number as string following the logical pattern MM consisting of two digits. The string matches the regex pattern 0[1-9]\|1[0-2] -[IsCalendarWeek](Common.xml#L881)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar week number as string following the logical pattern WW consisting of two digits. The string matches the regex pattern 0[1-9]\|[1-4][0-9]\|5[0-3] -[IsDayOfCalendarMonth](Common.xml#L890)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a calendar month. Valid values are between 1 and 31. -[IsDayOfCalendarYear](Common.xml#L898)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a calendar year. Valid values are between 1 and 366. -[IsCalendarYearHalfyear](Common.xml#L906)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and halfyear as string following the logical pattern (-?)YYYY(Y*)H consisting of an optional minus sign for years B.C. followed by at least five digits, where the last digit represents the halfyear. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})[1-2] -[IsCalendarYearQuarter](Common.xml#L916)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and quarter as string following the logical pattern (-?)YYYY(Y*)Q consisting of an optional minus sign for years B.C. followed by at least five digits, where the last digit represents the quarter. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})[1-4] -[IsCalendarYearMonth](Common.xml#L926)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and month as string following the logical pattern (-?)YYYY(Y*)MM consisting of an optional minus sign for years B.C. followed by at least six digits, where the last two digits represent the months January to December. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|1[0-2]) -[IsCalendarYearWeek](Common.xml#L937)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and week as string following the logical pattern (-?)YYYY(Y*)WW consisting of an optional minus sign for years B.C. followed by at least six digits, where the last two digits represent week number in the year. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|[1-4][0-9]\|5[0-3]) -[IsCalendarDate](Common.xml#L947)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar date: year, month and day as string following the logical pattern (-?)YYYY(Y*)MMDD consisting of an optional minus sign for years B.C. followed by at least eight digits, where the last four digits represent the months January to December (MM) and the day of the month (DD). The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|1[0-2])(0[1-9]\|[12][0-9]\|3[01]) The regex pattern does not reflect the additional constraint for "Day-of-month Values": The day value must be no more than 30 if month is one of 04, 06, 09, or 11, no more than 28 if month is 02 and year is not divisible by 4, or is divisible by 100 but not by 400, and no more than 29 if month is 02 and year is divisible by 400, or by 4 but not by 100. -[IsFiscalYear](Common.xml#L964)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year number as string following the logical pattern YYYY consisting of four digits. The string matches the regex pattern [1-9][0-9]{3} -[IsFiscalPeriod](Common.xml#L973)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal period as string following the logical pattern PPP consisting of three digits. The string matches the regex pattern [0-9]{3} -[IsFiscalYearPeriod](Common.xml#L982)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and period as string following the logical pattern YYYYPPP consisting of seven digits, where the last three digits represent the fiscal period in the year. The string matches the regex pattern ([1-9][0-9]{3})([0-9]{3}) -[IsFiscalQuarter](Common.xml#L992)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal quarter number as string following the logical pattern Q consisting of a single digit. The string matches the regex pattern [1-4] -[IsFiscalYearQuarter](Common.xml#L1000)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and quarter as string following the logical pattern YYYYQ consisting of five digits, where the last digit represents the quarter. The string matches the regex pattern [1-9][0-9]{3}[1-4] -[IsFiscalWeek](Common.xml#L1009)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal week number as string following the logical pattern WW consisting of two digits. The string matches the regex pattern 0[1-9]\|[1-4][0-9]\|5[0-3] -[IsFiscalYearWeek](Common.xml#L1017)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and week as string following the logical pattern YYYYWW consisting of six digits, where the last two digits represent the week number in the year. The string matches the regex pattern [1-9][0-9]{3}(0[1-9]\|[1-4][0-9]\|5[0-3]) -[IsDayOfFiscalYear](Common.xml#L1026)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a fiscal year. Valid values are between 1 and 371. -[IsFiscalYearVariant](Common.xml#L1033)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year variant -[MutuallyExclusiveTerm](Common.xml#L1041)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Only one term of the group identified with the Qualifier attribute can be applied -[DraftRoot](Common.xml#L1047)|[DraftRootType](#DraftRootType)|Root entities of business documents that support the draft pattern -[DraftNode](Common.xml#L1088)|[DraftNodeType](#DraftNodeType)|Entities in this set are parts of business documents that support the draft pattern -[DraftActivationVia](Common.xml#L1110)|\[[SimpleIdentifier](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)\]|Draft entities in this set are indirectly activated via draft entities in the referenced entity sets -[EditableFieldFor](Common.xml#L1114)|PropertyPath|The annotated property is an editable field for the referenced key property -[SemanticKey](Common.xml#L1144)|\[PropertyPath\]|The listed properties form the semantic key, i.e. they are unique modulo IsActiveEntity -[SideEffects](Common.xml#L1148)|[SideEffectsType](#SideEffectsType)|Describes side-effects of modification operations -[DefaultValuesFunction](Common.xml#L1231)|[QualifiedName](#QualifiedName)|Function to calculate default values based on user input that is only known to the client and "context information" that is already available to the service
The default values function must have a bound overload whose binding parameter type matches the annotation target
- for an entity set: collection of entity type of entity set
- for a navigation property: identical to the type of the navigation property (single- or collection-valued)
- for a bound action/function: identical to the binding parameter type of the annotated action/function
In addition the overload can have non-binding parameters for values that the user has already entered:
- for an entity set or navigation property: each non-binding parameter name and type must match the name and type of a property of the entity to be created
- for an action or function: each non-binding parameter name and type must match the name and type of a non-binding parameter of the action or function to be called
The result type of the default values function is a complex type whose properties correspond in name and type to a subset of
- the properties of the entity to create, or
- the parameters of the action or function to call -[DerivedDefaultValue](Common.xml#L1260) *([Experimental](Common.md#Experimental))*|String|Function import to derive a default value for the property from a given context.
Function import has two parameters of complex types:
- `parameters`, a structure resembling the entity type the parameter entity set related to the entity set of the annotated property
- `properties`, a structure resembling the type of the entity set of the annotated property
The return type must be of the same type as the annotated property.
Arguments passed to the function import are used as context for deriving the default value. The function import returns this default value, or null in case such a value could not be determined. -[FilterDefaultValue](Common.xml#L1281)|PrimitiveType?|A default value for the property to be used in filter expressions. -[FilterDefaultValueHigh](Common.xml#L1285) *([Experimental](Common.md#Experimental))*|PrimitiveType?|A default upper limit for the property to be used in 'less than or equal' filter expressions. -[DerivedFilterDefaultValue](Common.xml#L1290) *([Experimental](Common.md#Experimental))*|String|Function import to derive a default value for the property from a given context in order to use it in filter expressions.
Function import has two parameters of complex types:
- `parameters`, a structure resembling the entity type the parameter entity set related to the entity set of the annotated property
- `properties`, a structure resembling the type of the entity set of the annotated property
The return type must be of the same type as the annotated property.
Arguments passed to the function import are used as context for deriving the default value. The function import returns this default value, or null in case such a value could not be determined. -[SortOrder](Common.xml#L1314)|\[[SortOrderType](#SortOrderType)\]|List of sort criteria
The items of the annotated entity set or the items of the collection of the annotated entity type are sorted by the first entry of the SortOrder collection. Items with same value for this first sort criteria are sorted by the second entry of the SortOrder collection, and so on. -[RecursiveHierarchy](Common.xml#L1374) *(Deprecated)*|[RecursiveHierarchyType](#RecursiveHierarchyType)|Use terms [Aggregation.RecursiveHierarchy](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Aggregation.V1.md#RecursiveHierarchy) and [Hierarchy.RecursiveHierarchy](https://github.com/SAP/odata-vocabularies/blob/main/vocabularies/Hierarchy.md#RecursiveHierarchy) instead -[CreatedAt](Common.xml#L1422)|DateTimeOffset?|Creation timestamp -[CreatedBy](Common.xml#L1426)|[UserID?](#UserID)|First editor -[ChangedAt](Common.xml#L1430)|DateTimeOffset?|Last modification timestamp -[ChangedBy](Common.xml#L1434)|[UserID?](#UserID)|Last editor -[OriginalProtocolVersion](Common.xml#L1446)|String|Original protocol version of a converted (V4) CSDL document, allowed values `2.0` and `3.0` -[ApplyMultiUnitBehaviorForSortingAndFiltering](Common.xml#L1451) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Sorting and filtering of amounts in multiple currencies needs special consideration
TODO: add link to UX documentation on https://experience.sap.com/fiori-design/ -[mediaUploadLink](Common.xml#L1457) *([Experimental](Common.md#Experimental))*|URL|URL for uploading new media content to a Document Management Service
In contrast to the `@odata.mediaEditLink` this URL allows to upload new media content without directly changing a stream property or media resource. The upload request typically uses HTTP POST with `Content-Type: multipart/form-data` following RFC 7578. The upload request must contain one multipart representing the content of the file. The `name` parameter in the `Content-Disposition` header (as described in RFC 7578) is irrelevant, but the `filename` parameter is expected. If the request succeeds the response will contain a JSON body of `Content-Type: application/json` with a JSON property `readLink`. The newly uploaded media resource can be linked to the stream property by changing the `@odata.mediaReadLink` to the value of this `readLink` in a subsequent PATCH request to the OData entity. -[PrimitivePropertyPath](Common.xml#L1472) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|A term or term property with this tag whose type is (a collection of) `Edm.PropertyPath` MUST resolve to a primitive structural property -[WebSocketBaseURL](Common.xml#L1477) *([Experimental](Common.md#Experimental))*|URL|Base URL for WebSocket connections +[SecondaryKey](Common.xml#L220)|\[PropertyPath\]|The listed properties form a secondary key
Multiple secondary keys are possible using different qualifiers. Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), secondary keys cannot be used to address an entity in a resource path. +[MinOccurs](Common.xml#L229)|Int64|The annotated set or collection contains at least this number of items +[MaxOccurs](Common.xml#L233)|Int64|The annotated set or collection contains at most this number of items +[AssociationEntity](Common.xml#L237)|\[NavigationPropertyPath\]|Entity representing an n:m association with attributes +[DerivedNavigation](Common.xml#L244)|NavigationPropertyPath|Shortcut for a multi-segment navigation, contains the long path with all its segments +[Masked](Common.xml#L250) *(Deprecated)*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Use terms `MaskedValue` instead +[MaskedValue](Common.xml#L265) *([Experimental](Common.md#Experimental))*|String?|Property contains sensitive data that is by default not transferred
By default a masked property is excluded from responses and instead an instance annotation with this term is sent, containing a masked value that can be rendered by user interfaces. +[RevealOnDemand](Common.xml#L274) *([Experimental](Common.md#Experimental))*|Boolean|Unmasked data for this property can be requested with custom query option `masked-values=false` +[SemanticObject](Common.xml#L280)|String?|Name of the Semantic Object represented as this entity type or identified by this property +[SemanticObjectMapping](Common.xml#L283)|\[[SemanticObjectMappingType](#SemanticObjectMappingType)\]|Maps properties of the annotated entity type or sibling properties of the annotated property to properties of the Semantic Object
This allows "renaming" of properties in the current context to match property names of the Semantic Object, e.g. `SenderPartyID` to `PartyID`. Only properties explicitly listed in the mapping are renamed, all other properties are available for intent-based navigation with their "local" name. +[SemanticObjectUnavailableActions](Common.xml#L296)|\[String\]|List of actions that are not available in the current state of the instance of the Semantic Object +[IsInstanceAnnotation](Common.xml#L300)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Term can also be used as instance annotation; AppliesTo of this term specifies where it can be applied +[FilterExpressionRestrictions](Common.xml#L330) *(Deprecated)*|\[[FilterExpressionRestrictionType](#FilterExpressionRestrictionType)\]|Use term Capabilities.FilterRestrictions instead +[FieldControl](Common.xml#L373)|[FieldControlType?](#FieldControlType)|Control state of a property, parameter, or the media stream of a media entity
This term can be used for static field control, providing an enumeration member value in $metadata, as well as dynamically, providing a `Path` expression.
In the dynamic case the property referenced by the `Path` expression MUST be of type `Edm.Byte` to accommodate OData V2 services as well as V4 infrastructures that don't support enumeration types. +[ExceptionCategory](Common.xml#L430) *([Experimental](Common.md#Experimental))*|String|A machine-readable exception category +[Application](Common.xml#L435) *([Experimental](Common.md#Experimental))*|[ApplicationType](#ApplicationType)|... +[Timestamp](Common.xml#L455) *([Experimental](Common.md#Experimental))*|DateTimeOffset|... +[TransactionId](Common.xml#L460) *([Experimental](Common.md#Experimental))*|String|... +[ErrorResolution](Common.xml#L465) *([Experimental](Common.md#Experimental))*|[ErrorResolutionType](#ErrorResolutionType)|Hints for resolving this error +[Messages](Common.xml#L483)|\[ComplexType\]|Collection of end-user messages

The name of the message type is service-specific, its structure components are identified by naming convention, following the names of the OData error response structure.

The minimum structure is

+[additionalTargets](Common.xml#L499) *([Experimental](Common.md#Experimental))*|\[String\]|Additional targets for the message
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response +[longtextUrl](Common.xml#L505)|URL|Location of the message long text
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response +[numericSeverity](Common.xml#L511)|[NumericMessageSeverityType](#NumericMessageSeverityType)|Classifies an end-user message as info, success, warning, or error
This instance annotation can be applied to the `error` object and the objects within the `details` array of an OData error response +[MaximumNumericMessageSeverity](Common.xml#L516) *([Experimental](Common.md#Experimental))*|[NumericMessageSeverityType?](#NumericMessageSeverityType)|The maximum severity of all end-user messages attached to an entity, null if no messages are attached
This metadata annotation can be applied to entity types that are also annotated with term [`Common.Messages`](#Messages) +[IsActionCritical](Common.xml#L545)|Boolean|Criticality of the function or action to enforce a warning or similar before it's executed +[Attributes](Common.xml#L549)|\[PropertyPath\]|Attributes related to this property, which may occur in denormalized entity types +[RelatedRecursiveHierarchy](Common.xml#L553)|AnnotationPath|A recursive hierarchy related to this property. The annotation path must end in Aggregation.RecursiveHierarchy. +[Interval](Common.xml#L557)|[IntervalType](#IntervalType)|An interval with lower and upper boundaries described by two properties +[ResultContext](Common.xml#L580)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated entity type has one or more containment navigation properties. An instance of the annotated entity type provides the context required for determining the target entity sets reached by these containment navigation properties. +[SAPObjectNodeType](Common.xml#L588) *([Experimental](Common.md#Experimental))*|[SAPObjectNodeTypeType](#SAPObjectNodeTypeType)|The SAP Object Node Type represented by the annotated entity type
SAP Object Node Types define the structure of SAP Object Types, which are a generalization of Business Object, Technical Object, Configuration Object, and Analytical Object. +[Composition](Common.xml#L604) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated navigation property represents a logical composition, even though it is non-containment
The entities related via this navigation property have an existential dependency on their composition parent. The entity set of the composition parent MUST contain a NavigationPropertyBinding for this navigation property. +[SAPObjectNodeTypeReference](Common.xml#L613) *([Experimental](Common.md#Experimental))*|String|The entity referenced by the annotated property has the [`SAPObjectNodeType`](#SAPObjectNodeType) with this name
The entity containing the property and the entity referenced by it will in general have different SAP Object Node Types. +[IsNaturalPerson](Common.xml#L621)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|The annotated entity type (e.g. `Employee`) or annotation (e.g. `IsImageUrl`) represents a natural person +[ValueList](Common.xml#L627)|[ValueListType](#ValueListType)|Specifies how to get a list of acceptable values for a property or parameter
The value list can be based on user input that is passed in the value list request. The value list can be used for type-ahead and classical pick lists. +[ValueListRelevantQualifiers](Common.xml#L701)|\[[SimpleIdentifier](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)\]|List of qualifiers of relevant ValueList annotations
The value of this annotation is a dynamic expression for calculating the qualifiers of relevant value lists depending on the values of one or more other properties. +[ValueListWithFixedValues](Common.xml#L706)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|If specified as true, there's only one value list mapping and its value list consists of a small number of fixed values
Can be annotated with: +[ValueListShowValuesImmediately](Common.xml#L715) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|A value list with a very small number of fixed values, can decide to show all values immediately +[ValueListForValidation](Common.xml#L720)|String|Contains the qualifier of the ValueList or ValueListMapping that should be used for validation
An empty string identifies the ValueList or ValueListMapping without a qualifier. +[ValueListReferences](Common.xml#L725)|\[URL\]|A list of URLs of CSDL documents containing value list mappings for this parameter or property +[ValueListMapping](Common.xml#L730)|[ValueListMappingType](#ValueListMappingType)|Specifies the mapping between data service properties and value list properties
The value list can be filtered based on user input. It can be used for type-ahead and classical pick lists. There may be many alternative mappings with different qualifiers. +[IsCalendarYear](Common.xml#L842)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a year number as string following the logical pattern (-?)YYYY(Y*) consisting of an optional minus sign for years B.C. followed by at least four digits. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3}) +[IsCalendarHalfyear](Common.xml#L851)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a halfyear number as string following the logical pattern H consisting of a single digit. The string matches the regex pattern [1-2] +[IsCalendarQuarter](Common.xml#L860)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar quarter number as string following the logical pattern Q consisting of a single digit. The string matches the regex pattern [1-4] +[IsCalendarMonth](Common.xml#L869)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar month number as string following the logical pattern MM consisting of two digits. The string matches the regex pattern 0[1-9]\|1[0-2] +[IsCalendarWeek](Common.xml#L878)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar week number as string following the logical pattern WW consisting of two digits. The string matches the regex pattern 0[1-9]\|[1-4][0-9]\|5[0-3] +[IsDayOfCalendarMonth](Common.xml#L887)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a calendar month. Valid values are between 1 and 31. +[IsDayOfCalendarYear](Common.xml#L895)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a calendar year. Valid values are between 1 and 366. +[IsCalendarYearHalfyear](Common.xml#L903)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and halfyear as string following the logical pattern (-?)YYYY(Y*)H consisting of an optional minus sign for years B.C. followed by at least five digits, where the last digit represents the halfyear. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})[1-2] +[IsCalendarYearQuarter](Common.xml#L913)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and quarter as string following the logical pattern (-?)YYYY(Y*)Q consisting of an optional minus sign for years B.C. followed by at least five digits, where the last digit represents the quarter. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})[1-4] +[IsCalendarYearMonth](Common.xml#L923)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and month as string following the logical pattern (-?)YYYY(Y*)MM consisting of an optional minus sign for years B.C. followed by at least six digits, where the last two digits represent the months January to December. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|1[0-2]) +[IsCalendarYearWeek](Common.xml#L934)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar year and week as string following the logical pattern (-?)YYYY(Y*)WW consisting of an optional minus sign for years B.C. followed by at least six digits, where the last two digits represent week number in the year. The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|[1-4][0-9]\|5[0-3]) +[IsCalendarDate](Common.xml#L944)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a calendar date: year, month and day as string following the logical pattern (-?)YYYY(Y*)MMDD consisting of an optional minus sign for years B.C. followed by at least eight digits, where the last four digits represent the months January to December (MM) and the day of the month (DD). The string matches the regex pattern -?([1-9][0-9]{3,}\|0[0-9]{3})(0[1-9]\|1[0-2])(0[1-9]\|[12][0-9]\|3[01]) The regex pattern does not reflect the additional constraint for "Day-of-month Values": The day value must be no more than 30 if month is one of 04, 06, 09, or 11, no more than 28 if month is 02 and year is not divisible by 4, or is divisible by 100 but not by 400, and no more than 29 if month is 02 and year is divisible by 400, or by 4 but not by 100. +[IsFiscalYear](Common.xml#L961)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year number as string following the logical pattern YYYY consisting of four digits. The string matches the regex pattern [1-9][0-9]{3} +[IsFiscalPeriod](Common.xml#L970)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal period as string following the logical pattern PPP consisting of three digits. The string matches the regex pattern [0-9]{3} +[IsFiscalYearPeriod](Common.xml#L979)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and period as string following the logical pattern YYYYPPP consisting of seven digits, where the last three digits represent the fiscal period in the year. The string matches the regex pattern ([1-9][0-9]{3})([0-9]{3}) +[IsFiscalQuarter](Common.xml#L989)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal quarter number as string following the logical pattern Q consisting of a single digit. The string matches the regex pattern [1-4] +[IsFiscalYearQuarter](Common.xml#L997)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and quarter as string following the logical pattern YYYYQ consisting of five digits, where the last digit represents the quarter. The string matches the regex pattern [1-9][0-9]{3}[1-4] +[IsFiscalWeek](Common.xml#L1006)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal week number as string following the logical pattern WW consisting of two digits. The string matches the regex pattern 0[1-9]\|[1-4][0-9]\|5[0-3] +[IsFiscalYearWeek](Common.xml#L1014)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year and week as string following the logical pattern YYYYWW consisting of six digits, where the last two digits represent the week number in the year. The string matches the regex pattern [1-9][0-9]{3}(0[1-9]\|[1-4][0-9]\|5[0-3]) +[IsDayOfFiscalYear](Common.xml#L1023)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Day number relative to a fiscal year. Valid values are between 1 and 371. +[IsFiscalYearVariant](Common.xml#L1030)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Property encodes a fiscal year variant +[MutuallyExclusiveTerm](Common.xml#L1038)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Only one term of the group identified with the Qualifier attribute can be applied +[DraftRoot](Common.xml#L1044)|[DraftRootType](#DraftRootType)|Root entities of business documents that support the draft pattern +[DraftNode](Common.xml#L1085)|[DraftNodeType](#DraftNodeType)|Entities in this set are parts of business documents that support the draft pattern +[DraftActivationVia](Common.xml#L1107)|\[[SimpleIdentifier](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)\]|Draft entities in this set are indirectly activated via draft entities in the referenced entity sets +[EditableFieldFor](Common.xml#L1111)|PropertyPath|The annotated property is an editable field for the referenced key property +[SemanticKey](Common.xml#L1141)|\[PropertyPath\]|The listed properties form the semantic key, i.e. they are unique modulo IsActiveEntity +[SideEffects](Common.xml#L1145)|[SideEffectsType](#SideEffectsType)|Describes side-effects of modification operations +[DefaultValuesFunction](Common.xml#L1228)|[QualifiedName](#QualifiedName)|Function to calculate default values based on user input that is only known to the client and "context information" that is already available to the service
The default values function must have a bound overload whose binding parameter type matches the annotation target
- for an entity set: collection of entity type of entity set
- for a navigation property: identical to the type of the navigation property (single- or collection-valued)
- for a bound action/function: identical to the binding parameter type of the annotated action/function
In addition the overload can have non-binding parameters for values that the user has already entered:
- for an entity set or navigation property: each non-binding parameter name and type must match the name and type of a property of the entity to be created
- for an action or function: each non-binding parameter name and type must match the name and type of a non-binding parameter of the action or function to be called
The result type of the default values function is a complex type whose properties correspond in name and type to a subset of
- the properties of the entity to create, or
- the parameters of the action or function to call +[DerivedDefaultValue](Common.xml#L1257) *([Experimental](Common.md#Experimental))*|String|Function import to derive a default value for the property from a given context.
Function import has two parameters of complex types:
- `parameters`, a structure resembling the entity type the parameter entity set related to the entity set of the annotated property
- `properties`, a structure resembling the type of the entity set of the annotated property
The return type must be of the same type as the annotated property.
Arguments passed to the function import are used as context for deriving the default value. The function import returns this default value, or null in case such a value could not be determined. +[FilterDefaultValue](Common.xml#L1278)|PrimitiveType?|A default value for the property to be used in filter expressions. +[FilterDefaultValueHigh](Common.xml#L1282) *([Experimental](Common.md#Experimental))*|PrimitiveType?|A default upper limit for the property to be used in 'less than or equal' filter expressions. +[DerivedFilterDefaultValue](Common.xml#L1287) *([Experimental](Common.md#Experimental))*|String|Function import to derive a default value for the property from a given context in order to use it in filter expressions.
Function import has two parameters of complex types:
- `parameters`, a structure resembling the entity type the parameter entity set related to the entity set of the annotated property
- `properties`, a structure resembling the type of the entity set of the annotated property
The return type must be of the same type as the annotated property.
Arguments passed to the function import are used as context for deriving the default value. The function import returns this default value, or null in case such a value could not be determined. +[SortOrder](Common.xml#L1311)|\[[SortOrderType](#SortOrderType)\]|List of sort criteria
The items of the annotated entity set or the items of the collection of the annotated entity type are sorted by the first entry of the SortOrder collection. Items with same value for this first sort criteria are sorted by the second entry of the SortOrder collection, and so on. +[RecursiveHierarchy](Common.xml#L1371) *(Deprecated)*|[RecursiveHierarchyType](#RecursiveHierarchyType)|Use terms [Aggregation.RecursiveHierarchy](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Aggregation.V1.md#RecursiveHierarchy) and [Hierarchy.RecursiveHierarchy](https://github.com/SAP/odata-vocabularies/blob/main/vocabularies/Hierarchy.md#RecursiveHierarchy) instead +[CreatedAt](Common.xml#L1419)|DateTimeOffset?|Creation timestamp +[CreatedBy](Common.xml#L1423)|[UserID?](#UserID)|First editor +[ChangedAt](Common.xml#L1427)|DateTimeOffset?|Last modification timestamp +[ChangedBy](Common.xml#L1431)|[UserID?](#UserID)|Last editor +[OriginalProtocolVersion](Common.xml#L1443)|String|Original protocol version of a converted (V4) CSDL document, allowed values `2.0` and `3.0` +[ApplyMultiUnitBehaviorForSortingAndFiltering](Common.xml#L1448) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Sorting and filtering of amounts in multiple currencies needs special consideration
TODO: add link to UX documentation on https://experience.sap.com/fiori-design/ +[mediaUploadLink](Common.xml#L1454) *([Experimental](Common.md#Experimental))*|URL|URL for uploading new media content to a Document Management Service
In contrast to the `@odata.mediaEditLink` this URL allows to upload new media content without directly changing a stream property or media resource. The upload request typically uses HTTP POST with `Content-Type: multipart/form-data` following RFC 7578. The upload request must contain one multipart representing the content of the file. The `name` parameter in the `Content-Disposition` header (as described in RFC 7578) is irrelevant, but the `filename` parameter is expected. If the request succeeds the response will contain a JSON body of `Content-Type: application/json` with a JSON property `readLink`. The newly uploaded media resource can be linked to the stream property by changing the `@odata.mediaReadLink` to the value of this `readLink` in a subsequent PATCH request to the OData entity. +[PrimitivePropertyPath](Common.xml#L1469) *([Experimental](Common.md#Experimental))*|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|A term or term property with this tag whose type is (a collection of) `Edm.PropertyPath` MUST resolve to a primitive structural property +[WebSocketBaseURL](Common.xml#L1474) *([Experimental](Common.md#Experimental))*|URL|Base URL for WebSocket connections ## [TextFormatType](Common.xml#L120) @@ -122,24 +122,24 @@ Member|Value|Description [html](Common.xml#L124)|1|Plain text with markup that can validly appear directly within an HTML DIV element -## [SemanticObjectMappingType](Common.xml#L290) +## [SemanticObjectMappingType](Common.xml#L287) Maps a property of the annotated entity type or a sibling property of the annotated property to a property of the Semantic Object Property|Type|Description :-------|:---|:---------- -[LocalProperty](Common.xml#L292)|PropertyPath|Path to a local property that provides the value for the Semantic Object property -[SemanticObjectProperty](Common.xml#L295)|String|Name of the Semantic Object property +[LocalProperty](Common.xml#L289)|PropertyPath|Path to a local property that provides the value for the Semantic Object property +[SemanticObjectProperty](Common.xml#L292)|String|Name of the Semantic Object property -## [FilterExpressionRestrictionType](Common.xml#L344) *(Deprecated)* +## [FilterExpressionRestrictionType](Common.xml#L341) *(Deprecated)* Use term Capabilities.FilterRestrictions instead -## [FilterExpressionType](Common.xml#L356) *(Deprecated)* +## [FilterExpressionType](Common.xml#L353) *(Deprecated)* Use term Capabilities.FilterRestrictions instead -## [FieldControlType](Common.xml#L381) +## [FieldControlType](Common.xml#L378) Control state of a property When changes are requested, the value of this annotation in the before-image or after-image @@ -147,117 +147,117 @@ When changes are requested, the value of this annotation in the before-image or Member|Value|Description :-----|----:|:---------- -[Mandatory](Common.xml#L387)|7|Property is mandatory from a business perspective

A request that

fails entirely if this annotation is Mandatory in the after-image of the request. The empty string is an empty value. Service-specific rules may consider other values, also of non-string type, empty. Values in draft entities are never considered empty. Mandatory properties SHOULD be decorated in the UI with an asterisk. Null or empty values can also be disallowed by restricting the property value range with the standard type facet Nullable or terms from the Validation vocabulary.

-[Optional](Common.xml#L403)|3|Property may have a value
This value does not make sense as a static annotation value. -[ReadOnly](Common.xml#L407)|1|Property value cannot be changed
A request to change the property to a value that differs from the before-image fails entirely according to [OData-Protocol, section 11.4.3](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) if this annotation is given dynamically as `ReadOnly` in the before-image of the request.
To statically mark a property as read-only use term [Core.Computed](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Computed) instead. -[Inapplicable](Common.xml#L417)|0|Property has no meaning in the current entity state
A request that sets the property to a non-initial non-null value fails entirely if this annotation is `Inapplicable` in the after-image of the request.
This value does not make sense as a static annotation value.
Example for dynamic use: in a travel expense report the property `DestinationCountry` is inapplicable if trip type is domestic, and mandatory if trip type is international. -[Hidden](Common.xml#L427)|0|Deprecated synonym for Inapplicable, do not use
To statically hide a property on a UI use [UI.Hidden](UI.md#Hidden) instead +[Mandatory](Common.xml#L384)|7|Property is mandatory from a business perspective

A request that

fails entirely if this annotation is Mandatory in the after-image of the request. The empty string is an empty value. Service-specific rules may consider other values, also of non-string type, empty. Values in draft entities are never considered empty. Mandatory properties SHOULD be decorated in the UI with an asterisk. Null or empty values can also be disallowed by restricting the property value range with the standard type facet Nullable or terms from the Validation vocabulary.

+[Optional](Common.xml#L400)|3|Property may have a value
This value does not make sense as a static annotation value. +[ReadOnly](Common.xml#L404)|1|Property value cannot be changed
A request to change the property to a value that differs from the before-image fails entirely according to [OData-Protocol, section 11.4.3](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) if this annotation is given dynamically as `ReadOnly` in the before-image of the request.
To statically mark a property as read-only use term [Core.Computed](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Computed) instead. +[Inapplicable](Common.xml#L414)|0|Property has no meaning in the current entity state
A request that sets the property to a non-initial non-null value fails entirely if this annotation is `Inapplicable` in the after-image of the request.
This value does not make sense as a static annotation value.
Example for dynamic use: in a travel expense report the property `DestinationCountry` is inapplicable if trip type is domestic, and mandatory if trip type is international. +[Hidden](Common.xml#L424)|0|Deprecated synonym for Inapplicable, do not use
To statically hide a property on a UI use [UI.Hidden](UI.md#Hidden) instead -## [ApplicationType](Common.xml#L443) *([Experimental](Common.md#Experimental))* +## [ApplicationType](Common.xml#L440) *([Experimental](Common.md#Experimental))* Property|Type|Description :-------|:---|:---------- -[Component](Common.xml#L445)|String?|Software component of service implementation -[ServiceRepository](Common.xml#L448)|String?|... -[ServiceId](Common.xml#L451)|String?|... -[ServiceVersion](Common.xml#L454)|String?|... +[Component](Common.xml#L442)|String?|Software component of service implementation +[ServiceRepository](Common.xml#L445)|String?|... +[ServiceId](Common.xml#L448)|String?|... +[ServiceVersion](Common.xml#L451)|String?|... -## [ErrorResolutionType](Common.xml#L473) *([Experimental](Common.md#Experimental))* +## [ErrorResolutionType](Common.xml#L470) *([Experimental](Common.md#Experimental))* Property|Type|Description :-------|:---|:---------- -[Analysis](Common.xml#L475)|String?|Short hint on how to analyze this error -[Note](Common.xml#L478)|String?|Note for error resolution -[AdditionalNote](Common.xml#L481)|String?|Additional note for error resolution +[Analysis](Common.xml#L472)|String?|Short hint on how to analyze this error +[Note](Common.xml#L475)|String?|Note for error resolution +[AdditionalNote](Common.xml#L478)|String?|Additional note for error resolution -## [NumericMessageSeverityType](Common.xml#L524) +## [NumericMessageSeverityType](Common.xml#L521) **Type:** Byte Classifies an end-user message as info, success, warning, or error Allowed Value|Description :------------|:---------- -[1](Common.xml#L528)|Success - no action required -[2](Common.xml#L532)|Information - no action required -[3](Common.xml#L536)|Warning - action may be required -[4](Common.xml#L540)|Error - action is required +[1](Common.xml#L525)|Success - no action required +[2](Common.xml#L529)|Information - no action required +[3](Common.xml#L533)|Warning - action may be required +[4](Common.xml#L537)|Error - action is required -## [IntervalType](Common.xml#L563) +## [IntervalType](Common.xml#L560) Property|Type|Description :-------|:---|:---------- -[Label](Common.xml#L564) *([Experimental](Common.md#Experimental))*|String?|A short, human-readable text suitable for labels and captions in UIs -[LowerBoundary](Common.xml#L569)|PropertyPath|Property holding the lower interval boundary -[LowerBoundaryIncluded](Common.xml#L572)|Boolean|The lower boundary value is included in the interval -[UpperBoundary](Common.xml#L575)|PropertyPath|Property holding the upper interval boundary -[UpperBoundaryIncluded](Common.xml#L578)|Boolean|The upper boundary value is included in the interval +[Label](Common.xml#L561) *([Experimental](Common.md#Experimental))*|String?|A short, human-readable text suitable for labels and captions in UIs +[LowerBoundary](Common.xml#L566)|PropertyPath|Property holding the lower interval boundary +[LowerBoundaryIncluded](Common.xml#L569)|Boolean|The lower boundary value is included in the interval +[UpperBoundary](Common.xml#L572)|PropertyPath|Property holding the upper interval boundary +[UpperBoundaryIncluded](Common.xml#L575)|Boolean|The upper boundary value is included in the interval -## [SAPObjectNodeTypeType](Common.xml#L599) *([Experimental](Common.md#Experimental))* +## [SAPObjectNodeTypeType](Common.xml#L596) *([Experimental](Common.md#Experimental))* Information about an SAP Object Node Type Property|Type|Description :-------|:---|:---------- -[Name](Common.xml#L602)|String|The name of the SAP Object Node Type +[Name](Common.xml#L599)|String|The name of the SAP Object Node Type -## [ValueListType](Common.xml#L634) +## [ValueListType](Common.xml#L631) Property|Type|Description :-------|:---|:---------- -[Label](Common.xml#L655)|String?|Headline for value list, fallback is the label of the property or parameter -[CollectionPath](Common.xml#L659)|String|Resource path of an OData collection with possible values, relative to CollectionRoot -[CollectionRoot](Common.xml#L662)|String?|Service root of the value list collection; not specified means local to the document containing the annotation -[DistinctValuesSupported](Common.xml#L665)|Boolean|Indicates that the value list supports a 'distinct' aggregation on the value list properties defined via ValueListParameterInOut and ValueListParameterOut -[SearchSupported](Common.xml#L668)|Boolean|Value list supports the $search query option
The value of the target property is used as the search expression instead of in $filter -[FetchValues](Common.xml#L672)|[FetchValuesType?](#FetchValuesType)|Hint on when to fetch values -[PresentationVariantQualifier](Common.xml#L675)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Alternative representation of a value help, e.g. as a bar chart
Qualifier for annotation with term [UI.PresentationVariant](UI.md#PresentationVariant) on the entity set identified via CollectionPath -[SelectionVariantQualifier](Common.xml#L679)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Optional combination of parameters and filters to query the value help entity set
Qualifier for annotation with term [UI.SelectionVariant](UI.md#SelectionVariant) on the entity set identified via CollectionPath -[Parameters](Common.xml#L683)|\[[ValueListParameter](#ValueListParameter)\]|Instructions on how to construct the value list request and consume response properties +[Label](Common.xml#L652)|String?|Headline for value list, fallback is the label of the property or parameter +[CollectionPath](Common.xml#L656)|String|Resource path of an OData collection with possible values, relative to CollectionRoot +[CollectionRoot](Common.xml#L659)|String?|Service root of the value list collection; not specified means local to the document containing the annotation +[DistinctValuesSupported](Common.xml#L662)|Boolean|Indicates that the value list supports a 'distinct' aggregation on the value list properties defined via ValueListParameterInOut and ValueListParameterOut +[SearchSupported](Common.xml#L665)|Boolean|Value list supports the $search query option
The value of the target property is used as the search expression instead of in $filter +[FetchValues](Common.xml#L669)|[FetchValuesType?](#FetchValuesType)|Hint on when to fetch values +[PresentationVariantQualifier](Common.xml#L672)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Alternative representation of a value help, e.g. as a bar chart
Qualifier for annotation with term [UI.PresentationVariant](UI.md#PresentationVariant) on the entity set identified via CollectionPath +[SelectionVariantQualifier](Common.xml#L676)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Optional combination of parameters and filters to query the value help entity set
Qualifier for annotation with term [UI.SelectionVariant](UI.md#SelectionVariant) on the entity set identified via CollectionPath +[Parameters](Common.xml#L680)|\[[ValueListParameter](#ValueListParameter)\]|Instructions on how to construct the value list request and consume response properties **Applicable Annotation Terms:** - [QuickInfo](#QuickInfo) -## [FetchValuesType](Common.xml#L688) +## [FetchValuesType](Common.xml#L685) **Type:** Byte Hint on when to fetch values Allowed Value|Description :------------|:---------- -[1](Common.xml#L692)|Fetch values immediately without filter -[2](Common.xml#L696)|Fetch values with a filter +[1](Common.xml#L689)|Fetch values immediately without filter +[2](Common.xml#L693)|Fetch values with a filter -## [ValueListMappingType](Common.xml#L737) +## [ValueListMappingType](Common.xml#L734) Property|Type|Description :-------|:---|:---------- -[Label](Common.xml#L743)|String?|Headline for value list, fallback is the label of the property or parameter -[CollectionPath](Common.xml#L747)|String|Resource path of an OData collection with possible values, relative to the document containing the value list mapping -[DistinctValuesSupported](Common.xml#L750)|Boolean|Indicates that the value list supports a 'distinct' aggregation on the value list properties defined via ValueListParameterInOut and ValueListParameterOut -[FetchValues](Common.xml#L753)|[FetchValuesType?](#FetchValuesType)|Hint on when to fetch values -[PresentationVariantQualifier](Common.xml#L756)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Alternative representation of a value help, e.g. as a bar chart
Qualifier for annotation with term [UI.PresentationVariant](UI.md#PresentationVariant) on the value list entity set identified via CollectionPath in the ValueListReference annotation -[SelectionVariantQualifier](Common.xml#L760)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Optional combination of parameters and filters to query the value help entity set
Qualifier for annotation with term [UI.SelectionVariant](UI.md#SelectionVariant) on the entity set identified via CollectionPath -[Parameters](Common.xml#L764)|\[[ValueListParameter](#ValueListParameter)\]|Instructions on how to construct the value list request and consume response properties +[Label](Common.xml#L740)|String?|Headline for value list, fallback is the label of the property or parameter +[CollectionPath](Common.xml#L744)|String|Resource path of an OData collection with possible values, relative to the document containing the value list mapping +[DistinctValuesSupported](Common.xml#L747)|Boolean|Indicates that the value list supports a 'distinct' aggregation on the value list properties defined via ValueListParameterInOut and ValueListParameterOut +[FetchValues](Common.xml#L750)|[FetchValuesType?](#FetchValuesType)|Hint on when to fetch values +[PresentationVariantQualifier](Common.xml#L753)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Alternative representation of a value help, e.g. as a bar chart
Qualifier for annotation with term [UI.PresentationVariant](UI.md#PresentationVariant) on the value list entity set identified via CollectionPath in the ValueListReference annotation +[SelectionVariantQualifier](Common.xml#L757)|[SimpleIdentifier?](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier)|Optional combination of parameters and filters to query the value help entity set
Qualifier for annotation with term [UI.SelectionVariant](UI.md#SelectionVariant) on the entity set identified via CollectionPath +[Parameters](Common.xml#L761)|\[[ValueListParameter](#ValueListParameter)\]|Instructions on how to construct the value list request and consume response properties **Applicable Annotation Terms:** - [QuickInfo](#QuickInfo) -## [*ValueListParameter*](Common.xml#L769) +## [*ValueListParameter*](Common.xml#L766) **Derived Types:** @@ -271,97 +271,97 @@ Property|Type|Description Property|Type|Description :-------|:---|:---------- -[ValueListProperty](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[ValueListProperty](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -## [ValueListParameterIn](Common.xml#L774): [ValueListParameter](#ValueListParameter) +## [ValueListParameterIn](Common.xml#L771): [ValueListParameter](#ValueListParameter) Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -[LocalDataProperty](Common.xml#L775)|PropertyPath|Path to property that is used to filter the value list with `eq` comparison
In case the property path contains a collection-based navigation or structural property, the filter is a set of `eq` comparisons connected by `or` operators -[InitialValueIsSignificant](Common.xml#L779)|Boolean|Initial value, e.g. empty string, is a valid and significant value +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[LocalDataProperty](Common.xml#L772)|PropertyPath|Path to property that is used to filter the value list with `eq` comparison
In case the property path contains a collection-based navigation or structural property, the filter is a set of `eq` comparisons connected by `or` operators +[InitialValueIsSignificant](Common.xml#L776)|Boolean|Initial value, e.g. empty string, is a valid and significant value -## [ValueListParameterConstant](Common.xml#L783): [ValueListParameter](#ValueListParameter) +## [ValueListParameterConstant](Common.xml#L780): [ValueListParameter](#ValueListParameter) Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -[Constant](Common.xml#L784)|PrimitiveType|Constant value that is used to filter the value list with `eq` comparison, using the same representation as property default values, see [CSDL XML, 7.2.7 Default Value](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_DefaultValue) -[InitialValueIsSignificant](Common.xml#L787) *([Experimental](Common.md#Experimental))*|Boolean|Initial value, e.g. empty string, is a valid and significant value +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[Constant](Common.xml#L781)|PrimitiveType|Constant value that is used to filter the value list with `eq` comparison, using the same representation as property default values, see [CSDL XML, 7.2.7 Default Value](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_DefaultValue) +[InitialValueIsSignificant](Common.xml#L784) *([Experimental](Common.md#Experimental))*|Boolean|Initial value, e.g. empty string, is a valid and significant value -## [ValueListParameterConstants](Common.xml#L792): [ValueListParameter](#ValueListParameter) *([Experimental](Common.md#Experimental))* +## [ValueListParameterConstants](Common.xml#L789): [ValueListParameter](#ValueListParameter) *([Experimental](Common.md#Experimental))* Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -[Constants](Common.xml#L794)|\[PrimitiveType\]|List of constant values that are used to filter the value list with `eq` comparisons connected by `or` operators, using the same representation as property default values, see [CSDL XML, 7.2.7 Default Value](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_DefaultValue). Initial values are significant.
An empty list means a vacuous filter condition +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[Constants](Common.xml#L791)|\[PrimitiveType\]|List of constant values that are used to filter the value list with `eq` comparisons connected by `or` operators, using the same representation as property default values, see [CSDL XML, 7.2.7 Default Value](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_DefaultValue). Initial values are significant.
An empty list means a vacuous filter condition -## [ValueListParameterInOut](Common.xml#L801): [ValueListParameter](#ValueListParameter) +## [ValueListParameterInOut](Common.xml#L798): [ValueListParameter](#ValueListParameter) Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -[LocalDataProperty](Common.xml#L802)|PropertyPath|Path to property that is used to filter the value list with `startswith` comparison and filled from the picked value list item -[InitialValueIsSignificant](Common.xml#L805)|Boolean|Initial value, e.g. empty string, is a valid and significant value +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[LocalDataProperty](Common.xml#L799)|PropertyPath|Path to property that is used to filter the value list with `startswith` comparison and filled from the picked value list item +[InitialValueIsSignificant](Common.xml#L802)|Boolean|Initial value, e.g. empty string, is a valid and significant value **Applicable Annotation Terms:** - [Importance](UI.md#Importance) -## [ValueListParameterOut](Common.xml#L814): [ValueListParameter](#ValueListParameter) +## [ValueListParameterOut](Common.xml#L811): [ValueListParameter](#ValueListParameter) Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. -[LocalDataProperty](Common.xml#L815)|PropertyPath|Path to property that is filled from response +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[LocalDataProperty](Common.xml#L812)|PropertyPath|Path to property that is filled from response **Applicable Annotation Terms:** - [Importance](UI.md#Importance) -## [ValueListParameterDisplayOnly](Common.xml#L824): [ValueListParameter](#ValueListParameter) +## [ValueListParameterDisplayOnly](Common.xml#L821): [ValueListParameter](#ValueListParameter) Value list property that is not used to fill the edited entity Property|Type|Description :-------|:---|:---------- -[*ValueListProperty*](Common.xml#L770)|String|Path to property in the value list . Format is identical to PropertyPath annotations. +[*ValueListProperty*](Common.xml#L767)|String|Path to property in the value list . Format is identical to PropertyPath annotations. **Applicable Annotation Terms:** - [Importance](UI.md#Importance) -## [ValueListParameterFilterOnly](Common.xml#L832): [ValueListParameter](#ValueListParameter) *(Deprecated)* +## [ValueListParameterFilterOnly](Common.xml#L829): [ValueListParameter](#ValueListParameter) *(Deprecated)* All filterable properties of the value list can be used to filter -## [DraftRootType](Common.xml#L1052): [DraftNodeType](#DraftNodeType) +## [DraftRootType](Common.xml#L1049): [DraftNodeType](#DraftNodeType) Property|Type|Description :-------|:---|:---------- -[*PreparationAction*](Common.xml#L1094)|[QualifiedName?](#QualifiedName)|Action that prepares a draft document for later activation -[*ValidationFunction*](Common.xml#L1097) *(Deprecated)*|[QualifiedName?](#QualifiedName)|Separate validation without side-effects is not useful -[ActivationAction](Common.xml#L1053)|[QualifiedName](#QualifiedName)|Action that activates a draft document -[DiscardAction](Common.xml#L1056) *([Experimental](Common.md#Experimental))*|[QualifiedName?](#QualifiedName)|Action that discards a draft document -[EditAction](Common.xml#L1060)|[QualifiedName?](#QualifiedName)|Action that creates an edit draft -[NewAction](Common.xml#L1063)|[QualifiedName?](#QualifiedName)|Action that creates a new draft
New drafts may also be created by POSTing an empty entity without any properties to the entity set. -[AdditionalNewActions](Common.xml#L1067) *([Experimental](Common.md#Experimental))*|\[[QualifiedName](#QualifiedName)\]|Additional actions that create a new draft
Additional actions beside the default POST or standard `NewAction` that create a new draft. -[ShareAction](Common.xml#L1072)|[QualifiedName?](#QualifiedName)|Action that shares a draft document with other users
The action is bound to the draft document root node and has the following signature:
- `Users`: collection of structure with properties
  - `UserID` of type `String` and
  - `UserAccessRole` of type `String` with possible values `O` (owner, can perform all draft actions), and `E` (editor, can change the draft)
It restricts access to the listed users in their specified roles. +[*PreparationAction*](Common.xml#L1091)|[QualifiedName?](#QualifiedName)|Action that prepares a draft document for later activation +[*ValidationFunction*](Common.xml#L1094) *(Deprecated)*|[QualifiedName?](#QualifiedName)|Separate validation without side-effects is not useful +[ActivationAction](Common.xml#L1050)|[QualifiedName](#QualifiedName)|Action that activates a draft document +[DiscardAction](Common.xml#L1053) *([Experimental](Common.md#Experimental))*|[QualifiedName?](#QualifiedName)|Action that discards a draft document +[EditAction](Common.xml#L1057)|[QualifiedName?](#QualifiedName)|Action that creates an edit draft +[NewAction](Common.xml#L1060)|[QualifiedName?](#QualifiedName)|Action that creates a new draft
New drafts may also be created by POSTing an empty entity without any properties to the entity set. +[AdditionalNewActions](Common.xml#L1064) *([Experimental](Common.md#Experimental))*|\[[QualifiedName](#QualifiedName)\]|Additional actions that create a new draft
Additional actions beside the default POST or standard `NewAction` that create a new draft. +[ShareAction](Common.xml#L1069)|[QualifiedName?](#QualifiedName)|Action that shares a draft document with other users
The action is bound to the draft document root node and has the following signature:
- `Users`: collection of structure with properties
  - `UserID` of type `String` and
  - `UserAccessRole` of type `String` with possible values `O` (owner, can perform all draft actions), and `E` (editor, can change the draft)
It restricts access to the listed users in their specified roles. -## [DraftNodeType](Common.xml#L1093) +## [DraftNodeType](Common.xml#L1090) **Derived Types:** @@ -369,15 +369,15 @@ Property|Type|Description Property|Type|Description :-------|:---|:---------- -[PreparationAction](Common.xml#L1094)|[QualifiedName?](#QualifiedName)|Action that prepares a draft document for later activation -[ValidationFunction](Common.xml#L1097) *(Deprecated)*|[QualifiedName?](#QualifiedName)|Separate validation without side-effects is not useful +[PreparationAction](Common.xml#L1091)|[QualifiedName?](#QualifiedName)|Action that prepares a draft document for later activation +[ValidationFunction](Common.xml#L1094) *(Deprecated)*|[QualifiedName?](#QualifiedName)|Separate validation without side-effects is not useful -## [SimpleIdentifier](Common.xml#L1118) *(Deprecated)* +## [SimpleIdentifier](Common.xml#L1115) *(Deprecated)* Use type [Core.SimpleIdentifier](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#SimpleIdentifier) instead -## [QualifiedName](Common.xml#L1130) +## [QualifiedName](Common.xml#L1127) **Type:** String The namespace-qualified name of an OData construct in scope @@ -385,7 +385,7 @@ The namespace-qualified name of an OData construct in scope Alias-qualified names are not fully supported, and the use of namespace-qualified names is strongly recommended. -## [ActionOverload](Common.xml#L1135) +## [ActionOverload](Common.xml#L1132) **Type:** String The namespace-qualified name of an action with an optional overload @@ -395,7 +395,7 @@ The namespace-qualified name of an action, optionally followed by parentheses or by empty parentheses to identify the unbound overload, like in the `Target` attribute of an `Annotation`. -## [SideEffectsType](Common.xml#L1151) +## [SideEffectsType](Common.xml#L1148) Changes to the source properties or source entities may have side-effects on the target properties or entities. If neither TargetProperties nor TargetEntities are specified, a change to the source property values may have unforeseeable side-effects. @@ -409,35 +409,35 @@ This can also be used with OData V2 services: the annotation target is a functio Property|Type|Description :-------|:---|:---------- -[SourceProperties](Common.xml#L1163)|\[PropertyPath\]|Changes to the values of one or more of these structural properties may affect the targets -[SourceEntities](Common.xml#L1166)|\[NavigationPropertyPath\]|Changes to one or more of these entities may affect the targets. An empty path means the annotation target. -[TargetProperties](Common.xml#L1169)|\[String\]|These structural properties may be affected if the value of one of the sources changes
The syntax follows closely the syntax rules for `Edm.PropertyPath`, with the addition of `*` as the last path segment meaning all structural properties directly reached via the preceding path -[TargetEntities](Common.xml#L1173)|\[NavigationPropertyPath\]|These entities will be affected if the value of one of the sources changes. All affected entities need to be explicitly listed. An empty path means the annotation target. -[EffectTypes](Common.xml#L1176) *(Deprecated)*|[EffectType?](#EffectType)|All side effects are essentially value changes, differentiation not needed. -[TriggerAction](Common.xml#L1187)|[QualifiedName?](#QualifiedName)|Bound action to trigger side-effects after modifying an entity
Binding parameter type of the trigger action is the entity type annotated with `SideEffects`. The action does not have any additional parameters and does not return anything. It either succeeds with `204 No Content` or it fails with `4xx` or `5xx`. -[Discretionary](Common.xml#L1191) *([Experimental](Common.md#Experimental))*|Boolean|Indicates whether the client can decide if a side-effect should be triggered or not
The value of this property typically a static boolean value. It can be used by clients (e.g. by asking the end user) to decide if the side effect should be triggered or not. This indicator is only allowed in case a trigger action is given as only then the execution control of the side effect is provided to the client. +[SourceProperties](Common.xml#L1160)|\[PropertyPath\]|Changes to the values of one or more of these structural properties may affect the targets +[SourceEntities](Common.xml#L1163)|\[NavigationPropertyPath\]|Changes to one or more of these entities may affect the targets. An empty path means the annotation target. +[TargetProperties](Common.xml#L1166)|\[String\]|These structural properties may be affected if the value of one of the sources changes
The syntax follows closely the syntax rules for `Edm.PropertyPath`, with the addition of `*` as the last path segment meaning all structural properties directly reached via the preceding path +[TargetEntities](Common.xml#L1170)|\[NavigationPropertyPath\]|These entities will be affected if the value of one of the sources changes. All affected entities need to be explicitly listed. An empty path means the annotation target. +[EffectTypes](Common.xml#L1173) *(Deprecated)*|[EffectType?](#EffectType)|All side effects are essentially value changes, differentiation not needed. +[TriggerAction](Common.xml#L1184)|[QualifiedName?](#QualifiedName)|Bound action to trigger side-effects after modifying an entity
Binding parameter type of the trigger action is the entity type annotated with `SideEffects`. The action does not have any additional parameters and does not return anything. It either succeeds with `204 No Content` or it fails with `4xx` or `5xx`. +[Discretionary](Common.xml#L1188) *([Experimental](Common.md#Experimental))*|Boolean|Indicates whether the client can decide if a side-effect should be triggered or not
The value of this property typically a static boolean value. It can be used by clients (e.g. by asking the end user) to decide if the side effect should be triggered or not. This indicator is only allowed in case a trigger action is given as only then the execution control of the side effect is provided to the client. -## [EffectType](Common.xml#L1197) *(Deprecated)* +## [EffectType](Common.xml#L1194) *(Deprecated)* All side effects are essentially value changes, differentiation not needed. -## [SortOrderType](Common.xml#L1322) +## [SortOrderType](Common.xml#L1319) Exactly one of `Property`, `DynamicProperty` and `Expression` must be present Property|Type|Description :-------|:---|:---------- -[Property](Common.xml#L1324)|PropertyPath?|Sort property -[DynamicProperty](Common.xml#L1336)|AnnotationPath?|Dynamic property introduced by an annotation and used as sort property
If the annotation referenced by the annotation path does not apply to the same collection of entities as the one being sorted according to the [`UI.PresentationVariant`](UI.md#PresentationVariant) or `Common.SortOrder` annotation, this instance of `UI.PresentationVariant/SortOrder` or `Common.SortOrder` MUST be silently ignored.
Allowed terms: -[Expression](Common.xml#L1350) *([Experimental](Common.md#Experimental))*|PrimitiveType?|Dynamic expression whose primitive result value is used to sort the instances -[Descending](Common.xml#L1354)|Boolean?|Sort direction, ascending if not specified otherwise +[Property](Common.xml#L1321)|PropertyPath?|Sort property +[DynamicProperty](Common.xml#L1333)|AnnotationPath?|Dynamic property introduced by an annotation and used as sort property
If the annotation referenced by the annotation path does not apply to the same collection of entities as the one being sorted according to the [`UI.PresentationVariant`](UI.md#PresentationVariant) or `Common.SortOrder` annotation, this instance of `UI.PresentationVariant/SortOrder` or `Common.SortOrder` MUST be silently ignored.
Allowed terms: +[Expression](Common.xml#L1347) *([Experimental](Common.md#Experimental))*|PrimitiveType?|Dynamic expression whose primitive result value is used to sort the instances +[Descending](Common.xml#L1351)|Boolean?|Sort direction, ascending if not specified otherwise -## [RecursiveHierarchyType](Common.xml#L1387) *(Deprecated)* +## [RecursiveHierarchyType](Common.xml#L1384) *(Deprecated)* Use terms [Aggregation.RecursiveHierarchy](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Aggregation.V1.md#RecursiveHierarchy) and [Hierarchy.RecursiveHierarchy](https://github.com/SAP/odata-vocabularies/blob/main/vocabularies/Hierarchy.md#RecursiveHierarchy) instead -## [UserID](Common.xml#L1438) +## [UserID](Common.xml#L1435) **Type:** String User ID diff --git a/vocabularies/Common.xml b/vocabularies/Common.xml index e5253471..554c4859 100644 --- a/vocabularies/Common.xml +++ b/vocabularies/Common.xml @@ -218,15 +218,12 @@ - - - - - - - + + + Multiple secondary keys are possible using different qualifiers. + Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), + secondary keys cannot be used to address an entity in a resource path. - From f672425fc2cd8f84161bda84b0751f4db1f11144 Mon Sep 17 00:00:00 2001 From: Ralf Handl Date: Wed, 25 Sep 2024 09:54:43 +0200 Subject: [PATCH 2/3] Update vocabularies/Common.xml --- vocabularies/Common.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vocabularies/Common.xml b/vocabularies/Common.xml index 554c4859..74d1962d 100644 --- a/vocabularies/Common.xml +++ b/vocabularies/Common.xml @@ -222,7 +222,7 @@ Multiple secondary keys are possible using different qualifiers. Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), - secondary keys cannot be used to address an entity in a resource path. + secondary keys need not support addressing an entity in a resource path. From 559f49f283c9e42b40bc08059c8c99f3c5e96211 Mon Sep 17 00:00:00 2001 From: ralfhandl Date: Wed, 25 Sep 2024 07:55:30 +0000 Subject: [PATCH 3/3] auto-refreshed --- vocabularies/Common.json | 2 +- vocabularies/Common.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/vocabularies/Common.json b/vocabularies/Common.json index 57e01e94..2bfb0ddc 100644 --- a/vocabularies/Common.json +++ b/vocabularies/Common.json @@ -173,7 +173,7 @@ "$Type": "Edm.PropertyPath", "$AppliesTo": ["EntityType"], "@Core.Description": "The listed properties form a secondary key", - "@Core.LongDescription": "Multiple secondary keys are possible using different qualifiers.\n Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys),\n secondary keys cannot be used to address an entity in a resource path." + "@Core.LongDescription": "Multiple secondary keys are possible using different qualifiers.\n Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys),\n secondary keys need not support addressing an entity in a resource path." }, "MinOccurs": { "$Kind": "Term", diff --git a/vocabularies/Common.md b/vocabularies/Common.md index 1ec2390a..a34e3f0a 100644 --- a/vocabularies/Common.md +++ b/vocabularies/Common.md @@ -27,7 +27,7 @@ Term|Type|Description [IsUnit](Common.xml#L205)|[Tag](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#Tag)|Annotated property or parameter is a unit of measure [UnitSpecificScale](Common.xml#L209)|PrimitiveType|The number of fractional decimal digits of a currency amount or measured quantity
The annotated property contains a currency code or unit of measure, and the annotation value specifies the default scale of numeric values with that currency code or unit of measure. Can be used in e.g. a list of available currency codes or units of measure, or a list of measuring devices to specify the number of fractional digits captured by that device. [UnitSpecificPrecision](Common.xml#L214) *([Experimental](Common.md#Experimental))*|PrimitiveType|The number of significant decimal digits of a currency amount or measured quantity
The annotated property contains a currency code or unit of measure, and the annotation value specifies the default precision of numeric values with that currency code or unit of measure. Can be used in e.g. a list of available currency codes or units of measure, or a list of measuring devices to specify the number of significant digits captured by that device. -[SecondaryKey](Common.xml#L220)|\[PropertyPath\]|The listed properties form a secondary key
Multiple secondary keys are possible using different qualifiers. Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), secondary keys cannot be used to address an entity in a resource path. +[SecondaryKey](Common.xml#L220)|\[PropertyPath\]|The listed properties form a secondary key
Multiple secondary keys are possible using different qualifiers. Unlike [`Core.AlternateKeys`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#AlternateKeys), secondary keys need not support addressing an entity in a resource path. [MinOccurs](Common.xml#L229)|Int64|The annotated set or collection contains at least this number of items [MaxOccurs](Common.xml#L233)|Int64|The annotated set or collection contains at most this number of items [AssociationEntity](Common.xml#L237)|\[NavigationPropertyPath\]|Entity representing an n:m association with attributes