> > I think we're risking breaking the 'names should reflect what the > module does not how it does it rule'. > > On reflection I think a DTD, or similar, namespace is risky. > I think we'd be better off *ignoring* the use of XML in the > implementation (where possible) and just considering the abstract > functionality the module offers when thinking about suitable names.
I see this point. Hmm. My initial suggestion was an MRML top level namespace. What it does is treat multimedia retrieval markup language communication. MRML is a protocol for querying multimedia data. BTW: HTTP treats HTTP communication. Have you to any ideas with respect to that? Cheers, Wolfgang
