Greetings! A proposal for *new* abbreviations from OASIS TCs. Tried to make it short and simple. Do think a TC should choose an abbreviation at the outset. Debates about names (I have participated in them) are pretty much pointless. A good name won't make a bad standard good nor will a bad name impede the progress of a good standard. Same is true for abbreviations. I do think we need to allow a wider character set. Not many will take advantage of it but Western character set imperialism is coming to an end. Not real soon but its coming. Claiming that tokens are semantically opaque so long as they are written in ASCII is believed by fewer and fewer every year. My only problem is that Neo-Assyrian is unlikely to win when it changes. ;-) Sigh, well, that's the breaks. I do hope to get a copy of the complete CAD at some point. Not that it would make much difference now but it would be fun to read. I inserted a short requirements section so we could debate those as well. If we are going to ask others to have requirements we really should set a good example. Some are complex, some are simple. But we need them to know when to stop. Hope everyone is looking forward to a great weekend! Patrick PS: I think I owe a proposal on other "types" of deliverables for TCs. Will give it some thought over the weekend. -- 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 Attachment: OASIS-NewStandards-Abbreviations-Proposal-6Jan2012.pdf Description: Adobe PDF document