Skip to content

Commit

Permalink
Change "Unable" to "Unusable"
Browse files Browse the repository at this point in the history
  • Loading branch information
@sgrossberndt
sgrossberndt committed Nov 11, 2020
1 parent aea0113 commit 1cacd36
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions OJP_Trips.xsd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -929,7 +929,7 @@
</xs:group>
<xs:group name="TripStatusGroup">
<xs:annotation>
<xs:documentation>parameters which describe the current status of a TRIP</xs:documentation>
<xs:documentation>Parameters which describe the current status of a TRIP</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Unplanned" type="xs:boolean" default="false" minOccurs="0">
Expand All @@ -952,7 +952,7 @@
<xs:documentation>Whether this trip is delayed. Default is false.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Unable" type="xs:boolean" default="false" minOccurs="0">
<xs:element name="Unusable" type="xs:boolean" default="false" minOccurs="0">

This comment has been minimized.

Sign in to view

Copy link
@skinkie

skinkie Nov 16, 2020

Contributor

I would personally prefer something like unfeasible if we change this.

This comment has been minimized.

Sign in to view

Copy link
@sgrossberndt

sgrossberndt Nov 16, 2020

Author Contributor

I'd prefer infeasible then:

https://english.stackexchange.com/questions/207115/what-is-the-difference-between-unfeasible-and-infeasible

Unfeasible vs Infeasible

This comment has been minimized.

Sign in to view

Copy link
@skinkie

skinkie Nov 16, 2020

Contributor

I see what you did there. I was at the same page! :D
<xs:annotation>
<xs:documentation>Whether this trip cannot be used, due to operational delays and impossible transfers. Default is false.</xs:documentation>
</xs:annotation>
Expand Down

0 comments on commit 1cacd36

Please sign in to comment.