FYI, BINDMAPers… related to “anonymous publishing” and any other similar topic that comes up.
From:
Chet Ensign [mailto:]
Sent: Wednesday, March 13, 2013 5:56 PM
To: Steve Huston
Subject: Re: [amqp-bindmap] RE: Cross-TC work product?
Hi Steve,
I saw this. So then yes, you should just decide which TC will develop it, request a working draft template from TC Admin and treat it as a standards track work product. That way, it will end up published with all the other TC work products on the OASIS Library.
You may want to consider whether you would ever expect to see such documents reach OASIS Standard stage or not.
DITA for example is going to create several packages of the overall DITA spec (using some but not all) but they are going to include it in the full spec package so that it can all become an OASIS Standard in one vote. XACML on the other hand has a bunch of associated standards work products that stand on their own and are currently at CS stage and may stay that way.
As for 'not standing on its own' - our cover page has a section for Related content and there you can say 'this works in conjunction with AMQP v1.0' - so there are ample ways to indicate that a work product goes hand in hand with a larger piece.
/chet
On Wed, Mar 13, 2013 at 12:21 PM, Steve Huston <
> wrote:
We talked about this in our meeting yesterday; it is definitely not an internal committee type of thing. It will more likely be normative.
From:
[mailto: ] On Behalf Of Steve Huston
Sent: Monday, March 11, 2013 3:31 PM
To:
Subject: [amqp-bindmap] FW: Cross-TC work product?
What do you think folks? Is “anonymous publishing” a normative work, or more committee note?
From:
Chet Ensign [ mailto: ]
Sent: Monday, March 11, 2013 2:24 PM
To: Steve Huston
Subject: Re: Cross-TC work product?
Hmm. Steve, is this a normative piece of work or could it be considered a Committee Note - an explanatory piece on how to accomplish something using AMQP?
/chet
On Mon, Mar 11, 2013 at 2:08 PM, Steve Huston <
> wrote:
Hi Chet,
We have a curious situation in the AMQP Binding and Mappings (BINDMAP)
TC I'd like your opinion on. There's a technical area called "anonymous publishing" which arose during work on a BINDMAP area - this came up in the context of JMS mapping work in the TC, but it's a common area which will probably come up in other AMQP work in both the BINDMAP and core AMQP TC efforts. What's the best way to handle this from OASIS point of view? I was thinking that it should be a committee draft, probably in AMQP (but that's debatable), but it will be very short and wouldn't stand on its own - it doesn't make sense outside of AMQP. But if it were an internal TC document, it wouldn't be visible outside OASIS, and that's not what we really want either in order to remain open.
Some other members of the TC think this type of decision will probably arise again, so we would like your opinion on how to best handle it.
Thoughts?
Thanks, -Steve Huston Chair, AMQP BINDMAP
--
/chet
----------------
Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on: LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
--
/chet
----------------
Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on: LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
