OASIS Transformational Government Framework TC

Hi all,  I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.  -  [Brown 2011]           P. Brown,   Introducing Pattern Languages ,   http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error  - " As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "   -- returns a 404 in the Civil Service web page  - " A good example of Supplier Management Guidelines is available at:   www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists  Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.  If you prefer to fix them, here are the steps to take.  1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.  2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.  3. After that ballot passes, we will be back on track.  If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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

Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto:tgf@lists.oasis-open.org] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - "As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "  -- returns a 404 in the Civil Service web page    - "A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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  

You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD.  The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be:  - Create an Errata draft as a Committee Specification Draft and a copy of the OS with applied errata to go with it. Put that out for 15 day public review.  - After the review, vote to approve it as an Approved Errata. We then publish the Approved Errata and the OASIS Standard with Approved Errata and update the Latest Version links to point to the OS with Approved Errata.  This is all covered under section 3.4.2 Public Review of a Candidate OASIS Standard. (Sorry to bore with a long email but want you to know your options...) Choices and timelines are:  1. Fix now as Non-Material Change, vote for CS, vote again to COS. The hit is about 3 weeks to get back where we are now.  2. Proceed with 60 day public review. *If* no comments received during the review, go to OS vote. *If* OS vote passes, publish OS and proceed with Errata. No hit timewise, some extra steps & time for you at the end.  3. Proceed with 60 day public review. *If* comments received on the broken links, request Sp Maj Vote to continue to OS vote anyway. If OS vote passes, continue with errata process. The hit is an extra 8 to 10 days while you take the steps to request the ballot, etc.  4. Proceed with 60 day public review. Proceed with OS vote. If OS vote fails to pass, go back to CSD stage and start again.  So, your safest option is to fix it now, incurring about another 3 weeks to work things through. The other options carry some risk, mainly of negative PR and possible impact on the OS vote. If you get through the OS vote ok, you can fix with the errata process after the OS is published.  Best,  /chet On Wed, Dec 12, 2012 at 9:26 AM, John Borras < johnaborras@yahoo.co.uk > wrote: Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto: tgf@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - "As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "  -- returns a 404 in the Civil Service web page    - "A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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

TC Members   A quick straw poll please, replies in next 24 hours if possible.  Which way dos anyone feel we should go?   Seems like the fix now option is the best in the long run even though it introduces a little delay?   No doubt Peter can fix the link to his website and I’ll sort out the other two links which UK Gov has moved.   John   From: Chet Ensign [mailto:chet.ensign@oasis-open.org] Sent: 12 December 2012 14:44 To: John Borras Cc: Paul Knight; Anne Hendry; TGF TC List Subject: Re: [tgf] Question re TGF Pattern Language Core COS01   You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD.    The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be:    - Create an Errata draft as a Committee Specification Draft and a copy of the OS with applied errata to go with it. Put that out for 15 day public review.    - After the review, vote to approve it as an Approved Errata. We then publish the Approved Errata and the OASIS Standard with Approved Errata and update the Latest Version links to point to the OS with Approved Errata.    This is all covered under section 3.4.2 Public Review of a Candidate OASIS Standard. (Sorry to bore with a long email but want you to know your options...) Choices and timelines are:    1. Fix now as Non-Material Change, vote for CS, vote again to COS. The hit is about 3 weeks to get back where we are now.    2. Proceed with 60 day public review. *If* no comments received during the review, go to OS vote. *If* OS vote passes, publish OS and proceed with Errata. No hit timewise, some extra steps & time for you at the end.    3. Proceed with 60 day public review. *If* comments received on the broken links, request Sp Maj Vote to continue to OS vote anyway. If OS vote passes, continue with errata process. The hit is an extra 8 to 10 days while you take the steps to request the ballot, etc.    4. Proceed with 60 day public review. Proceed with OS vote. If OS vote fails to pass, go back to CSD stage and start again.    So, your safest option is to fix it now, incurring about another 3 weeks to work things through. The other options carry some risk, mainly of negative PR and possible impact on the OS vote. If you get through the OS vote ok, you can fix with the errata process after the OS is published.    Best,    /chet     On Wed, Dec 12, 2012 at 9:26 AM, John Borras < johnaborras@yahoo.co.uk > wrote: Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto: tgf@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - "As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "  -- returns a 404 in the Civil Service web page    - "A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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  

