Re: [gnso-vi-feb10] Group on documenting "harms"

[tim@xxxxxxxxxxx]

I have only been responding to the idea of trying to quantify the likelihood or 
probability of the harms, not the enumeration of the harms themselves.

Tim

-----Original Message-----
From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
Date: Wed, 28 Jul 2010 18:10:12 
To: Tim Ruiz<tim@xxxxxxxxxxx>
Cc: Avri Doria<avri@xxxxxxx>; <Gnso-vi-feb10@xxxxxxxxx>
Subject: Re: [gnso-vi-feb10] Group on documenting "harms"

  Hi Tim,

I would really like to understand your position better.

On the one hand you give blanket support to Rack, effectively opening up 
CO to 15%, but resist any further oping based on the fear of potential 
abuse and harms, but on the other hand, you are not willing to discuss 
just what these fears entail? How do you believe RACK will solve any one 
of these feared harms while it has no further safeguards but a blanket 
15% limitation? Would not a stricter policy and set of rules be a better 
way to deal with these harms?

Effectively, what I am looking for is a list of what things you assume 
will result from VI and (to a lesser extent) increased CO which are 
completely prevented by RACK.

Volker
> It's where you find yourself when you fail to recognize reality. IMO,
> the reality is if you want to go down the road of likelihood,
> probability, etc. it result in a lot of wasted time due either to more
> debate and disagreement about it or the result will get shot full of
> holes later.
>
> And this discussion is not a matter of someone not agreeing with me. It
> is a matter of two different opinions, with more than one propopent for
> each, in what I see as an unending debate that will result in nothing
> productive or useful.
>
>
>
> Tim
>
>
> -------- Original Message --------
> Subject: Re: [gnso-vi-feb10] Group on documenting "harms"
> From: Avri Doria<avri@xxxxxxx>
> Date: Wed, July 28, 2010 10:28 am
> To: Gnso-vi-feb10@xxxxxxxxx
>
>
>
> On 28 Jul 2010, at 17:15, Tim Ruiz wrote:
>
>> But more to my previous point, the fact that this thread even exists
>> makes my point. If we go there, it is never never land yet once again.
>
> I do not understand this.
>
> people disagree with you, ergo, we are in never never land?
>
> What is never never land anyway? a place in Australia?
>
> a.
>
>


-- 
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.key-systems.net/facebook
www.twitter.com/key_systems

Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 1861 - Zweibruecken
Umsatzsteuer ID.: DE211006534

Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen 
Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder 
Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht 
nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder 
telefonisch in Verbindung zu setzen.

--------------------------------------------

Should you have any further questions, please do not hesitate to contact us.

Best regards,

Volker A. Greimann
- legal department -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Follow us on Twitter or join our fan community on Facebook and stay updated:
www.key-systems.net/facebook
www.twitter.com/key_systems

CEO: Alexander Siffrin
Registration No.: HR B 1861 - Zweibruecken
V.A.T. ID.: DE211006534

This e-mail and its attachments is intended only for the person to whom it is 
addressed. Furthermore it is not permitted to publish any content of this 
email. You must not use, disclose, copy, print or rely on this e-mail. If an 
addressing or transmission error has misdirected this e-mail, kindly notify the 
author by replying to this e-mail or contacting us by telephone.