[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: homePostalAddress attribute
On Sat, Nov 16, 2002 at 10:20:10PM +0100, Tony Earnshaw wrote:
> It's not what I believe or not, personally I couldn't care less, as long
> as everything works as it should, for both clients and servers.
The only way to be sure of that in the long run is for everthing to
conform to the standard. As has been shown by a previous poster, the
standard is clear about the correct format and newlines do not come
into it.
The limit of 6 lines and 30 chars per line has been debated many times
too. It seems low to many people, but it was derived from another
international standard so presumably there are systems out there that
depend on it.
> And a lot more besides, obviously (see the posts about ACIs and jpegs):
>
> # jpegPhoto
> # Used to store one or more images of a person using the JPEG File
> # Interchange Format [JFIF].
> # Note that the jpegPhoto attribute type was defined for use in the
> # Internet X.500 pilots but no referencable definition for it could be
> # located.
> attributetype ( 0.9.2342.19200300.100.1.60
> NAME 'jpegPhoto'
> DESC 'RFC2798: a JPEG image'
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.28 )
>
> It does *not* store "or more" images, it stores just one, since there's
> no EQUALITY and no MATCH.
You don't need matching rules to store multiple values. You just need
the *absence* of the SINGLE-VALUE tag. jpegPhoto is not marked
SINGLE-VALUE so I see no problem with storing several photos in one
entry.
Andrew
--
-----------------------------------------------------------------------
| From Andrew Findlay, Skills 1st Ltd |
| Consultant in large-scale systems, networks, and directory services |
| http://www.skills-1st.co.uk/ +44 1628 782565 |
-----------------------------------------------------------------------