> I think we should just have two new relation modifiers:
> which indicate the encoding of the term; and if it turns out
> in the future that there is also a need to convey
> content-type, then that should be handled by a new relation
> modified when it's needed.
> foo.image =/cql.base64/cql.content-type="image/gif"
Ah, I hadn't appreciated that /xxx=yyy form of the relational modifier.
A modifier of cql.content-type= would be useful to use in the music
context set instead of my current music.mimeEncoded.