Greetings! Seriously behind on this and other projects but attempting to catch up. Requirement for abbreviations for OASIS specifications or notes: 1) Must uniquely identify the OASIS specification, standard or note among OASIS documents produced by the naming TC. (There isn't any way a TC can control what other TCs or groups outside of OASIS may or may not do. Requiring the naming TC to use unique names is both reasonable and enforceable.) Q: Should we allow the TAB to pick up prior OASIS specifications and standards that lack "official" abbreviations? 2) OASIS abbreviations must be change when an OASIS specification becomes an OASIS standard, to enable unique identification of either an OASIS specification or OASIS standard. 3) OASIS abbreviations must reflect the status of OASIS work as an OASIS specification, standard or note. That is to say that official abbreviations are not assigned to any document prior to its final status. 4) OASIS abbreviations must not appear in drafts prior to the final draft for approval as an OASIS specification, standard or note. Reasoning if we want abbreviations to be usefully used for OASIS work, the abbreviations must have some certain reference. Not may mean this or that. 5) OASIS abbreviations should be used wherever the name of an OASIS standard, specification or note appears on the OASIS website. Negative requirements (not required) 6) OASIS abbreviations are not required to contain the name "OASIS" or the TC Name in full or abbreviation. 7) OASIS abbreviations are not required contain version or date information, although it is observed one or both of those may be helpful to readers where multiple versions exist or are anticipated. 8) OASIS abbreviations are not required to form meaningful acronyms in any language, although that may be expected by readers. Is that a good starting set? I know it needs more, etc. but thought that would at least get us started. Hope everyone is looking forward to a great weekend! Patrick PS: Apologies for picking this up too late to discuss today. -- Patrick Durusau
patrick@durusau.net 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) OASIS Technical Advisory Board (TAB) - member Another Word For It (blog):
http://tm.durusau.net Homepage:
http://www.durusau.net Twitter: patrickDurusau