Technical Advisory Board (TAB)

And if we just worry about HTML, this is a very scriptable app...  - Find an <h tag - Find the number and the title string (the toughest part of the whole enterprise)  - Write an <a tag with an mailto ref in the form  <a href= href= mailto:tosca-comment@lists.oasis-open.org >tosca-comment@lists.oasis-open.org ?subject=Comment%20on%202.1%20Non-Normative%20References"> around a little comment icon - Repeat...  And Patrick, as you noted, marry this with Rob's script that turns -comment emails into JIRA issues and we have a very sweet little comment turnaround enhancment for TCs to use.  Now... how to get it done?  -- /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 Title: Topology and Orchestration Specification for Cloud Applications Version
1.0











Topology and Orchestration Specification for Cloud
Applications Version 1.0

Candidate OASIS Standard 01

11 June 2013







2       Language
Design



The TOSCA language introduces a grammar for describing service
templates by means of Topology Templates and plans. The focus is on design time
aspects, i.e. the description of services to ensure their exchange. Runtime
aspects are addressed by providing a container for specifying models of plans
which support the management of instances of services.

The language provides an extension mechanism that can be
used to extend the definitions with additional vendor-specific or
domain-specific information.

2.1
Dependencies on Other Specifications

TOSCA utilizes the following specifications:


XML Schema 1.0


2.2 Notational Conventions

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL
NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this
document are to be interpreted as described in [RFC2119].

This specification follows XML naming and design rules as
described in [UNCEFACT XMLNDR] , i.e. uses upper
camel-case notation for XML element names and lower camel-case notation for XML
attribute names.

2.3 Normative
References

[RFC2119] S.
Bradner, Key words for use in RFCs to Indicate Requirement Levels , http://www.ietf.org/rfc/rfc2119.txt ,
IETF RFC 2119, March 1997.

[RFC 2396] Uniform Resource Identifiers (URI): Generic
Syntax, RFC 2396, available via http://www.faqs.org/rfcs/rfc2396.html

[XML Base] XML Base (Second Edition), W3C Recommendation,
http://www.w3.org/TR/xmlbase/

[XML Infoset] XML Information
Set, W3C Recommendation, http://www.w3.org/TR/2001/REC-xml-infoset-20011024/


[XML Namespaces] Namespaces
in XML 1.0 (Second Edition), W3C Recommendation, http://www.w3.org/TR/REC-xml-names/

[XML Schema Part 1] XML
Schema Part 1: Structures, W3C Recommendation, October 2004, http://www.w3.org/TR/xmlschema-1/

[XML Schema Part 2] XML
Schema Part 2: Datatypes, W3C Recommendation, October 2004, http://www.w3.org/TR/xmlschema-2/

[XMLSpec] XML
Specification, W3C Recommendation, February 1998, http://www.w3.org/TR/1998/REC-xml-19980210


 

2.4 Non-Normative References

[BPEL 2.0] Web Services
Business Process Execution Language Version 2.0 . OASIS Standard. 11 April
2007. http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html .

[BPMN 2.0] OMG Business
Process Model and Notation (BPMN) Version 2.0, http://www.omg.org/spec/BPMN/2.0/

[OVF] Open
Virtualization Format Specification Version 1.1.0, http://www.dmtf.org/standards/published_documents/DSP0243_1.1.0.pdf

[XPATH 1.0] XML Path
Language (XPath) Version 1.0, W3C Recommendation, November 1999, http://www.w3.org/TR/1999/REC-xpath-19991116

[UNCEFACT XMLNDR] UN/CEFACT XML Naming and Design Rules Technical
Specification, Version 3.0, http://www.unece.org/fileadmin/DAM/cefact/xml/UNCEFACT+XML+NDR+V3p0.pdf






