Posts Tagged ‘use’

Use of Software and those computer defences again

Tuesday, March 31st, 2009

You’ll recall that SAG licensed its database software to RWWA. RWWA engaged KAZ to provide disaster recovery services and installed a copy of the software on KAZ’ off-site servers. Meckerracher J dismissed SAG’s claim that this was unlicensed and therefore infringement of its copyright. (link via my attempt to summarise here).

The Full Court has substantially dismissed the appeal, but found the judge was wrong to the extent his Honour considered s 47F of the Copyright Act 1968 would have provided a defence also.

On the question of licence construction, their Honours found that the proposed use fell within the terms of the licensed use “for … emergency restart purposes“:

34 The phrase “for … emergency restart purposes” is more ample than, for example, “in order to restart the System in an emergency”. A penumbra surrounds “emergency restart”. It is a natural reading of the composite phrase to include within its coverage testing whether the copied System will restart should an emergency occur.

35 If one were to regard the phrase “for … emergency restart purposes” as open to two constructions, SAG’s construction, in our view, results in a meaning that would be unreasonable or inconvenient. The purpose behind clause 12.3 is to protect RWWA from serious loss in an emergency, whether caused by a breakdown of its mainframe or some external event putting it out of action. It would be an unreasonable and inconvenient result if RWWA were to be unable to take sensible steps to make it more likely that the purpose behind clause 12.3 would be achieved, by testing the copied system in order to maximise the chance of the restart occurring in the event of an emergency arising.

36 Further, we agree with the primary judge’s observation quoted at [28] that SAG’s interpretation would make clause 12.3 a pointless exception to the other prohibitive or restrictive provisions of the agreement, and that such a construction would provide very little scope for achieving the purpose of clause 12.3 described above.

The expert evidence was also consistent with this.

While the Licence Agreement did (by clause 1.4) expressly prohibit the software being installed at any location other than the “designated location”, the clause had to be read in context and clause 12.3, as SAG acknowledged, did permit RWWA to use the software “for archival or emergency restart purposes”. Clause 1.2,which prohibited “use” on anything other than the designated hardware, similarly had to be read down.

If the terms of the licence had not been capable of construction to permit this (fairly typical) type of disaster recovery strategy, however, s 47F would not have protected RWWA. S 47F provides a limited defence for “security testing”. However:

55 What s 47F(1) permits is the reproduction of the original copy for the purpose of testing the security of that copy. The original copy is the copy RWWA is licensed to use. The permitted testing is of the security of that copy. The passages from the primary judge’s reasons quoted at [49] appear to us to be saying that the testing of the functionality of the DR Copy at the DR Site is the testing of the security of the original copy at Osborne Park. That, in our view, is not what s 47F(1) authorises. On the facts of this case, what it permits is the making of a copy of the installed copy at Osborne Park for the purpose of testing the security of the installed copy. As it seems to us, the primary judge’s construction of the provision enables the DR Copy at the DR Site to be tested so as to determine its efficacy should the installed copy at Osborne Park for some reason be no longer available.

and, given the unchallenged expert evidence on the issue:

68 For the above reasons we are unable to accept RWWA’s contention, which the primary judge appears to have adopted, that “testing … the security of the original copy” extends to what was done at the DR Site, namely testing of the DR Copy to ensure that the System would be capable of being restarted and operated without the loss of data. In our view, “testing … the security of the original copy” should be confined to testing the original to ascertain its security from unauthorised access or against electronic or other invasion.

The Court noted, but did not need to consider the correctness, of his Honour’s conclusion that s 47C would also have protected RWWA.

So, an appellate level illustration providing some confirmation of how strictly the the Courts will approach the gobbledygook enacted in the special computer program defences. Make sure you draft your software licences to provide the protection actually needed – especially if the software needs to be used in a “disaster recovery” situation.

Software AG (Australia) Pty Ltd v Racing & Wagering Western Australia [2009] FCAFC 36 (Spender, Sundberg and Siopis JJ)

  • Share/Bookmark

Beery barefeet on appeal

Friday, March 27th, 2009

Curiouser and Curiouser!

