Re: OASIS website issues

Thanks Norm & just to give a bit more feedback...

First, I want to make sure that there's no confusion between working drafts and approved Work Products - Committee Specification Draft, Committee Specification Public Review Draft, Committee Specification, etc. OASIS provides the infrastructure for working drafts - the Kavi document repository and the SVN repository (which may migrate to Git at some point). Your working drafts migrate to the OASIS platforms when you approve them as CSDs and start the advancement process towards OASIS Standard.

I certainly don't want to give the wrong impression about the activity around DocBook. But I also can't direct people to something that looks like it is an official work product in some way when it is in fact a TC working draft with no official standing from the OASIS process point of view.

If you approve some package of specs as a Committee Draft, then I can load them and make them available from docs.oasis-open.org/docbook.

And you don't have to put them through public review until you are ready to move forward towards CS and then OS. TOSCA went through I think 6 CSDs before they finally went out for public review. If you want to keep things as CSDs, that is not a problem.

I'm ready to talk with the TC and explore possible solutions anytime.

Best,

/chet

On Wed, Jun 19, 2013 at 10:16 AM, Norman Walsh <ndw@nwalsh.com> wrote:

Hi folks,

Pursuant to my action to follow up with OASIS about the issues with
the DocBook files at www.oasis-open.org, I had an email exchange with
Chet Ensign.

It boils down like this:

> Hey Norm, realized I also didn't answer this one:
>
>>> I'm not eliminating anything that has been in place historically.
>>> That is the official record and I would be out of place to change
>>> it. I'm just ensuring that the process is handled going forward.
>>
>> I'm not sure that's appropriate. It means we'll have an aging collection of
>> documents that gives the misleading impression that DocBook development has
>> stalled.
>>
>> I think if updating /docbook is no longer appropriate, we should make all those
>> URIs redirect to a "used-to-be-on-OASIS" landing page on docbook.org.
>
> That would also violate the OASIS rules, specifically sect. 2.8 which starts: "The official
> copies of all resources of the TC and its associated Subcommittees, including web pages,
> documents, email lists and any other records of discussions, must be located only on facilities
> designated by OASIS. TCs and SCs may not conduct official business or technical discussions,
> store documents, or host web pages on servers or systems not designated by OASIS."
>
> Really, what needs to happen is for the TC to get right with God and work within the rules of
> the organization. Work in progress belongs in one of the sanctioned facilities provided and the
> approved Committee Spec Drafts, Committee Specs and OASIS Standards need to advance through the
> normal channels of approvals, public reviews and ballots so that they can be published in the
> archive of record, docs.oasis-open.org.
>
> I am willing to fight to get old URLs redirected to the proper locations on the OASIS
> infrastructure. But not off.

I really don't know what to do next. As far as I can tell, updating
the pages on the OASIS site means sending every change through the
formal review process.

Be seeing you,
norm

--
Norman Walsh <ndw@nwalsh.com> | To create a little flower is the
http://www.oasis-open.org/docbook/ | labour of ages.-- Blake
Chair, DocBook Technical Committee |

--

/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

docbook-tc message