OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-rm] Revised SOA-RM Editor Role Descriptions Document

We should explicitly state that each active member of the TC is an author of the resulting document. Authoring is the preeminant role, an editor is to convey the ideas and if necessary enhance the communication through wordsmithing, organization and presentation.
I am concerned that the tact we are taking  will lead to more volume in the document than is needed. Personally I believe that we could probably get away with one picture and some explainatory text. I also know that it is harder to write a short document than a long one especially when trying to communicate new ideas.
I concur with the suggestion I believe was made by Frank McCabe to wait until we get to know each other before we decide on an editorial team (and I would add editorial approach).
I do take issue with your proposal "..     each assigned the responsibility of maintaining a distinct and meaningful portion of the reference model". This presupposes what the end product is, and determining what is the reference model is what we are trying to accomplish.

While I do not feel it is necessary that 'my words' be used I am interested in insuring that ideas and concepts are portrayed in the manner the author intended. It would appear that virtually every contributor will be an editor. Following the approach we are on I too want to be an editor.


Thomas Erl <terl@serviceorientation.org> wrote:
I have uploaded a revised version of the "Proposed Role Descriptions for
SOA-RM Editors" document that takes into account feedback received since it
was originally published.

For those of you interested, here is a summary of the changes:

- There have been suggestions that the role of the individual who assumes
responsibility for assembling a master document from the editor
contributions be labeled as "Chief Editor" or "Lead Editor". There was a
subsequent objection to the use of any terminology that would imply a
hierarchy or authority on the part of this role. The term "Custodian" has
been suggested, so I changed the term to "Editor & Custodian".

- There was a further objection to the notion that the Editor & Custodian be
in any way distinguished from the other editors. It is therefore being
proposed that all editors be listed (in alphabetical order by last name) as
equal contributors on the SOA-RM specification. This is in line with our
goal of balancing the workload across all members of the team.

Please let me know if there are any further objections or change requests.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]