Technical Advisory Board (TAB)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! I continue to find: "TCs should be the main driver behind their self-certification program. But OASIS should facilitate or at least supervise and exercise managerial oversight." Deeply problematic. Not just for the politics but for the implication that TCs propose and move forward with self-certification without express OASIS approval. Recall that we have all agreed that there will be a substantial burden on both OASIS and the participants to undertake such a program. I cringe at the thought of a TC deciding with excess enthusiasm that they want to do self-certification and entangling OASIS in that effort, only to fail to follow through. Which would devalue the entire process at OASIS. Could we say something along the lines of: "OASIS should create an administrative structure to review self-certification proposals that originate in TCs, judging such proposals on the basis of commitments to provide resources, completeness, and maturity of the proposals. Not every proposals for self-certification need be accepted as an OASIS sponsored self-certification effort." Should a TC want to go elsewhere to fail at self-certification, it won't reflect badly on the OASIS self-certification program. Yes, the TC supplies the request and resources, but given the involvement of the OASIS brand, OASIS should have its hand on the start switch. Hope everyone is at the start of a great week! Patrick PS: I may have a few more comments but I need to get to the PR that is due tomorrow. - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWN5ejAAoJEFPGsgi3MgycSTgP/AtXqWsfPjyUriky9Vd5gy8t ubi/Vzb1ek1fEmOu3KHUauO4TNA18gaHV4rWbTdiu5pEN03L+O50uZZQaEzTzrD7 mpN2qVkB/+Xg9mVlnuh1B/JEaZeSOsOQJ8qJHPiqOM0IxE2BXXt6x3gWhYQtEMez OA9NUewnd/pV5quYCC3EgiVwbEEhVr1Q7tRTR/2zrABQK3yVLTVWDYhhkld4z6/i P5+2ehb92nrsNymH0UwAVwZskGqh1GTwK9RMEZntzsXNoQeifrcvpVuETv5N3Ntz K6uaSrfTJr3+aekL/iuHsYjmrhAA1fmg1aw7eYSh9G5t2La7EbFMx4M1bldFpSpj 2kIE1H2uyHf9+umYGM+lZvtjdQCqdCUsnpjxx2wYDErsK2khbBtjNIfeLYsThW4q 5TI5mEZ7xbJpCePmwzKq/xB7l3ls+JK8NfrxVgla2RKIc9bLWopd4Gg/4IEZC808 lSQz+Hpz6UMSZnKBmxFnHWT/V0McooNp71MaxqMEW19/x0+KRM/EwqruK98Te06D 7hpOSBx5/gFxk9RcwZQ6JdKxGo/hUBdDjkTrkMWsBkQsrPwcYJnoj2+yZSeOXHGc 5FQR5FYSxP7MAgpyoQCY2l206NDHa7nruQLcwl5hFJVPjkIhH37PoeKy+JC7BrLx iEvvMVGK9MoawT5Fvq/d =FCAV -----END PGP SIGNATURE-----

