RE: [Ecrit] LoST Review

["Drage, Keith \(Keith\)" <drage at alcatel-lucent.com>]

To the final comment.

Technically the "+" is not part of E.164. E.164 provides for different number types, e.g. international, local, but does not say how they are distinguished except to indicate that prefixes exist that can perform this.

The "+" comes from another ITU-T recommendation that defines the provision of telephone numbers in a readable format, e.g. for business cards. And incidently this recommendation uses " " rather than "-" as a digit separator.

Regards

Keith

> -----Original Message-----
> From: Andrew Newton [mailto:andy at hxr.us] 
> Sent: 31 January 2007 16:14
> To: "Patrik Fältström"
> Cc: ecrit at ietf.org
> Subject: Re: [Ecrit] LoST Review
> 
> 
> On Jan 31, 2007, at 11:06 AM, Patrik Fältström wrote:
> >>>>> 5.2.  Time of Last Update: The 'lastUpdated' Attribute
> >>>>>
> >>>>>    The 'lastUpdated' attribute describes when the 
> mapping was last
> >>>>>    changed.  The contents of this attribute is a timezoned XML 
> >>>>> type
> >>>>>    dateTime, in canonical representation.  The attribute is 
> >>>>> REQUIRED.
> >>>>
> >>>> Note that according to 3.2.7.2 of http://www.w3.org/TR/2001/REC- 
> >>>> xmlschema-2-20010502/#dateTime (maybe I am looking at the wrong
> >>>> source) the canonical representation of a time is always 
> in UTC, so 
> >>>> the timezoned canonical version will always have 'Z' as the 
> >>>> timezone indicator.
> >>>>
> >>>> This is what you want?
> >>
> >> I think so, though we could be a bit more explicit, huh?
> >
> > No no. I just wanted you to understand that the way *I* read your 
> > spec, the dateTime will always be in UTC. Just so people do not 
> > misunderstand what the paragraph in 5.2 say.
> >
> > I think using UTC is fine.
> 
> Then you read it correctly... or said more accurately, your 
> interpretation is as we intended.  I still think we could be 
> a heck of a lot more specific.
> 
> >>>>>    It contains a string of digits, * and # that a user on a
> >>>>>    device with a 12-key dial pad could use to reach that 
> >>>>> particular
> >>>>>    service.
> >>>>
> >>>> Reference a syntax specification. Max 15 char in the 
> string as in 
> >>>> E.164?
> >>
> >> I don't believe emergency numbers such as 911 or 112 or E.164 
> >> numbers.
> >
> > Correct, as countries (Sweden at least) have as a 
> requirement for E. 
> > 164 that it is possible to call an E.164 from any other E.164. They 
> > are from the same "namespace" though...and because of that have 
> > similar constraints. Maybe that is in the schema though?
> 
>  From the schema:
> 
>        element ns1:serviceNumber {
>          xsd:string { pattern = "[0-9*#]+" }
>        }?,
> 
> We don't say anything about E.164.  And E.164 numbers cannot 
> be dialed on a lot of phones.  How do you dial the beginning "+"  
> character.  These are dialstrings that must be recognized by the UA.
> 
> -andy
> _______________________________________________
> Ecrit mailing list
> Ecrit at ietf.org
> https://www1.ietf.org/mailman/listinfo/ecrit
> 

_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit