Re: [Ecrit] Service Classification ... Was RE: Reminder: Virtual Interim Meeting

"Andrea G. Forte" <andreaf@cs.columbia.edu> Thu, 11 February 2010 04:41 UTC

Return-Path: <andreaf@cs.columbia.edu>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECF433A7654 for <ecrit@core3.amsl.com>; Wed, 10 Feb 2010 20:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20thChLWP6z2 for <ecrit@core3.amsl.com>; Wed, 10 Feb 2010 20:40:58 -0800 (PST)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by core3.amsl.com (Postfix) with ESMTP id 9D82428C110 for <ecrit@ietf.org>; Wed, 10 Feb 2010 20:40:58 -0800 (PST)
Received: from [128.59.20.159] (irt-af.cs.columbia.edu [128.59.20.159]) (user=agf2104 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o1B4g3cw017421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Feb 2010 23:42:09 -0500 (EST)
Message-ID: <4B738AA3.7000707@cs.columbia.edu>
Date: Wed, 10 Feb 2010 23:42:11 -0500
From: "Andrea G. Forte" <andreaf@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
References: <3D3C75174CB95F42AD6BCC56E5555B45022A571B@FIESEXC015.nsn-intra.net> <3D3C75174CB95F42AD6BCC56E5555B45022A574F@FIESEXC015.nsn-intra.net> <00B091B3-44FA-423A-9221-41CBF9B568D2@cs.columbia.edu> <3D3C75174CB95F42AD6BCC56E5555B45022D5CC9@FIESEXC015.nsn-intra.net>
In-Reply-To: <3D3C75174CB95F42AD6BCC56E5555B45022D5CC9@FIESEXC015.nsn-intra.net>
Content-Type: multipart/alternative; boundary="------------090609060904030200010106"
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: ecrit@ietf.org
Subject: Re: [Ecrit] Service Classification ... Was RE: Reminder: Virtual Interim Meeting
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 04:41:02 -0000

Hannes,

while I see Lisa's point, I do not think that the solution is to just 
let "others" deal with it or not to deal with it at all. Building one 
comprehensive list of all possible items is not possible and that is why 
we define a way for other people to add new terms (policy-urn draft) to 
the list. Whomever will try to tackle this issue will face the same 
kinds of problems.
Since the IETF is defining protocols and standards for the provisioning 
of location-based services I think it makes sense for the IETF to pave 
the road for defining new labels. Yes, there are many issues involved in 
defining new terms and in deciding how to categorize such terms but 
there is where the "expert" review comes into help. It would be up to 
the expert reviewer(s) as such to be able to mediate and assign the 
correct label to the correct category and perhaps to decide how to 
"import" previously defined terms.

We need something that is consistent among service providers. If not, 
let's not talk service URNs and LoST any more and let's just go back to 
Google local search.

-Andrea

http://www.cs.columbia.edu/~andreaf 
<http://www.cs.columbia.edu/%7Eandreaf/>

On 2/10/2010 3:14 PM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
> Hi Henning,
>
> Cullen essentially pointed out that service classification is rather
> complicated and we should consult some other folks outside the IETF
> (since they have tried similar things already and failed).
>
> I then solicited more feedback from Lisa and see provided roughly the
> following response:
>
> ---
>
> In effect, this actually starts to move into W3C Semantic Web territory,
> thus I've cc'ed Mark Nottingham.  You could check out the W3C's pages on
> ontology<http://www.w3.org/standards/semanticweb/ontology>  as well as
> vertical apps<http://www.w3.org/standards/semanticweb/applications>  and
> <http://www.w3.org/2001/sw/sweo/public/UseCases/>  -- it's in the
> vertical apps that specific themed vocabularies get developed.  For
> example, the city of Zaragoza developed an ontology for city services
> <http://www.w3.org/2001/sw/sweo/public/UseCases/Zaragoza/>
>
> I believe many of these vocabularies get developed in vertical industry
> consortia and for specific coordination activities.  For example, the
> classifications of diseases was begun as a scholarly activity in the
> 18th century, and international uniform classification of causes of
> death was adopted in 1853.  Different disease and cause--of-death
> classifications have popped up in different countries and different
> industries, and there have been constant and painful attempts to unify.
> It is a tremendous amount of work to revise the list of causes of death
> and when one does so, statistics change in ways that can't be compared
> forward and backward.    For example --
> see<http://wonder.cdc.gov/mortSQL.html>, where the datasets for two
> very similar disease classification systems are completely disjoint.
>
> Contrasting the classification of diseases to classification of
> services: in the case of diseases, only professionals tend to know about
> disease classification codes.  Thus, uniformity can be encouraged in
> professional training.  New diseases are comparably rare; they are
> studied carefully and there are recognized venues for analysing the type
> and classification of new diseases.   In the case of services, we have a
> free for all where anybody can invent a new service (hey, I'm now
> offering custom knit sweater fit analyses at my yarn studio) and all
> kinds of people are expected to search for them.
>
> I believe the incredible range, scope and dynamism of classifying
> services means that any vocabulary definition mechanism will be awfully
> limited.
>
> ---
>
> I have no good suggestion on how to reflect the feedback in these two
> documents:
> http://tools.ietf.org/html/draft-forte-ecrit-service-urn-policy
> http://tools.ietf.org/id/draft-forte-ecrit-service-classification
>
> Maybe someone else in the working group has or maybe someone in the
> application area can provide us with help.
>
> Ciao
> Hannes
>
>
>
>    
>> -----Original Message-----
>> From: ext Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
>> Sent: 08 February, 2010 17:54
>> To: Tschofenig, Hannes (NSN - FI/Espoo)
>> Cc: ecrit@ietf.org
>> Subject: Re: [Ecrit] Reminder: Virtual Interim Meeting
>>
>> Since "shadow boxing" and "tea leaf reading" aren't
>> particularly productive, would the ADs consider revealing
>> those concerns? I'm not sure how else we can have a productive
>> discussion that doesn't just tread over the same old ground.
>>
>> Henning
>>
>> On Feb 8, 2010, at 10:16 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>>
>>      
>>> Hi all,
>>>
>>> Andrea suggested to also put the revision of the Service URN to the
>>> agenda. He has updated the document but there are concerns from the
>>> side of our Ads. Feedback from the group would also appreciated.
>>>
>>> Thoughts about the addition of the document for discussion to the
>>> agenda?
>>>
>>> Ciao
>>> Hannes
>>>
>>>
>>>        
>>>> -----Original Message-----
>>>> From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On
>>>> Behalf Of ext Tschofenig, Hannes (NSN - FI/Espoo)
>>>> Sent: 08 February, 2010 16:50
>>>> To: ecrit@ietf.org
>>>> Subject: [Ecrit] Reminder: Virtual Interim Meeting
>>>>
>>>> Hi all,
>>>>
>>>> Please keep our virtual interim meeting Thursday Feb. 11
>>>>          
>> 8AM-10AM EST
>>      
>>>> (New York).
>>>>
>>>> We plan to discuss the PSAP callback mechanism, see
>>>>
>>>>          
>> http://tools.ietf.org/id/draft-schulzrinne-ecrit-psap-callback-01.txt
>>      
>>>> , and to make some progress on the solution front.
>>>>
>>>> The Webex info can be found below.
>>>>
>>>> Ciao
>>>> Hannes&  Marc
>>>>
>>>>
>>>> -- WEBEX
>>>>
>>>> Date: Thursday, February 11, 2010
>>>> Time: 8:00 am, Eastern Standard Time (New York, GMT-05:00)  Meeting
>>>> Number: 209 813 488  Meeting Password: ietf
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> To join the online meeting (Now from iPhones too!)
>>>> -------------------------------------------------------
>>>> 1. Go to
>>>> https://ciscosales.webex.com/ciscosales/j.php?ED=133856902&UID=
>>>> 0&PW=NNjA
>>>> 5ZTg4YzJm&RT=MiMxMQ%3D%3D
>>>> 2. Enter your name and email address.
>>>> 3. Enter the meeting password: ietf
>>>> 4. Click "Join Now".
>>>>
>>>> To view in other time zones or languages, please click the link:
>>>>
>>>> https://ciscosales.webex.com/ciscosales/j.php?ED=133856902&UID=
>>>> 0&PW=NNjA
>>>> 5ZTg4YzJm&ORT=MiMxMQ%3D%3D
>>>>
>>>> ----------------------------------------------------------------
>>>> ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes
>>>> ----------------------------------------------------------------
>>>>
>>>> The affected toll free numbers are: (866) 432-9903 for the San
>>>> Jose/Milpitas area and (866) 349-3520 for the RTP area.
>>>>
>>>> Please dial the local access number for your area from the
>>>>          
>> list below:
>>      
>>>> - San Jose/Milpitas (408) area: 525-6800
>>>> - RTP (919) area: 392-3330
>>>>
>>>> -------------------------------------------------------
>>>> To join the teleconference only
>>>> -------------------------------------------------------
>>>> 1. Dial into Cisco WebEx (view all Global Access Numbers at
>>>> http://cisco.com/en/US/about/doing_business/conferencing/index.html
>>>> 2. Follow the prompts to enter the Meeting Number (listed
>>>> above) or Access Code followed by the # sign.
>>>>
>>>> San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330
>>>>
>>>> US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117
>>>>
>>>> India: +91.80.4350.1111 Germany: +49.619.6773.9002
>>>>
>>>> Japan: +81.3.5763.9394 China: +86.10.8515.5666
>>>>
>>>> -------------------------------------------------------
>>>> For assistance
>>>> -------------------------------------------------------
>>>> 1. Go to https://ciscosales.webex.com/ciscosales/mc
>>>> 2. On the left navigation bar, click "Support".
>>>>
>>>> You can contact me at:
>>>> mlinsner@cisco.com
>>>> 1-919 476 7083
>>>>
>>>> To add this meeting to your calendar program (for example Microsoft
>>>> Outlook), click this link:
>>>>
>>>> https://ciscosales.webex.com/ciscosales/j.php?ED=133856902&UID=
>>>> 0&ICS=MI&
>>>> LD=1&RD=2&ST=1&SHA2=vAuFJ4sX5SuD8pTdUg8W6UR7Yr24ecYH0d3iPGYygGE
>>>> =&RT=MiMx
>>>> MQ%3D%3D
>>>>
>>>> The playback of UCF (Universal Communications Format) rich media
>>>> files requires appropriate players. To view this type of rich media
>>>> files in the meeting, please check whether you have the players
>>>> installed on your computer by going to
>>>> https://ciscosales.webex.com/ciscosales/systemdiagnosis.php
>>>>
>>>> Sign up for a free trial of WebEx
>>>> http://www.webex.com/go/mcemfreetrial
>>>>
>>>> http://www.webex.com
>>>>
>>>>
>>>>
>>>> IMPORTANT NOTICE: This WebEx service includes a feature that allows
>>>> audio and any documents and other materials exchanged or viewed
>>>> during the session to be recorded. By joining this session, you
>>>> automatically consent to such recordings. If you do not consent to
>>>> the recording, do not join the session.
>>>>
>>>> _______________________________________________
>>>> Ecrit mailing list
>>>> Ecrit@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ecrit
>>>>
>>>>          
>>> _______________________________________________
>>> Ecrit mailing list
>>> Ecrit@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ecrit
>>>
>>>        
>>
>>      
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>
>