<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Benjamin,<br>
thanks a lot for summing up part of the discussion! <br>
Without voting for A or B at the moment, only a few remarks
concerning Institutional membership interspersed in your text:<br>
Hoping that the discussion continues,<br>
Joachim<br>
<br>
<br>
Am 10.04.14 12:40, schrieb Benjamin Wolff Bohl:<br>
</div>
<blockquote cite="mid:53467524.5000503@edirom.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Dear all,<br>
thanks for starting discussion on the proposals!<br>
<br>
For some short replies and digest of the comments in the
googleDoc:<br>
<br>
The Guidelines definitely are the most important product of MEI,
together with the schema. An it sounds wise not to overload the
production of these documents with organizational / bureaucratic
matters. I think this is something everybody should keep in mind
;-)<br>
<br>
Institutional Membership seems to have a lot of potential
discussion. her e are some questions to help us get clear what
MEI wants:<br>
- 1) A general question that could be raised in this context is
whether the idea of Institutional Membership should be an issue
not tied to a specific model but of general interest for MEI and
thus any future model of its organization?<br>
<br>
- 2) Designating three levels of Institutional Membership with
respective increase of fees should result in more than just a
label. This only motivates to support with the lowest membership
and even if wanted it might get hard to argue to spend more
money if it doesn't bring more benefits.<br>
<br>
- 3) Should Institutional Members (of any level or just highest
level) have a seat in the Board? Should these be allowed the
right to vote or not<br>
I think the danger you describe in the following point 4 is an
important argument against seats in the Board. The system of
buying votes or seats is extremely un-democratic. We should
accept that an Institutional Member has one vote as each
individual member and try to find other means of "award" for
such fine institutions who are willing to promote the MEI
community. So I very much sympathize with your proposal under 5)
(which is the "TEI" one).<br>
</div>
</blockquote>
We should also avoid - if there will be an individual fee on the
long term - that institutions spending, e.g., 500 $ see this as
paying for their 200 individual members. That's no problem at the
moment at all - but perspectively. So I plea for treating individual
and institutional members alike - at least concerning their rights
to vote or being elected.<br>
<blockquote cite="mid:53467524.5000503@edirom.de" type="cite">
<div class="moz-cite-prefix"> - 4) If institutional Memberships
allow for a voting seat in the Board, how avoid the risk of
buying control over MEI?<br>
<br>
- 5) Why not tie the fees for Institutional Membership to the
size of the institution an d their annual budget?<br>
<br>
<br>
<blockquote type="cite">Model C, while innovative, feels like
it's imposing a structure to interest groups that should just
happen naturally. I see this as being ultimately
counterproductive, partly because it's kind of predictable
that one or two groups will always have the bigger cut, simply
because of what MEI offers.</blockquote>
<br>
I'm not sure what you mean with "such things". The general
statements concerning Interest Groups impose the structure to
them. The idea of Model C in this context is that in contrary to
having exclusively Board members form the groups with the
"bigger cut" it allows smaller groups to participate in the
Board, not least because the ratios for sending group members to
the Board is in favour of smaller groups.<br>
</div>
</blockquote>
Imagine we have 15 interest groups (whow, fine!!....) - all should
send a member in the Board? How should such a big board operate? <br>
<blockquote cite="mid:53467524.5000503@edirom.de" type="cite">
<div class="moz-cite-prefix"> <br>
<br>
Best wishes,<br>
Benjamin<br>
<br>
<pre class="moz-signature" cols="72">***********************************************************
Musikwissenschaftliches Seminar Detmold/Paderborn
BMBF-Projekt "Freischütz Digital"
Benjamin Wolff Bohl
Gartenstraße 20
D–32756 Detmold
Tel. +49 (0) 5231 / 975-669
Fax: +49 (0) 5231 / 975-668
E-Mail: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:bohl@edirom.de">bohl@edirom.de</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.freischuetz-digital.de">http://www.freischuetz-digital.de</a>
***********************************************************</pre>
Am 09.04.2014 01:57, schrieb Raffaele Viglianti:<br>
</div>
<blockquote
cite="mid:CAMyHAnOzbdhLUiW7M889S=Od4y0hGtKNkDBa5+eEWhngO0Z5Sg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello everyone,
<div><br>
</div>
<div>Many thanks to the Strategy Development Group - you all
clearly put a lot of effort into producing a well organized
and clear document.</div>
<div><br>
</div>
<div>I left a few specific comments on the document itself. In
general, I prefer Model B: it's lean and reflects well the
size of the community. It also keeps the focus on the
Guidelines and releases, which I agree with Sigfrid are the
most important product of this community. I feel model B
will allows us to move forward without having to jump
through too many administrative hoops, while tasking people
with essential admin responsibilities. The idea of
institutional sponsorship from Model A is good, though it
might need some clearer bylaws. Model C, while innovative,
feels like it's imposing a structure to interest groups that
should just happen naturally. I see this as being ultimately
counterproductive, partly because it's kind of predictable
that one or two groups will always have the bigger cut,
simply because of what MEI offers.</div>
<div><br>
</div>
<div>Thanks again for all you work!</div>
<div>Raff</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Apr 8, 2014 at 6:31 AM,
Sigfrid Lundberg <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:slu@kb.dk"
target="_blank">slu@kb.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Benjamin and all other contributors to the strategy
document!<br>
<br>
Thanks for good work!<br>
<br>
I have to say that I'm leaning towards the A alternative,
or something close to it. The reason for that is that the
MEI guidelines is our most important product (and I
suppose that it will be so for years to come). Hence I
think that the technical committee is needed as the
maintainer of that document and as an entity that assumes
the responsibility for its development. I'm not sure the
board should have that responsibility. There are people
who have the capacities needed for work both in a board
and being a guideline editor, but perhaps not
simultaneously?<br>
<br>
A gambit for a discussion from between an XML query and a
transform.<br>
<br>
Yours,<br>
<br>
Sigfrid<br>
<br>
________________________________________<br>
Fra: mei-l [<a moz-do-not-send="true"
href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>]
på vegne af Benjamin Wolff Bohl [<a
moz-do-not-send="true" href="mailto:bohl@edirom.de">bohl@edirom.de</a>]<br>
Sendt: 2. april 2014 15:13<br>
Til: Music Encoding Initiative<br>
Emne: [MEI-L] Proposals MEI Strategy Development Group<br>
<div class="HOEnZb">
<div class="h5"><br>
Dear MEI-L,<br>
<br>
after Music Encoding Conference 2013 MEI Strategy
Development Group<br>
(MEI-Strat) was formed in order to elaborate proposals
for future<br>
organization of MEI community. During the past months
we have been<br>
working in order to start discussion on potential
future forms of<br>
organizing MEI community.<br>
<br>
Now with the Music Encoding Conference 2014 being just
around the corner<br>
it seems appropriate to start discussion on this
subject matter, as we<br>
hope to distil a common community consensus on what
might be new and<br>
openly communicated structures of MEI. Furthermore we
intend to prepare<br>
presenations and a basis for further discussion for
this year's<br>
conference (May 20-23 in Charlottesville, VA).<br>
<br>
==A short disclaimer==<br>
Please be aware that anything in the proposal is
indicative and subject<br>
to discussion, be it the individual proposals in
general, or specific<br>
details, e.g. the length of terms for elected members.<br>
<br>
==Words of thank==<br>
We thank the MEI community for the possibility to work
on this subject<br>
matter, and for the confidence in our group!<br>
I personally like to thank all collaborators for their
time, effort and<br>
good thoughts all of which were provided on expense of
their private<br>
free time!<br>
<br>
==The Discussion==<br>
The document containing our proposals is openly
available online via<br>
google-Drive (no login required). Although
modification of the text is<br>
not possible comments may be inserted by anyone with
the link. Feel free<br>
to provide your identity when commenting or just
submit anonymously.<br>
Of course it is not intended to discuss all raised
topics in the<br>
document. A lively discussion on MEI-L would be warmly
welcome so bring<br>
anything of interest to discussion there!<br>
<br>
==The Document==<br>
<a moz-do-not-send="true"
href="https://docs.google.com/document/d/1IBvbKFM1fo4lwyFnIYnneUhfwTj4DLrAmtCSUfqzeQs/edit?usp=sharing"
target="_blank">https://docs.google.com/document/d/1IBvbKFM1fo4lwyFnIYnneUhfwTj4DLrAmtCSUfqzeQs/edit?usp=sharing</a><br>
<br>
<br>
With many thanks to all collaborators,<br>
for the MEI Strategy Development Group,<br>
Benajmin W. Bohl<br>
- Keeper<br>
<br>
--<br>
***********************************************************<br>
Musikwissenschaftliches Seminar Detmold/Paderborn<br>
BMBF-Projekt "Freischütz Digital"<br>
Benjamin Wolff Bohl<br>
Gartenstraße 20<br>
D–32756 Detmold<br>
<br>
Tel. <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%205231%20%2F%20975-669"
value="+495231975669">+49 (0) 5231 / 975-669</a><br>
Fax: <a moz-do-not-send="true"
href="tel:%2B49%20%280%29%205231%20%2F%20975-668"
value="+495231975668">+49 (0) 5231 / 975-668</a><br>
E-Mail: <a moz-do-not-send="true"
href="mailto:bohl@edirom.de">bohl@edirom.de</a><br>
<br>
<a moz-do-not-send="true"
href="http://www.freischuetz-digital.de"
target="_blank">http://www.freischuetz-digital.de</a><br>
***********************************************************<br>
<br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a moz-do-not-send="true"
href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a moz-do-not-send="true"
href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l"
target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a moz-do-not-send="true"
href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a moz-do-not-send="true"
href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l"
target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mei-l mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mei-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a>
<a class="moz-txt-link-freetext" href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a>
</pre>
</blockquote>
<br>
</body>
</html>