On Mon, Oct 8, 2012 at 12:56 PM, Lee Passey <lee@passkeysoft.com> wrote: On 10/6/2012 8:36 AM, Greg Newby wrote: This is, more or less, exactly what I said we needed. There is no resistance to any of this. I even asked for input on figuring out what the requirements & enforcement would look like. The first, and I think non-negotiable, requirement is that whatever standard is selected it must have a reasonably complete set of markup to capture all the features of a book. Figuring out just what this "reasonably complete" set of features is is nonetheless problematic. This is the first and only requirement. And not reasonably complete, absolutely complete. You can't format what you can't identify. But, if you identify everything, you can format it any way you want with software. And the list of things to identify can be done easily if your markup is extensible, because you keep adding markup identifiers until you don't need any more. The rest of your requirements is just details and there are any number of equivalent schemes; they are interchangeable as long as the things requiring identification are unambiguously tagged or otherwise clearly identifiable.