I concur with you John.  Joe Sent from my smart phone ------------------------------------ Joe Wheeler MTG Management Consultants LLC jdw@mtgmc.com Mobile (206) 849-7772 On Dec 12, 2012, at 6:58 AM, "John Borras" < johnaborras@yahoo.co.uk > wrote: TC Members   A quick straw poll please, replies in next 24 hours if possible.  Which way dos anyone feel we should go?   Seems like the fix now option is the best in the long run even though it introduces a little delay?   No doubt Peter can fix the link to his website and I’ll sort out the other two links which UK Gov has moved.   John   From: Chet Ensign [ mailto:chet.ensign@oasis-open.org ] Sent: 12 December 2012 14:44 To: John Borras Cc: Paul Knight; Anne Hendry; TGF TC List Subject: Re: [tgf] Question re TGF Pattern Language Core COS01   You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD.    The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be:    - Create an Errata draft as a Committee Specification Draft and a copy of the OS with applied errata to go with it. Put that out for 15 day public review.    - After the review, vote to approve it as an Approved Errata. We then publish the Approved Errata and the OASIS Standard with Approved Errata and update the Latest Version links to point to the OS with Approved Errata.    This is all covered under section 3.4.2 Public Review of a Candidate OASIS Standard. (Sorry to bore with a long email but want you to know your options...) Choices and timelines are:    1. Fix now as Non-Material Change, vote for CS, vote again to COS. The hit is about 3 weeks to get back where we are now.    2. Proceed with 60 day public review. *If* no comments received during the review, go to OS vote. *If* OS vote passes, publish OS and proceed with Errata. No hit timewise, some extra steps & time for you at the end.    3. Proceed with 60 day public review. *If* comments received on the broken links, request Sp Maj Vote to continue to OS vote anyway. If OS vote passes, continue with errata process. The hit is an extra 8 to 10 days while you take the steps to request the ballot, etc.    4. Proceed with 60 day public review. Proceed with OS vote. If OS vote fails to pass, go back to CSD stage and start again.    So, your safest option is to fix it now, incurring about another 3 weeks to work things through. The other options carry some risk, mainly of negative PR and possible impact on the OS vote. If you get through the OS vote ok, you can fix with the errata process after the OS is published.    Best,    /chet     On Wed, Dec 12, 2012 at 9:26 AM, John Borras < johnaborras@yahoo.co.uk > wrote: Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto: tgf@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - "As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "  -- returns a 404 in the Civil Service web page    - "A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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  

