RS:valueLine valueTable: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [checked revision] |
m (Creation) |
m (Change to template) |
||
| Line 1: | Line 1: | ||
{{elementDocu| | |||
= | elementName = valueLine | ||
|semantics = | |||
The element {{RS:Tag|valueLine}} is part of the complex construction of a {{RS:Tag|valueTable}}. Please refer to {{RS:Doc|valueTable}} for details. | |||
{{deu|Das element {{RS:Tag|valueLine}} ist Bestandteil der komplexen Struktur der {{RS:Tag|valueTable}}. Details sind unter {{RS:Doc|valueTable}} zu finden.}} | |||
: | |||
|parent = | |||
{{RS:Doc|valueTable}} | |||
= | |childs = | ||
{{RS:Doc|values}} | |||
: | |||
|ownAttributes = | |||
* {{attr|xValue}}: This is the value of the x-ccordinate for this line in the {{RS:Tag|valueTable}}. | |||
|constraints = | |||
The element is mandatory if the parent {{RS:Doc|valueTable}} is used. Per {{RS:Doc|valueTable}} the occurance is unlimited, i.e. there is one instance of {{RS:Doc|valueLine}} for each value of the x-coordinate. Subsequently the attribute {{attr|xValue}} is mandatory as well. It also requests an unlimted number of child elements of {{RS:Doc|values}} for the related values of the y-coordinate. | |||
|backHome = RS:elements | |||
}} | |||
Revision as of 17:41, 2 June 2009
valueLine
Schema description / Schemenbeschreibung
Position of valueLine in the XML-Tree / Position von valueLine im XML-Baum
- Parent: valueTable
- Children: values
Multiplicity / Anzahl
Semantics / Bedeutung
The element <valueLine> is part of the complex construction of a <valueTable>. Please refer to valueTable for details.
Das element <valueLine> ist Bestandteil der komplexen Struktur der <valueTable>. Details sind unter valueTable zu finden.
Attributes of valueLine / Attribute von valueLine
- xValue: This is the value of the x-ccordinate for this line in the <valueTable>.
Syntactic Constraints / Syntaktische Beschränkungen
The element is mandatory if the parent valueTable is used. Per valueTable the occurance is unlimited, i.e. there is one instance of valueLine for each value of the x-coordinate. Subsequently the attribute xValue is mandatory as well. It also requests an unlimted number of child elements of values for the related values of the y-coordinate.
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.