...
| Page Properties |
|---|
|
| Status | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | progress |
|---|
|
|
|---|
| Priority |
|
|---|
| Note |
|
|---|
| Assignee | Antje |
|---|
Resources- Antje: page created as a copy of the schema tutorial
- Inga - Review
- Überschriften für Tutorials sind aktiv formuliert - was mache ich ... Using property definitions several times | Overwriting property attribute "required"
- Einsortieren würde ich erst einmal vor dem Tagging in der Navigation
- "property type" (e.g. integer / date / string) vs. "property definition"
- "object type" vs "object type definitions" - siehe z.B. im excerpt
- defined properties are "referenced" in an object type definition vs. "selected"
- Heading "Overwriting by a Secondary Object Type Definition" - An alternative possibility is the usage of a secondary object type on which the object type definition can be based. => verstehe den Satz nicht - was meint hier "based" - "enhanced" und nicht die OTdefinition, sondern die Instanz selbst ...
- "non-static" vs. "floating" - wenn dies dann zur Laufzeit oder direkt beim Import hinzugefügt wird ... fehlt mir noch als Info in dem Absatz
- Ich fände es gut, wie property definition mit in jedem Beispiel aufzuführen - damit der Initalwert sichtbarer ist - sind zwar 6 Zeilen aber wäre mir leichter gefallen zu lesen
- Heading "Handling of Multiple Property References"
- specifying ... es wird nur das Attribut genannt - wäre es nicht sinnvoll dies mit
propertyreference zu erwähnen - CODE - zweiter SOT ist ohne attribute - ist das richtig so? / initial ist es ebenfalls auf
false gesetzt - wird dann überschrieben?
|
...
| Excerpt |
|---|
This tutorial shows how to use reference the same property type definition in different object typestype definitions, in some of them as a required property type and in others as a non-required property type. |
| Section |
|---|
|
| Column |
|---|
Table of Contents| Table of Contents |
|---|
| maxLevel | 3 |
|---|
| exclude | (Table of Contents|Read on|Another Tutorial|Another Concept Article|Another interesting Tutorial|Managing the Schema|Schema - Defining Object Types|DMS Endpoints) |
|---|
|
|
|
...
An alternative possibility is using a to reference a property in an object type definition is to include a floating secondary object type on which . Also in the secondary object type definition can be based. Also, a propertyReference can be used to set a value for the required attribute for a property in the definition of the secondary object type. The required attribute value specified in the original property definition is again overwritten.
In the example code below, the editor property is not included directly in the imported2 document type definition. But it is based on the non-static (floating) secondary object type noeditor. The definition of noeditor uses the editor property and sets its required attribute to false by means of a propertyReference. Thus, for objects of the type imported2, the editor property will be available and optional.
...
In an object type definition, it is possible to set a value for the required attribute of a property, and additionally include multiple secondary object types specifying the required attribute for the same property as well. If at least one definition implies required=true, this attribute will be true for every object of the corresponding type. The value true dominates over false regardless of the location of the propertyReference.
...