Attachment: comment1.jpeg Description: JPEG image Attachment: oasis-logo.jpg Description: JPEG image

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chet, Thanks! Yes, the rub is getting the section #. The text of a title isn't an issue, that's easy enough to grab and recreate the matched element and put it in the mailto:. The real problem is calculating the section #, which varies according to fairly complex rules. I am looking at the XHTML export script for ODF which may be adaptable to the XSLT we would need for ODF source documents. Thinking if we can adapt that, then we could "export" to ODF-comment version, PDF-comment version and XHTML-comment version. Hope you are having a great day! Patrick On 09/03/2013 06:21 PM, Chet Ensign wrote: > And if we just worry about HTML, this is a very scriptable app... > > - Find an <h tag - Find the number and the title string (the > toughest part of the whole enterprise) - Write an <a tag with an > mailto ref in the form > > <a href=" mailto:tosca-comment@lists.oasis-open.org > ?subject=Comment%20on%202.1%20Non-Normative%20References"> > > around a little comment icon > > - Repeat... > > And Patrick, as you noted, marry this with Rob's script that turns > -comment emails into JIRA issues and we have a very sweet little > comment turnaround enhancment for TCs to use. > > Now... how to get it done? > > > > > --------------------------------------------------------------------- > > 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 > > - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 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.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSJ0bBAAoJEAudyeI2QFGoHOoQALom4vJV2KYmoTvgu2MUPQ7T qJob9J8HfM5qRo8aLF2P/9BQz+nVH8cbV5aFAv2seHFg5rgloUJWfGqQkHP7PqfE /hz/ivcRTSKcw8VBlPRPXF1+R7fFSqyF2IKFqXwx0USyMkAXyFLV8+KhGNHDTv5u w6euuw8u0pvIKOWo1BjBBn+1M97WtPjLqPGbyG9nHEis9oXXRyHvWrkWkHIcXcKp Dm4YQo5MWEzKroIdq/H+h/EiQJGA0uvs8iPWATEKZK9UY7PO/9IcpoEDRYJcDGBe Qme7mRNEq3YIgkWLhkcsDaZWBXRyw9dr08108xKj07fPq1d1/r5vzG2mQZHwo9Fq lG3+nrRARhAjLU/UTfm4OBR0SJoVjMcTQMf3dSck/B78xiLbe4DQwMuxKC4lpb5B AsOqI1ZTTX2cCwequRX5EUogv+K3wJdqqwl5TTjanGPyyGSycn+MGPfLh1DaWfC1 LMgngilx+l2D5xMYyVijuSGrp6cCKBz0TiZf6vrTic1LycBK1nmfJ4YpoebPWD5y 4N35PoTIJO/X3kuw+U+l+lpRe8r3deMkm/8SLAqy+H8XRzkwpNVWBo5h7eKaXSNF ybnV6rI5tlzTeh6VF8WlK6ePyyyDFpmCEsxTdAB7mKZJt1vSviUbkbGBGNL8rcmG RFSmfFbRPNbZXE9aUfRo =ZDGQ -----END PGP SIGNATURE-----

