112.6. The toplevel element netex:ServiceCalendar

netex:ServiceCalendar

netex:ServiceCalendar_VersionStructure

Type for ENTITY.

The element content starts with items inherited from the base type:

@nameOfClass

1:1

netex:NameOfClass

Name of Class of the ENTITY. Allows reflection. Fixed for each ENTITY type.

@id

1:1

netex:ObjectIdType

Identifier of ENTITY.

@dataSourceRef

1:1

netex:DataSourceIdType

Name of source of the data.

@created

1:1

xs:dateTime

Date ENTITY was first created.

@changed

1:1

xs:dateTime

Date ENTITY or version was last changed.

@modification

1:1

netex:ModificationEnumeration

Nature of last modification: new, revise, delete, unchanged, delta. Default is "new".

@version

1:1

netex:VersionIdType

Version number of entity. The value may be "any" or a VERSION number adhering to agreed-upon formatting and interpretation rules (representing, e.g., a number or a date). Consecutive VERSION numbers should be strictly increasing.

@status

1:1

netex:StatusEnumeration

Whether ENTITY is currently in use. Default is "active".

@derivedFromVersionRef

1:1

netex:VersionIdType

Version of this object from which this version of ENTITY was derived.

@compatibleWithVersionFrameVersionRef

1:1

netex:VersionIdType

Version of frame from with which this version of ENTITY is compatible. Assumes Frame of the same Id as current frame.

@derivedFromObjectRef

1:1

netex:ObjectIdType

Identity of object from which this object of ENTITY was derived. Normally the same.

@responsibilitySetRef

1:1

netex:ResponsibilitySetIdType

Reference to RESPONSIBILITY SET for managing the object. If absent, then responsibility is same as for containing context of this object.

Base type content is restricted, resulting in the following own content:

@id

1:1

netex:ServiceCalendarIdType

The element contains none or one of the following elements (a-b)

netex:EntityInVersionGroup

a

netex:validityConditions

-1:1

+netex:validityConditions_RelStructure

VALIDITY CONDITIONs conditioning entity.

b

→‍netex:ValidBetween

-1:*

+local-type: typedef-353.5

OPTIMISATION. Simple version of a VALIDITY CONDITION. Comprises a simple period. NO UNIQUENESS CONSTRAINT.

netex:alternativeTexts

0:1

+netex:alternativeTexts_RelStructure

Additional Translations of text elements.

netex:DataManagedObjectGroup

→‍netex:keyList

0:1

+netex:KeyListStructure

A list of alternative Key values for an element.

→‍netex:privateCodes

0:1

+netex:PrivateCodesStructure

A list of private codes that uniquely identifiy the element. May be used for inter-operating with other (legacy) systems. +v2.0

→‍netex:Extensions

0:1

+netex:ExtensionsStructure

User defined Extensions to ENTITY in schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

→‍netex:BrandingRef

0:1

>netex:BrandingRefStructure

Reference to a BRANDING.

netex:ServiceCalendarGroup

netex:Name

0:1

+netex:MultilingualString

Name of SERVIC CALENDAR.

netex:ShortName

0:1

+netex:MultilingualString

Short Name of SERVIC CALENDAR.

netex:FromDate

0:1

xs:date

Start date of Calendar.

netex:ToDate

0:1

xs:date

End date of SERVICE CALENDAR. Date is INCLUSIVE.

netex:DayTimesGroup

netex:EarliestTime

0:1

xs:time

Earliest time that day starts. Default is 00:00

netex:DayLength

0:1

xs:duration

Length of day. Used to work out latest time that day runs to. Default is 24hourse.

netex:ServiceCalendarContentGroup

netex:dayTypes

0:1

+netex:dayTypes_RelStructure

Reusable DAY TYPE used in calendar.

netex:timebands

0:1

+netex:timebands_RelStructure

Reusable Time bands used in calendar.

netex:operatingDays

0:1

+netex:operatingDays_RelStructure

Days found in Calendar between start and end date. Dates must fall between the start and end date of the calendar. There is a day for every date in the calendar validity period. Days do not have to be explicitly declared if there is no additional information.

netex:operatingPeriods

0:1

+netex:operatingPeriods_RelStructure

OPERATING PERIODs belonging to calendar. Named periods. Must fall within the overall validity period of the calendar.

netex:dayTypeAssignments

0:1

+netex:dayTypeAssignments_RelStructure

Assignments of DAY TYPEs to specific OPERATING DAYs. The same DAY TYPE may be assigned to multiple Operating dates, and vice versa.