The Full Court has affirmed the trial judge’s finding that Gallo’s registration of the trade mark BAREFOOT for wine should be removed for non-use. However, the Full Court has overturned his Honour’s finding that Lion Nathan’s use of Barefoot Radler for beer did not infringe that registration (before it was removed). Consequently, the Full Court has found that Lion Nathan did infringe the registration up until the date the registration was removed from the Register.

Gallo acquired the trade mark by assignment. Neither it nor the assignor had ever consciously used it in Australia.  However, some wine bearing the trade mark had made their way into Australia for resale via, presumably, a parallel importer. (More detailed summary of the facts from the decision at 1st instance here and here – the internal links are broken I’m afraid.)

On the question of whether or not Gallo (or its predecessor) had used the trade mark as a trade mark, the Full Court said:

34 In our opinion, the conclusion of the primary judge was correct. The contention of Gallo that an owner of a registered trademark uses the mark in Australia simply because goods to which the owner (or an authorised user) has affixed the mark are traded in the ordinary course of trade in Australia should be rejected.

and

38 …. The essence of Gallo’s case in this matter is this is all that is necessary to establish use in Australia by the manufacturer or producer. However, that is not what the Full Court said. Projection by the manufacturer of goods bearing its mark into the course of trade in Australia was the other factor which, together with the display, sale or offering for sale, led to the conclusion that there had been use of the mark in Australia by the manufacturer and its owner. We think fairly plainly what the Full Court was saying was that for there to be use in Australia of the mark by the owner, the owner of the mark must have engaged in conduct of some type which the owner might reasonably contemplate would result in dealings with its goods marked with its mark in Australia while the goods were in the course of trade.

As a matter of interpretation, the Full Court concluded, contrary to Lion Nathan, that the trade mark could be expunged only from the date the Court made the order under s 101.

This was particularly significant because the Full Court, as noted above, found that Lion Nathan’s use infringed the trade mark while it was registered.

First, the Full Court rejected the trial judge’s finding that beer and wine were not goods of the same description:

72 The primary judge accepted that there were a number of factors which supported the view that Lion Nathan’s beer and wine were goods at the same description. They were both alcoholic beverages and generally distributed by this same major wholesale distributors. The beer was intended to be an appealing alternative to wine and in developing the product, Lion Nathan deliberately set out to attract people who did not drink beer. Indeed it was developed with the deliberate objective of enticing consumers who previously drank wine but not beer. Producers of alcoholic beverages are no longer confined to the production of beer, as opposed to wine, and large producers of alcoholic beverages now produce a range of products and market themselves as doing so. Companies which were once brewers now market and distribute a range of products including beer, wine, spirits, cider and non-alcoholic drinks. Wine and beer are now frequently distributed by the same retailers. We agree that these matters point, and in our opinion point convincingly, to Lion Nathan’s beer and wine being goods of the same description.

73 The considerations which led his Honour to reach the opposite conclusion are, in our opinion, of materially less significance. The first, which concerned the origin of the goods, focused on the manner of manufacture of beer on the one hand and wine on the other. While this clearly establishes that they are not the same goods, it is unlikely that this difference would be significant to the consuming public if, as his Honour found, large producers of alcoholic beverages produce a range of products. Additionally it is important to bear in mind that this issue is being considered in the more general context of whether consumers might see the goods as having the same trade origin: Southern Cross at 606. The same can be said of the next consideration relied on by his Honour, namely the specific manner of sale in restaurants on the one hand and retail outlets on the other. If large producers of alcoholic beverages are producing a range of products then the fact that the wine might be sold in a slightly different way would not be a difference of significance to the consuming public who may come to consider the trade origins of Lion Nathan’s beer. The next consideration was the manner in which beer is consumed, that is drunk for its refreshing qualities, and not, like wine, consumed in a “sipping fashion”. For our part, we doubt this is a relevant consideration. Nor do we think the last consideration, the detailed corporate structure of Lion Nathan, is of any real significance.

Then, the Full Court upheld the trial judge’s finding that Lion Nathan’s BAREFOOT RADLER trade mark was deceptively similar to Gallo’s trade mark.

Finally, the Full Court rejected Lion Nathan’s attempt to rely on the (rarely used) proviso to s 120(2)(b) which provides:

However, the person is not taken to have infringed the trade mark if the person establishes that using the sign as the person did is not likely to deceive or cause confusion.

