Current Mark design does not enforce a namespace standard. Namespace can be easily captured in Mark, e.g. {'ns:elmt' 'xml:attr':'value' ...} XML Namespace seem

Current Mark design does not enforce a namespace standard. Namespace can be easily captured in Mark, e.g. {'ns:elmt' 'xml:attr':'value' ...} XML Namespace seems to have a lot issues, thus Mark does not want to enforce something exactly following it. Namespace in Mark, currently, is left upto the application user to define it. We might be able to come up with a better way to define namespace. As for the name, you can just use Mark. I use '{mark}' as an alternative name, to make it more graphical, more impressive.