I absolutely agree with that.  The only question in my mind at this point is WHICH master format.  TEI is nice because it literally can handle anything you want to throw at it.  However, that flexibility means it ain't that easy to learn.
<div><br /></div>
<div>RST seems pretty easy to deal with (95% of what you type is just what's on the page). It also seems like it's be fairly easy to adopt directly into DP's workflow, too. &nbsp;But my fear is that it will start to show problems in some of the non-fiction we get. &nbsp;For instance ... how will it handle some of the math stuff we've seen?</div>
<div><br /></div>
<div>My preference is for RST to win simply because of the lower entry bar, but ... *shrug*</div>
<div><br /></div>
<div>Josh<br /><br />
<p>On Feb 3, 2012, <strong>don kretz</strong> &lt;dakretz@gmail.com&gt; wrote:</p>
<div class="replyBody">
<blockquote class="email_quote" style="border-left: 2px solid #267fdb; margin: 0pt 0pt 0pt 1.8ex; padding-left: 1ex;">Josh, I think single-master-format is the only workable option. I'd add to that, though, that the texts should incorporate all reasonably collectable content
<div>during the original project, even if it's expected that it will be superfluous. Then strip it out for all devices; but it will still be there in the original.</div>
<div><br /></div>
<div>BTW, this is as much for simplicity as for comprehensiveness. It's just easier for everyone if the instructions are the same for all projects.</div>
<div><br /></div>
<div>This in turn implies that it may be a mistake to use an output format that we actually intend to use for some devices as the master format.</div>
<div><br /></div>
</blockquote>
</div>
</div>