Skip to content

Constraint bugs #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Aurige wants to merge 2 commits into from
Closed

Constraint bugs #49

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
222eb63
Merge pull request #1 from NeTEx-CEN/master
Aurige Feb 20, 2019
8f49665
Addition of missing reference in constraint key
Aurige Feb 22, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 19 additions & 8 deletions xsd/NeTEx_publication.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,32 +16,43 @@
<Contributor>CEN TC278 WG3 SG9 Team.</Contributor>
<Coverage>Europe</Coverage>
<Creator>First Drafted for NeTEx version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@netex.org.uk</Creator>
<Date><Modified>2017-08-10</Modified>Rename PassengerContractEvent to PassengerContractEntry
<Date>
<Modified>2017-08-10</Modified>Rename PassengerContractEvent to PassengerContractEntry
Add constraints for CustomerPurchasePackage, CustomerPurchasePackageElement, CustomerPurchaseParameterAssignment
Add constraints for CustomerAccount, CustomerAccountStatus, TypeOf CustomerAccount,
Add constraints for CustomerEligibility, UserProfileEligibility, CommercialProfileEligibility, ResidentialQualifactionEligibility
</Date>
<Date><Modified>2017-06-29</Modified>CR048 add constraints WHITE LIST
<Date>
<Modified>2017-06-29</Modified>CR048 add constraints WHITE LIST
Fix: Add Constraint on CUSTOMER
CR00310 add constraints on JOURNEY PART POSITION
</Date>
<Date><Modified>2017-05-09</Modified>Correct COnstraints for PointOnRoute
<Date>
<Modified>2017-05-09</Modified>Correct COnstraints for PointOnRoute
Add Missing Constraints For CommonSectionMember / PointOnSection and LinkOnSection er
Add Missing Constraints For GroupOfServicesMember , JourneyAccounting DelegatedResponsibilitySet
Reinstate Constraints for CAll
Fix constraints that were missing namespace on subpart
</Date>
<Date><Modified>2017-03-27</Modified>Various 1.1 changes see CRS.
<Date>
<Modified>2017-03-27</Modified>Various 1.1 changes see CRS.
CR0038 revise constraints on ResponsibilityRole </Date>
<Date><Modified>2011-01-17</Modified>V0.94 <!-- Revised--></Date>
<Date>
<Modified>2011-01-17</Modified>V0.94 <!-- Revised-->
</Date>
<Date>
<Created>2010-09-04</Created>
<!-- Created from Siri.xsd -->
</Date>
<Description><p>netex Xml is an XML representation of the Transmodel model that can be used to exchange data objects between netex databases and other services.</p>.
<Description>
<p>netex Xml is an XML representation of the Transmodel model that can be used to exchange data objects between netex databases and other services.</p>.
<p> The same netex Xml of netex data objects can be used both in fine grained protocols that exchange one or more objects at a time, such as the SIRI based netex Xml web service, and in bulk publication exchange formats used to exchange whole data sets. </p>
<p>This netex Publication exchange XML schema defines a bulk delivery format to exchange netex objects as an XML document. (It has no dependency on SIRI).
<ul><li>For each data object type it describes an XML representation which can be used to exchange netex data.</li><li>It also describes filters to describe requests for publishing data. These can be used both to configure the publication, and to describe the contents of the published document, for example all Network Objects, or all current traffic events.</li><li>A particular use of the netex Publication Exchange format is to publish data from a NeTEx system: at regular intervals as an Xml document which can be transmitted to other systems by FTP or other communication transport means. </li></ul>
<ul>
<li>For each data object type it describes an XML representation which can be used to exchange netex data.</li>
<li>It also describes filters to describe requests for publishing data. These can be used both to configure the publication, and to describe the contents of the published document, for example all Network Objects, or all current traffic events.</li>
<li>A particular use of the netex Publication Exchange format is to publish data from a NeTEx system: at regular intervals as an Xml document which can be transmitted to other systems by FTP or other communication transport means. </li>
</ul>
</p>
</Description>
<Format>
Expand Down Expand Up @@ -1208,7 +1219,7 @@ Provides a general purpose wrapper for NeTEx data content.</xsd:documentation>
<xsd:field xpath="@version"/>
</xsd:keyref>
<xsd:key name="Place_AnyVersionedKey">
<xsd:selector xpath=".//netex:Place | .//netex:TopographicPlace | .//netex:RoadAddress | .//netex:PostalAddress | .//netex:Garage | .//netex:StopPlace | .//netex:Quay | .//netex:BoardingPosition | .//netex:AccessSpace | .//netex:StopPlaceEntrance | .//netex:FlexibleStopPlace | .//netex:FlexibleArea | .//netex:HailAndRideArea | .//netex:PointOfInterest | .//netex:PointOfInterestSpace | .//netex:PointOfInterestEntrance | .//netex:PathJunction | .//netex:SiteEntrance | .//netex:Parking | .//netex:ParkingBay | .//netex:ParkingArea | .//netex:VehicleStoppingPlace"/>
<xsd:selector xpath=".//netex:Place | .//netex:TopographicPlace | .//netex:RoadAddress | .//netex:PostalAddress | .//netex:Garage | .//netex:StopPlace | .//netex:Quay | .//netex:BoardingPosition | .//netex:AccessSpace | .//netex:EquipmentPlace | .//netex:StopPlaceEntrance | .//netex:FlexibleStopPlace | .//netex:FlexibleArea | .//netex:HailAndRideArea | .//netex:PointOfInterest | .//netex:PointOfInterestSpace | .//netex:PointOfInterestEntrance | .//netex:PathJunction | .//netex:SiteEntrance | .//netex:Parking | .//netex:ParkingBay | .//netex:ParkingArea | .//netex:VehicleStoppingPlace "/>
<xsd:field xpath="@id"/>
<xsd:field xpath="@version"/>
</xsd:key>
Expand Down