> That seems fine presuming it can always be parsed -- i.e., is there an
> escape mechanism that ensures that special characters like [:=,;] will not
> cause problems if they appear in a link property value?

If there is already an escape mechanism for [=,;], it should be trivial 
to add the colon. If there is no such mechanism, we're not making things 
considerably worse.

So I think we agree on the general approach; details can be ironed out 
during code review. I plan to look into this after integrating Brussels 
Persistence, sometime in May.

thanks,
-Artem

Reply via email to