untitled

Online "Book Flights" facility for an airline

As we begin Part 8, we have:

a rule taxonomy,
some rule statement templates and sub-templates for generating rule statements of each type,
metarules defining which template is used for each rule type and how,
a set of rule statements, and
the fact types the rule statements are based on.

Rule Taxonomy

Cardinality rules: data must be present or absent, and/or is restricted in terms of the number of instances.

Mandatory data rules: one or more data items are required in a particular context.

Mandatory data item rules: a particular single data item must be present.
Mandatory option selection rules: one of a set of pre-defined options must be specified.
Mandatory group rules: at least one of a group of data items must be present.

Prohibited data rules: a particular data item is not allowed in a particular context.
Singular data rules: only one instance of a particular data item is allowed in a particular context.
Dependent cardinality rules: the number of instances of a data item depends on some other data, as in rule statement RS25.

Data content rules: data is constrained to certain values.

Value set rules: a data item (or combination of data items) must have a value from a discrete set.
Match rules: a data item must be the same as or different to some other data item.
Range rules: a data item must have a value from within a continuous range.
Uniqueness constraints: a data item (or combination of data items) must be different from other instances of the same data item.

Rule Statement Templates

RT15.	{{The\|Each} <term 1> {(if any)\|} that <verb phrase 1>\|} each <term 2> {<qualifying clause>\|} must <verb phrase 2> <cardinality> <term 3> {<preposition> {each\|the} <term 4>\|} {{if\|unless} <conditional clause>\|}.
		(from which rule statements RS8, RS9, RS12 to RS17, RS40 to RS47, RS53, RS54, and RS61 to RS63 can be generated)
RT16.	Each <term 1> {<qualifying clause>\|} must {({if\|unless} <conditional clause>)\|} specify whether {{or not\|} {it\|the <term 2>} <verb phrase 1> {<article> <term 3>\|}\| {it\|the <term 4>} <verb phrase 2> <or-list>}.
		(from which rule statements RS26 to RS29 can be generated)
RT17.	Each <term 1> {<qualifying clause>\|} must <verb phrase> {a\|an} <term 2>, {a\|an} <term 3> or both {{if\|unless} <conditional clause>\|}.
		(from which rule statement RS30 can be generated)
RT18.	Each <term 1> {<qualifying clause>\|} must <verb phrase> {a\|an} <term 2> or {a\|an} <term 3> but not both {{if\|unless} <conditional clause>\|}.
		(from which rule statement RS31 can be generated)
RT19.	Each <term 1> {<qualifying clause>\|} must {({if\|unless} <conditional clause>)\|} <verb phrase> <cardinality> of the following: <or-list>.
		(from which rule statements RS32, RS34, and RS35 can be generated)
RT20.	{A\|An} <term 1> {<qualifying clause>\|} must not <verb phrase> {a\|an} <term 2> {{if\|unless} <conditional clause>\|}.
		(from which rule statement RS11 can be generated)
RT21.	The <term 1> {<qualifying clause>\|} {(if any)\|} that <verb phrase> each <term 2> {<qualifying clause>\|} must be <predicate> {{if\|unless} <conditional clause>\|}.
		(from which rule statements RS19, RS21 to RS24, RS38, RS39, and RS55 can be generated)
RT22.	The combination of <simple and-list> {<qualifying clause>\|} {(if any)\|} that <verb phrase> each <term 2> {<qualifying clause>\|} must be <combination predicate> {{if\|unless} <conditional clause>\|}.
		(from which rule statements RS56 and RS60 can be generated)
RT23.	The <set function> of {the\|} <term 1> that <verb phrase> each <term 2> must be <predicate> {{if\|unless} <conditional clause>\|}.
		(from which rule statement RS25 can be generated)

Rule Statement Sub-templates

ST1.	<cardinality> ::=
		{exactly\|at {least\|most}\|at least <positive integer> and at most} <positive integer>
ST19.	<predicate> ::=
		{<value set predicate>\|<match predicate>\|<range predicate>\| <equality predicate>\|<uniqueness predicate>}
