{"id":969,"date":"2010-04-28T15:12:02","date_gmt":"2010-04-28T19:12:02","guid":{"rendered":"http:\/\/2d823b65bb.nxcli.io\/?p=969"},"modified":"2010-07-03T11:56:58","modified_gmt":"2010-07-03T15:56:58","slug":"naming-of-standards","status":"publish","type":"post","link":"https:\/\/www.robweir.com\/blog\/2010\/04\/naming-of-standards.html","title":{"rendered":"The Naming of Standards"},"content":{"rendered":"<p>I am occasionally asked, what is the correct name of the<a href=\"http:\/\/opendocument.xml.org\/\"> ODF standard<\/a>?\u00a0 Is it &#8220;OpenDocument Format&#8221;?\u00a0 Or is it &#8220;Open Document Format&#8221;, with a space between &#8220;Open&#8221; and &#8220;Document&#8221;?<\/p>\n<p>I&#8217;d like (hopefully) to clear this up.<\/p>\n<p>The naming decision happened back in 2004.\u00a0 At that point Sun had contributed their specification for the OpenOffice XML format to OASIS,\u00a0 and a new TC was using that specification as the basis for developing a new standard.\u00a0 But what should the new standard be called?<\/p>\n<p>Some wanted it to be called &#8220;OfficeDocument&#8221;, emphasizing its primary scope of use.\u00a0 Others wanted to call it &#8220;OpenDocument&#8221;, making its openness (a new thing in the office-document world at that time) more central, and acknowledging that its applicability was for more than just office editors.<\/p>\n<p>So, as only a committee can do, a compromise was forged incorporated both ideas.\u00a0 The resulting <a href=\"http:\/\/www.oasis-open.org\/committees\/tc_home.php?wg_abbrev=office\">official name<\/a> of the standard became, &#8220;OASIS Open Document Format for Office Applications (OpenDocument)&#8221;.<\/p>\n<p>If you are citing the standard for official reasons, that is the name to use.\u00a0 (Or the ISO name which is even longer).\u00a0 But clearly, that name is too long for casual use, or even use in technical writing,\u00a0 so we need a shorter, more convenient name.\u00a0 I&#8217;ll note the terms I&#8217;ve seen used, as well as my personal thoughts on whether they are\u00a0 a good idea:<\/p>\n<ul>\n<li>ODF &#8212; This is what you&#8217;ll hear it called in OASIS, where the term is unambiguous.\u00a0 However, in other circles ODF can mean other things, from &#8220;Organ Donation Foundation&#8221; to &#8220;Oregon Department of Forestry&#8221;.\u00a0 So, in writing, even on this blog, I will typically use a longer form first, and only then use the acronym.\u00a0 This is also more search-engine friendly.<\/li>\n<li>Open Document Format &#8212; This is certainly always correct and is my preferred longer form.<\/li>\n<li>OpenDocument &#8212; This is also correct, the short name explicitly given in the standard.\u00a0 We use it, for example, in the registered MIME content types for ODF.\u00a0 I tend to see this more used to refer to the technology rather than the format itself.\u00a0 So, &#8220;OpenDocument applications&#8221; or &#8220;OpenDocument toolkits&#8221;.\u00a0 But if I had omnipotent powers, I&#8217;d eliminate this short name and make the short name official &#8220;ODF&#8221;.<\/li>\n<li>OpenDocument Format &#8212; This is less correct, using the official short name and then appending a proper case &#8220;Format&#8221; after it.\u00a0 It is hard to justify, but it does occur in many places.<\/li>\n<li>OpenDoc &#8212; This is absolutely wrong.\u00a0 <a href=\"http:\/\/en.wikipedia.org\/wiki\/Opendoc\">OpenDoc<\/a> is the name of an unrelated technology Apple developed in the 1990s.<\/li>\n<\/ul>\n<p>When the IBM Terminology group contacted me on this (and yes we apparently have such a group) my advice to them &#8212; and I commend\u00a0 the same to you &#8212; is:<\/p>\n<ol>\n<li>When citing the standard, use the official name &#8220;OASIS Open Document Format for Office Applications (OpenDocument) v1.1&#8221;.<\/li>\n<li>When referring to the format in general, call it &#8220;Open Document Format&#8221;\u00a0 at its first use in a document, and then feel free to abbreviate it as &#8220;ODF&#8221;.<\/li>\n<\/ol>\n<p>There are those who say that standards also have a THIRD NAME, a secret name that they use only for themselves.\u00a0 What deep and inscrutable name ODF calls itself is a matter of some speculation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I am occasionally asked, what is the correct name of the ODF standard?\u00a0 Is it &#8220;OpenDocument Format&#8221;?\u00a0 Or is it &#8220;Open Document Format&#8221;, with a space between &#8220;Open&#8221; and &#8220;Document&#8221;? I&#8217;d like (hopefully) to clear this up. The naming decision happened back in 2004.\u00a0 At that point Sun had contributed their specification for the OpenOffice [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[9],"tags":[],"class_list":{"0":"post-969","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-odf","7":"entry"},"_links":{"self":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/969","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/comments?post=969"}],"version-history":[{"count":12,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/969\/revisions"}],"predecessor-version":[{"id":974,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/969\/revisions\/974"}],"wp:attachment":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/media?parent=969"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/categories?post=969"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/tags?post=969"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}