Jean-Baptiste Quenot wrote:
* Antonio Fiol (JIRA):
Three possible approaches:
- Investigate further on the meaning of name;something other than
name;lang-something and try to map that into meaningful XML attributes.
e.g. description;lang-en --> <ldap:description xml:lang="en">
- Split the attribute name at the first ";" and put the rest as an attribute. For
example, the attribute could be called "attrs".
e.g. description;lang-en --> <ldap:description attrs="lang-en">
This second approach is the best, unless the mentioned RFCs
mentions that the hyphen "lang-en" is a name-value delimiter.
According to [1], there might be multiple options separated by ';'. So LDAP
transformer should at least parse all options and output them, probably as space
separated list:
description;foo;bar;lang-en --> <ldap:description options="foo bar lang-en">
In addition it's probably good idea to parse well known options, so result can
be:
description;foo;bar;lang-en --> <ldap:description xml:lang="en" options="foo
bar">
Vadim
[1] http://www.ietf.org/rfc/rfc2251.txt, Chapter 4.1.5
