Add a Street schema to Physical Address eXchange Schema Standard

In the PAX schema, streetNamePhonetic is a fact about a Street. Do we need a separate street schema to provide the proper home for this field? localityNamePhonetic is a fact about a locality so is best left as a proposed addition to BCGNIS.

A street schema can also be used to validate street fields in the new-civic-addresses file. For example, let's say the Salmon Arm address authority provides the following street records:

|Name|Value
|--|--
streetName|10
streetType|Ave
streetDirection|NE
localityName|SalmonArm
subCountryCode|BC

If they also provide the following civic addresses:

|Name|Value
|--|--
civicNumber|101
streetName|10
streetType|Ave
streetDirection|N
localityName|SalmonArm
subCountryCode|BC

this address will be rejected by the geocoder data integration process because there is no 10 Ave N in Salmon Arm according to their street schema.

The street schema can also be used to validate streets in submitted road segment files . This allows for checking for mispelled streetNames between blocks of a street in the same locality, and unknown streetTypes, streetDirections, and streetQualifiers