Here's a small smooth stone with which I hope to down a lot of birds
(not necessarily for Sebastian's dinner though)

The current <figure> element has a content model which permits all sorts
of textual things within it. P4  makes clear that the intention is that
these should be transcribed from the image whose presence the <figure>
denotes. The image itself is indicated (in pure P4) by an entity
attribute pointing to an external graphic entity, or (in practice) by a
URL attribute.   There is no wrapper element combining a graphic with
its heading etc. There is no way of embedding graphic content expressed
using SVG or even the TEI tags for trees within a <figure>, though there
is a <figDesc> "surrogate" for the graphic information.

I propose to address these concerns as follows:

1. Introduce a new core element called <graphic> with a URL attribute
(or whatever the TEI Workgroup on Standoff finally decides it should be
called).

2. Introduce a new wrapper element to hold text content of a graphic,
called <figText>, with content model mle the current <figure> content model.

3. Introduce a new class tei.figContent, with members <graphic>,
<eTree>, <eg> (or whatever we decide to call that thing), <figText> ).

4. Redefine the content model of <figure> to be
   (%(tei.figContent), figDesc?, head?)


What I don't know is how to add an SVG element into the mix. Ideally, I
would like to add <svg:something> to the tei.figContent class. Suggestions?