Ditto.  Fix now. jenny On 12/12/2012 7:57 AM, Joseph D. Wheeler wrote: I concur with you John.  Joe Sent from my smart phone ------------------------------------ Joe Wheeler MTG Management Consultants LLC jdw@mtgmc.com Mobile (206) 849-7772 On Dec 12, 2012, at 6:58 AM, John Borras < johnaborras@yahoo.co.uk > wrote: TC Members   A quick straw poll please, replies in next 24 hours if possible.  Which way dos anyone feel we should go?   Seems like the fix now option is the best in the long run even though it introduces a little delay?   No doubt Peter can fix the link to his website and I’ll sort out the other two links which UK Gov has moved.   John   From: Chet Ensign [ mailto:chet.ensign@oasis-open.org ] Sent: 12 December 2012 14:44 To: John Borras Cc: Paul Knight; Anne Hendry; TGF TC List Subject: Re: [tgf] Question re TGF Pattern Language Core COS01   You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD.    The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be:    - Create an Errata draft as a Committee Specification Draft and a copy of the OS with applied errata to go with it. Put that out for 15 day public review.    - After the review, vote to approve it as an Approved Errata. We then publish the Approved Errata and the OASIS Standard with Approved Errata and update the Latest Version links to point to the OS with Approved Errata.    This is all covered under section 3.4.2 Public Review of a Candidate OASIS Standard. (Sorry to bore with a long email but want you to know your options...) Choices and timelines are:    1. Fix now as Non-Material Change, vote for CS, vote again to COS. The hit is about 3 weeks to get back where we are now.    2. Proceed with 60 day public review. *If* no comments received during the review, go to OS vote. *If* OS vote passes, publish OS and proceed with Errata. No hit timewise, some extra steps & time for you at the end.    3. Proceed with 60 day public review. *If* comments received on the broken links, request Sp Maj Vote to continue to OS vote anyway. If OS vote passes, continue with errata process. The hit is an extra 8 to 10 days while you take the steps to request the ballot, etc.    4. Proceed with 60 day public review. Proceed with OS vote. If OS vote fails to pass, go back to CSD stage and start again.    So, your safest option is to fix it now, incurring about another 3 weeks to work things through. The other options carry some risk, mainly of negative PR and possible impact on the OS vote. If you get through the OS vote ok, you can fix with the errata process after the OS is published.    Best,    /chet     On Wed, Dec 12, 2012 at 9:26 AM, John Borras < johnaborras@yahoo.co.uk > wrote: Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto: tgf@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  .   -- returns a 404 in the Civil Service web page    - A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp   -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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  