Right now, I'm only thinking of HTML. Where a TC generates their own HTML from XML, we could tell them how to do it. For everything else, I think a simple rule will get it 90% of the time, only missing stuff that is screwed up anyway.  Literally, (a) go to an <h# tag, (b) strip out all the other tags inside it and replace them with blank spaces, (c) reduce any 2 or more blanks spaces to 1 space, (d) remove any line breaks. What you have left is the section number and the title.  Should work for the vast majority of our HTML files.  /c On Wed, Sep 4, 2013 at 10:42 AM, Patrick Durusau < patrick@durusau.net > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chet, Thanks! Yes, the rub is getting the section #. The text of a title isn't an issue, that's easy enough to grab and recreate the matched element and put it in the mailto:. The real problem is calculating the section #, which varies according to fairly complex rules. I am looking at the XHTML export script for ODF which may be adaptable to the XSLT we would need for ODF source documents. Thinking if we can adapt that, then we could "export" to ODF-comment version, PDF-comment version and XHTML-comment version. Hope you are having a great day! Patrick On 09/03/2013 06:21 PM, Chet Ensign wrote: > And if we just worry about HTML, this is a very scriptable app... > > - Find an <h tag - Find the number and the title string (the > toughest part of the whole enterprise) - Write an <a tag with an > mailto ref in the form > > <a href= href= mailto:tosca-comment@lists.oasis-open.org >tosca-comment@lists.oasis-open.org > ?subject=Comment%20on%202.1%20Non-Normative%20References"> > > around a little comment icon > > - Repeat... > > And Patrick, as you noted, marry this with Rob's script that turns > -comment emails into JIRA issues and we have a very sweet little > comment turnaround enhancment for TCs to use. > > Now... how to get it done? > > > > > --------------------------------------------------------------------- > > 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 > > - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 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.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSJ0bBAAoJEAudyeI2QFGoHOoQALom4vJV2KYmoTvgu2MUPQ7T qJob9J8HfM5qRo8aLF2P/9BQz+nVH8cbV5aFAv2seHFg5rgloUJWfGqQkHP7PqfE /hz/ivcRTSKcw8VBlPRPXF1+R7fFSqyF2IKFqXwx0USyMkAXyFLV8+KhGNHDTv5u w6euuw8u0pvIKOWo1BjBBn+1M97WtPjLqPGbyG9nHEis9oXXRyHvWrkWkHIcXcKp Dm4YQo5MWEzKroIdq/H+h/EiQJGA0uvs8iPWATEKZK9UY7PO/9IcpoEDRYJcDGBe Qme7mRNEq3YIgkWLhkcsDaZWBXRyw9dr08108xKj07fPq1d1/r5vzG2mQZHwo9Fq lG3+nrRARhAjLU/UTfm4OBR0SJoVjMcTQMf3dSck/B78xiLbe4DQwMuxKC4lpb5B AsOqI1ZTTX2cCwequRX5EUogv+K3wJdqqwl5TTjanGPyyGSycn+MGPfLh1DaWfC1 LMgngilx+l2D5xMYyVijuSGrp6cCKBz0TiZf6vrTic1LycBK1nmfJ4YpoebPWD5y 4N35PoTIJO/X3kuw+U+l+lpRe8r3deMkm/8SLAqy+H8XRzkwpNVWBo5h7eKaXSNF ybnV6rI5tlzTeh6VF8WlK6ePyyyDFpmCEsxTdAB7mKZJt1vSviUbkbGBGNL8rcmG RFSmfFbRPNbZXE9aUfRo =ZDGQ -----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 -- /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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chet, You mean you don't want us to look for the most difficult and time consuming process possible???? ;-) You are right of course. The TCs prepare HTML anyway and a simple script could produce the result we are seeking. Apologies for jumping to the complicated solution first! Ah, btw, on going back to <h# doesn't get you the section number, it gets you the level of the heading. But you are on the right track. - From an HTML file on my desktop: <h3><a name="_Toc364092981"></a><a name="_Toc362936024">4.1.2 Validating Integrity</a></h3> What I need to do is: 1) Capture the text content: "4.1.2 Validating Integrity" 2) Recreate the <h3> insert text-content <a href=" mailto:mailinglist?subject=text-content" ;>Comment</a></h3> Done. Yes? With a little tinkering we should be able to capture toc links as well but I don't know how valuable that will be in a review draft. Thanks! Hope you are having a great day! Patrick On 09/04/2013 11:00 AM, Chet Ensign wrote: > Right now, I'm only thinking of HTML. Where a TC generates their > own HTML from XML, we could tell them how to do it. For everything > else, I think a simple rule will get it 90% of the time, only > missing stuff that is screwed up anyway. > > Literally, (a) go to an <h# tag, (b) strip out all the other tags > inside it and replace them with blank spaces, (c) reduce any 2 or > more blanks spaces to 1 space, (d) remove any line breaks. What you > have left is the section number and the title. > > Should work for the vast majority of our HTML files. > > /c > > > On Wed, Sep 4, 2013 at 10:42 AM, Patrick Durusau > <patrick@durusau.net>wrote: > > Chet, > > Thanks! > > Yes, the rub is getting the section #. > > The text of a title isn't an issue, that's easy enough to grab and > recreate the matched element and put it in the mailto:. > > The real problem is calculating the section #, which varies > according to fairly complex rules. > > I am looking at the XHTML export script for ODF which may be > adaptable to the XSLT we would need for ODF source documents. > > Thinking if we can adapt that, then we could "export" to > ODF-comment version, PDF-comment version and XHTML-comment > version. > > Hope you are having a great day! > > Patrick > > On 09/03/2013 06:21 PM, Chet Ensign wrote: >>>> And if we just worry about HTML, this is a very scriptable >>>> app... >>>> >>>> - Find an <h tag - Find the number and the title string (the >>>> toughest part of the whole enterprise) - Write an <a tag with >>>> an mailto ref in the form >>>> >>>> <a href=" mailto:tosca-comment@lists.oasis-open.org >>>> ?subject=Comment%20on%202.1%20Non-Normative%20References"> >>>> >>>> around a little comment icon >>>> >>>> - Repeat... >>>> >>>> And Patrick, as you noted, marry this with Rob's script that >>>> turns -comment emails into JIRA issues and we have a very >>>> sweet little comment turnaround enhancment for TCs to use. >>>> >>>> Now... how to get it done? >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> >>>> > >>>> 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 >>>> >>>> > >>>> >> >> --------------------------------------------------------------------- >> >> 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 >> >> > >> > - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 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.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSJ4qOAAoJEAudyeI2QFGoUGQQAOCV54glFyqrPExlQOIrBrdb QGU52DIdbrcAixi1/bbCPVAgRhm8gJEH2beua43Zguv+oNXLHvfJOvLHA35YMFCA /Vy9RLWnLZtFkkl4JgeXNOOXtVq83Y9CzlXqzEQTSnkEVeSKU8X4/3frIhRH3/1c WqQ8ukK5Fk4zRQFARZA8mVzy328LX4KDrdZ0emFHHtzpPKkIFhZYvrKOreNjvQZ/ 5NLpYkEdvILF8PNliELZ4V5KzPb6xACUFBNDly/fh0H64Y7Rmo+FxzckBr5fdxaU R2I/D8KQ3jjqh466rTbw82hV+y3End+V0zShpzNT52JEGZ5schpHeuGxZp1zg++q GWHiuw611JOvm2OeIFinxJ6a/+wYAnJ2xx1JHuVlzxONUfJnPIMHKEEHSr+d45p8 8kpvMD7G2u7cYcj4h+kSN0lRVxidlOQR/UPb7Tgrgf3i0ddfK7f8rR8NsNiqKDMi zuxuUnELemc28BKmDhGaeXgnKcY4/WJTubGiyjfJj6IGqDI/DUkHVrN/XJvq6HZv zGAFqOINfqfJtFaaNjsuBSsbFNoy9QFG38GK1ST4PrtBckzE/PiTAQJpfxkKeHMz Q0WefrSajOb5x9oKSfCigoh+jBkp4Dk5J2G1JxJjZLQVaUkCmn+8On5NVMto+MzD IXaxmfPBebF8oBkGWDSU =byfT -----END PGP SIGNATURE-----

