As an alternative approach, I would suggest having a single multi- valued attribute that would contain URIs expressing the location of the attribute. This would push various issues, such as which location system is being used, out to the URIs. This is a good thing as such issues are not unique to LDAP/X.500.

-- Kurt


On Jul 27, 2009, at 10:19 AM, Ivan Shmakov wrote:

Adam Tauno Williams <awilliam...> writes:

Hello. Is there a standardized (or regularly used) attribute defined for
continents, besides country, st, locality?

Not that I've ever seen.  There are a couple of definitions of
longitude/latitude floating about, but nothing for continent.

        I wonder, what other geographic ``variables'' (or objects?) have
        found their way to LDAP?  To put it differently, the (latitude,
        longitude) pair describes a point on the Earth's surface.  Are
        there existing LDAP attributes (or object classes?) that will
        allow one to describe more complex ``features'' upon the Earth's
        surface, such as, e. g., polygons?

Debian:

attributetype ( 1.3.6.1.4.1.9586.100.4.2.7
       NAME 'latitude'
       DESC 'latitude coordinate'
       EQUALITY caseExactIA5Match
       SUBSTR caseExactIA5SubstringsMatch
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )

        And also:

--cut: http://openosi.org/osi/display/oid/1.3.6.1.4.1.27630.2.1.1.23 --
attributetype ( 1.3.6.1.4.1.27630.2.1.1.23
       NAME ( 'osiLatitude' 'latitude'  )
DESC 'Latitude in decimal degree notation, negative sign for South'
       EQUALITY caseExactIA5Match
       SUBSTR caseExactIA5SubstringsMatch
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
       SINGLE-VALUE )

...

  SYNONYM OID
    * 1.3.6.1.4.1.9586.100.4.2.7 (Debian userdir-ldap.schema)
--cut: http://openosi.org/osi/display/oid/1.3.6.1.4.1.27630.2.1.1.23 --

[...]

GNOME has defined it as well:

attributetype ( 1.3.6.1.4.1.3319.7.7
       NAME 'latitude'
       DESC 'latitude coordinate'
       EQUALITY caseExactIA5Match
       SUBSTR caseExactIA5SubstringsMatch
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )

        Seems to be not used much, as Google lists only two matches for
        the OID.

[...]

--
FSF associate member #7257



Reply via email to