ST3.	<value set predicate> ::=
		one of the <term> {<qualifying clause>\|}
			(used in rule statements RS21 and RS22)
ST4.	<match predicate> ::=
		{the same as\|different to} the <term> {<qualifying clause>\|}
			(used in rule statement RS23)
ST16.	<range predicate> ::=
		{<time range predicate>\|<non-time range predicate>}
ST17.	<time range predicate> ::=
		{no\|} {later\|earlier} than {<literal>\| {<literal> {after\|before}\|} the <term> {<qualifying clause>\|}}
			(used in rule statements RS19 and RS20)
ST18.	<non-time range predicate> ::=
		{{no\|} {more\|less} than} <literal>\| {{no\|} {more\|less} than\|at {least\|most} <literal> more than} the <term> {<qualifying clause>\|}}
			(used in rule statement RS24)
ST9.	<equality predicate> ::=
		{not\|} equal to {<literal>\|the <term> {<qualifying clause>\|}}
			(used in rule statement RS25)
ST20.	<uniqueness predicate> ::=
		different to the <term 1> that <verb phrase> each other <term 2> {<qualifying clause>\|}
			(used in rule statement RS55)
ST31.	<qualifying clause> ::= {that\|who}<condition>
ST7.	<set function> ::=
		{number\|total\|maximum\|minimum\| average\|mean\|median\|mode}
ST11.	<article> ::= {a\|an\|the}
ST15.	<or-list> ::= {<simple or-list>\|<complex or-list>}
ST12.	<simple or-list> ::=
		{<article> <term 1> or <article> <term 2>\| <article> <term 3>, <simple or-list>}
ST14.	<complex or-list> ::=
		• <article> <term 1>\|<simple and-list>}; or {• <article> <term 1>\|<simple and-list>}\|<complex or-list>}
ST13.	<simple and-list> ::=
		{<article> <term 1> and <article> <term 2>\| <article> <term 3>, <simple and-list>}
ST21.	<combination predicate> ::=
		{<combination value set predicate>\| <combination uniqueness predicate>}
ST22.	<combination value set predicate> ::=
		one of the combinations of <simple and-list> {<qualifying clause>\|}
			(used in rule statement RS60)
ST23.	<combination uniqueness predicate> ::=
		different to the combination of <simple and-list> that <verb phrase> each other <term> {<qualifying clause>\|}
			(used in rule statement RS56)
ST24.	<conditional clause> ::=
		{<simple conditional clause>\|<and-conditional clause>\| <or-conditional clause>}
ST25.	<simple conditional clause> ::=
		<condition subject> <condition>
ST26.	<and-conditional clause> ::=
		<simple conditional clause> and {<simple conditional clause>\|<and-conditional clause>}
ST27.	<or-conditional clause> ::=
		<simple conditional clause> or {<simple conditional clause>\|<or-conditional clause>}
ST28.	<condition subject> ::=
		{the\|that\|any\|every} <term> {<qualifying clause>\|>}
ST29.	<condition> ::=
		{<verb phrase> {{<article>\|each\|that} <term> {<qualifying clause>\|}\|}\| is <predicate>}

Metarules

Rule type	Template	Metarules
Mandatory data item rule	RT15	<cardinality> ::= {exactly <positive integer>\| at least <positive integer> {and at most <positive integer>\|}}
Mandatory option selection rule	RT16
Mandatory group rule	RT17	if either or both of 2 items in the group
	RT18	if only 1 of 2 items in the group
	RT19	if more than 2 items in the group
Prohibited data rule	RT20
Singular data rule	RT15	<cardinality> ::= {exactly\|at most} one
Dependent cardinality rule	RT23	<set function> ::= number
Value set rule	RT21	<predicate> ::= <value predicate> if only 1 data item
Value set rule	RT22	<combination predicate> ::= <combination value set predicate> if combination of data items
Match rule	RT21	<predicate> ::= <match predicate>
Range rule	RT21	<predicate> ::= <range predicate>
Uniqueness constraint	RT21	<predicate> ::= <uniqueness predicate> if only 1 data item
Uniqueness constraint	RT22	<combination predicate> ::= <combination uniqueness predicate> if combination of data items