I strongly resonate with Patrick's comment and suggested edit. An even more concise edit might be: "OASIS Staff and Board should work with TCs expressing interest in self-certification to determine the viability of their proposal and whether it can result in an OASIS-sponsored self-certification effort." The reason it's phrased this way: it's unlikely that a TC would just go and formulate a self-cert proposal without consulting with Chet along the way. My sense is that we would have our technical and biz-dev team involved from the onset. Or pro-actively ask whether self-cert or cert is in the TC's "business-plan", same way we ask about interop demos or plugfests today. This excellent document has got me thinking about cost and the way other orgs have solved the problem of putting the tests together. Don Thibeau explained how OIX banded with several European agencies to get FP7 funding for development; which was very clever but might be difficult to emulate. As you probably recall, SAML testing was developed for Kantara by Rik Drummond's company. The startup cost was quite high [but this was a higher level of testing than self-cert]. Testing for OASIS Energy Interop (a.k.a. ADR) is done outside OASIS in OpenADR. The tests were outsourced to an Indian company. [Seems to happen a lot, with good results]. KMIP is doing self-cert on hardware hosted by SNIA. While we are missing out on these opportunities, those three are not examples of projects we would have pursued. In fact we had to admit that we were not in the business of hosting testing environments when KMIP asked us to partner with SNIA. But CTI comes to mind as a project we could sink our teeth in. TOSCA is a close second. On 11/2/2015 9:04 AM, Patrick Durusau wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! I continue to find: "TCs should be the main driver behind their self-certification program. But OASIS should facilitate or at least supervise and exercise managerial oversight." Deeply problematic. Not just for the politics but for the implication that TCs propose and move forward with self-certification without express OASIS approval. Recall that we have all agreed that there will be a substantial burden on both OASIS and the participants to undertake such a program. I cringe at the thought of a TC deciding with excess enthusiasm that they want to do self-certification and entangling OASIS in that effort, only to fail to follow through. Which would devalue the entire process at OASIS. Could we say something along the lines of: "OASIS should create an administrative structure to review self-certification proposals that originate in TCs, judging such proposals on the basis of commitments to provide resources, completeness, and maturity of the proposals. Not every proposals for self-certification need be accepted as an OASIS sponsored self-certification effort." Should a TC want to go elsewhere to fail at self-certification, it won't reflect badly on the OASIS self-certification program. Yes, the TC supplies the request and resources, but given the involvement of the OASIS brand, OASIS should have its hand on the start switch. Hope everyone is at the start of a great week! Patrick PS: I may have a few more comments but I need to get to the PR that is due tomorrow. - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWN5ejAAoJEFPGsgi3MgycSTgP/AtXqWsfPjyUriky9Vd5gy8t ubi/Vzb1ek1fEmOu3KHUauO4TNA18gaHV4rWbTdiu5pEN03L+O50uZZQaEzTzrD7 mpN2qVkB/+Xg9mVlnuh1B/JEaZeSOsOQJ8qJHPiqOM0IxE2BXXt6x3gWhYQtEMez OA9NUewnd/pV5quYCC3EgiVwbEEhVr1Q7tRTR/2zrABQK3yVLTVWDYhhkld4z6/i P5+2ehb92nrsNymH0UwAVwZskGqh1GTwK9RMEZntzsXNoQeifrcvpVuETv5N3Ntz K6uaSrfTJr3+aekL/iuHsYjmrhAA1fmg1aw7eYSh9G5t2La7EbFMx4M1bldFpSpj 2kIE1H2uyHf9+umYGM+lZvtjdQCqdCUsnpjxx2wYDErsK2khbBtjNIfeLYsThW4q 5TI5mEZ7xbJpCePmwzKq/xB7l3ls+JK8NfrxVgla2RKIc9bLWopd4Gg/4IEZC808 lSQz+Hpz6UMSZnKBmxFnHWT/V0McooNp71MaxqMEW19/x0+KRM/EwqruK98Te06D 7hpOSBx5/gFxk9RcwZQ6JdKxGo/hUBdDjkTrkMWsBkQsrPwcYJnoj2+yZSeOXHGc 5FQR5FYSxP7MAgpyoQCY2l206NDHa7nruQLcwl5hFJVPjkIhH37PoeKy+JC7BrLx iEvvMVGK9MoawT5Fvq/d =FCAV -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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 -- Laurent Liscia, CEO OASIS: Advancing open standards for the information society (510) 669-1261 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open Take a tour of OASIS at: http://www.oasis-open.org/home/tour.php

