Re: [SoundComp-Develop] Language definition wiki page

[<js...@ya...>]

Dear soundcomp members,

During the previous days, I largely extended the language definition page, to give an example of the discussion  I would like to take place.
It is clearly divided into a more formal lower part and an upper discussion part.

First, we have to "fill up" the upper discussion part, to see what finally needs to be formalized. Then much later we can continue and formalize it in the lower part (with constant review that what we did is consistent with the previous discussion, or redefining fragments in the upper part when formalizing it points out inconsistencies in our definition). Do not care about the formal lower part right now (unless you really want to).

What I am doing up there, I consider far from complete or perfect (I am just one single human with one single, limited view and opinion). Everything there is still a proposal or draft, do not view anything as completely fixed. Don't be afraid to edit there - even plainly wrong edits can always get reverted if necessary.

Please attempt to join there - discuss from a requirements point of view, technical feasibility at this point is not the main issue but will come later - I only may intervene if I see a proposal is probably not possible to implement. Usually this will not require cancelling anything, just slightly tuning the definition. The more different approaches are taken into account, the better the result should get. And it really needs no technical skills at this point - just thinking about "what options may be necessary or useful to generate a desired aural or musical result". Remember, the goals are maximizing flexibility, minimizing necessary effort, and being not too difficult to comprehend.

I really hope that some of you have some input. If there is something unclear at this point, it is essential to resolve this as we just define the very basics of using soundcomp, so do not give up but ask if I did not manage to make stuff clear to understand.

Too much is still missing - and despite all effort towards simplicity I may show a tendency to make things more complicated than they need to be, in which case you all are encouraged to correct me with better proposals. And also I may miss important use cases - that you should point out as well anytime you see them.


Best regards,

Jan

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. 
http://mail.yahoo.com