Rule Statements

RS8.	Each flight booking request must specify exactly one departure date.
RS9.	Each flight booking request for a return journey must specify exactly one return date.
RS11.	A flight booking request for a one-way journey must not specify a return date.
RS12.	Each flight booking request must specify exactly one origin city.
RS13.	Each flight booking request must specify exactly one destination city.
RS14.	Each flight booking request must specify exactly one number of passengers.
RS15.	Each flight booking request must specify at most one frequent flier membership.
RS16.	Each flight booking confirmation must specify at least one passenger name.
RS17.	Each flight booking confirmation must specify exactly one payment arrangement.
RS19.	The departure date specified by each flight booking request must be no earlier than today.
RS20.	The return date (if any) specified by each flight booking request must be no earlier than the departure date specified by that flight booking request.
RS21.	The origin city specified by each flight booking request must be one of the cities served by the airline.
RS22.	The destination city specified by each flight booking request must be one of the cities served by the airline.
RS23.	The destination city specified by each flight booking request must be different to the origin city specified by that flight booking request.
RS24.	The number of passengers specified by each flight booking request must be no less than one.
RS25.	The number of passenger names specified by each flight booking confirmation must be equal to the number of passengers specified by the flight booking request that gives rise to that flight booking confirmation.
	Note that "number of" is styled as part of the term number of passengers in rule statements RS24 and RS25 but also as a keyword (as number of passenger names) in RS25. While number of passengers is a defined term for a data item that is used in a flight booking request transaction, passenger name also refers to a data item which appears more than once in a flight booking confirmation transaction, but there is no "number of passenger names" data item as such. In other words "number of" in number of passenger names is a set function referring to the cardinality of a data item rather than a data item itself.
RS26.	Each flight booking request must specify whether or not the passengers must travel on the specified dates.
RS27.	Each flight booking confirmation must specify whether or not the paying party wishes to include a CO2 offset payment.
RS28.	Each flight booking request must specify whether it is for a return journey, a one-way journey or a multi-stop journey.
RS29.	Each flight booking confirmation must specify whether the payment is a credit card payment or an electronic transfer payment.
RS30.	Each flight booking confirmation must specify a mobile phone number, an e-mail address or both.
RS31.	Each flight booking confirmation must specify a credit card or an electronic transfer payment receipt but not both.
RS32.	Each flight booking confirmation must specify exactly one of the following: a postal address, an e-mail address or a fax number.
RS34.	Each flight booking confirmation must specify exactly one of the following: • a mobile phone number; or • an origin city daytime phone number and an origin city evening phone number.
RS35.	Each flight booking confirmation must specify exactly one of the following: • a mobile phone number; or • an origin city daytime phone number and an origin city evening phone number and a destination city daytime phone number and a destination city evening phone number.
RS37.	Each bag that weighs more than 20kg must be labelled with a 'heavy bag' label.
RS38.	The departure time of the return flight (if any) specified by each flight booking confirmation must be no earlier than 1 hour after the arrival time of the outgoing flight specified by that flight booking confirmation.
RS39.	The departure time of the outgoing flight specified by each flight booking confirmation that is made online must be no earlier than 3 hours after the booking confirmation time of that flight booking confirmation.
RS40.	The postal address (if any) specified in each flight booking confirmation must include at least one address line.
RS41.	The postal address (if any) specified in each flight booking confirmation must include exactly one placename.
RS42.	The postal address (if any) specified in each flight booking confirmation must include exactly one postal code.
RS43.	The postal address (if any) specified in each flight booking confirmation must include exactly one country name.
RS44.	Each passenger name specified in each flight booking confirmation must include exactly one first name.
RS45.	Each passenger name specified in each flight booking confirmation must include exactly one last name.
RS46.	Each flight booking confirmation for a one-way journey must specify exactly one flight.
RS47.	Each flight booking confirmation for a return journey must specify exactly two flights.
RS53.	Each flight booking confirmation must specify exactly one travel class for each flight.
RS54.	Each flight booking confirmation must specify exactly one fare class for each flight.
RS55.	The record locator allocated to each confirmed flight booking must be different to the record locator allocated to each other confirmed flight booking.
RS56.	The combination of departure date, flight number, departure city and seat number specified by each seat allocation must be different to the combination of departure date, flight number, departure city and seat number specified by each other seat allocation.
RS60.	The combination of placename and postal code included in the postal address (if any) specified by each flight booking confirmation must be one of the combinations of placename and postal code allocated by the postal authority of the country specified in that postal address if the airline can access the postal code information from that postal authority.
RS61.	Each flight booking confirmation must specify exactly one set of passport details for each passenger if any flight specified in that flight booking confirmation is international.
RS62.	Each flight booking confirmation must specify exactly one date of birth for each passenger if that flight booking confirmation specifies an insurance option.
RS63.	Each flight booking confirmation must specify exactly one escorting party at the destination city if every passenger specified in that flight booking confirmation is less than 12 years of age.