I worked that in like this:  " TCs should be the main driver behind  their self-certification program. OASIS staff should work with TCs expressing interest in self-certification to determine the viability of their proposal and whether it can result in an OASIS-sponsored self-certification effort. If the proposal is deemed viable, OASIS should supervise and exercise managerial oversight similar to the way staff manages TCs today ."    On Mon, Nov 2, 2015 at 12:30 PM, Laurent M Liscia < laurent.liscia@oasis-open.org > wrote: I strongly resonate with Patrick's comment and suggested edit. An even more concise edit might be: "OASIS Staff and Board should work with TCs expressing interest in self-certification to determine the viability of their proposal and whether it can result in an OASIS-sponsored self-certification effort." The reason it's phrased this way: it's unlikely that a TC would just go and formulate a self-cert proposal without consulting with Chet along the way. My sense is that we would have our technical and biz-dev team involved from the onset. Or pro-actively ask whether self-cert or cert is in the TC's "business-plan", same way we ask about interop demos or plugfests today. This excellent document has got me thinking about cost and the way other orgs have solved the problem of putting the tests together. Don Thibeau explained how OIX banded with several European agencies to get FP7 funding for development; which was very clever but might be difficult to emulate. As you probably recall, SAML testing was developed for Kantara by Rik Drummond's company. The startup cost was quite high [but this was a higher level of testing than self-cert]. Testing for OASIS Energy Interop (a.k.a. ADR) is done outside OASIS in OpenADR. The tests were outsourced to an Indian company. [Seems to happen a lot, with good results]. KMIP is doing self-cert on hardware hosted by SNIA. While we are missing out on these opportunities, those three are not examples of projects we would have pursued.  In fact we had to admit that we were not in the business of hosting testing environments when KMIP asked us to partner with SNIA. But CTI comes to mind as a project we could sink our teeth in. TOSCA is a close second. On 11/2/2015 9:04 AM, Patrick Durusau wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! I continue to find: "TCs should be the main driver behind  their self-certification program. But OASIS should facilitate or at least supervise and exercise managerial oversight." Deeply problematic. Not just for the politics but for the implication that TCs propose and move forward with self-certification without express OASIS approval. Recall that we have all agreed that there will be a substantial burden on both OASIS and the participants to undertake such a program. I cringe at the thought of a TC deciding with excess enthusiasm that they want to do self-certification and entangling OASIS in that effort, only to fail to follow through. Which would devalue the entire process at OASIS. Could we say something along the lines of: "OASIS should create an administrative structure to review self-certification proposals that originate in TCs, judging such proposals on the basis of commitments to provide resources, completeness, and maturity of the proposals. Not every proposals for self-certification need be accepted as an OASIS sponsored self-certification effort." Should a TC want to go elsewhere to fail at self-certification, it won't reflect badly on the OASIS self-certification program. Yes, the TC supplies the request and resources, but given the involvement of the OASIS brand, OASIS should have its hand on the start switch. Hope everyone is at the start of a great week! Patrick PS: I may have a few more comments but I need to get to the PR that is due tomorrow. - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWN5ejAAoJEFPGsgi3MgycSTgP/AtXqWsfPjyUriky9Vd5gy8t ubi/Vzb1ek1fEmOu3KHUauO4TNA18gaHV4rWbTdiu5pEN03L+O50uZZQaEzTzrD7 mpN2qVkB/+Xg9mVlnuh1B/JEaZeSOsOQJ8qJHPiqOM0IxE2BXXt6x3gWhYQtEMez OA9NUewnd/pV5quYCC3EgiVwbEEhVr1Q7tRTR/2zrABQK3yVLTVWDYhhkld4z6/i P5+2ehb92nrsNymH0UwAVwZskGqh1GTwK9RMEZntzsXNoQeifrcvpVuETv5N3Ntz K6uaSrfTJr3+aekL/iuHsYjmrhAA1fmg1aw7eYSh9G5t2La7EbFMx4M1bldFpSpj 2kIE1H2uyHf9+umYGM+lZvtjdQCqdCUsnpjxx2wYDErsK2khbBtjNIfeLYsThW4q 5TI5mEZ7xbJpCePmwzKq/xB7l3ls+JK8NfrxVgla2RKIc9bLWopd4Gg/4IEZC808 lSQz+Hpz6UMSZnKBmxFnHWT/V0McooNp71MaxqMEW19/x0+KRM/EwqruK98Te06D 7hpOSBx5/gFxk9RcwZQ6JdKxGo/hUBdDjkTrkMWsBkQsrPwcYJnoj2+yZSeOXHGc 5FQR5FYSxP7MAgpyoQCY2l206NDHa7nruQLcwl5hFJVPjkIhH37PoeKy+JC7BrLx iEvvMVGK9MoawT5Fvq/d =FCAV -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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 -- Laurent Liscia, CEO OASIS: Advancing open standards for the information society (510) 669-1261 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open Take a tour of OASIS at: http://www.oasis-open.org/home/tour.php --------------------------------------------------------------------- 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 -- /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 