The Full Court foreshadowed that this was a tough requirement to hurdle:

76 …. However, any conclusion about deceptive similarity would usually inform consideration of whether the actual use was likely to deceive or cause confusion. In a sense, an affirmative answer to the question of whether the alleged infringing mark was deceptively similar would be the starting point. If it was, then it would, in many instances, render it more likely (though not inevitable) that the actual use of the allegedly infringing mark was likely to deceive or cause confusion. Also relevant, in our opinion, would be the matters considered in determining whether the alleged infringer’s goods are of the same description as the goods in respect of which the registered mark is registered.

Lion Nathan had not satisfied this requirement here. The facts that the usage was on beer, the beer was packaged in six packs and in retail stores from the “beer” section did not help:

77 …. The use of the image of a bare foot with the words “BAREFOOT RADLER” would be more likely to reinforce the significance or prominence of the word “BAREFOOT”. The fact that the allegedly infringing mark was on beer packaged in the way described does not, in our opinion, tell against the likelihood that a person looking at beer packaged in this way would think that the beer originated from Gallo. If, in a retail liquor outlet, there was beer bearing the trade mark “BAREFOOT RADLER” where the word “RADLER” was the description of a type of beer and also wine with the trade mark “BAREFOOT” immediately followed by a description of the type of wine (by reference to grape type), then there is, in our opinion, little room to doubt that it is likely many would view the former as originating from the producer of the latter.

The matter will be remitted to the trial judge to deal with remedies. Wonder what the damages will be?

So, it would seem you should bring and conclude your non-use action before you launch the product. That will require a client with a very long term commitment to the brand!

E & J Gallo Winery v Lion Nathan Australia Pty Limited [2009] FCAFC 27 (Moore, Edmonds and Gilmour JJ)

  • Share/Bookmark

Not using a trade mark

Friday, January 30th, 2009

An Austrian company, Maselli, sells clothing under its brand WELLNESS.  It has the trade mark registered for clothing in class 25 and also in classes 16 (for printed matter) and class 32 (for alcohol free drinks).  It gave away bottles of a non-alcoholic drink bearing the WELLNESS brand, but never sold the drinks independently of the clothing.

On application by Silberquelle, a producer of alcohol free drinks,  the ECJ has ruled that affixing the mark to goods, which are given away free of charge to purchasers of other goods, is not genuine use of the trade mark for the free goods in the EU.

That is, it should follow that Maselli’s mark will be revoked.

Here, of course, there has to be use as a trade mark and the use (as a trade mark) has to be in good faith see s. 92 and Gallo v Lion Nathan

As the IPKat asks, what happens to a newspaper’s trade mark where the newspaper is given away free?

Ever since the old Irish case about “Golden Pages” TM, where a classified directory was given away for free, but contained paid advertising, we have thought the trade mark was being used in the course of trade (or in more modern parlance, in good faith as a trade mark).  Wonder if that’s still the case?

C-495/07 Silberquelle GmbH v Maselli-Strickmode GmbH

  • Share/Bookmark

Madrid system and ‘foreign’ trade marks in the USA

Monday, September 8th, 2008

So, you’re not a USA-based trade mark owner and you’ve got your “trademark” registered in the US through the Madrid system.  That means you don’t have to worry about all those annoying requirements actually to use the trade mark there, doesn’t it?

Well, no.

Saunders & Silverstein  lay out all the pitfalls that you are going to have to hurdle here.

Lid dip to the Kat with the plummy accent.

  • Share/Bookmark

A case on computer software licences and back ups in Australia

Thursday, September 4th, 2008

A rare and interesting decision on the scope of (mainframe) computer software licences and s 47C (computer program back-ups) and s 47F (security testing) of the Copyright Act:

RWWA (which runs the West Australian TAB).  SAG granted it a non-transferable, non-exclusive licence to run the ADABAS database management software on its mainframe computer.  This was the software used for its its betting business.  

In addition to installing the software on its mainframe computer, RWWA arranged with KAZ to use KAZ’ mainframe for a ‘warm’ disaster recovery site: RWWA stored a mirror-image disk copy on KAZ’s mainframe computer.  Although a copy was stored on KAZ’s mainframe, it was not loaded into ‘memory’ except when being used in an actual disaster recovery situation or routine testing to ensure the back-up would work. Prior to this, RWWA had used back-up tapes stored off-site.