Fact Types

FT1.	flight booking request specifies departure date
FT2.	flight booking request is for journey
FT3.	return journey is a category of journey
FT4.	flight booking request specifies return date
FT5.	one-way journey is a category of journey
FT6.	flight booking request is for return journey
		(derived from fact types FT2 and FT3)
FT7.	flight booking request is for one-way journey
		(derived from fact types FT2 and FT5)
FT8.	flight booking request specifies origin city
FT9.	flight booking request specifies destination city
FT10.	flight booking request specifies number of passengers
FT11.	flight booking request specifies frequent flier membership
FT12.	flight booking confirmation specifies passenger name
FT13.	flight booking confirmation specifies payment arrangement
FT14.	airline serves city
FT15.	flight booking request gives rise to flight booking confirmation
FT16.	passenger must travel on the specified dates
FT17.	paying party wishes to include a CO2 offset payment
FT18.	flight booking request is for return journey
FT19.	flight booking request is for one-way journey
FT20.	flight booking request is for multi-stop journey
FT21.	payment is for flight booking request
FT22.	credit card payment is a category of payment
FT23.	electronic transfer payment is a category of payment
FT24.	flight booking confirmation specifies mobile phone number
FT25.	flight booking confirmation specifies e-mail address
FT26.	flight booking confirmation specifies credit card
FT27.	flight booking confirmation specifies electronic transfer payment receipt
FT28.	flight booking confirmation specifies postal address
FT29.	flight booking confirmation specifies fax number
FT30.	flight booking confirmation specifies origin city daytime phone number
FT31.	flight booking confirmation specifies origin city evening phone number
FT32.	flight booking confirmation specifies destination city daytime phone number
FT33.	flight booking confirmation specifies destination city evening phone number
FT34.	bag weighs weight
FT35.	bag is labelled with label
FT36.	'heavy bag' label is a category of label
FT37.	flight has departure time
FT38.	flight booking confirmation specifies flight
FT39.	outgoing flight is a category of flight
FT40.	return flight is a category of flight
FT41.	flight has arrival time
FT42.	flight booking confirmation is made online
FT43.	flight booking confirmation has booking confirmation time
FT44.	postal address includes address line
FT45.	postal address includes placename
FT46.	postal address includes postal code
FT47.	postal address includes country name
FT48.	postal address includes first name
FT49.	postal address includes last name
FT50.	flight booking confirmation is for return journey
		(derived from fact types FT6 and FT15)
FT51.	flight booking confirmation is for one-way journey
		(derived from fact types FT7 and FT15)
FT54.	flight booking confirmation specifies travel class for flight
FT55.	flight booking confirmation specifies fare class for flight
FT56.	record locator is allocated to confirmed flight booking
FT57.	departure date is specified by seat allocation
FT58.	fllight number is specified by seat allocation
FT59.	departure city is specified by seat allocation
FT60.	seat number is specified by seat allocation

Note

The font and colour conventions used in these rule statements, fact types, and templates reflect those in the SBVR, namely: underlined teal for terms, italic blue for verb phrases, orange for keywords, and double-underlined green for names and other literals.