Re: [stir] Questions about stir-certificates

[Paul Kyzivat <[e-mail]>]

On 10/30/17 11:51 PM, Martin Thomson wrote:

>> A couple of things:
>>
>> 1. The count text has not been updated since we added “*" and “#” and I’m thinking that count was only supposed to apply to the parts of the TN that are not related to the “*" and “#”.
>>
>> 2. To answer your question: yes it’s the number plus the next 9 and overflows should be prohibited.
>>
>> How about the following for #2 in s9:
>>
>>   2.  Telephone numbers can be listed in a range (in the
>>        TelephoneNumberRange format), which consists of a starting
>>         telephone number and then an integer count of numbers within the
>>         range, where the valid boundaries of ranges may vary according to
>>         national policies.  count has the following constraints: overflow into
>>         more digits isn’t permitted, e.g., “123” + 100 is not allowed; count
>>         only applies to the telephone number and not to digits associated
>>         with “*” or “#”.
>>
>> In the above I am not sure the words a quite right.
> 
> Does "not to digits associated with “*” or “#”" mean?
> 
> a. a count can't be used with a number that includes either "*" or "#"
> b. a count applies to the numerical value preceding any "*" or "#"
> b. a count applies to the numerical value after the final "*" or "#",
> if any are present
> c. something else
> 
> (a) seems right to me.  I can see a case for describing a range of
> extensions, but it probably makes sense to disavow that use case and
> have the bare number asserted on its own.  Thus, I would say:
> 
>> national policies.  A count is added to the numeric value of the telephone number.  A count cannot cause the telephone number to increase in length, thus "123" + 100 is not valid.  A number that includes "*" or "#" cannot be included in TelephoneNumberRange.
> 
> That suggests a different grammar might be useful, so maybe you really
> do mean b.

+1 to a different grammar, restricting the start for a range to just a 
numeric string, or whatever is intended. And then an explicit generation 
rule for the additional numbers in the range.

What is supposed to be done for variable length numbering schemes?

	Thanks,
	Paul