> Also just indicating that the term is base64 encoded is not quite
> sufficient for the same reason that I called the modifier mimeEncoded
> rather than base64Encoded in the Music Context set - which is ...

> The problem with having a base64Encoded modifier is that although I know
> how to decode the data, I've no idea what the thing is I get once
> decoded (is this a string with stange character in, an audio wave file,

A good point.  I think we need -both- though, for when you just want to
base64 encode a string term and not faff around with all the mime headers
to say specifically that it's a text/plain string.

Rob

       ,'/:.          Dr Robert Sanderson ([log in to unmask])
     ,'-/::::.        http://www.o-r-g.org/~azaroth/
   ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.
I L L U M I N A T I  L5R Shop: http://www.cardsnotwords.com/