Works well for me - thanks Chet and Patrick. On 11/2/2015 10:20 AM, Chet Ensign wrote: I worked that in like this:  TCs should be the main driver behind  their self-certification program. OASIS staff should work with TCs expressing interest in self-certification to determine the viability of their proposal and whether it can result in an OASIS-sponsored self-certification effort. If the proposal is deemed viable, OASIS should supervise and exercise managerial oversight similar to the way staff manages TCs today .     On Mon, Nov 2, 2015 at 12:30 PM, Laurent M Liscia < laurent.liscia@oasis-open.org > wrote: I strongly resonate with Patrick's comment and suggested edit. An even more concise edit might be: OASIS Staff and Board should work with TCs expressing interest in self-certification to determine the viability of their proposal and whether it can result in an OASIS-sponsored self-certification effort. The reason it's phrased this way: it's unlikely that a TC would just go and formulate a self-cert proposal without consulting with Chet along the way. My sense is that we would have our technical and biz-dev team involved from the onset. Or pro-actively ask whether self-cert or cert is in the TC's business-plan , same way we ask about interop demos or plugfests today. This excellent document has got me thinking about cost and the way other orgs have solved the problem of putting the tests together. Don Thibeau explained how OIX banded with several European agencies to get FP7 funding for development; which was very clever but might be difficult to emulate. As you probably recall, SAML testing was developed for Kantara by Rik Drummond's company. The startup cost was quite high [but this was a higher level of testing than self-cert]. Testing for OASIS Energy Interop (a.k.a. ADR) is done outside OASIS in OpenADR. The tests were outsourced to an Indian company. [Seems to happen a lot, with good results]. KMIP is doing self-cert on hardware hosted by SNIA. While we are missing out on these opportunities, those three are not examples of projects we would have pursued.  In fact we had to admit that we were not in the business of hosting testing environments when KMIP asked us to partner with SNIA. But CTI comes to mind as a project we could sink our teeth in. TOSCA is a close second. On 11/2/2015 9:04 AM, Patrick Durusau wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! I continue to find: TCs should be the main driver behind  their self-certification program. But OASIS should facilitate or at least supervise and exercise managerial oversight. Deeply problematic. Not just for the politics but for the implication that TCs propose and move forward with self-certification without express OASIS approval. Recall that we have all agreed that there will be a substantial burden on both OASIS and the participants to undertake such a program. I cringe at the thought of a TC deciding with excess enthusiasm that they want to do self-certification and entangling OASIS in that effort, only to fail to follow through. Which would devalue the entire process at OASIS. Could we say something along the lines of: OASIS should create an administrative structure to review self-certification proposals that originate in TCs, judging such proposals on the basis of commitments to provide resources, completeness, and maturity of the proposals. Not every proposals for self-certification need be accepted as an OASIS sponsored self-certification effort. Should a TC want to go elsewhere to fail at self-certification, it won't reflect badly on the OASIS self-certification program. Yes, the TC supplies the request and resources, but given the involvement of the OASIS brand, OASIS should have its hand on the start switch. Hope everyone is at the start of a great week! Patrick PS: I may have a few more comments but I need to get to the PR that is due tomorrow. - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWN5ejAAoJEFPGsgi3MgycSTgP/AtXqWsfPjyUriky9Vd5gy8t ubi/Vzb1ek1fEmOu3KHUauO4TNA18gaHV4rWbTdiu5pEN03L+O50uZZQaEzTzrD7 mpN2qVkB/+Xg9mVlnuh1B/JEaZeSOsOQJ8qJHPiqOM0IxE2BXXt6x3gWhYQtEMez OA9NUewnd/pV5quYCC3EgiVwbEEhVr1Q7tRTR/2zrABQK3yVLTVWDYhhkld4z6/i P5+2ehb92nrsNymH0UwAVwZskGqh1GTwK9RMEZntzsXNoQeifrcvpVuETv5N3Ntz K6uaSrfTJr3+aekL/iuHsYjmrhAA1fmg1aw7eYSh9G5t2La7EbFMx4M1bldFpSpj 2kIE1H2uyHf9+umYGM+lZvtjdQCqdCUsnpjxx2wYDErsK2khbBtjNIfeLYsThW4q 5TI5mEZ7xbJpCePmwzKq/xB7l3ls+JK8NfrxVgla2RKIc9bLWopd4Gg/4IEZC808 lSQz+Hpz6UMSZnKBmxFnHWT/V0McooNp71MaxqMEW19/x0+KRM/EwqruK98Te06D 7hpOSBx5/gFxk9RcwZQ6JdKxGo/hUBdDjkTrkMWsBkQsrPwcYJnoj2+yZSeOXHGc 5FQR5FYSxP7MAgpyoQCY2l206NDHa7nruQLcwl5hFJVPjkIhH37PoeKy+JC7BrLx iEvvMVGK9MoawT5Fvq/d =FCAV -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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 -- Laurent Liscia, CEO OASIS: Advancing open standards for the information society (510) 669-1261 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open Take a tour of OASIS at: http://www.oasis-open.org/home/tour.php --------------------------------------------------------------------- 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 -- /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  -- Laurent Liscia, CEO OASIS: Advancing open standards for the information society (510) 669-1261 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open Take a tour of OASIS at: http://www.oasis-open.org/home/tour.php