On 5/9/07, Mike Taylor <[log in to unmask]> wrote:
> Yes.  The point of this extension is that it's an extension, intended
> in part to serve a model of what extensions should look like.  If we
> throw our hands up and change the core specifications every time an
> extension comes along, we're admitting that we got the extension
> mechanism wrong.

So if we're testing the waters of SRU extensions I think what is
lacking here is a process more than any technical capability. I'm
thinking something like the following could work:

1. someone suggests the extension on sru-implementors
2. someone drafts the proposed extension and make it available on the web
3. more discussion on sru-implementors about draft
4. someone edits draft appropriately
5. a group votes (not sure who)
6. publish draft (or not)

Does something like this already exist? Or is it just:

1. try to convince someone who controls the web pages
2. publish

I only bring this up because I feel like I really need 2 to understand
the current discussion.

//Ed