[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm-ra] Fwd: [soa-rm] Public Review of Reference Architecture Foundation for Service Oriented Architecture Version 1.0
No problem! Mary On Nov 15, 2009, at 9:26 PM, Rex Brooks wrote: > Hi Mary, > > No, I did not mean that any changes in the text of the document were missing. I was referring only to the filename and title page. > > My understanding is that a TC votes to approve a Working Draft as a Committee Draft, and then the actual document is produced with the correct filename (using "cd"), title page (using "Committee Draft") and date. > > Then the TC then votes to approve the Committee Draft for Public Review, at which time (even if it is in the same TC meeting) the Committee Draft is changed to a Public Review Draft on the title page and the filename is changed from "-cd0x-rev0x" to "-pr0x-rev0x" per the naming convention example: > > http://docs.oasis-open.org/exampleTC/nutMarkup/v2/nut2.0-pr02-rev03.pdf > > which is found at http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata.html#specURIs . > > However, the previous examples don't use the .../nut/nut20.-pr02-rev03 and the text above the example reads: > > "This example is not intended to imply, e.g., that the path/filename design here illustrated MUST be used in any similar situation. Most matters of filename design and URI design are left to the discretion of TCs." > > So, this is apparently a moot point. > > My misunderstanding. Apologies. > > Cheers, > Rex > > Mary McRae wrote: >> Hi Rex, >> >> Not sure what you're referring to - CD03 was approved to send for public review; creation of another unique version as PR isn't necessary; in fact it only complicates matters since that would mean the previous version of PR02 would be CD03 - in effect the same version. Filenames are determined by the TC; I used what was supplied. >> >> The next step in the approval process will be as Committee Specification; that happens post-review depending on comments received and TC's desired steps. >> >> Are you saying that what was submitted to me does not include some changes that were to be incorporated in the spec prior to public review submission? I have no control over that; I highly recommend TCs do not approve something as a CD until all of the editorial changes have, in fact, been made and verified. >> >> Regards, >> >> Mary >> >> >> Mary P McRae >> Director, Standards Development >> Technical Committee Administrator >> OASIS: Advancing open standards for the information society >> email: mary.mcrae@oasis-open.org web: www.oasis-open.org >> twitter: @fiberartisan #oasisopen >> phone: 1.603.232.9090 >> >> Standards are like parachutes: they work best when they're open. >> >> >> >> On Nov 15, 2009, at 2:43 PM, Rex Brooks wrote: >> >> >>> HI Ken, Everyone, >>> >>> I didn't check what we sent out last time, but I sent the following message below the horizontal rule, as explanation when I forwarded the official announcement. >>> (I didn't want to cause more delay so I did not point out to Mary that the PR release should have the pr designation in the filename and the indication of Public Review Draft on the title page. Since getting it out was the priority and we can fix the foobars, I just let it go, but I will personally double check it before the final goes out since it needs the progression from cd-03 to pr-03 to (hopefully after approval) os (OASIS Standard). Apparently all that happened was that the last set of changes were not made. At least we have the cd designation in the filename and the title page designation of Committee Draft correct. This is not the time for showstoppers. >>> >>> Here's what I added to the official notification: >>> >>> ------------------------------------------------------------------------ >>> To: NCOIC Services WG, NEER-IPT, >>> >>> I am forwarding the announcement of the Public Review that starts today of the Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF) Version 1.0 from the OASIS Service Oriented Architecture Reference Model Technical Committee (SOA-RM TC). >>> >>> This is a 60-Day Public Review and the instructions for making comments are included in the message below. We consider it critical to get the highest level of feedback we can from the groups we consider key stakeholders, such as NCOIC. For those of you who have been using an earlier draft, it is strongly urged that you download and use the document of record from the url in the message below. We prefer that comments be as specific as possible, citing the section number(s) and line number(s) to which the comment/issue refers. >>> >>> This is considered a major milestone in the process of delivering the best foundation for more concrete specific SOA reference architectures based on the OASIS Reference Model for Service Oriented Architecture (SOA_RM). We consider it the logical elaboration of the SOA-RM. We are asking for feedback at this stage in order to ensure that the finished SOA-RAF will provide the most consistent, measurably usable framework from which specific reference architectures and, ultimately, wholly concrete solution architectures can be developed. With your able assistance, we aim to provide a SOA-RAF with the highest level of confidence that it will fulfill its goals and objectives effectively, efficiently, scalably and durably. >>> >>> Best Regards, >>> Rex Brooks >>> ------------------------------------------------------------------------ >>> Cheers, >>> Rex >>> >>> >>> Ken Laskey wrote: >>> >>>> Congratulations! We have published PR2. >>>> >>>> I'll be sending an email to the soa-rm list encouraging dissemination far and wide, but before I do this, I was looking to see what we sent out as general review guidance when PR1 went out for review. In particular, besides using the Excel spreadsheet internally, did we provide the template externally too? I remember getting a few external comments but I don't remember if we massaged those into our format or if they came in that way. >>>> >>>> I've looked through my email archives and haven't found anything particularly useful. Can anyone else find or recall anything? >>>> >>>> Ken >>>> >>>> Begin forwarded message: >>>> >>>> >>>>> *From: *Mary McRae <mary.mcrae@oasis-open.org <mailto:mary.mcrae@oasis-open.org>> >>>>> *Date: *November 13, 2009 11:41:58 PM EST >>>>> *To: *"members@lists.oasis-open.org <mailto:members@lists.oasis-open.org>" <members@lists.oasis-open.org <mailto:members@lists.oasis-open.org>>, "tc-announce@lists.oasis-open.org <mailto:tc-announce@lists.oasis-open.org>" <tc-announce@lists.oasis-open.org <mailto:tc-announce@lists.oasis-open.org>> >>>>> *Cc: *"soa-rm@lists.oasis-open.org <mailto:soa-rm@lists.oasis-open.org>" <soa-rm@lists.oasis-open.org <mailto:soa-rm@lists.oasis-open.org>>, OASIS TAB <tab@lists. >>>>> oasis-open.org> >>>>> *Subject: **[soa-rm] Public Review of Reference Architecture Foundation for Service Oriented Architecture Version 1.0* >>>>> >>>>> To OASIS members, Public Announce Lists: >>>>> >>>>> The OASIS Service Oriented Architecture Reference Model TC has recently approved the following specification as a Committee Draft and approved the package for public review: >>>>> >>>>> Reference Architecture Foundation for Service Oriented Architecture Version 1.0 >>>>> >>>>> The public review starts today, 14 November 2009, and ends 13 January 2009. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. We also welcome interested parties to join the TC as it continues to further development of its specifications. Please feel free to distribute this announcement within your organization and to other appropriate mail lists. >>>>> >>>>> More non-normative information about the specification and the technical committee may be found at the public home page of the TC at: >>>>> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at: >>>>> http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=soa-rm. >>>>> >>>>> Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at: >>>>> http://lists.oasis-open.org/archives/soa-rm-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. >>>>> >>>>> The specification document and related files are available here: >>>>> >>>>> Editable Source: >>>>> http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-cd-02.doc >>>>> PDF: >>>>> http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-cd-02.pdf >>>>> HTML: >>>>> http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-cd-02.html >>>>> >>>>> >>>>> This specification was previous submitted for a 60-day review on 9 May 2008 under the title: Reference Architecture for Service Oriented Architecture Version 1.0.[1] >>>>> >>>>> OASIS and the OASIS Service Oriented Architecture Reference Model TC welcome your comments. >>>>> >>>>> >>>>> Mary P McRae >>>>> Director, Standards Development and Technical Committee Administration >>>>> OASIS: Advancing open standards for the information society >>>>> email: mary.mcrae@oasis-open.org >>>>> web: www.oasis-open.org >>>>> twitter: @fiberartisan #oasisopen >>>>> phone: 1.603.232.9090 >>>>> >>>>> >>>>> [1] http://lists.oasis-open.org/archives/tc-announce/200805/msg00003.html >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this mail list, you must leave the OASIS TC that >>>>> generates this mail. Follow this link to all your TCs in OASIS at: >>>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>>>> >>>>> >>>> ----------------------------------------------------------------------------- >>>> Ken Laskey >>>> MITRE Corporation, M/S H305 phone: 703-983-7934 >>>> 7515 Colshire Drive fax: 703-983-1379 >>>> McLean VA 22102-7508 >>>> >>>> >>>> >>>> >>>> >>>> >>> -- >>> Rex Brooks >>> President, CEO >>> Starbourne Communications Design >>> GeoAddress: 1361-A Addison >>> Berkeley, CA 94702 >>> Tel: 510-898-0670 >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >> >> > > > -- > Rex Brooks > President, CEO > Starbourne Communications Design > GeoAddress: 1361-A Addison > Berkeley, CA 94702 > Tel: 510-898-0670 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]