Re: [Ecrit] Terminology section (<draft-schulzrinne-ecrit-requirements-01.txt>)

[Henning Schulzrinne <hgs at cs.columbia.edu>]

Tschofenig, Hannes wrote:
> hi all, 
>
>
>    address: A description of a location of a person, organization, or
>       building, most often consisting of numerical and text elements
>       such as street number, street name, and city arranged in a
>       particular format.
>
> # why do we need to define what an address is? 

Since this might be confused with (say) a network address.



>    administrative domain: An area or group of services falling with in a
>       specific category or jurisdictional boundary.
>
> # why do we need this term? 

If not used, it clearly can go.

>    Basic Emergency Service: Basic Emergency Service allows a user to
>       reach a PSAP serving its current location, but the PSAP may not be
>       able to determine the identity or geographic location of the
>       caller (except by having the call taker ask the caller).
>
> # why do we need to distinguish between basic and enhanced emergency
> service? 

Because it differs in the requirements, albeit not for the mapping 
protocol. Basic emergency services only need mapping and location 
accurate enough for mapping, but do not deliver location information 
suitable for dispatch to the call taker.



>    domain authentication and validation entity: A node that has
>       authority within a given domain to authenticate and validate user
>       location information.
>
> # i think we don't use this term anymore in the document. 

Agreed.

> # haven't we once said that we want to use either psap or ecc. i
> remember that we agreed to use the term psap. 

Yes, this should be PSAP throughout.


>    ESRP (Emergency Services Routing Proxy): An ESRP is a call routing
>       entity that invokes the location-to-URL mapping, which in turn may
>       return either the URL for another ESRP or the PSAP.  (In a SIP
>       system, the ESRP would typically be a SIP proxy, but could also be
>       a Back-to-back user agent (B2BUA).
>
> # do we really all these geo-specific terms?

No, we don't. Some of the original documents provided more architecture, 
so they contributed these terms.



>    geocoding: The process of finding the location of a street address on
>       a map.  The location can be an x,y coordinate or a feature such as
>       a street segment, postal delivery location, or building.  In GIS,
>       geocoding requires a reference dataset that contains address
>       attributes for the geographic features in the area of interest.
>
>    geographic coordinates: A representation (measurement) of a location
>       on the earth's surface expressed in degrees of latitude and
>       longitude.
>
>    geographic coordinate system: A reference system that uses latitude
>       and longitude to define the locations of points on the surface of
>       a sphere or spheroid.
>
>    geographic transformation: A method of converting data between two
>       geographic coordinate systems (datums).
>
>    geographic location: A reference to a locatable point described by a
>       set of defined coordinates within a geographic coordinate system,
>       (e.g. lat/lon within WGS-84 datum)

I don't think we need any of these, except possibly the latter.

> # more terminology is required: i would like to see terms for the
> mapping protocol (or something similar). 
> additionally, the client and the server actors using the protocol are
> required (e.g., mapping protocol client and the server)



> # what is the name for the 'process for determining the location to uri
> mapping' ? resolution? 

Mapping? This would go nicely with 'mapping server'.



> # additionally, we need a name for an 'iterative' and a 'recursive'
> query to the distributed directory. 
> # a definition for the 'distributed directory' or 'distributed database'
> is also needed. 

Distributed mapping service?


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