Defer merging current spec to new OASIS template until release of next CSD

This avoids two big edit cycles, one now and one before the spec release, leaving the one at the end of the spec release which can't be avoided.

On the 4/1/2013 TC meeting it was motioned and accepted by the TC:
Proposal: the editors shall open a new jira issue, targeted for v.next, stating the the specification(s) will need to be updated to the latest oasis templates. The issue shall also include the latest template document that the TC recently received from the oasis staff for reference.