ReSpec extension architecture question

Robin et. al,

I know that we have discussed a next generation ReSpec.  That's exciting,
but honestly I have more immediate needs and I don't hate the current
architecture.

However, one of my immediate needs I don't have a clear idea how to
satisfy.  I could use some help.

The PFWG is developing a core ARIA spec and now has an environment in which
it is possible to define extension specs.  The extension specs will be
referencing LOTS of stuff in the core spec, and will also need some
(relatively dynamic) data structures from the core spec in order to
populate certain parts of the extension spec so that it is a seamless
extension.

That's great, and I have a design for it.  However, in order to support the
design, I really need a way to easily stringify some JS structures from the
core spec and save them.  That's not terribly challenging code-wise.  But I
really want to add an item to the ReSpec UI pull down menu.  Something like
"Save Role Info" that would generate a specific file and let the user save
it to disk.

I could pour through the code and find a hook for this.  Or add one if it
doesn't exist.  But I have 100 other things to do too, so before I do that,
help?  Is there an easy way for a ReSpec document to add to the UI without
creating a custom profile?  Or is there some other clever way to get this
data out of one spec and into another without building a backend data
service?

-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.