[tei-council] to id or not to id

[Syd Bauman]

> One could argue that the core should remain pure, and have only
> xml:id and xml:lang. But that a P4 compatibility module could
> introduce the @id/@xml:id choice. This would have the advantage
> that P5 users who wanted to work in this way would have to be
> more explicit about it, by adding a new module to their
> portfolio.

This is, in fact, what the SO work-group recommended. Council did not
explicitly address the suggestion for the add-on module that swaps
id= for xml:id=, IDREF for tei.pointer, and IDREFS for tei.pointers.

In principle I think such a module is a good idea, whether it's just
an ID/IDREF module or a complete "P4 Compatibility" module. (Or
both. :-)