Autoexport from the XML-Schema for element generic:name of railML ® version 3.2 |
| Documentation
|
Established, human-readable short string in natural language, giving the object a name. Not intended for machine interpretation.
|
| Subschema
|
generic
|
| Parents*
|
alternative,
announcement,
approvedBy,
areaElementProjection,
balise,
baliseGroup,
border,
bufferStop,
category,
checkedBy,
commercialTrain,
concessionaire,
contractor,
crossesElement,
crossing,
customer,
derailerIS,
detector,
electrificationSection,
elementState,
ellipticalProjection,
etcsArea,
etcsLevelTransition,
genericArea,
geometricPositioningSystem,
geometryPoint,
gradientCurve,
hasHmiIndication,
hasOperatorCommand,
holiday,
horizontalCurve,
infrastructureManager,
infrastructureState,
infrastructureVisualization,
keeper,
keyLockIS,
levelCrossingIS,
line,
linearElementProjection,
linearPositioningSystem,
loadingGauge,
manufacturer,
mediaCategory,
mileageChange,
netElement,
netRelation,
network,
networkResource,
operationalPoint,
operationalTrain,
operationalUndertaking,
operator,
organizationalUnit,
overCrossing,
owner,
passengerTextInfo,
phase,
platform,
platformEdge,
project,
radioBlockCentreBorder,
railwayUndertaking,
reserve,
restrictionArea,
revisedBy,
revision,
screenPositioningSystem,
serviceSection,
signalIS,
speedProfile,
speedSection,
spotElementProjection,
stoppingPlace,
switchIS,
timetableScenario,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
transportService,
tunnelGateIS,
underCrossing,
usesSymbol,
validity,
vehicleManufacturer,
vehicleOperator,
weightLimit
|
| Children
|
None
|
Attributes:
- description: should be interpreted in its elements' context, substantiates the name (optional;
xs:string),
- name: should be interpreted in its elements' context (e.g. signal/name, vehicle/name) (obligatory;
xs:string)
|
*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.
|