Hi all,

I've been working on some prototypes of a mapping tool from Java to LDAP and
back. The only really
sticky point I have for mapping simple primitive properties lies in the area
of representing real values
in the directory.  There is no real syntax in LDAP.  Nor are there
matchingRules for attributes with this
syntax.  ASN.1 defines an encoding for REAL data types here:

http://www.itu.int/ITU-T/studygroup.../X.690-0207.pdf

I'm going to move forward and just ignore Java floats and doubles for now.
However I would really like
to devise a simple encoding for the base, and mantissa of these entities to
be able to track them without
rounding errors due to their persistence in the directory.  There's been a
lot of conversation about this
topic but no one has actually stepped up and done it.  Here's some links to
these convos:

http://www.openldap.org/lists/openl...3/msg00065.html

Does anyone think they can take a stab at writing an LDAP syntax description
for REAL numbers
and providing the required SyntaxChecker and matchingRules for it as well?

Thanks,
Alex

[ Post a follow-up to this message ]

If there is no urgency, I think we just need a JIRA as a reminder...

Writing a SC for float could be a PITA, so if we can differ it for a
while, that would be perfect.

On 7/22/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
> Hi all,
>
> I've been working on some prototypes of a mapping tool from Java to LDAP =
and
> back. The only really
> sticky point I have for mapping simple primitive properties lies in the a=
rea
> of representing real values
> in the directory.  There is no real syntax in LDAP.  Nor are there
> matchingRules for attributes with this
> syntax.  ASN.1 defines an encoding for REAL data types here:
>
>
> http://www.itu.int/ITU-T/studygroup.../X.690-0207.pdf
>
> I'm going to move forward and just ignore Java floats and doubles for now=
.
> However I would really like
> to devise a simple encoding for the base, and mantissa of these entities =
to
> be able to track them without
> rounding errors due to their persistence in the directory.  There's been =
a
> lot of conversation about this
> topic but no one has actually stepped up and done it.  Here's some links =
to
> these convos:
>
>
> http://www.openldap.org/lists/openl...3/msg00065.html
>
>  Does anyone think they can take a stab at writing an LDAP syntax
> description for REAL numbers
> and providing the required SyntaxChecker and matchingRules for it as well=
?
>
> Thanks,
> Alex
>
>


--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com

[ Post a follow-up to this message ]

No problem - I don't see float's floating around much these days.  We
certainly do not
need it for the configuration beans.

Alex

On 7/22/07, Emmanuel Lecharny <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbc
ol=seagreen]
>
> If there is no urgency, I think we just need a JIRA as a reminder...
>
> Writing a SC for float could be a PITA, so if we can differ it for a
> while, that would be perfect.
>
> On 7/22/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.o
rg> wrote: 
> and 
> area 
> now. 
> to 
> a 
> to 
> well? 
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>[/vbcol]

[ Post a follow-up to this message ]