Subject: FW: MOVING TGF to OASIS STANDARD?
As part of our discussions on the timeline for a v2 of the TGF we might consider the possibility of moving v1 to a full OASIS Standard now that the restriction on getting 3 Statements of Use from only OASIS members has been removed. If we think that a v2 is still some way off, say 6-9 months, then we might do well to push v1 to OASIS Standard. Given the guidance below about the form that Statements need to take, ie "Ministry/Organisation is using the TGF etc" I would suggest we could ask CST, Fujitsu, South Australia, Birmingham Council, others, to provide a Statement? What do you think, is this a route we should attempt? John -----Original Message----- From: Chet Ensign [mailto:firstname.lastname@example.org] Sent: 29 November 2011 13:42 To: John Borras Cc: Peter F Brown Subject: Re: FW: [members] (PR) 15-day Public Review for TGF Pattern Language - Core Patterns v1.0 and TGF Primer v1.0 Oh, the quote is "...saying whether its use included...". If interoperation isn't relevant to the application of the specification then of course you needn't provide any. I sent the new definition along mainly because of (a) the bit about listing the conformance clauses that apply and (b) making sure the SoU comes from the Primary Rep. If you have a statement along the lines of "Ministry xx of the government of NZ is using TGF PL v1.0 in its yyy system in compliance with clauses x, y and z. This application does not require interoperation of multiple implementations." then you have met the requirements of the definition. Best, /chet On Tue, Nov 29, 2011 at 3:39 AM, John Borras <email@example.com> wrote: > Peter > > It strikes me that the SOA Reference Model would have the same problem > as us in getting 3 Statements of Use. There's no interoperability > between systems involved in TGF or SOA so how can we give the required > Statements? Perhaps Colin is right, this is one for the TAB. Views? > > John > > -----Original Message----- > From: firstname.lastname@example.org [mailto:email@example.com] On > Behalf Of Colin Wallis > Sent: 28 November 2011 22:26 > To: 'John Borras'; 'TGF TC List' > Subject: RE: [tgf] FW: [members] (PR) 15-day Public Review for TGF > Pattern Language - Core Patterns v1.0 and TGF Primer v1.0 > > Agreed John, it's not applicable. Not only will we need a work around > for our case, (and check what the exemption process is in OASIS) but > alert the TAB. > > Cheers > Colin > > -----Original Message----- > From: firstname.lastname@example.org [mailto:email@example.com] On > Behalf Of John Borras > Sent: Monday, 28 November 2011 9:35 p.m. > To: 'TGF TC List' > Subject: FW: [tgf] FW: [members] (PR) 15-day Public Review for TGF > Pattern Language - Core Patterns v1.0 and TGF Primer v1.0 > > Please see below for an updated requirement for Statements of Use. I > don't see how any of you can say "its use included the interoperation > of multiple independent implementations", that's just not applicable > in the case of the TGF. We'll have to find a work-around for that. > > John > > > -----Original Message----- > From: Chet Ensign [mailto:firstname.lastname@example.org] > Sent: 27 November 2011 14:10 > To: John Borras > Subject: Re: [tgf] FW: [members] (PR) 15-day Public Review for TGF > Pattern Language - Core Patterns v1.0 and TGF Primer v1.0 > > John, just FYI. Check the TC Process as the definition has been > updated - still substantially the same but a bit more detail required: > > In Definitions: "Statement of Use", with respect to a Committee > Specification, is a written statement by an OASIS Organizational > Member stating that it is successfully using or implementing that > specification in accordance with the conformance clauses specified in > Section 2.18, identifying those clauses that apply, and stating > whether its use included the interoperation of multiple independent > implementations. A Statement of Use must be endorsed by the > Organizational Member's Primary Representative." > > On Sun, Nov 27, 2011 at 7:19 AM, John Borras <email@example.com> > wrote: >> If we are quick to deal with any comments arising from this review we > could >> clear them and approve both documents at our next meeting on 15th Dec. >> >> >> >> That would pave the way for going to the next step of full OASIS >> Standard but for that we will need 3 Statements of Use. Below is an >> extract from > the >> TC Handbook on this topic: >> >> Often a Work Product will remain at the Committee Specification stage >> for > a >> period of time while implementations are developed and tested. Only >> when a TC has received at least three Statements of Use from OASIS >> Organizational Members certifying that they have successfully >> implemented or are using > the >> specification in accordance with the specification's conformance >> clause(s) is the TC able to progress the Work Product to Candidate >> OASIS Standard > and >> submit it for OASIS Standard ballot. >> >> Statements of Use: >> >> § A written statement by an OASIS Organizational Member stating that >> it > is >> successfully using or implementing a specification in accordance with >> the conformance clauses stated therein; and stating whether its use >> included > the >> interoperation of multiple independent implementations >> >> I would assume Chris could provide one Statement, but who else - Nig, > Colin, >> ??? We can discuss this on the next call. >> >> >> >> John >> >> >> >> From: firstname.lastname@example.org [mailto:email@example.com] On >> Behalf Of firstname.lastname@example.org >> Sent: 26 November 2011 17:32 >> To: email@example.com; firstname.lastname@example.org; >> email@example.com; firstname.lastname@example.org; >> email@example.com; firstname.lastname@example.org >> Subject: [members] (PR) 15-day Public Review for TGF Pattern Language >> - > Core >> Patterns v1.0 and TGF Primer v1.0 >> >> >> >> The OASIS Transformational Government Framework TC  members have > produced >> an updated Committee Specification Draft (CSD) and Committee Note >> Draft >> (CND) and submitted these drafts for 15-day public review: >> >> Transformational Government Framework (TGF) Pattern Language Core >> Patterns Version 1.0 Committee Specification Draft 02 / Public Review >> Draft 02 >> 16 November 2011 >> >> Transformational Government Framework Primer Version 1.0 Committee >> Note Draft 02 / Public Review Draft 02 >> 16 November 2011 >> >> Specification Overview: >> >> The Transformational Government Framework (TGF) is a practical "how to" >> standard for the design and implementation of an effective program of >> technology-enabled change at national, state or local government >> level. It describes a managed process of ICT-enabled change in the >> public sector, which puts the needs of citizens and businesses at the >> heart of that > process >> and which achieves significant and transformational impacts on the >> efficiency and effectiveness of government. >> >> The TGF Pattern Language is a formalization of the Framework that is >> both human-readable and machine-tractable. This document constitutes >> the > initial >> set of patterns that form the core of the TGF Pattern Language. This >> set > may >> be revised and/or extended from time to time as appropriate. >> >> The TGF Primer is intended to serve as an introduction to and >> detailed overview of the Framework. It also covers the Framework's >> rationale, purpose, scope, and intended use. >> >> TC Description: >> The Transformational Government TC is advancing an overall framework >> for using information technology to improve the delivery of public services. >> Unlike traditional e-Government strategies of the past, >> Transformational Government begins with citizen engagement to assure >> greater use and return on investment. >> >> The work of the TC includes defining the framework, identifying use >> cases, and providing adoption guidance for governments around the >> world, > regardless >> of their history in implementing eGov. >> >> Public Review Period: >> The public review starts 28 November 2011 and ends 13 December 2011. >> These documents were previously submitted for 30-day public reviews >> . This 15-day review is limited in scope to changes made from the >> previous > review. >> Changes are highlighted in the diff-marked PDFs file included in the >> ZIP files containing the CSPRD and CNPRD drafts. >> >> This is an open invitation to comment. OASIS solicits feedback from >> potential users, developers and others, whether OASIS members or not, >> for the sake of improving the interoperability and quality of its >> technical work. >> >> URIs: >> >> The complete package of the prose specification document and related >> files are available in the ZIP distribution files at: >> >> Transformational Government Framework (TGF) Pattern Language Core >> Patterns Version 1.0 >> > http://www.oasis-open.org/committees/download.php/44449/tgf-pl-core-v1 > .0-csp > rd02.zip >> >> Transformational Government Framework Primer Version 1.0 >> > http://www.oasis-open.org/committees/download.php/44450/tgf-primer-v1. > 0-cnpr > d02.zip >> >> Additional information about the specification and the OASIS >> Transformational Government Framework TC may be found at the TC's >> public home page located at: >> >> http://www.oasis-open.org/committees/tgf/ >> >> Comments may be submitted to the TC by any person through the use of >> the OASIS TC Comment Facility which can be accessed via the button >> labeled > "Send >> A Comment" at the top of the TC public home page, or directly at: >> >> http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=tgf >> >> Feedback submitted by TC non-members for this work and for other work >> of this TC is publicly archived and can be viewed at: >> >> http://lists.oasis-open.org/archives/tgf-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. In connection with these > public >> reviews of TGF Pattern Language - Core Patterns v1.0 and TGF Primer >> v1.0, > we >> call your attention to the OASIS IPR Policy  applicable especially >>  > to >> the work of this technical committee. All members of the TC should be >> familiar with this document, which may create obligations regarding >> the disclosure and availability of a member's patent, copyright, >> trademark and license rights that read on an approved OASIS >> specification. OASIS invites any persons who know of any such claims >> to disclose these if they may be essential to the implementation of >> the above specification, so that notice of them may be posted to the notice page for this TC's work. >> >> ========== Additional references: >> >>  OASIS Transformational Government Framework TC: >> http://www.oasis-open.org/committees/tgf/ >> >>  Public review announcements: >> >> 30-day Public Review for TGF Pattern Language Core Patterns Version >> 1.0, > 26 >> September 2011: >> http://lists.oasis-open.org/archives/tc-announce/201109/msg00008.html >> 30-day Public Review for Transformational Government Framework Primer >> Version 1.0, 28 September 2011: >> http://lists.oasis-open.org/archives/tc-announce/201109/msg00009.html >> >>  http://www.oasis-open.org/who/intellectualproperty.php >> >>  http://www.oasis-open.org/committees/tgf/ipr.php >> http://www.oasis-open.org/policies-guidelines/ipr#licensing_req >> Non-Assertion Mode >> >> Best Regards, >> >> /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-378-3472 >> Mobile: +1 201-341-1393 >> >> --------------------------------------------------------------------- >> This email list is used solely by OASIS for official consortium communications. >> Opt-out requests may be sent to email@example.com, >> however, > all >> members are strongly encouraged to maintain a subscription to this list. > > > > -- > > /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-378-3472 > Mobile: +1 201-341-1393 > > Follow OASIS on: > LinkedIn: http://linkd.in/OASISopen > Twitter: http://twitter.com/OASISopen > Facebook: http://facebook.com/oasis.open > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: firstname.lastname@example.org > For additional commands, e-mail: email@example.com > > ==== > CAUTION: This email message and any attachments contain information > that may be confidential and may be LEGALLY PRIVILEGED. If you are not > the intended recipient, any use, disclosure or copying of this message > or attachments is strictly prohibited. If you have received this email > message in error please notify us immediately and erase all copies of > the message and attachments. Thank you. > ==== > > --------------------------------------------------------------------- > To unsubscribe, e-mail: firstname.lastname@example.org > For additional commands, e-mail: email@example.com > -- /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-378-3472 Mobile: +1 201-341-1393 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open