I attempted to load the schema to Apache Directory Studio and it died because of this invalid name.

May I ask how you got the schema to load? By using ldapsearch?
$ ldapsearch [...] -b "cn=schema" objecclasses attributetypes

I'm not sure if you are asking about steps I did in Apache Directory Studio or the schema export itself.

I used "on-line schema editor" in Apache DS, see attached video. (I used ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130125).

ApacheDS throws more detailed traceback to the console, see [https://issues.apache.org/jira/browse/DIRSTUDIO-871 this bug report].

I did schema -> LDIF export before reporting the original bug to Apache DS. Command I used:
{{{
ldapsearch -o ldif-wrap=no -Y GSSAPI -b "cn=schema" '(objectClass=subSchema)' -s sub objectClasses attributeTypes matchingRules matchineRuleUse dITStructureRules nameForms dITContentRules ldapSyntaxes
}}}

attachment
apache-ds-online-schema-editor.ogg

Petr, thanks a lot for the complete input. You gave me everything I wanted to get.
--noriko

This bug was fixed along with ticket #561.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/577

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.