Yes, exactly. I pulled some HTML specs down and just tried removing all the tags between <h#> and </h#> and leaving just the text and that seems pretty reliable. The only things that might screw it up are things that mean there's something wrong with the tag anyway. For example, I remember a situation where a TC had created headings using bolded text instead of the section header style. But in that case, it's busted anyway.  I think there's value in thinking about how to extend it - but to me, what is really nice is the idea that we could test it out with some interested TCs in HTML only without a big effort.  /c On Wed, Sep 4, 2013 at 3:31 PM, Patrick Durusau < patrick@durusau.net > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chet, You mean you don't want us to look for the most difficult and time consuming process possible???? ;-) You are right of course. The TCs prepare HTML anyway and a simple script could produce the result we are seeking. Apologies for jumping to the complicated solution first! Ah, btw, on going back to <h# doesn't get you the section number, it gets you the level of the heading. But you are on the right track. - From an HTML file on my desktop: <h3><a name="_Toc364092981"></a><a name="_Toc362936024">4.1.2 Validating Integrity</a></h3> What I need to do is: 1) Capture the text content: "4.1.2 Validating Integrity" 2) Recreate the <h3> insert text-content <a href= href= mailto:mailinglist >mailinglist ?subject=text-content">Comment</a></h3> Done. Yes? With a little tinkering we should be able to capture toc links as well but I don't know how valuable that will be in a review draft. Thanks! Hope you are having a great day! Patrick On 09/04/2013 11:00 AM, Chet Ensign wrote: > Right now, I'm only thinking of HTML. Where a TC generates their > own HTML from XML, we could tell them how to do it. For everything > else, I think a simple rule will get it 90% of the time, only > missing stuff that is screwed up anyway. > > Literally, (a) go to an <h# tag, (b) strip out all the other tags > inside it and replace them with blank spaces, (c) reduce any 2 or > more blanks spaces to 1 space, (d) remove any line breaks. What you > have left is the section number and the title. > > Should work for the vast majority of our HTML files. > > /c > > > On Wed, Sep 4, 2013 at 10:42 AM, Patrick Durusau > < patrick@durusau.net >wrote: > > Chet, > > Thanks! > > Yes, the rub is getting the section #. > > The text of a title isn't an issue, that's easy enough to grab and > recreate the matched element and put it in the mailto:. > > The real problem is calculating the section #, which varies > according to fairly complex rules. > > I am looking at the XHTML export script for ODF which may be > adaptable to the XSLT we would need for ODF source documents. > > Thinking if we can adapt that, then we could "export" to > ODF-comment version, PDF-comment version and XHTML-comment > version. > > Hope you are having a great day! > > Patrick > > On 09/03/2013 06:21 PM, Chet Ensign wrote: >>>> And if we just worry about HTML, this is a very scriptable >>>> app... >>>> >>>> - Find an <h tag - Find the number and the title string (the >>>> toughest part of the whole enterprise) - Write an <a tag with >>>> an mailto ref in the form >>>> >>>> <a href= href= mailto:tosca-comment@lists.oasis-open.org >tosca-comment@lists.oasis-open.org >>>> ?subject=Comment%20on%202.1%20Non-Normative%20References"> >>>> >>>> around a little comment icon >>>> >>>> - Repeat... >>>> >>>> And Patrick, as you noted, marry this with Rob's script that >>>> turns -comment emails into JIRA issues and we have a very >>>> sweet little comment turnaround enhancment for TCs to use. >>>> >>>> Now... how to get it done? >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> >>>> > >>>> 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 >>>> >>>> > >>>> >> >> --------------------------------------------------------------------- >> >> 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 >> >> > >> > - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 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.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSJ4qOAAoJEAudyeI2QFGoUGQQAOCV54glFyqrPExlQOIrBrdb QGU52DIdbrcAixi1/bbCPVAgRhm8gJEH2beua43Zguv+oNXLHvfJOvLHA35YMFCA /Vy9RLWnLZtFkkl4JgeXNOOXtVq83Y9CzlXqzEQTSnkEVeSKU8X4/3frIhRH3/1c WqQ8ukK5Fk4zRQFARZA8mVzy328LX4KDrdZ0emFHHtzpPKkIFhZYvrKOreNjvQZ/ 5NLpYkEdvILF8PNliELZ4V5KzPb6xACUFBNDly/fh0H64Y7Rmo+FxzckBr5fdxaU R2I/D8KQ3jjqh466rTbw82hV+y3End+V0zShpzNT52JEGZ5schpHeuGxZp1zg++q GWHiuw611JOvm2OeIFinxJ6a/+wYAnJ2xx1JHuVlzxONUfJnPIMHKEEHSr+d45p8 8kpvMD7G2u7cYcj4h+kSN0lRVxidlOQR/UPb7Tgrgf3i0ddfK7f8rR8NsNiqKDMi zuxuUnELemc28BKmDhGaeXgnKcY4/WJTubGiyjfJj6IGqDI/DUkHVrN/XJvq6HZv zGAFqOINfqfJtFaaNjsuBSsbFNoy9QFG38GK1ST4PrtBckzE/PiTAQJpfxkKeHMz Q0WefrSajOb5x9oKSfCigoh+jBkp4Dk5J2G1JxJjZLQVaUkCmn+8On5NVMto+MzD IXaxmfPBebF8oBkGWDSU =byfT -----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 -- /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