In a 268 paragraph decision, McKerracher J has held that RWWA did not breach of its licence by doing this and, in any event, was protected from copyright infringement by ss 47C and s 47F of the Copyright Act.  

The main issues were whether or not RWWA’s off-site storage and testing of the back-up and/or the involvement of KAZ entitled SAG to claim additional licence or maintenance fees (up to several hundred thousand dollars per annum).  In broad summary, SAG contended that

(1) storage and, in particular, the testing of the back-up was in breach of cl. 12.3 and required further maintenance fees or

(2) the involvement of KAZ was in breach of cl. 1.5 which prohibited ‘outsourcing’.

Cl. 1.5 provided:

1.5 The Licensee shall not assign, sub-licence, sell, lease, encumber, charge or otherwise in any manner attempt to transfer this Licence or any of its rights or obligations hereunder. The Licensee may not allow any third party to operate the System(s) on its behalf as part of any outsourcing, facilities management, application service provision or similar type of arrangement.

Clause 12.3 provided

12.3 Software AG hereby expressly authorises the Licensee to copy the System(s) (in object code only) and the Documentation for archival or emergency restart purposes PROVIDED THAT no more than (3) copies made by the Licensee of the then current system version shall exist at any time and all old versions shall be destroyed.

In rejecting SAG’s claims that cl. 12.3 did not protect RWWA, McKerracher J found:

186 Clause 12.3 is intended to be permissive. Objectively viewed, its purpose is to permit the licensee to reproduce the software to the extent that may be required for emergency restart purposes. To merely copy the distribution tapes or cartridges would be of limited practical use for that purpose. This is common ground amongst all experts. To construe cl 12.3 as being confined simply to copying tapes or cartridges of the unconfigured and uninstalled System would be a construction that is at least unreasonable and inconvenient but would also be unjust.

187 It is common ground that the System as supplied does include some source code. When the source code is converted to object code and is then linked to create load modules on installation of the System, the System as installed and configured then becomes a copy ‘in object code only’ and there is a copying of the System for emergency restart purposes.

and

203 As there is no technical meaning, the question is one of construction of the Licence Agreement. In my view the only sensible construction is that when the Licence Agreement refers to ‘use’ it means using the System within RWWA’s ordinary business or some other business, not for occasional testing for one DR Site. This must be so, in my view, if the DR Copy at the DR Site is authorised by cl 12.3 as I conclude that it is.

205 If the use by RWWA of the DR Site is authorised by cl 12.3, then the question as to whether or not the System is otherwise in use (for cl 1.1(d)), in my view, falls away. I consider that the use is so authorised.

Further, the copy was made for the purposes of emergency restart:

209 In a business which has an extremely high turnover of transactions and a substantial financial turnover, each day of delay is significant. In my view there is no scope for the argument that emergency restart simply means that the business has sustained a disaster or emergency which will require a restart at some leisurely pace in a week or so. In my opinion the whole concept of emergency restart means that as an essential part of a highly sophisticated business environment, the restart is required as quickly as reasonably possible.

Taking into account similar considerations, his Honor found that ss 47C and 47F would also operate to protect RWWA.

Nor was there any ‘outsourcing’ in breach of cl. 1.5:

249 Mr Fink who has had very extensive experience in the mainframe industry rejects the suggestion that the arrangement or contract between KAZ and RWWA is one which constitutes outsourcing in any sense. Rather, as a matter of practice and in accordance with the nature of the arrangement between KAZ and RWWA by its contractual documents, what KAZ provides to RWWA is an environment for the equipment on which the DR Copy will be loaded should an emergency occur. RWWA retains responsibility for the DR process. There is no evidentiary basis for suggesting that KAZ is in any way involved in operating the System. Without that evidence which, had it been available, may have been the closest there was to any ‘outsourcing’, none of the other suggested actions could constitute ‘outsourcing’ as it is used in the Licence Agreement.

Racing & Wagering Western Australia v Software AG (Australia) Pty Ltd [2008] FCA 1332 (29 August 2008)

  • Share/Bookmark