Next in thread →
Next in month →
Re: [emergency] EDXL_DE - Notes from the meeting to help with minutes and issues list.
In particular, check: http://www.ietf.org/html.charters/enum-charter.html and more germane: http://www.ietf.org/html.charters/iptel-charter.html The latter specifically "The focus of the IP Telephony (iptel) group is on the problems related to naming and routing for Voice over IP (VoIP) protocols. Naming is accomplished through the use of the tel URI, which specifies a URI for telephone numbers. The tel URI was originally defined in RFC 2806, which was developed outside of any IETF working group. The iptel working group is responsible for updating the specification based on extensive experience with the tel URI. It is chartered to develop any extensions to the tel URI, such as support for number portability indicators and trunk groups." Cheers Carl ----- Original Message ----- From: "Michelle Raymond" <> To: "Renato Iannella" <>; "Emergency_Mgt_TC TC" <> Sent: Thursday, August 18, 2005 8:29 PM Subject: Re: [emergency] EDXL_DE - Notes from the meeting to help with minutes and issues list. > Is there a URI for type "phone number"? Or a standardized way of > representing a phone number as a URI? Perhaps there is. > > - Michelle > > On 8/18/05, Renato Iannella <> wrote: >> >> >> On 19 Aug 2005, at 12:07, Michelle Raymond wrote: >> >> >> Why not reuse: >> >> >> >> <valueListUrn>valueListUrn</valueListURN> >> >> <value>value</value> >> >> >> >> here? >> > The <valueListUrn> contains the name of a certified list maintained by >> > the Community of Interest (COI) for the referencing of values. >> > >> > We didn't know of any existing such "lists" that describe formats for >> > contacting a person, group or system. Some example types are(email >> > address, instant message address, phone number, and USMTF). Without >> > knowledge of "lists" that can be readily accessed, we chose to keep it >> > very generic and call it a 'scheme,' allowing any "string" for the >> > time being. >> >> Why not use a URI - most (if not all) addressing schemes of note should >> have a URI form to support interoperability and uniqueness. >> >> >> >> Cheers... Renato Iannella >> National ICT Australia (NICTA) >> >> >> -------------------------------------------------------------------------- >> This email and any attachments may be confidential. They may contain legally >> privileged information or copyright material. You should not read, copy, >> use or disclose them without authorisation. If you are not an intended >> recipient, please contact us at once by return email and then delete both >> messages. We do not accept liability in connection with computer virus, >> data corruption, delay, interruption, unauthorised access or unauthorised >> amendment. This notice should not be removed. >> > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >
Next in thread →
Next in month →