home tune search software learn abc discuss about blog Starbound/LOTRO contact  

  [abc standard: home | current | route-map | updating | proposals]

 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
abc:standard:updating [2012/08/15 13:26]
cwalshaw
abc:standard:updating [2014/07/12 08:03] (current)
cwalshaw
Line 3: Line 3:
 The abc standard is open to new [[abc:​standard:​proposals|proposals]] from anyone, although proposals require **support from the abc user community** before being incorporated. The abc standard is open to new [[abc:​standard:​proposals|proposals]] from anyone, although proposals require **support from the abc user community** before being incorporated.
  
-The aim of the process is to provide an inclusive, transparent and considered method for updates to progress (and a procedure which doesn'​t have the bottleneck of requiring my input at every stage).+The aim of the following ​process is to provide an inclusive, transparent and considered method for updates to progress (and a procedure which doesn'​t have the bottleneck of requiring my input at every stage)
 + 
 +=== Guidelines for new syntax === 
 + 
 +//In order of importance//,​ the aims for any new syntax are that it should result in abc code which is **clear**, **suggestive** and **compact**;​ furthermore,​ the syntax should be **unique**, if possible, and its description in the standard should be **concise** and **straightforward**. 
 + 
 +Specifically:​ 
 +  - the resulting abc code should be as **clear** as possible to humans, preferably without requiring the reader to look up the usage in the standard 
 +  - the resulting abc code should be **suggestive** of standard staff notation, provided that this does not compromise (1) 
 +  - the resulting abc code should be as **compact** as possible, provided that this does not compromise (1) and (2) 
 +  - the syntax should, where possible, provide a **unique** method to achieve each effect, provided that this does not compromise (1), (2) and (3) 
 +  - the description of the syntax should be **concise**,​ i.e. giving a lot of information clearly and in a few words, and **straightforward**,​ i.e. uncomplicated and easy to understand, provided that this does not compromise (1), (2), (3) and (4) 
 + 
 +This means that, for example, minimising the size of the abc code is not the first priority if it reduces clarity and suggestiveness. It also means that it //is// acceptable to have two methods of achieving the same effect, particularly if it helps clarity. Finally, although it is important that the standard document does not become bloated and overcomplicated,​ ultimately it is the clarity, suggestiveness and compactness of the resulting abc code which has a higher priority.
  
 === Submitting a proposal === === Submitting a proposal ===
abc/standard/updating.1345037169.txt.gz · Last modified: 2012/08/15 13:26 by cwalshaw
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki