> Hallvard B Furuseth writes:
[...]
>>> * Create an attribute option range "coordinate-" so
>>> that you can create one attribute description set for each
>>> coordinate system:
>>> attribute "latitude;coordinate-a", value "1"
>>> attribute "latitude;coordinate-b", value "2"
>>>
Ivan Shmakov writes:
> > Hallvard B Furuseth writes:
>
> > Solutions:
> > * Make a single attribute with all three values.
> > attribute "position", values ("a 1 9", "b 2 8", "c 3 7").
> > Syntax Directory String or IA5 String, plus a client-defined syntax
> > which clients are respons
> Michael Ströder writes:
> Ivan Shmakov wrote:
> Michael Ströder writes:
[...]
>>> But encouraging all the LDAP server vendors to implement an
>>> additional syntax can take some time. ;-)
>> The system I'm working on is going to have somewhat narrow field of
>> use, so, in pr
> Kurt Zeilenga writes:
[...]
> 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
On Jul 27, 2009, at 11:16 AM, Michael Ströder wrote:
Kurt Zeilenga wrote:
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 be
> Hallvard B Furuseth writes:
>> * allow any number of (coordinate system, latitude, longitude)
>> triplets to be specified.
>> The last approach seems to be the most flexible. However, I don't
>> know if it's possible to ``tie'' attributes into such a ``triples''
>> with LDAP?
> Lik
Kurt Zeilenga wrote:
> 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
Ivan Shmakov wrote:
>> Michael Ströder writes:
> > Defining your own LDAP syntax would be the solution (similar to
> > RFC2307 NIS Netgroup Triple, OID 1.3.6.1.1.1.0.0).
>
> ACK. Thanks.
>
> > But encouraging all the LDAP server vendors to implement an
> > additional syntax can ta
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 u
> Michael Ströder writes:
>> It seems that the cases when the same real world object is described
>> by several DIT entries are not uncommon.
>> The only thing that comes to my mind is a separate multi-value
>> attribute holding the DNs of all the DIT entries known to describe
>> the sa
> Michael Ströder writes:
[...]
>> * designate some ``standard coordinate system'' (like: WGS 84) for
>> the attributes (like: `latitudeWGS84', `longitudeWGS84'); convert
>> the values on the client side whenever a non-standard coordinate
>> system is to be used;
[...]
>> To my mind,
Ivan Shmakov writes:
> (...)
> * allow any number of (coordinate system, latitude, longitude)
> triplets to be specified.
> (...)
> The last approach seems to be the most flexible. However, I
> don't know if it's possible to ``tie'' attributes into such a
> ``triple
Ivan Shmakov wrote:
> It seems that the cases when the same real world object is
> described by several DIT entries are not uncommon.
> [..]
> The only thing that comes to my mind is a separate multi-value
> attribute holding the DNs of all the DIT entries known to
> d
Ivan Shmakov wrote:
> ... One of the biggest shocks I've ever experienced in my life
> was caused by the observation that there's /infinite/ /number/
> of (latitude, longitude) pairs for (almost) any given point on
> the Earth surface, depending on the reference ellipsoid [1
It seems that the cases when the same real world object is
described by several DIT entries are not uncommon. E. g., a
person may work in an organization, and for the purposes of this
organization be described by an entry and be a member of some
project, and
> Adam Tauno Williams 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.
> Deb
> Adam Tauno Williams 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.
17 matches
Mail list logo
