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
Last revision Both sides next revision
abc:standard:updating [2013/03/05 17:05]
cwalshaw
abc:standard:updating [2013/03/05 17:12]
cwalshaw
Line 5: Line 5:
 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). 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).
  
-=== (Draft) Guidelines for proposal ​===+=== (Draft) 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**. //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**.
Line 13: Line 13:
   - the resulting abc code should be **suggestive** of standard staff notation, provided that this does not compromise (1)   - 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 resulting abc code should be as **compact** as possible, provided that this does not compromise (1) and (2)
-  - the syntax should, where possible, ​be **unique**, provided that this does not compromise (1), (2) and (3)+  - 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)   - 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.+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.txt ยท Last modified: 2014/07/12 08:03 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