Technical Advisory Board (TAB)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Ignore the poor formatting of the HTML and look at the content. ;-) Just a starting place for the Citation Guide work that I think we should iterate over in point releases. There is little point to waiting months (or longer) to start helping TCs. Surely they are aware of point releases of software and we should do the same with documentation such as this proposed guide. I can probably do the screen-shot guides in the next day or so, perhaps before our next meeting. I think those should be in PDF but am willing to do HTML if the TAB thinks that will be better. They will be as rough and crude as this page so get your red pens ready for substance and style comments. Hope everyone is having a great week! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Co-Chair, OpenDocument Format TC (OASIS) Editor, OpenDocument Format TC, Project Editor ISO/IEC 26300 Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Co-Editor, ISO 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) iQIcBAEBAgAGBQJU0nZ9AAoJEAudyeI2QFGoaD4P/R1MLhpeOl/9gJRslVgywzBI 7D6pMlxCy1oxXUUjXELjPnMJ3FkQ3eaur82c0fE42omyf4gkQUDn7+Txqj9ZUJ/G +dN8bDJpX6UR2fihVe6tm3G521VGQk/h4sAa/dHgAN9q4UeWsRcCxa+wDMRXvkh2 fsTyDE+qmSonjh/tQsF/hZUZdk1B8VvhvrCUGb7dE+V8brB3TgFCmMDYEe2hK02x 2A4J+o9E9FZrKDupmJQ7HrqF5h2jJrmcqD26tQdCN7KzjKpK8Hn9Dp3Kixhly7XA R0bQlUtcHd/Y/K5D9sK30y73MPWbctIGng+M9cgqLWzCpUfuiFR1zqYGy0tRz9Kt nFCQYuXnEk0lqarGxaTlZrhGEcmVT0vGj6nAQE7qvAzsdKvGqM5JMhT6nUK8i8yl lzuPkDZYx3ZFggL7fzhzaWCuvj8UVHA2DLmoIi/8RTc8nVJdE3K2EH6r3NLD746p 1jEYcAAC/zOnzVkUTbYXMgv1ZEx8DbxehURIcu6GkS4VO22G8aDt8SQdgj+t6xXo iTRjyHxcdUMupJRFvm/zVh2/LYjqZxwPXDHRWbB/U28Br+cxAGsr+AW4Ysif4Q37 ggwOVKLjTWlgWoq9EXPxWxluUgf5URrav967PUIkNGj2Lkdu4Ey3tyGHG23pjzFK 36O3xSBrtG/oKnXGnmG1 =2HZ4 -----END PGP SIGNATURE----- Title: TAB Citation Guide - Version 0.01 TAB Citation Guide - Version 0.01 Introduction After reviewing dozens of Oasis TC work products, the TAB has noticed that getting citations correct is a real issue for TCs. Not hard to understand, we all copy-n-paste from prior versions, drafts, work others have done, etc. Unfortunately, that results, more often than not, in references that detract from the hard work the TC has done on its work product. It's like getting a resume where the person mis-spells the name of your company. Not too impressive. Yes? To help TCs get citations correct the first time and not after a TAB review, the TAB is in the process of constructing this citation guide for TCs. We will be releasing it as point releases so you can benefit from what we have done so far, and make comments on how we can improve it as a work product. Not unlike a software project. Please address your feedback to: (insert TAB address). Citation References Citation references are sources that specify how a particular group of citations should be cited. For example, most TCs will cite RFCs (from the IETF) in their work products. The IETF maintains a list of RFCs and how they should be cited. As do other groups. At this stage of development of this guide, the TAB is provides a link to the citation reference and a screen-shot guide to using the citation reference in a separate PDF file. RFCs - RFC Reference List - RFC Screen-Shot Guide. W3C - W3C Citation Generator - W3C Screen-Shot Guide. Patrick Durusau

Good start. Based on the Board conversation yesterday, this would go over well.  It occurs to me that a *start* for OASIS citations might be for me to modify the standards list by adding the citation formats to them. It would take work - the %#@# thing is hand edited HTML. But then we could add it to the list...  On Wed, Feb 4, 2015 at 2:44 PM, Patrick Durusau < patrick@durusau.net > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Ignore the poor formatting of the HTML and look at the content. ;-) Just a starting place for the Citation Guide work that I think we should iterate over in point releases. There is little point to waiting months (or longer) to start helping TCs. Surely they are aware of point releases of software and we should do the same with documentation such as this proposed guide. I can probably do the screen-shot guides in the next day or so, perhaps before our next meeting. I think those should be in PDF but am willing to do HTML if the TAB thinks that will be better. They will be as rough and crude as this page so get your red pens ready for substance and style comments. Hope everyone is having a great week! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Co-Chair, OpenDocument Format TC (OASIS) Editor, OpenDocument Format TC, Project Editor ISO/IEC 26300 Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Co-Editor, ISO 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) iQIcBAEBAgAGBQJU0nZ9AAoJEAudyeI2QFGoaD4P/R1MLhpeOl/9gJRslVgywzBI 7D6pMlxCy1oxXUUjXELjPnMJ3FkQ3eaur82c0fE42omyf4gkQUDn7+Txqj9ZUJ/G +dN8bDJpX6UR2fihVe6tm3G521VGQk/h4sAa/dHgAN9q4UeWsRcCxa+wDMRXvkh2 fsTyDE+qmSonjh/tQsF/hZUZdk1B8VvhvrCUGb7dE+V8brB3TgFCmMDYEe2hK02x 2A4J+o9E9FZrKDupmJQ7HrqF5h2jJrmcqD26tQdCN7KzjKpK8Hn9Dp3Kixhly7XA R0bQlUtcHd/Y/K5D9sK30y73MPWbctIGng+M9cgqLWzCpUfuiFR1zqYGy0tRz9Kt nFCQYuXnEk0lqarGxaTlZrhGEcmVT0vGj6nAQE7qvAzsdKvGqM5JMhT6nUK8i8yl lzuPkDZYx3ZFggL7fzhzaWCuvj8UVHA2DLmoIi/8RTc8nVJdE3K2EH6r3NLD746p 1jEYcAAC/zOnzVkUTbYXMgv1ZEx8DbxehURIcu6GkS4VO22G8aDt8SQdgj+t6xXo iTRjyHxcdUMupJRFvm/zVh2/LYjqZxwPXDHRWbB/U28Br+cxAGsr+AW4Ysif4Q37 ggwOVKLjTWlgWoq9EXPxWxluUgf5URrav967PUIkNGj2Lkdu4Ey3tyGHG23pjzFK 36O3xSBrtG/oKnXGnmG1 =2HZ4 -----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

On Thu, Feb 5, 2015 at 11:20 AM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Good start. Based on the Board conversation yesterday, this would go over well.  It occurs to me that a *start* for OASIS citations might be for me to modify the standards list by adding the citation formats to them. It would take work - the %#@# thing is hand edited HTML. But then we could add it to the list...  Chet, I already have in hand some 480+ [properly] formatted citations for OASIS specifications (including standards), so a lot of the hardest work is already complete.  Adding that data to the HTML (standards) document or a derivative would be trivial, by comparison.   Multiple dozens or hundreds of hours already spent on  this.  Sorry not to have updated TAB more recently about the work Patrick and I are doing WRT OASIS specification bibliographic metadata. I'll check the TAB list: I thought I sent a recent update on progress. - Robin   On Wed, Feb 4, 2015 at 2:44 PM, Patrick Durusau < patrick@durusau.net > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Ignore the poor formatting of the HTML and look at the content. ;-) Just a starting place for the Citation Guide work that I think we should iterate over in point releases. There is little point to waiting months (or longer) to start helping TCs. Surely they are aware of point releases of software and we should do the same with documentation such as this proposed guide. I can probably do the screen-shot guides in the next day or so, perhaps before our next meeting. I think those should be in PDF but am willing to do HTML if the TAB thinks that will be better. They will be as rough and crude as this page so get your red pens ready for substance and style comments. Hope everyone is having a great week! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Co-Chair, OpenDocument Format TC (OASIS) Editor, OpenDocument Format TC, Project Editor ISO/IEC 26300 Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Co-Editor, ISO 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) iQIcBAEBAgAGBQJU0nZ9AAoJEAudyeI2QFGoaD4P/R1MLhpeOl/9gJRslVgywzBI 7D6pMlxCy1oxXUUjXELjPnMJ3FkQ3eaur82c0fE42omyf4gkQUDn7+Txqj9ZUJ/G +dN8bDJpX6UR2fihVe6tm3G521VGQk/h4sAa/dHgAN9q4UeWsRcCxa+wDMRXvkh2 fsTyDE+qmSonjh/tQsF/hZUZdk1B8VvhvrCUGb7dE+V8brB3TgFCmMDYEe2hK02x 2A4J+o9E9FZrKDupmJQ7HrqF5h2jJrmcqD26tQdCN7KzjKpK8Hn9Dp3Kixhly7XA R0bQlUtcHd/Y/K5D9sK30y73MPWbctIGng+M9cgqLWzCpUfuiFR1zqYGy0tRz9Kt nFCQYuXnEk0lqarGxaTlZrhGEcmVT0vGj6nAQE7qvAzsdKvGqM5JMhT6nUK8i8yl lzuPkDZYx3ZFggL7fzhzaWCuvj8UVHA2DLmoIi/8RTc8nVJdE3K2EH6r3NLD746p 1jEYcAAC/zOnzVkUTbYXMgv1ZEx8DbxehURIcu6GkS4VO22G8aDt8SQdgj+t6xXo iTRjyHxcdUMupJRFvm/zVh2/LYjqZxwPXDHRWbB/U28Br+cxAGsr+AW4Ysif4Q37 ggwOVKLjTWlgWoq9EXPxWxluUgf5URrav967PUIkNGj2Lkdu4Ey3tyGHG23pjzFK 36O3xSBrtG/oKnXGnmG1 =2HZ4 -----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 -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783