On 17/11/15 13:29, James Cummings wrote:
> Now, I know what your answer will be: We
> want human-readable and encodable private URI values, no encoder can
> type in 300011851 and know what it means.
Unless you use smart content completion. I wonder... That would require
a layer of configurable redirection inside a smart editor, right? To
provide a list of values (potential fillers) with their descriptions
taken from designated elements.