Same. From: Jenny Huang Sent: ?12/?13/?2012 3:20 To: Joseph D. Wheeler Cc: John Borras ; TGF TC List ; Paul Knight ; Anne Hendry ; Chet Ensign Subject: Re: [tgf] Question re TGF Pattern Language Core COS01 - URGENT Ditto.  Fix now. jenny On 12/12/2012 7:57 AM, Joseph D. Wheeler wrote: I concur with you John.  Joe Sent from my smart phone ------------------------------------ Joe Wheeler MTG Management Consultants LLC jdw@mtgmc.com Mobile (206) 849-7772 On Dec 12, 2012, at 6:58 AM, "John Borras" < johnaborras@yahoo.co.uk > wrote: TC Members   A quick straw poll please, replies in next 24 hours if possible.  Which way dos anyone feel we should go?   Seems like the fix now option is the best in the long run even though it introduces a little delay?   No doubt Peter can fix the link to his website and I’ll sort out the other two links which UK Gov has moved.   John   From: Chet Ensign [ mailto:chet.ensign@oasis-open.org ] Sent: 12 December 2012 14:44 To: John Borras Cc: Paul Knight; Anne Hendry; TGF TC List Subject: Re: [tgf] Question re TGF Pattern Language Core COS01   You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD.    The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be:    - Create an Errata draft as a Committee Specification Draft and a copy of the OS with applied errata to go with it. Put that out for 15 day public review.    - After the review, vote to approve it as an Approved Errata. We then publish the Approved Errata and the OASIS Standard with Approved Errata and update the Latest Version links to point to the OS with Approved Errata.    This is all covered under section 3.4.2 Public Review of a Candidate OASIS Standard. (Sorry to bore with a long email but want you to know your options...) Choices and timelines are:    1. Fix now as Non-Material Change, vote for CS, vote again to COS. The hit is about 3 weeks to get back where we are now.    2. Proceed with 60 day public review. *If* no comments received during the review, go to OS vote. *If* OS vote passes, publish OS and proceed with Errata. No hit timewise, some extra steps & time for you at the end.    3. Proceed with 60 day public review. *If* comments received on the broken links, request Sp Maj Vote to continue to OS vote anyway. If OS vote passes, continue with errata process. The hit is an extra 8 to 10 days while you take the steps to request the ballot, etc.    4. Proceed with 60 day public review. Proceed with OS vote. If OS vote fails to pass, go back to CSD stage and start again.    So, your safest option is to fix it now, incurring about another 3 weeks to work things through. The other options carry some risk, mainly of negative PR and possible impact on the OS vote. If you get through the OS vote ok, you can fix with the errata process after the OS is published.    Best,    /chet     On Wed, Dec 12, 2012 at 9:26 AM, John Borras < johnaborras@yahoo.co.uk > wrote: Is it alright to carry on with the Public Review and then correct them as part of the comments process?   Surely that’s a quicker route?   John   From: tgf@lists.oasis-open.org [mailto: tgf@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: 12 December 2012 14:22 To: TGF TC List Cc: Paul Knight; Anne Hendry Subject: [tgf] Question re TGF Pattern Language Core COS01   Hi all,    I have a question for the TC. We found several broken links in the TGF Pattern Language Core as we prepared the Candidate OASIS Standard.    -  [Brown 2011]           P. Brown,  Introducing Pattern Languages ,  http://peterfbrown.com/patternlanguages.aspx , March 2011.   -- returns a 404 error    - "As an example see the UK’s eGovernment Competency Framework which is available at  www.civilservice.gov.uk/my-civil-service/networks/professional/it/framework.aspx  . "  -- returns a 404 in the Civil Service web page    - "A good example of Supplier Management Guidelines is available at:  www.ogc.gov.uk/contract_management_strategic_supplier_management.asp  " -- returns a message that the OGC website no longer exists    Before we go any further with processing I'm checking to see if you want to proceed to the public review and OS vote with these broken links in the document.    If you prefer to fix them, here are the steps to take.    1. You can treat them as Non-Material Changes. Fix them, keep a log of the changes, create a new working draft and request a ballot to approve it as a new CS.    2. After that ballot closes, we'll expedite publishing of the fixed CS. You can then request a new ballot to approve the CS as a COS.    3. After that ballot passes, we will be back on track.    If you simply want us to proceed with the current draft. just let me know. The choice is up to you.      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-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   --------------------------------------------------------------------- To unsubscribe, e-mail: tgf-unsubscribe@lists.oasis-open.org For additional commands, e-mail: tgf-help@lists.oasis-open.org

Me too kohn Arnaud Envoyé à partir de Lotus Traveler Joseph D. Wheeler --- Re: [tgf] Question re TGF Pattern Language Core COS01 - URGENT --- De : "Joseph D. Wheeler" <jdw@mtgmc.com> A "John Borras" <johnaborras@yahoo.co.uk> Cc "TGF TC List" <tgf@lists.oasis-open.org>, "Paul Knight " <paul.knight@oasis-open.org>, "Anne Hendry" <anne.hendry@oasis-open.org>, "Chet Ensign" <chet.ensign@oasis-open.org> Date : mer., 12 déc. 2012 15:59 Objet Re: [tgf] Question re TGF Pattern Language Core COS01 - URGENT


I concur with you John. 


Joe

Sent from my smart phone
------------------------------------
Joe Wheeler
MTG Management Consultants LLC
jdw@mtgmc.com
Mobile (206) 849-7772


On Dec 12, 2012, at 6:58 AM, "John Borras" < johnaborras@yahoo.co.uk > wrote:







TC Members
 
A quick straw poll please, replies in next 24 hours if possible.  Which way dos anyone feel we should go?   Seems like the fix now option is the best in the
long run even though it introduces a little delay?
 
No doubt Peter can fix the link to his website and I €™ll sort out the other two links which UK Gov has moved.
 
John
 

From: Chet Ensign [ mailto:chet.ensign@oasis-open.org ]

Sent: 12 December 2012 14:44
To: John Borras
Cc: Paul Knight; Anne Hendry; TGF TC List
Subject: Re: [tgf] Question re TGF Pattern Language Core COS01

 
You don't want to do that. The TC Process says that if you make changes to the COS, you start over with a new CSD. 

 


The faster route would be to put it up for the ballot, approve and publish the OS, and then create an Errata with the links fixed. The process would be: 


 


- Create an Errata draft as a Committee -Vos données ont été tronquées.

Disclaimer