It should be possible to use entity references to encode these characters in URLs. See https://dev.w3.org/html5/html-author/charref Maybe I'm misunderstanding the problem, but can we simply encode the URLs, rather than restricting the names?
best, Colin On Mon, Oct 23, 2017, at 14:12, Randall Hauch wrote: > Here's the link to KIP-212: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74684586 > > I do think it's worthwhile to define the rules for connector names. > However, I think it would be better to describe the current restrictions > for names outside of them appearing within URLs. For example, if we can > keep connector names relatively free of constraints but instead define > how > names should be encoded when used within URLs (e.g., URL encoding), then > we > may not have (m)any backward compatibility issues other than fixing some > bugs related to proper encoding/decoding. > > Thoughts? > > > On Mon, Oct 23, 2017 at 3:44 PM, Sönke Liebau < > soenke.lie...@opencore.com.invalid> wrote: > > > All, > > > > I've created a KIP to discuss enforcing of rules on what characters are > > allowed in connector names. > > > > Since this may break api calls that are currently working I figured a KIP > > is the better way to go than to just create a jira. > > > > I'd love to hear your input on this! > >
