re: schema format questions

[John B. <joh...@ne...>]

Hi folks.

Sorry not to comment on the schema stuff. New changes look great. I'd like 
to ask about the following though:


Peter Marschall wrote:

> > I have two questions about the frmat of schema entries that may be a
> > little off topic, but bay also affect perl-ldap:
> > 
> > * Is ' (single quote) legal inside qdstrings in schema definitions 
> >   RFC2252 does not explicitely deny it. It simply gives the
> >   following definitions
> > 
> >       dstring         = 1*utf8
> >       qdstring        = whsp "'" dstring "'" whsp
> > 
> >   without defining utf8 further
> >   Since a single quote is a utf8 character, this could mean
> >   that single quotes inside qdstrings are really allowed.
> >   So
> >       DESC 'New Object's FS Rights'
> >   might be a legal description.

Yep. But the question for me is whether ( and ) and whitespace are
permitted (which they presumably are although I must confess to not having
checked utf8 :-) because that makes the whole thing technically unparsable
unless I am missing something.

What about:

attributeTypes: ( 2.16.840.1.113719.1.56.4.1.1 NAME 'newObjectSFSRights'
 DESC 'Standard Attribute' SYNTAX 2.16.840.1.113719.1.1.5.1.15{64512}
 X-NDS_NAME 'New Object' s FS Rights - correct this time :-)'
 X-NDS_NOT_SCHED_SYNC_IMMEDIATE '1' )

? How can you parse that sensibly? (Even in perl...)

The '1*utf8' seems to make a nonsense of any possibility of parsing.

Peter Marschall wrote:

> > I do not ask this just for fun.
> > I find the assumptions made by Net::LDAP::Schema reasonable
> > (since the things above make parsing the schema quite hard).

Graham Barr wrote:

> Right. Its not so much that it is hard, but it will be slower.

I don't see how it is possible at all, without defining an additional
escape mechanism or list of disallowed characters (the previous approach).


regards,

jb