As say Stingray when posting the document, it deserves a new trheat.
(excuse my poor english)
http://noticeboard.a...11/08/JN024.pdf
8 questions from Oracle about the possibilities and limits of his collaboration with other equipment, Challenger or Defender.
The most important: .
Any prior agreement or arrangement about sharing performance data is illegal without exception (art. 33.4).
You can share the performance data, but, in this case, you are using the other boat as a "Surrogate Yacht", and you can't build a "second" boat, because it's a "thirth"
The truth is that, after reading the Protocol, the interpretation of the Kiwis-LR was caught by the hair ...
Luna Rossa tries to interprete the 33.1 and 33.2 as guarantors of rights, but the text is trying to put prohibitions limiting collaboration, not ensure rights.
Oracle raises 8 questions from less to more collaboration.
According to the responses to Oracle, before 2013, a team can, without bring consequences:
1 .- Give a complete design to another participant.
2 .- Share molds in different shipyards. Or build in the same yard, provided that it's an independent one, because if one of the teams have already constructed two boats (in "it's" yard), although one of them is for the other team, no more boats can be constructed by the "builder" team.
3 .- Sailing, testing the boats and training together.
(But. .. and here begins the limitations
By sharing the test data of the other boat for the development of your own boat, the other is considered a "Surrogate Yacht" which counts as a second boat, and you can not build a third one. And if they made an agreement to that, then they are falling under the prohibition of 33.4.
4 .- A team can test own boat with the wings, sails, appendages, or other equipment of another team (until 2013), but then the other is using the boat of the first team as a "Surrogate Yacht" and they can not build a second ship.
5 .- Although not sail together, two teams can share performance data, but then both are using the other as "Surrogate Yatch", and can't build a second ship. And if there is prior agreement for sharing, falls under the prohibition of 33.4.
6 .- Members of a team can sail aboard the other for training and development, but then it is the same: both are using two boats to design development, and can not build another.
7 .- In 2013, if they are training together with mixed crews, it is hard to think they do not return with information on performance, prohibited from sharing in that year. And the other boat is used for development, could not build another boat.
8 .- If a team makes a preliminary agreement to take advantage derived from points 1 to 5, is in any case against the prohibition of agreements referred to in 33.4. And that agreement would also have the effect of the two teams are already using two ships, and could not make another one.
_____________________
Result, in my opinion:
Change the names of Oracle and Competitor B for ETNZ and Luna Rossa (or whatever) and you get the following:
The agreement between ETNZ and Luna Rossa is against the Protocol.
They have released the agreement assuming an interpretation of the text of the Protocol has not been accepted (and I think caught by the hair).
Some sayed it would be possible to take advantage of these rules and to make even a second (third) boat if you do not "share" the performance data you get from your boat, but the other team measures your boat from the outside, and you measure the other boat from the outside . If you have two identical boats, the data of resistance and structural loads are the same, and the speed data are not given by the other team, but by you from outside ...
But the problem is that ETNZ and LR have already made public that they have reached an agreement ... without asking about the legality of the agreement ... And now, the prohibition of agreements do not have exceptions. And their interpretation of the Protocol is flawed, and they are out of bounds.
I guess they can say it was an interpretation of good will, break the agreement, and working in the limits we now know it is legal ...
In any case, pending the question asked by Artemis, precisely on the specific terms of the agreement ETNZ-LR. Maybe not needed.
Let's see what happens.
Clearly, these rules allow collaboration between two teams who want to build only one boat each. They take all advantages of sharing everything until 2013, and do not mind not being able to make a second boat (which would be the third prohibited ...). It is possible as long as there is no "agreement", but only actual sharing. This implies that, if you say it's over, it's over. The other has nothing to say.
TEXT:
DISCUSSION on Articles 33.1, 33.2 & 33.4
25. Luna Rossa Challenge 2013, in its submission of 17th December, asserts that '…33.4 is a general anti-avoidance clause that must be interpreted in the context of the rights granted by 33.1 and 33.2'. The Jury disagrees. It is not appropriate to interpret Articles 33.1 and 33.2 as 'giving rights'. Each Article starts with a prohibition, followed by limited relief from that prohibition. The relief relates only to the particular prohibition contained in the Article. For
example, a Competitor may take advantage of the relief described in (a) to (e) in Article 33.2, but must nevertheless comply with Article 33.4 which stands alone and applies at all times.
Each of the clauses in question stands alone, but needs to each be read so that they are consistent with other Articles.
26. The Jury sees no justification to treat any of the four parts of Article 33 as being superior or inferior to any other part, or subject to any 'read-down'. Article 33.4 stands alone and applies at all times. Accordingly, some actions that might not be prohibited by Article 33.1 or 33.2 might be prohibited by Article 33.4.
27. Articles 33.1 and 33.2 are not, as several submissions suggested, 'permissive' rules. They prohibit certain activities after 1st January 2013 that would otherwise not be prohibited.
28. Without Articles 33.1 and 33.2, two Competitors (or potential Competitors) may have a common designer, and may share or exchange AC72 Class design or performance information or equipment, provided there is no 'agreement, arrangement or other understanding', as described in Article 33.4, between the Competitors.
29. However Articles 33.1 and 33.2 tell us that from 1st January 2013, two Competitors (or potential Competitors) may not have a common designer, nor share or exchange AC72 Class design or performance information or equipment.
30. Articles 33.1, 33.2 and 33.4 must be read in conjunction with Article 29.2(a) which provides a clear requirement that Competitors 'may build, acquire or otherwise obtain a maximum of two new AC72 Yachts'.
31. The Jury determines that for Article 33.4 to apply, three requirements have to be satisfied:
(a) There must be an 'agreement, arrangement or other understanding, whether legally enforceable or not', between ORACLE Racing and another entity (e.g. Competitor B (CB));
( B) The arrangement involves CB directly or indirectly building or acquiring one or more yachts of any type; and
© ORACLE Racing can (not 'will' or 'did') directly or indirectly obtain, in any manner whatever, design or performance information regarding CB's yacht for use in the program of design, development or challenge of ORACLE Racing.
THE ORACLE QUESTIONS
QUESTION 1
32. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR enters into an arrangement to provide a complete design package to CB for an AC72 Yacht?
This arrangement would conclude prior to 1 January 2013.
33. Answer: Yes. There is no Article that prohibits a Competitor from providing to another Competitor, before 1st January 2013, a 'complete design package' for an AC72 yacht.
QUESTION 2(a)
34. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB enter into an arrangement using the same builder(s) to build both AC72 Yachts (including hulls, wings and appendages) and the hulls are constructed to comply with the CIC requirements of the Deed as agreed in the Protocol? This arrangement would conclude prior to 1st January 2013.
35. Answer: Yes. There is no Article that prohibits a Competitor from engaging, before 1st January 2013, a builder who is also building an AC72 yacht for another Competitor. However should the builder not be independent from both Competitors, one of the Competitors will now have built two AC72 Yachts and thus be prohibited from building another by Article 29.2(a).
QUESTION 2( B)
36. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB enter into an arrangement using different builder(s) to build both AC72 Yachts (including hulls, wings and appendages) and the hulls are constructed to comply with the CIC requirements of the Deed as agreed in the Protocol? The builders share moulds and/or use moulds that are the same or similar geometry to construct certain components including Hulls, cross structure, Wing Spars, wing flaps and appendages. This arrangement would conclude prior to 1st January 2013.
37. Answer: Yes. There is no Article that prohibits, before 1st January 2013, two Competitors using different builders who share moulds.
QUESTION 3
38. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB sail their AC72 Yachts in collaboration? They conduct a two boat test program to develop their design. Each yacht would not sail more than 30 days and this arrangement would conclude prior to 1st January 2013.
39. Yes. There is no Article that prohibits the conducting of mere practice races between two Competitors' yachts but if there is an arrangement to share performance information then there is likely to be a breach of Article 33.4. Also, for both OR and CB the other Competitor's AC72 would meet the definition of 'Surrogate Yacht' (Article 1.1 (xx)). Using such Surrogate Yacht for training or for testing and development as described in Article 29.4 would constitute the acquisition of an AC72. While this does not breach any Article of the Protocol in itself, this would then prohibit either Competitor from acquiring, building or otherwise obtaining another AC72, as limited by Article 29.2(a).
QUESTION 4
40. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR tests a component (such as a wing or daggerboards or sails) belonging to CB on its AC72 Yacht?
41. Answer: No. The Jury concurs with ETNZ's submission that using components of another Competitor in their own yacht will inevitably involve the exchange of design and probably performance information which is prohibited under Article 33.2 after 1st January 2013. This may also result in result in CB using a Surrogate Yacht as set out in Article 29.4. While this
does not breach any Article of the Protocol in itself, this would then prohibit CB from acquiring another AC72.
QUESTION 5
42. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB share performance data obtained prior to 1st January 2013?
43. Answer: Yes. There is no article that prohibits two Competitors from sharing performance data obtained prior to 1st January 2013, provided Article 33.4 is not breached by virtue of an agreement between the two Competitors. However, both OR and CB will be using each other's boats for their development. They will therefore be Surrogate Yachts for each other, as set out in Article 29.4 and then both of them will be prohibited from building another AC72 Yacht under Article 29.2.
QUESTION 6
44. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if Crew employed by OR sail on CB's yacht while it is sailing in collaboration with OR's yacht? Each yacht would not sail more than 30 days and this arrangement concludes prior to 1st January 2013.
45. Answer: Yes. However, both OR and CB will be using each other's boats for their development. They will therefore be Surrogate Yachts for each other, as set out in Article 29.4 and then building another yacht becomes prohibited under Article 29.2.
QUESTION 7
46. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if after 1st January 2013, OR and CB continue to sail together from time to time? Crew employed by OR would sail on CB's yacht after 1st January 2013 and up until the first race of the Regatta.
47. Answer: Probably not, because it would almost certainly breach Article 33.2. It is hard to envisage that the crew will not return with design or performance information. Because they will also be using each other's boats for development and training they will be Surrogate Yachts for each other, as set out in Article 29.4 and then building another yacht becomes prohibited under Article 29.2.
QUESTION 8
48. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR enter into an arrangement to provide what is detailed in points 1, 2(a) or 2( B) , 3, 4 and 5 with CB? OR would build another AC72 Yacht while CB would not.
49. Answer: No. This would breach Article 33.4 and the arrangement would have the effect of ORACLE Racing acquiring a second AC72 Yacht. Should they then build another AC72 Yacht, it would be their third, which would breach Articles 29.2(a).
(excuse my poor english)
http://noticeboard.a...11/08/JN024.pdf
8 questions from Oracle about the possibilities and limits of his collaboration with other equipment, Challenger or Defender.
The most important: .
Any prior agreement or arrangement about sharing performance data is illegal without exception (art. 33.4).
You can share the performance data, but, in this case, you are using the other boat as a "Surrogate Yacht", and you can't build a "second" boat, because it's a "thirth"
The truth is that, after reading the Protocol, the interpretation of the Kiwis-LR was caught by the hair ...
Luna Rossa tries to interprete the 33.1 and 33.2 as guarantors of rights, but the text is trying to put prohibitions limiting collaboration, not ensure rights.
Oracle raises 8 questions from less to more collaboration.
According to the responses to Oracle, before 2013, a team can, without bring consequences:
1 .- Give a complete design to another participant.
2 .- Share molds in different shipyards. Or build in the same yard, provided that it's an independent one, because if one of the teams have already constructed two boats (in "it's" yard), although one of them is for the other team, no more boats can be constructed by the "builder" team.
3 .- Sailing, testing the boats and training together.
(But. .. and here begins the limitations
By sharing the test data of the other boat for the development of your own boat, the other is considered a "Surrogate Yacht" which counts as a second boat, and you can not build a third one. And if they made an agreement to that, then they are falling under the prohibition of 33.4.
4 .- A team can test own boat with the wings, sails, appendages, or other equipment of another team (until 2013), but then the other is using the boat of the first team as a "Surrogate Yacht" and they can not build a second ship.
5 .- Although not sail together, two teams can share performance data, but then both are using the other as "Surrogate Yatch", and can't build a second ship. And if there is prior agreement for sharing, falls under the prohibition of 33.4.
6 .- Members of a team can sail aboard the other for training and development, but then it is the same: both are using two boats to design development, and can not build another.
7 .- In 2013, if they are training together with mixed crews, it is hard to think they do not return with information on performance, prohibited from sharing in that year. And the other boat is used for development, could not build another boat.
8 .- If a team makes a preliminary agreement to take advantage derived from points 1 to 5, is in any case against the prohibition of agreements referred to in 33.4. And that agreement would also have the effect of the two teams are already using two ships, and could not make another one.
_____________________
Result, in my opinion:
Change the names of Oracle and Competitor B for ETNZ and Luna Rossa (or whatever) and you get the following:
The agreement between ETNZ and Luna Rossa is against the Protocol.
They have released the agreement assuming an interpretation of the text of the Protocol has not been accepted (and I think caught by the hair).
Some sayed it would be possible to take advantage of these rules and to make even a second (third) boat if you do not "share" the performance data you get from your boat, but the other team measures your boat from the outside, and you measure the other boat from the outside . If you have two identical boats, the data of resistance and structural loads are the same, and the speed data are not given by the other team, but by you from outside ...
But the problem is that ETNZ and LR have already made public that they have reached an agreement ... without asking about the legality of the agreement ... And now, the prohibition of agreements do not have exceptions. And their interpretation of the Protocol is flawed, and they are out of bounds.
I guess they can say it was an interpretation of good will, break the agreement, and working in the limits we now know it is legal ...
In any case, pending the question asked by Artemis, precisely on the specific terms of the agreement ETNZ-LR. Maybe not needed.
Let's see what happens.
Clearly, these rules allow collaboration between two teams who want to build only one boat each. They take all advantages of sharing everything until 2013, and do not mind not being able to make a second boat (which would be the third prohibited ...). It is possible as long as there is no "agreement", but only actual sharing. This implies that, if you say it's over, it's over. The other has nothing to say.
TEXT:
DISCUSSION on Articles 33.1, 33.2 & 33.4
25. Luna Rossa Challenge 2013, in its submission of 17th December, asserts that '…33.4 is a general anti-avoidance clause that must be interpreted in the context of the rights granted by 33.1 and 33.2'. The Jury disagrees. It is not appropriate to interpret Articles 33.1 and 33.2 as 'giving rights'. Each Article starts with a prohibition, followed by limited relief from that prohibition. The relief relates only to the particular prohibition contained in the Article. For
example, a Competitor may take advantage of the relief described in (a) to (e) in Article 33.2, but must nevertheless comply with Article 33.4 which stands alone and applies at all times.
Each of the clauses in question stands alone, but needs to each be read so that they are consistent with other Articles.
26. The Jury sees no justification to treat any of the four parts of Article 33 as being superior or inferior to any other part, or subject to any 'read-down'. Article 33.4 stands alone and applies at all times. Accordingly, some actions that might not be prohibited by Article 33.1 or 33.2 might be prohibited by Article 33.4.
27. Articles 33.1 and 33.2 are not, as several submissions suggested, 'permissive' rules. They prohibit certain activities after 1st January 2013 that would otherwise not be prohibited.
28. Without Articles 33.1 and 33.2, two Competitors (or potential Competitors) may have a common designer, and may share or exchange AC72 Class design or performance information or equipment, provided there is no 'agreement, arrangement or other understanding', as described in Article 33.4, between the Competitors.
29. However Articles 33.1 and 33.2 tell us that from 1st January 2013, two Competitors (or potential Competitors) may not have a common designer, nor share or exchange AC72 Class design or performance information or equipment.
30. Articles 33.1, 33.2 and 33.4 must be read in conjunction with Article 29.2(a) which provides a clear requirement that Competitors 'may build, acquire or otherwise obtain a maximum of two new AC72 Yachts'.
31. The Jury determines that for Article 33.4 to apply, three requirements have to be satisfied:
(a) There must be an 'agreement, arrangement or other understanding, whether legally enforceable or not', between ORACLE Racing and another entity (e.g. Competitor B (CB));
( B) The arrangement involves CB directly or indirectly building or acquiring one or more yachts of any type; and
© ORACLE Racing can (not 'will' or 'did') directly or indirectly obtain, in any manner whatever, design or performance information regarding CB's yacht for use in the program of design, development or challenge of ORACLE Racing.
THE ORACLE QUESTIONS
QUESTION 1
32. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR enters into an arrangement to provide a complete design package to CB for an AC72 Yacht?
This arrangement would conclude prior to 1 January 2013.
33. Answer: Yes. There is no Article that prohibits a Competitor from providing to another Competitor, before 1st January 2013, a 'complete design package' for an AC72 yacht.
QUESTION 2(a)
34. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB enter into an arrangement using the same builder(s) to build both AC72 Yachts (including hulls, wings and appendages) and the hulls are constructed to comply with the CIC requirements of the Deed as agreed in the Protocol? This arrangement would conclude prior to 1st January 2013.
35. Answer: Yes. There is no Article that prohibits a Competitor from engaging, before 1st January 2013, a builder who is also building an AC72 yacht for another Competitor. However should the builder not be independent from both Competitors, one of the Competitors will now have built two AC72 Yachts and thus be prohibited from building another by Article 29.2(a).
QUESTION 2( B)
36. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB enter into an arrangement using different builder(s) to build both AC72 Yachts (including hulls, wings and appendages) and the hulls are constructed to comply with the CIC requirements of the Deed as agreed in the Protocol? The builders share moulds and/or use moulds that are the same or similar geometry to construct certain components including Hulls, cross structure, Wing Spars, wing flaps and appendages. This arrangement would conclude prior to 1st January 2013.
37. Answer: Yes. There is no Article that prohibits, before 1st January 2013, two Competitors using different builders who share moulds.
QUESTION 3
38. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB sail their AC72 Yachts in collaboration? They conduct a two boat test program to develop their design. Each yacht would not sail more than 30 days and this arrangement would conclude prior to 1st January 2013.
39. Yes. There is no Article that prohibits the conducting of mere practice races between two Competitors' yachts but if there is an arrangement to share performance information then there is likely to be a breach of Article 33.4. Also, for both OR and CB the other Competitor's AC72 would meet the definition of 'Surrogate Yacht' (Article 1.1 (xx)). Using such Surrogate Yacht for training or for testing and development as described in Article 29.4 would constitute the acquisition of an AC72. While this does not breach any Article of the Protocol in itself, this would then prohibit either Competitor from acquiring, building or otherwise obtaining another AC72, as limited by Article 29.2(a).
QUESTION 4
40. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR tests a component (such as a wing or daggerboards or sails) belonging to CB on its AC72 Yacht?
41. Answer: No. The Jury concurs with ETNZ's submission that using components of another Competitor in their own yacht will inevitably involve the exchange of design and probably performance information which is prohibited under Article 33.2 after 1st January 2013. This may also result in result in CB using a Surrogate Yacht as set out in Article 29.4. While this
does not breach any Article of the Protocol in itself, this would then prohibit CB from acquiring another AC72.
QUESTION 5
42. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR and CB share performance data obtained prior to 1st January 2013?
43. Answer: Yes. There is no article that prohibits two Competitors from sharing performance data obtained prior to 1st January 2013, provided Article 33.4 is not breached by virtue of an agreement between the two Competitors. However, both OR and CB will be using each other's boats for their development. They will therefore be Surrogate Yachts for each other, as set out in Article 29.4 and then both of them will be prohibited from building another AC72 Yacht under Article 29.2.
QUESTION 6
44. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if Crew employed by OR sail on CB's yacht while it is sailing in collaboration with OR's yacht? Each yacht would not sail more than 30 days and this arrangement concludes prior to 1st January 2013.
45. Answer: Yes. However, both OR and CB will be using each other's boats for their development. They will therefore be Surrogate Yachts for each other, as set out in Article 29.4 and then building another yacht becomes prohibited under Article 29.2.
QUESTION 7
46. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if after 1st January 2013, OR and CB continue to sail together from time to time? Crew employed by OR would sail on CB's yacht after 1st January 2013 and up until the first race of the Regatta.
47. Answer: Probably not, because it would almost certainly breach Article 33.2. It is hard to envisage that the crew will not return with design or performance information. Because they will also be using each other's boats for development and training they will be Surrogate Yachts for each other, as set out in Article 29.4 and then building another yacht becomes prohibited under Article 29.2.
QUESTION 8
48. Would ORACLE Racing (OR) and Competitor B (CB) remain compliant with the Rules if OR enter into an arrangement to provide what is detailed in points 1, 2(a) or 2( B) , 3, 4 and 5 with CB? OR would build another AC72 Yacht while CB would not.
49. Answer: No. This would breach Article 33.4 and the arrangement would have the effect of ORACLE Racing acquiring a second AC72 Yacht. Should they then build another AC72 Yacht, it would be their third, which would breach Articles 29.2(a).
Last edited by a moderator: