possible plenary discussion: What's the deal for the Target developer?

[Al Gilman <asgilman@iamdigex.net>]

We had a thread of discussion in v2b which started off with some remarks that
Eugene made about "the deal that the target developer commits to" to implement
AIAP-URC.  It has to be clear (at the time of an implementation decision) what
the deal is, so that there are not latent gotchas in what we are expecting
vs. what a target developer is expecting as they decide to implement the 
standard.

This thread remained a loose end in the wrap-up of the v2b discussions.

However, now we have an exercise to tell an overall top-level story.

This would appear to try to describe both

- the parts of the standard
- the deal for an implementing target-developer

in one fell swoop.

This IMHO is not the way to keep the stories clear.  So before we start to
make commitments about what we say are the parts of the standard, perhaps we
should spend some time on the topic of "What is the deal for an
AIAP-URC-implementing target developer?"

I think that this is a separate narrative, i.e. has a separate topic tree,
from "the parts of the standard."  I believe the connections between
the parts of this story and "the parts of the standard" is a many-to-many
graph, not following the same decomposition into subtopics collected into
supertopics.

If people think this is worth plenary time, I would offer to prepare a
presentation to serve as a discussion starter.  Can't promise to have it out
by the two-week rule.  It will not be in the form of a proposed decision,
rather a stalking horse to see how much agreement we can arrive at.  Would
also be glad to see anyone else take this on.  But it might help us to have
this conversation at this plenary.

Al