>>>>> Michael Ströder <michael...> writes:
>>>>> Ivan Shmakov wrote:
>>>>> Michael Ströder <michael...> 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 practice, it would probably be sufficient to provide a
>> single implementation (did I say OpenLDAP?) supporting the syntax.
> So you'd have to implement that LDAP syntax for OpenLDAP and
> preferrably contribute it to the OpenLDAP project.
Surely. Adapting patches to the every new version of the
package forever is definitely off my plans.
> Note that it would be helpful if you write an Internet Draft for it
> and pushing it to at least an informational RFC.
Hopefully I'd be able to do at least the technical part. The
whole system is in, what I'd call it, the ``deep research''
stage.
>> The question is, how would an LDAP DSA (DUA) treat attributes having
>> the syntax unknown to it? Would it, e. g., simply treat their
>> values as binary strings?
> No. An attribute type description contains a reference to the SYNTAX
> by OID. OpenLDAP won't even start if the syntax is not implemented.
[...]
> Another approach in OpenLDAP is to use slapo-constraint to let the
> DSA check whether the attribute values match additional constraints
> (see man page). Again for composed attribute values only a regex
> checking would be applicable.
ACK. Thanks.
[...]
>>> for all the coordinate systems and encourage people to register
>>> their coordinate systems.
>> This could be the easiest part, as there're already developed
>> ``vocabularies'' of coordinate systems. In particular, I believe
>> WKT [1] uses one.
>> [1] http://en.wikipedia.org/wiki/Well-known_text
> I'm not familiar with this stuff but it's good to rely on existing
> and well-maintained registries.
Yes.
--
FSF associate member #7257
