The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Introduction
Documentation
Unfortunately see the documentation of <IS:point> and its attributes directly in the corresponding UML diagram (link to the railML® website).
Syntax
Autoexport from the XML-Schema for element IS:point of railML ® version 3.2 |
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
infrastructure
|
| Parents*
|
gmlLocations
|
| Children
|
description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)
|
Attributes:
- srsDimension: This attribute is not documented in the schema! (optional;
xs:positiveInteger),
- srsName: This attribute is not documented in the schema! (optional;
xs:anyURI),
- id: This attribute is not documented in the schema! (optional;
xs:ID); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Autoexport from the XML-Schema for element IS:point of railML ® version 3.1 |
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
infrastructure
|
| Parents*
|
gmlLocations
|
| Children
|
description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)
|
Attributes:
- srsDimension: This attribute is not documented in the schema! (optional;
xs:positiveInteger),
- srsName: This attribute is not documented in the schema! (optional;
xs:anyURI),
- id: This attribute is not documented in the schema! (optional;
xs:ID); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues