...
| 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?
|
...
The metadata structure of object types has to be defined in the schema. In this definition, properties are selected referenced that should be connected to the object type. Each property is in turn defined in the schema by the specification of its attributes. The properties can be selected referenced or not selected referenced in object type definitions, but their attributes are fixed and can not be modified. There required attribute is the only exception as it can be overwritten by a propertyReference in object type definitions. This makes it possible to decide for each property individually whether it is required in every single object type definition or not. Since schema structures can even be changed at runtime, yuuvis® Momentum offers a high flexibility in terms of document lifecycle management.
...
| Code Block |
|---|
| language | yml |
|---|
| title | Overwriting of the required attribute by object type definition |
|---|
| linenumbers | true |
|---|
|
<propertyStringDefinition>
<id>editor</id>
<propertyType>string</propertyType>
<cardinality>single</cardinality>
<required>true</required>
</propertyStringDefinition>
<typeDocumentDefinition>
<id>imported1</id>
<baseId>system:document</baseId>
<propertyReference required="false">editor</propertyReference>
<contentStreamAllowed>allowed</contentStreamAllowed>
</typeDocumentDefinition> |
...
| Code Block |
|---|
| language | yml |
|---|
| title | Overwriting of the required attribute by secondary object type definition |
|---|
| linenumbers | true |
|---|
|
<propertyStringDefinition>
<id>editor</id>
<propertyType>string</propertyType>
<cardinality>single</cardinality>
<required>true</required>
</propertyStringDefinition>
<typeDocumentDefinition>
<id>imported2</id>
<baseId>system:document</baseId>
<contentStreamAllowed>allowed</contentStreamAllowed>
<secondaryObjectTypeId static="false">noeditor</secondaryObjectTypeId>
</typeDocumentDefinition>
<typeSecondaryDefinition>
<id>noeditor</id>
<baseId>system:secondary</baseId>
<propertyReference required="false">editor</propertyReference>
</typeSecondaryDefinition> |
...
| Code Block |
|---|
| language | yml |
|---|
| title | Object type definition and secondary object type definitions |
|---|
| linenumbers | true |
|---|
|
<propertyStringDefinition>
<id>editor</id>
<propertyType>string</propertyType>
<cardinality>single</cardinality>
<required>true</required>
</propertyStringDefinition>
<typeDocumentDefinition>
<id>imported3</id>
<baseId>system:document</baseId>
<propertyReference required="false">editor</propertyReference>
<contentStreamAllowed>allowed</contentStreamAllowed>
<secondaryObjectTypeId static="false">noeditor</secondaryObjectTypeId>
<secondaryObjectTypeId static="false">witheditor</secondaryObjectTypeId>
</typeDocumentDefinition>
<typeSecondaryDefinition>
<id>noeditor</id>
<baseId>system:secondary</baseId>
<propertyReference required="false">editor</propertyReference>
</typeSecondaryDefinition>
<typeSecondaryDefinition>
<id>witheditor</id>
<baseId>system:secondary</baseId>
<propertyReference>editor</propertyReference>
</typeSecondaryDefinition> |
The definition of the secondary object type noeditor overwrites the required attribute of the editor property to false. This value equals the specification in the imported3 object type definition. In contrast, the definition of witheditor includes the editor property by means of a propertyReference but does not explicitly specify a value for the required attribute. This means that the value true from the property definition will be used for witheditor.
...