I shall set out, in what I intend to be for the main part an uncontroversial way, the relevant background facts.
Mr Conacher founded the 3D Safety business in the late 1980s. The first of his companies to commence operations was Services. It was an importer and distributor of industrial products, and a provider of safety-related services. It focused in particular on risky activities in the mining, construction and infrastructure industries.
Systems commenced to operate in about 2002. Its business was and has since continued to be the provision of safety management systems. For about five years, it offered paper-based safety management systems. They were converted to online management systems in about 2007.
The 3D system (that is to say, the consolidated online safety management system) was developed by Wishbone, in conjunction with McGirr information technology (McGirr). The agreement between Wishbone and McGirr provided that Wishbone would own all intellectual property (including copyright) in McGirr's work product created for Wishbone. Wishbone licenses the technology to Systems, and Systems is the exclusive user of that technology.
The e-Induct system was first developed in about 2007, by a partnership called BCP Marketing. Mr Culbert was a partner in that partnership. On 6 May 2009, the partners assigned the intellectual property rights in the e-Induct system to EIFY (then known as e-Induct).
The e-Induct system has always delivered online induction training to workers. As I have noted, it includes other functionality as well.
The parties first explored joining their operations in about 2008. Mr Culbert demonstrated the e-Induct system to Mr Conacher. They tendered to prospective customers including Woolworths (an existing customer of EIFY) and Thiess. Ultimately, the proposals went nowhere. The parties continued on their separate ways.
Messrs Culbert, Conacher and Morrow returned to the idea of a joint venture in February 2011. They met on 11 February 2011, and thereafter promoted the two systems together to various potential users. The terms of the proposed joint venture were not defined (and were never defined). The parties did not agree on fundamental matters such as structure, contributions, distribution of profits and the like.
In April 2011, Messrs Culbert and Conacher met representatives of Thiess. Thiess was an existing user of the 3D system. Messrs Culbert and Conacher sought to show that the e-Induct induction system and plant management functions could be accessed through the 3D system, although the two systems had not been integrated (nor were they ever).
A written quotation was sent to Thiess, which included an amount of $18,000 for "induction development, and deployment…". Thiess accepted the offer. The induction program was prepared and tested, and Thiess used it on a project known as the "Liebherr" project. The invoiced amount was paid to Group, which by then had been incorporated as the joint venture vehicle. Nonetheless, at the time of the negotiations with Thiess, no formal joint venture structure had been agreed, let alone documented.
In May 2011, Mr Culbert prepared a document showing how he thought the two systems might be integrated, or could work together. Mr Morrow registered the domain name "3D Safety.net", and Mr Culbert caused Group to be incorporated. The parties arranged to see a lawyer, Mr Mansfield of Addisons Lawyers.
Messrs Culbert, Conacher and Morrow met Mr Mansfield on 20 May 2011. After the meeting, Mr Mansfield circulated an email raising a number of matters for their consideration. The matters to be considered included how the parties would conduct their operations so that Group would have its own business free of competition from EIFY and 3D Safety; royalties for intellectual property contributed by each of the joint venturers; and profit distributions.
Those matters were never resolved. Further, although Mr Mansfield's firm produced a suite of draft documents for the contemplated joint venture, those documents were never reduced to a final form or executed.
In late May 2011, Group made proposals to Mirvac in connection with projects known as Era and Pinnacle. For the reasons I have given above [51] , I conclude that each of those offers was one made by Group, not EIFY. The contracts resulting from acceptance of those offers were likewise contracts made between Group and the offerees.
Joint venture discussions continued, although as I have said the parties never finalised, let alone formalised, the terms of their arrangement. Nonetheless, they continued to work as though the joint venture were proceeding. They sought to integrate the 3D System into the e-Induct system. Initially, that involved rewriting the source code of the 3D System into the language in which the e-Induct system was written, and developing an "interim integration" that could be used until the two systems were fully integrated.
Integration (real or apparent) was essential, because the real selling-point of the joint venture was that customers would have access, through the one system, to induction, plant management, access control and site control services (features of the e-induct system) and the various functionality aspects of the 3D System. The parties perceived, I think correctly, that the ability of users to manage all those functions through the one system, which would store in one accessible place all relevant data relating to all aspects of the systems' operation, was very attractive.
The prime object of the parties' attention was the Lend Lease development at Barangaroo. For that, it was essential that the two systems should function seamlessly together. The parties had a number of meetings, and exchanged a number of documents, directed to ensuring that they could meet Lend Lease's deadline. The problem was that Lend Lease apparently required the system to be functional by the end of September 2011, because it was proposing to commence the project at the beginning of 2012. The parties agreed that it was "critical" to complete the rewrite of the 3D systems' source code to the language of the source code of the e-induct system.
On 20 July 2011, Messrs Culbert and Conacher met. They signed a document referred to as "Schedule Three". That document referred to the "critical" timeline, and noted that the parties might terminate their relationship if the rewrite were not complete by 30 September 2011. The document noted, further, that if the deadline were not met and the project was terminated, Systems might develop its own online induction system, and compete with EIFY. I should say that Mr Culbert gave evidence that the document was not signed on 20 July 2011. I do not accept that evidence.
Messrs Conacher and Morrow were concerned that EIFY might not be able to meet the timeline (more accurately, deadline) of 30 September 2011. They understood that EIFY's site access system, which as I have said is a component of the e-Induct system, was important. They therefore investigated whether a similar system could be obtained from a third party supplier. As part of that investigation, they spoke to Mr Nanayakara of McGirr, and the three of them met the representatives of the manufacturer or distributor of software called Inner Range.
The meeting with Inner Range took place on 28 July 2011. The representative of Inner Range said that there was an available off-the-shelf solution. Mr Culbert denied that there was such a product available commercially. Whether or not that is correct (and I regard Mr Culbert's denial as motivated more by self-interest than a concern for the truth), the simple fact is that this is what Messrs Conacher and Morrow were told.
On 29 July 2011, Messrs Culbert, Conacher and Morrow met. Mr Conacher handed Mr Culbert a letter which said, among other things, that in the view of 3D Safety, it and e-Induct did not "bring an equal and comparable offering to a joint venture". Accordingly, the letter said, it was 3D Safety's view "that the proposed joint venture cannot succeed in its present format". 3D Safety expressed a desire "to hold discussions on a different structure and relationship".
Mr Culbert denied that he was given this letter. I do not accept his denial. Surrounding circumstances, including that on 1 August 2011 Mr Conacher started to prepare what he called a "Memorandum of Understanding" proposing a different structure for the joint venture relationship, are consistent with the letter's having been handed over on 29 July. So, too, are further communications between the parties in August and early September 2011 seeking to redefine the basis on which the joint venture might proceed.
By 30 September 2011, the integration had not been completed. Neither side sought to terminate the joint venture. Work continued on the integration process. A meeting was arranged for 29 November 2011, to show what progress had been made on integration. The meeting was a failure, as was the demonstration of the integrated system.
A further meeting was held on 9 December 2011, so that the integrated system could be demonstrated. Again, the meeting and the demonstration failed. Mr Culbert accepted that he had said there would be a functioning integrated system available to demonstrate at the meeting, but that the integrated system was not then working. [52]
On the failure of the demonstration, Mr Conacher handed Mr Culbert a letter terminating the joint venture. Mr Culbert accepted that, given the history of the attempts to integrate the systems and the failures to achieve integration, that was decision was open to Mr Conacher (or 3D Safety) [53] .
On 15 December 2011, the directors of Group held the meeting to which I have referred already [54] . The principal matters of significance discussed at that meeting were the process of termination, or perhaps winding-up, of the joint venture, the rights of the parties to conduct their own businesses thereafter, and how the existing Thiess Liebherr project might be managed in the future. The parties also reached and signed a form of acknowledgment as to the intellectual property rights of Wishbone and EIFY. That acknowledgment is important for EIFY's case on confidential information, and that is the context in which I shall deal with it.
Thereafter, generally, the parties went their own ways. EIFY continued to pursue the opportunity to do work for Lend Lease on the Barangaroo Project. Systems continued to develop its own system which could deliver online inductions and other forms of training, and could operate together with Services' online safety management system. The work for that was done by Mr Malthus, as an employee first of McGirr and later of 3D Safety.
[2]
Approach to resolution of the issues
I turn at last to the issues. I shall start with the confidential information case. For convenience, I propose to consider separately the contractual case (in the various ways in which it was formulated) and the claim for confidence in equity. Having done so, I will deal with the case of breach.
Next, I shall consider the claim in copyright, dealing first with the question of whether copyright subsists, and second, to the extent that the copyright does subsist, with the question of breach.
Next, I shall deal with the case based on misleading or deceptive conduct.
That leaves, from the issues set out at [8] above, the question of remedies. Since I have concluded that EIFY has not made good its case (however formulated), no question of remedy arises.
Before commencing to deal with the issues, I point out that their resolution has been made difficult both by the way the case was run and by the way that EIFY put its case in its final submissions. The matter was fixed for hearing on an estimate of 10 days. That estimate proved to be grossly inadequate. A further 10 hearing days were required. For reasons of convenience to Counsel, the further 10 days could not run consecutively. There was a week's break between the third and fourth weeks of the hearing.
That week's break, together with a shorter break in the last week of hearing, should have enabled the parties to prepare their final submissions in a way that analysed, issue by issue, the relevant evidence (referring to it where necessary), and put such arguments as were appropriate.
Unfortunately, EIFY's closing written submissions did not do so. For example, they started by referring retrospectively [55] to a number of propositions that were said to have been "developed in oral submissions". They did not attempt to canvass the evidence other than by way of what might be called line item references to some passages of it. To some extent, that deficiency was addressed in oral submissions. However, the oral submissions were not directed clearly to the issues as EIFY had stated them.
To compound the problem, EIFY's oral submissions did not fulfil the promise implicit in its written submissions. On the contrary, the oral submissions referred repeatedly to matters that they said would be fully developed in the written submissions. This the latter failed to do.
As a result, and because of the lack of focus and attention to the pleadings or the stated issues, chunks of EIFY's case fell, as it were, between the gaps.
Further, EIFY's closing submissions, both oral and written, paid little attention to the structure of the pleaded case. That was unfortunate, particularly where Mr Andronos had made it clear that the defendants proposed to hold EIFY to the limits of its pleaded case.
Again, on the question of breach of duties of confidence, the written submissions for EIFY asserted unhelpfully to the effect that it "will ultimately submit that the defendants breached duties of confidentiality"; and stated without elaboration baldly and conclusory submissions (for example, that it was "plain that [the defendants] have violated the… Terms of Use").
Another problem with EIFY's submissions was their occasional reliance on evidence that had been rejected. For example, when dealing with the proposition that 3D Safety had copied EIFY's object code, the submissions referred to Professor Braun's report, as setting out "the argument". Leaving aside whether that is an appropriate exercise for an expert to undertake, the only paragraphs that could be said to have essayed this (and none went so far as the submissions suggested) had been rejected.
EIFY devoted considerable effort in both its written and its oral submissions in seeking to demonstrate that the defendants had gone into the joint venture as a sham, intending to use it to deprive EIFY of its confidential property. Acceptance of that submission would require, as Mr Andronos submitted, acceptance that much of the contemporaneous documentation was sham: created as a cloak to conceal the asserted true motive. No attempt was made to demonstrate that. Indeed, it was never put to Mr Conacher or Mr Morrow that back in 2011, they had set about creating false and misleading documents for the purpose of disguising their suggested true plan.
In the result, the oral submissions concluded on 4 August 2017, but neither side had replied in any significant way to the written (or oral) submissions of the other. Therefore, and with considerable reluctance, I permitted a further period of time for each to provide written submissions in reply. Again to suit the convenience of counsel, I fixed 14 days as the time within which those submissions should be provided.
Perhaps, the matter could have been dealt with on the basis of the submissions that had been put up until the end of the oral hearing. However, that would have created significant injustice for each party. The extent of that injustice, from the prospective of EIFY, can be assessed by the fact that it is really only EIFY's written submissions in reply that brings some coherence and structure to the way that it seeks to argue its case.
It is worth giving some content to the magnitude of the task:
1. EIFY's opening outline of submissions comprised 19 pages.
2. The defendants' comprised 25 pages.
3. EIFY's written closing submissions comprised 46 pages, and they were supported by many pages described as a "schedule of relevant passages" in the cross-examination of Mr Conacher.
4. The defendants' written closing submissions comprised 94 pages. They were supported by a schedule comparing various forms of the induction material, comprising 29 pages.
5. EIFY's written submissions in reply comprised 72 pages; and
6. The defendants' written submissions in reply comprised 31 pages.
All in all, the task of trying to work out what each party's case was, and what submissions it put on the various issues, required me to work back and forth between over 270 pages, comprised in six different documents, some of which had detailed supporting schedules, and in addition to have regard to the transcript of each side's closing oral submissions.
In the result, between the delays and the detail, I may have missed some important submission put for one party or the other. It is undesirable that litigation should be conducted in a way that makes this possible.
One consequence of the extraordinary length of the parties' submissions is that any attempt to summarise them would be both productive of enormous waste of time and paper and, quite possibly, unhelpful. Accordingly, in dealing with the issues, I shall refer to the submissions only to the extent that it is necessary to outline the essential disputes. Further, in an attempt to keep these reasons within some manageable limits, I propose to deal with the dispositive issues, and not to decide disputed questions of fact where, for reasons that I shall give, it is unnecessary to do so.
The court book was another source of extreme vexation and inefficiency. As originally propounded, it comprised 29 volumes. It was apparent that very little thought had gone into the selection of the material to be comprised in those 29 volumes. It was even more apparent that no thought whatsoever had gone into arranging the material in those volumes in any logical, structured or most importantly chronological fashion.
I said that I would not permit the tender of such an ill-disciplined monster. Thereafter, over some days, the bulk of the material was reduced to nine volumes. However, the organisational and chronological problems were not corrected. The result is that although the volume of material to be consulted has been considerably reduced, the difficulty of finding any particular document has been reduced only marginally. Further, because of the disorganisation of the remaining nine volumes, it is often necessary to consult two or even three volumes to put together a coherent chronological sequence of documents or events.
[3]
EIFY's confidential information case: introduction
In broad outline, EIFY claims that Services, Systems, and Messrs Conacher and Morrow owed it duties of confidence. Those duties are said to have arisen either from contract or in equity.
The contractual claim is based on the proposition that Messrs Conacher and Morrow registered on the e-Induct system, and thereby created accounts for Services or Systems (or, perhaps, both). In doing so, EIFY says, they accepted its terms and conditions, which included specific provisions relating to confidentiality, both personally and so as to bind the companies.
Further, EIFY says, the acknowledgment as to intellectual property that was signed following the meeting of 15 December 2011 has contractual effect, and contains specific recognition of its intellectual property rights and as to its confidential information to which, in the course of the joint venture, representatives of 3D Safety were given access.
EIFY says that although the claim to confidence in equity is independent of its rights in contract, its contractual rights are important because they help to emphasise that the information imparted to 3D Safety was confidential. That information, EIFY says, was given to Messrs Conacher and Morrow (and, more generally, 3D Safety) in circumstances where they must have recognised that it was confidential, and that they were not at liberty to deal with it as they wished. Further, EIFY says, the information was of a kind which is inherently susceptible of protection in equity.
EIFY submits, further, that Messrs Conacher and Morrow, or 3D Safety, owed it fiduciary duties arising both from the position of "vulnerability" in which EIFY found itself vis à vis 3D Safety, and out of the joint venture relationship that had subsisted.
[4]
The claim based on acceptance of EIFY's terms of use
[5]
The evidence as to registration
EIFY's computer records show, and it is not controversial, that Mr Conacher and Mr Morrow were registered as users on the e-Induct system. The sequence and detail of those registrations is as follows:
1. on 14 February 2011, Mr Morrow was registered with the email address and username "sm@3dss.com.au", and with reference to the company name "3D Safety Services Pty Ltd".
2. On 11 April 2011, Mr Conacher was registered with no email address, but with the username "aconacher" and with reference to the company name "3D Safety Services Pty Ltd".
3. On 31 August 2011, Mr Conacher was registered again with the email address and username "tc@3dss.com.au", and with reference to the company name "3D Safety Services Pty Ltd".
4. On 5 October 2011, Mr Morrow was registered again, with no email address but with the username "simon.morrow@3dss.com.au", and with reference to the company name "3D Safety Services Pty Ltd".
As to the first registration of Mr Morrow, EIFY's records show that the registration came from a computer or server having an IP (Internet Protocol) address which, it is uncontroversial, was associated with 3D Safety.
It is also uncontroversial that the simple fact that Messrs Conacher and Morrow were registered (or, indeed, that anyone else was registered) on the e-Induct system does not necessarily prove that they themselves did it. The evidence shows that from time to time Mr Culbert and others at EIFY created registrations for third parties for various purposes, including so that potential customers could test the site.
Finally (as to non-controversial matters), the defendants now accept that a registration could not be effected on the e-Induct system without clicking the box, or icon, against the words "I agree to the Terms and Conditions" ("the terms of use") which appears on the screen at one stage of the registration process. Mr Andronos criticised that evidence (which came from Mr Culbert) as "baldly conclusory", but it was unchallenged, and there was no evidence to the contrary. A screenshot of a page in the registration sequence shows that after details (name, address, username, password and the like) are given, there is provision for the intending registrant to click against the words in question; the choices thereafter are to "Continue Registration" or to "Cancel".
EIFY says that Messrs Conacher and Morrow created their own registrations, and thus that as part of that process, each of them clicked to signify acceptance of EIFY's terms of use as they stood at the time. Messrs Conacher and Morrow deny that they registered themselves. Mr Andronos submitted that it had not been shown that someone else had not created the registration for them.
Mr Corsaro relied on what he submitted was circumstantial evidence that supported the inference that Messrs Conacher and Morrow had registered themselves. He relied also on the evidence of those men in cross-examination.
Before I move to the detail of that evidence, I should note that EIFY's records show that many other people who were known to be employees of 3D Safety registered, in some cases at least from the IP address to which I have referred already. None of those people were called to give evidence.
[6]
Mr Morrow
Mr Morrow's affidavit referred only to one registration which he said was effected on about 12 April 2011. That was done, he said, either by Mr Culbert or by someone else at EIFY [56] . It will be seen that the date, 12 April 2011, does not correspond to either of the dates when Mr Morrow was registered (14 February or 5 October 2011), but is a day after Mr Conacher was first registered (11 April 2011).
Mr Morrow referred to an email by which, he said, "access logins and passwords for e-Induct's system" were provided to him. That email is part of a chain of emails between Mr Conacher and Mr Culbert. Mr Morrow is not shown as an addressee of, or someone who was copied into, that email. The chain starts with an email from Mr Conacher to Mr Culbert on 11 April 2011 at 6:57pm stating:
Patch I'm registered in 3D Safety Services.
EIFY's records show that the first registration of Mr Conacher had occurred about 30 minutes earlier, at 6:26pm.
Mr Culbert replied at 1:30am on the following day. His response is significant. It states, among other things:
I have given 3D Safety access to LOR, Abigroup, Leighton and ResMed.
I have also given your account access to the site manager…
I have also assigned a token to your account…
I checked out your photo too. Can you add one that is closer to your face please? Once you have done this, I will send you a card. The access details for the cameras are:
Nepean
Username: LOR
Password: LOR Nepean1
Eastern Creek
Username: LOR
Password: LOR Nepean2
Let me know if you want me to take you through any of it to make sure you can present it all in the best light possible.
Mr Conacher replied at 9:03am on 12 April:
Will do. I like that photo!!
I have omitted from Mr Culbert's email reference to the various functions to which "your account" had access, and details of the tokens that were assigned (the evidence is that users of the e-Induct system needed to purchase "tokens" so they could complete the induction process, or access any other of its functions).
Mr Conacher gave an explanation of the background to that exchange of emails in para 154 of his affidavit sworn 31 May 2017. That paragraph reads:
I had another meeting with Alan Cook of Mirvac on 12 April 2011. Culbert did not attend this meeting. However, I wanted to show Cook the presentation I had given to Thiess which incorporated aspects of the online induction content. On 11 April 2011 I sent an email to Culbert asking for a login. Culbert responded on the morning of 12 April 2011. Copies of these emails are exhibited at tab 20 of Exhibit AC1.
The emails to which Mr Conacher referred are those that I have just summarised.
In para 155 of the same affidavit, Mr Conacher said:
To the best of my knowledge, [Mr] Culbert or someone working for e-Induct registered me following my request on 11 April 2011.
I might note that Mr Corsaro objected to that passage; it was rejected; Mr Corsaro then cross-examined on it, with the result that it was reinstated as evidence, for whatever it might be worth.
Against that background, the last paragraph of Mr Culbert's email of 12 April 2011 [57] should be understood to be referring to the proposed presentation to Thiess.
The usernames and passwords set out in Mr Culbert's email bear no relationship to any of the usernames under which, and passwords with which, Messrs Conacher and Morrow were registered on the e-Induct system. For that reason and others, Mr Culbert's email cannot be referable to the registration of Mr Morrow that had occurred two months earlier, nor to the subsequent registrations of Messrs Morrow and Conacher later in 2011.
On 5 October 2011 (the date of Mr Morrow's second registration, which is shown as having occurred at 3:55pm on that day), Mr Morrow sent an email to Mr Culbert at 4:18pm. The email stated, among other things:
I was trying to do the induction as a trial of the questions, and I registered, however it seems I already have registered as sm@3dss.com.au.
When I tried to get my passwords sent, the process sent me an email (below) however the link kicked me out after two redirections as I didn't have a valid session.
Are you able to reset it?
With that email, Mr Morrow forwarded an email from EIFY which stated:
A password recovery request for your e-Induct account sm@3dss.com.au was requested.
The forwarded email gave instructions on how to proceed including, if there were a need to change the password, to access a particular link that was given. If there is somewhere in the evidence any reply from Mr Culbert to that email, I was not taken to it.
The "password recovery" email was sent to Mr Morrow at 3:55pm on 5 October 2011. Mr Morrow agreed in cross-examination that he was trying to register on that day, but that he could not complete the registration [58] . He said (perhaps inconsistently with his email) that he did not know how he had been registered earlier, but suggested "that either someone at the plaintiff set up those details as if I were a worker ready to go" [59] . He did not say what was the alternative that is implicit in his use of the word "either".
Mr Morrow then agreed that after someone "set [him] up as if [he] were a worker ready to go", that person sent him a username and password [60] . He identified the email in question as being that sent at 1:30am on 12 April 2011 from Mr Culbert to Mr Conacher [61] .
I should say that Mr Morrow suggested that he had been registered on the e-Induct system in 2008. That may be so. Mr Culbert's evidence, which on this point I accept, was that by 2011, all earlier registrations had been purged from the e-Induct system.
It is obvious that Mr Culbert's email of 12 April 2011 could have had nothing to do with the registration shown to have been effected in Mr Morrow's name some two months earlier. The usernames and passwords do not resemble those shown on either of Mr Morrow's registrations. And on analysis (as Mr Conacher ultimately accepted, but Mr Morrow would not), the access to which that email referred had nothing to do with the e-Induct system at all. It was, rather, concerned with access to some sort of security camera system at a LORAC project involving the extension of the Nepean District Hospital.
The defendants have not produced any other evidence showing a request by Mr Morrow to EIFY, to provide him with a registration on the e-Induct system, or with a username and password for that registration. They have not produced any record emanating from EIFY providing such registration or other details. The only contemporaneous evidence that either Mr Morrow or Mr Conacher can identify has nothing to do with the registrations that are shown to have been effected in their names. Neither Mr Morrow nor Mr Conacher suggests that he instructed someone at 3D Safety to register for him.
The proper inference on the whole of the evidence as it stands is that Mr Morrow registered on the e-Induct system on 14 February 2011, and did so from an IP address associated with 3D Safety. I so find. The very fact that EIFY's records show the registration as having emanated from that IP address tells against the suggestion that Mr Culbert, or someone else at EIFY, created the registration for Mr Morrow. So, although to a much lesser extent, does the lack of any curiosity (as to prior registration) in Mr Morrow's email of 5 October 2011.
Given what is now effectively the unchallenged evidence of Mr Culbert, to the effect that as part of completing the registration, the registrant must click to denote acceptance of EIFY's terms of use, I find that Mr Morrow did so. I accept, as Mr Andronos submitted, that it does not follow from this that he read the terms of use.
[7]
Mr Conacher
I turn to the specific evidence as to Mr Conacher. Mr Andronos submitted that Mr Conacher's email to Mr Culbert of 11 April 2011, "Patch I'm registered in 3D Safety Services [62] ", should be read literally: namely, as saying no more than that Mr Conacher was registered on the 3D Safety Services system. I do not accept that. There is no reason why Mr Culbert would have wanted to know that (assuming that he did not already know it), and no reason why it was important for Mr Conacher to inform Mr Culbert of that.
The email was sent 31 minutes after the registration that is shown to have been effected in Mr Conacher's name on 11 April 2011. The obvious inferences available from this sequence are that:
1. Mr Conacher completed the registration, giving the company name as "3D Safety Services Pty Ltd"; and
2. sent the email to Mr Culbert to confirm this.
The statement "I'm registered in 3D Safety Services", read in context, must mean that Mr Conacher had registered in the name of, or giving the company name of, 3D Safety Services Pty Ltd.
The factual background in my view provides support for the drawing of the inferences set out at [300]. Mr Conacher had arranged a meeting with Thiess on 12 April 2011. He wanted to demonstrate the e-Induct system to Thiess. To do that, he needed to be registered. Mr Culbert knew that Mr Conacher was going to demonstrate the system to Thiess. Thus, he had an interest in knowing that registration had been completed. And Mr Culbert showed, in the last passage of his email from which I quoted at [281] above, that he was aware of the purpose of the registration.
Mr Culbert's email makes no sense if it is read as confirmation that he (or someone else at EIFY) had created a registration for Mr Conacher. The username and passwords that he notified do not correspond to those shown on the registration of 11 April 2015. Even leaving aside the fact that the username and passwords refer to security cameras on LORAC's Nepean Hospital project, the email simply could not be confirmation of the registration that was actually effected a few hours earlier.
Likewise, Mr Culbert's repeated references to "your account" confirm that he understood that Mr Conacher had registered so as to create an account, presumably in the name of Services, on the e-Induct system. Mr Conacher's reply did not take issue with that.
Finally (before moving to Mr Conacher's cross-examination on this issue), the request for a better photograph made sense if Mr Conacher had registered on the e-Induct System (registrants were supposed to provide a photograph), and no sense whatsoever if all Mr Conacher were doing was confirm that he was registered in some system maintained by "3D Safety Services".
Mr Conacher accepted that the evidence based on EIFY's records showed that someone had registered under the name "Tony Conacher" on 11 April 2011, at the time and given the details to which I have referred already. However, he said, it was merely a coincidence that 31 minutes later, he sent the email "I'm registered in 3D Safety Services" [63] . He suggested, in the course of this passage of his evidence, that "Mr Culbert would have registered me in his system", and denied that he himself had registered [64] .
When Mr Conacher was taken to Mr Culbert's email of 12 April 2011, he accepted that the username and passwords contained in it had nothing to do with access to the e-Induct system [65] . He was asked, more than once, to identify the email or emails by which Mr Culbert sent the login details, and said "I don't know where to find them" and "I can't produce them" [66] . Mr Conacher was re-examined [67] at some length. He was not taken to any email (or other document) providing login details for the e-Induct system. Nor was any such document identified in the course of submissions.
As I have said, EIFY's records show a second registration in Mr Conacher's name, occurring on 31 August 2011. He denied that he had registered on that occasion [68] .
On 21 October 2011, Mr Conacher sent an email to Mr Sebastian Culbert (Mr Culbert's brother, who worked at EIFY). The email was copied to Mr Culbert and its subject was "Thiess Induction". The email stated:
I part completed the induction at Thiess on Wednesday to demonstrate to them. I have now uploaded the correct images, photos, license and white card. My log in is tc@3dss.com.au password tony. If I want to do it again will
I need a new token, if so can you send it to me?...
Please note I am entered in the e-Induct system twice as 3D Safety System PL abn and 3D Safety Services abn.
It is clear from this email that Mr Conacher knew (as the fact was) that he was registered twice on the e-Induct system. His evidence in chief did not refer to this. Nor is there any evidence of any request for, or confirmation of, the second registration. There is only the non-contentious fact of two registrations.
I conclude that Mr Conacher did register on the e-Induct website, in particular on 11 April 2011, and thus that when he did so, he clicked to signify acceptance of the terms of use. Again, it does not follow that he had any actual knowledge of the content of those terms and conditions.
Before leaving the facts relevant to the question of acceptance of the terms and conditions, I should note that Mr Culbert's evidence could have been read as stating that a user of the e-Induct system was required to click, to indicate acceptance of the terms of use, each time he or she accessed the site. If it were intended to suggest that, it is not borne out by the evidence. On the evidence, acceptance of the terms is required only once, during the process of registration. Thus, if someone had set up an account for (for example) Mr Conacher, and in the course of doing so had clicked to indicate acceptance of the terms of use, Mr Conacher would not have been required to do the same each time he accessed the site under that registration.
[8]
Construction and effect of the terms of use
There was considerable debate as to the proper construction and effect of EIFY's terms of use. The version that was proved was said to have been current from 5 March 2010 to 19 December 2011. I set out the principal parts of those terms of use to which reference was made in the course of submissions:
The following describes the terms on which e-Induct offers you access to our services.
Welcome to e-Induct's User Agreement. This Agreement describes the terms and conditions that govern your usage of our services at www.einduct.com and our other related websites (each a "Site"). Before you may utilise our Site you must read, agree with and accept all of the terms and conditions contained in this Agreement and e-Induct's policies, including its Privacy Policy (the "Policies"). Use of the Site constitutes your acceptance of the terms and conditions, which take effect immediately on your first use of the Site. The Policies change from time to time and you agree that they form part of this Agreement. Policies of particular importance are the policies relating to: Privacy; Fees and Services, and Fraud. Each time you use our services you confirm your agreement be bound and acknowledge any changes to the Agreement (including the Policies). You also undertake to familiarise yourself with and comply with the Policies relevant to your use of our Site and the services provided under this Agreement (as may be amended from time to time). As you read this Agreement, you should also access and read the information contained in the other pages and websites referred to in this Agreement.
…
1. Usage Eligibility
e-Induct enters into agreements with clients to develop and customise online induction systems for their businesses (each a "Client). Each Client can then direct each of its employees, officers, agents and contractors (each a "User") to complete a customised online induction course in respect of their business ("Induction"). In the case of a Client's contractors and their sub-contractors (each an "Authorised User"), the Authorised User car register on our Site and purchase Tokens (as defined below) for Inductions to be completed by themselves and/or their respective employees, officers and agents (also "Users"). For the sake of clarity, "Authorised User", in the context of this Agreement, only refers to a person that registers on the Site and purchases Tokens and "User" refers to a person that takes an Induction (who may or may not also be an "Authorised User").
Some parts of the Site require registration. You are solely responsible for the confidentiality and use of and access to the e-Induct content and Sites using your username, password or ID.
…
Our services are only available to, and may only be used by, individuals and corporate entities that can form legally binding contracts under applicable law.
Each User or Authorised user that accesses the Site must be the individual whose Personal Information (as defined below) has been entered for the User or Authorised User, as the case may be. In the case of an Authorised User that is not a natural person, the individual that access the Site on behalf of the Authorised Use must be duly authorised by the Authorised User to do so.
…
5. Access and Interference
You agree that you will not use any robot, spider, other automatic device, or manual process to monitor or copy our web pages or the content contained herein without our prior written permission. You agree that you will not use any device, software or routine to interfere or attempt to interfere with the proper working of our Site. You agree that you will not take any action that imposes an unreasonable or disproportionately large load on our infrastructure. Much of the information on our Site is updated on a real time basis and is proprietary or is licensed to e-Induct® by our Clients or third parties. You agree that you will not copy, reproduce, alter, modify, create derivative works, or publicly display any content from our Site without the prior written permission of e-Induct or of the party authorised to grant such permission.
As might be expected, Mr Corsaro placed particular reliance on the introductory passage and on cl 5. As to the former, he noted that it stated that the terms of use were "the terms on which e-Induct offers you access to our services" and that users were required to accept those terms before they utilised the "Site". That applied, he submitted, to everyone who had access to the system. For the reasons indicated above, that cannot be correct, in respect of any users of the site who had not registered. Acceptance of the terms of use was required only on registration.
Mr Corsaro noted that some provisions in the terms of use referred to specific classes of user. For example, cl 2.2 (which I have not set out) deals with the purchase of tokens by "Users" or "Authorised Users".
Mr Corsaro pointed in his submission to the wide words of cl 5. He submitted, somewhat optimistically, that the clause "could not have been clearer", and that it prohibited any copying of the webpages or their content, and the creation of derivative works based on content taken from the website.
Mr Andronos submitted, based on the introductory words of the terms of use, that they regulated use of the website itself - the e-Induct system. A person who used the website was required to accept the terms of use, and use of the website was taken to constitute acceptance. In this context, he submitted, "use" referred to use by a "Client" for whom (as cl 1 states) e-Induct had agreed to develop and customise an online induction system. It followed, he submitted, that the terms of use did not regulate access by persons who did not have such a contractual relationship with EIFY.
Mr Andronos submitted that cl 5, properly construed, indicated that much of the information on the website was the property of, or licensed from, persons other than EIFY including, in particular, "Clients". Thus, he submitted, it was those third parties whose permission was required to perform any of the otherwise prohibited acts. In those circumstances, Mr Andronos submitted, if permission to copy (for example) were obtained from the relevant third party, it was not necessary to obtain as well permission from EIFY to do so.
Further, Mr Andronos submitted, where the prohibition in cl 5 applied, it was limited to the specific subjects that were stated.
In any event, Mr Andronos submitted, the terms of use could bind only Messrs Conacher and Morrow. It was they who registered, not Services or Systems. Mr Corsaro submitted in reply that the evidence showed that they had registered as "Managing Director" (Mr Conacher) and "Director" (Mr Morrow), and had done so in respect of "3D Safety Services Pty Ltd" in each case.
It is convenient to start by dealing with the last point. The evidence to which Mr Corsaro referred was a document created by Mr Culbert based on his interrogation of EIFY's records using Structured Query Language (SQL) commands. The data that he obtained corresponded to the queries that he entered. However, the only copy of the registration page that is in the evidence (at least, the only copy to which I was taken) does not appear to require the registrant to indicate a company name (in the sense that provision of a company name is not said to be a "mandatory field"). It does require the specification of the "Company ABN" and it may be accepted that this, if entered correctly, would enable the identification of the company. Likewise, it provides for a specification of the registrant's "Job Title", although that is not a required field (unlike the ABN). The strong impression that one gets from the registration page is that the process of registration is one undertaken by individuals, because after all it is individuals who will access the site.
The terms of use do not appear to say anything about the relationship between a registrant and the company denoted by specification of the ABN. They are directed to "you", and are said to govern "your use of our services". Usage of those services is said to constitute "your acceptance of the terms and conditions".
The strong impression conveyed by the terms of use overall is that they are directed to regulating the basis on which each person who has access to the website exercises that access. The terms of use appear to distinguish between those who access the website ("you") and those with whom EIFY "enters into agreements" ("Clients").
In the absence of any express acknowledgment, either in the registration webpages or in the terms of use themselves, that an individual who registers and thereafter accesses the site accepts the terms of use not only in his or her own right but also on behalf of his or her employer, I think that Mr Andronos' submission on this point is correct. By clicking to acknowledge their acceptance of the terms of use, Messrs Conacher and Morrow indicated that they personally accepted those terms. That must mean that they agreed to accept those terms of use as regulating their personal access to the website. It does not follow, and I do not find, that by doing so they agreed to bind Services or Systems to those terms of use.
In short, Messrs Conacher and Morrow were bound by the terms of use. Services and Systems were not.
I turn to the proper construction of cl 5. The most relevant prohibitions are those contained in the first and last sentences. However, those sentences must be considered in the scheme of cl 5 as a whole. The terms of use bear some indications of careful drafting. There was no evidence as to who prepared them, or what (if anything) was used as a model or basis for their content. It may be a mistake to put over-much emphasis on the structure and sequence of cl 5. Nonetheless, I think, one should give some attention to the way that the prohibitions are developed, and should seek to find individual work for each of them to do.
Structurally, cl 5 comprises five sentences, four of which are prohibitory in terms. The prohibitory sentences, each of which presumably was intended to have separate work to do, are the first, second, third and fifth. The fourth sentence is not in terms prohibitory. It appears, both from its placement and its content, to be explanatory of or introductory to the fifth sentence.
The first sentence of cl 5 imposes a blanket prohibition on (among other things) copying, either by some automatic device or by some manual process, "our webpages or the content contained herein" unless "our written permission" is first obtained.
In context, the words "our … permission" must mean that it is the permission of EIFY that is required. That is made clear by the introductory paragraph of the terms of use, referring to "our services" in a way that makes it clear that those are services provided by EIFY via the website. Again, the second introductory paragraph (which I have not set out) says that "[w]e may amend the terms and conditions of this Agreement from time to time". It refers to "our Site". Clearly enough, the entity reserving the right to amend the terms of use is EIFY. There are similar provisions, referring to EIFY in the first person plural, throughout the terms of use.
Thus, the first sentence of cl 5 requires the prior written permission of EIFY to any copying (automated or manual) of any of the webpages on the Site or the content in the Site. That is structurally separate to the subjects and substance of the two following prohibitions.
The second sentence of cl 5 is directed to protecting the proper working of EIFY's "Site". So, too, is the third. Together, they seek to protect the integrity and efficient operation of the "Site" and the "infrastructure".
The last sentence seems to be concerned principally (although not exclusively) with third party material. That I think is made clear by the immediately preceding sentence, referring to "information" that "is proprietary or licensed to [EIFY] by our Clients or third parties". The word "proprietary" in that sentence presumably should be taken to mean that the information is the property of someone; is owned by someone. That information (at least, much of it) is apparently the information of Clients or other third parties, and is the subject of the prohibitions in the last sentence The Clients or third parties whose information it is are those whose prior written permission is required for the copying, reproduction etc of that information.
If one tries to read the components of cl 5 consistently, giving each work to do, the result would seem to be as follows. The first sentence prohibits the copying of the webpages themselves, without the consent of EIFY. The second and third sentences prohibit various actions relating to or affecting the operation of the Site or of EIFY's "infrastructure".
The last sentence prohibits the copying, reproduction etc of content taken "from our Site" without the prior written permission of the person whose "content" that is. Read in conjunction with the immediately preceding sentence, the last sentence would appear to prohibit the copying, reproduction etc of information taken from the web pages, as opposed to copying of those pages themselves or their content. Even so construed, there is some degree of overlap between the first and last prohibitions. But reading them that way seems to me to produce a scheme that is, within reason, workable and not totally repetitious.
The final point to make about the last sentence of cl 5 is that, when read in conjunction with the preceding sentence, it does not exclude the possibility that some of the information of the Site may be that of EIFY itself. That would seem to follow from the proposition that "much" of that information (but by inference, not all of it) is the property of Clients or third parties. Where information is the property of EIFY itself, as opposed to its Clients or third parties, then, so it seems to me, the last sentence would require the consent of EIFY before any of the otherwise prohibited acts could be undertaken. Again, that reading reinforces the proposition that there is an overlap between the first and last sentences of cl 5. Acknowledging the overlap seems to me to be preferable to reading one prohibition or the other down to the point where, in effect, it is meaningless.
So construed, the last sentence of cl 5 would refer (although not exclusively) to online inductions that EIFY hosted on its website for customers. That is what happened with the Thiess and Mirvac inductions. It may be said that the content of those inductions was "proprietary" to Thiess or Mirvac, as the case may be. They could be described as "Clients or third parties". The prohibition contained in the fifth sentence would prevent the copying, reproduction etc of the content of those inductions. Of course, the first sentence of cl 5 would be likely to have the same effect.
However, even if the material of "Clients or third parties" was copied, in breach of either or both of those prohibitions, it is difficult to see how EIFY would suffer loss. By hypothesis, the material copied would not be its. To the extent that the material was confidential, it would be confidential to the "Clients or third parties" whose material it was. To the extent that it was copyright, that copyright would subsist in the "Clients or third parties".
It may be that EIFY had undertaken some contractual duty to keep the material of "Clients and third parties" confidential, and to prevent it from being copied. It may be that, if such material were copied, EIFY might suffer loss. But even if such loss were in principle recoverable by EIFY from the copier as damages for breach of contract, that is not among the heads of loss that EIFY asserts in this case. EIFY does not say that it has suffered because either Thiess or Mirvac has made a claim against it for permitting their supposedly confidential or copyright material to be copied by 3D Safety.
[9]
Conclusions on the contractual duty of confidence based on the terms of use
I conclude that Messrs Conacher and Morrow owed a contractual duty of confidence in accordance with cl 5 of the terms of use, as I have construed that clause. I conclude that Services and Systems did not.
[10]
The claim based on the asserted oral joint venture agreement
To this claim fails, for two reasons. The first is that although EIFY pleaded that an oral joint venture agreement was made, the only terms pleaded were said to be implied terms of good faith in the performance of the contract, and that each party should do what it could to give the other the benefit of the contract [69] . There was no pleading of any term as to confidentiality; and in consequence no pleading that any such term (of the alleged oral joint venture agreement) had been breached.
The other answer to this aspect of the case is that to the extent that it depends on acceptance of Mr Culbert as a witness of credit, it must fail in the absence of corroboration. There was nothing in the contemporaneous documents which suggests that Mr Culbert communicated to Messrs Conacher and Morrow, and they accepted, that EIFY's information as to its system was confidential.
In the course of submissions, Mr Corsaro referred to the suite of draft agreements prepared by Mr Mansfield's firm. He submitted that these were some evidence of the existence of the oral agreement that, he said, they were intended to formalise, and its terms. That submission cannot be accepted. The first and obvious point is that a draft agreement proves nothing more than the drafter's view of what was necessary to give effect to his instructions. There was no evidence from Mr Mansfield as to any instructions, either in general or on the topic of confidentiality.
The other, and equally fatal, point is that the documents in question were expressly prepared as discussion drafts, so that EIFY and 3D Safety could give instructions as to the terms of the agreement and the content of the documents in their final form. It is obvious from the surrounding emails that the details of the joint venture arrangement were extremely broad and imprecise. In the result, no one took the matter any further, and the documents were not redrafted (and a fortiori, were not executed). Mr Culbert accepted that no agreement was reached at the meeting, and that much work remained to be done before that happened [70] .
[11]
The claim in contract based on the acknowledgment of 15 December 2011
It is convenient to set out Resolution 2 from the meeting of 15 December 2011, pursuant to which the acknowledgment was brought into existence:
2. Identifying and documenting the intellectual Property each party owns and brought to the Joint Venture.
Agreed to prepare an agreement which outlines the confidentiality and Intellectual Property each party brought to the joint venture. Draft was tabled and agreed upon. Simon to "mirror" the undertakings for eInduct and 3D Safety and include with minutes (Refer Annexure).
The acknowledgment itself was prepared at the conclusion of the meeting and signed by Messrs Culbert, Conacher and Morrow on that day. It reads as follows:
Intellectual Property owned by Wishbone Pty Limited ("Wishbone") and eInduct
It is acknowledged that as a result of the Joint Venture with eInduct, officers and staff of eInduct Pty Limited were given access to confidential and privileged information on the workings, structure and content of the 3D Safety Management System ("3D SMS").
A strategic "Wish list" of modifications, features and improvements which forms the basis of future development and strategic direction of 3D SMS was provided to Patrick via email on 13 July 2011.
This access and information was provided in good faith on the understanding that eInduct will not use the information, structure, content, layout, process, knowledge and strategic plans obtained as a result of the process to create a financial gain, advantage or benefit to eInduct which results in a financial loss, disadvantage or penalty to Wishbone or 3D SMS.
It is acknowledged that as a result of the Joint Venture with 3D Safety, eInduct provided officers and staff of 3D Safety access to confidential and privileged information on the content of the eInduct System ("eInduct").
This access and information was provide in good faith on the understanding that 3D Safety will not use the information, content, layout, process, knowledge and strategic plans obtained as a result of the process to create a financial gain, advantage or benefit to 3D Safety which results in a financial loss, disadvantage or penalty to eInduct.
The first point to note is that the document is cast in terms of "acknowledgment", not in terms of "agreement". It refers to actions that had occurred at some time in the past, and seeks to record the bases (or a basis) on which those actions were performed. It does not contain any promise by one party to the other that, as a matter of contract, it will bind itself in accordance with those actions (even if they could be given sufficient content and certainty to be capable of having contractual force).
Further, the acknowledgment does not identify, except at the level of extreme generality, what it is that the parties might have regarded as confidential to EIFY on the one hand, or 3D Safety on the other. On one reading, as Mr Andronos submitted, the acknowledgment is circular. The confidential information is information "obtained as a result of the process": that is to say, the "process" by which EIFY made available confidential and privileged information about its system.
The acknowledgment does not indicate that all information made available by one side to the other was to be regarded as confidential. If it is legitimate to read the acknowledgment in conjunction with the resolutions which immediately preceded it, and which contemplated, its execution, it would appear that the parties considered that the Plant Module and the Procurement Portal were the confidential information of EIFY, but that the content of each of those modules was not.
Since no part of EIFY's case complained about infringement of the Plant Module or the Procurement Portal (whatever those things may be), this analysis does not assist in deriving, from the terms of the acknowledgment, any relevant agreement as to confidentiality.
Mr Morrow said in the course of cross-examination [71] that Mr Culbert never identified the information that he claimed to be confidential. That answer was not challenged (either then or at any time in the next two days of the cross-examination of Mr Morrow). I set out that portion of Mr Morrow's cross-examination:
Q. The position was that you, as far as you were concerned, Mr Conacher and Mr Culbert, each agreed that you would make or give undertakings under the full acknowledgement that I took you to a moment ago and which was subsequently signed; is that correct?
A. Yes.
Q. And 3D would mirror the undertakings that e-Induct were going to give?
A. Yes. We had a fairly - we tried to tease that out. There had always been a challenge in identifying what the plaintiff identified as confidential and privileged. I just couldn't seem to get anywhere to progress it and Mr Culbert eventually said, "Just do the same thing, just do whatever you're doing for you, do it for me".
Q. The undertakings were going to be mirrored, in other words, is that right?
A. Yes.
Notwithstanding my reservations as to Mr Morrow's credibility, I accept that portion of his evidence. As I have noted, it was not challenged, although there was more than ample opportunity to do so. Further, bearing in mind the broad and general terms of the acknowledgment, the evidence seems to me to be consistent with the probabilities, regarded objectively.
Accordingly, the claim in contract based on the acknowledgment of 15 December 2011 fails.
[12]
The equitable duty of confidence
Mr Corsaro submitted that the equitable duty of confidence arose on two bases:
1. as to some of the information alleged to be confidential, because EIFY provided it to the defendants for the limited purpose of the proposed joint venture; and
2. as to all the information said to be confidential, because it was imparted to the defendants in circumstances imposing an obligation of confidence [72] .
It will be seen that those bases overlap; the former may perhaps be said to be a subset, or particular example, of circumstances falling within the latter.
Mr Corsaro accepted that it was necessary to identify with specificity the information said to be confidential [73] . In closing written submissions, Mr Corsaro identified the confidential information as follows:
[54] In Corrs Pavey Whiting & Byrne v Collector of Customs for Vic (1987) 14 FCR 434, Gummow J imposed an additional element - that the information must be identified with specificity. The plaintiff submits that the following information obtained by the defendants satisfies the necessary criteria of being confidential information in the relevant sense:
(a) the graphical and textual elements of each of the eInduct Induction Web Pages, being those elements as selected, arranged, modified and displayed on each Web Page (in short - the induction content or web pages);
(b) the relationship existing between each of the Web Pages, being the order and arrangement of the pages which provided an important structural order for a worker proceeding through an online induction process for induction onto a construction site. In this regard, the sequential steps that the eInduct Online Induction System imposed on a person undertaking an online induction and the means by which the program directed a user through the following sequence, all features of the eInduct Online Induction System:
(i) the display of a company's registers;
(ii) the ABN of company and how that is checked against the ABN Register;
(iii) the way an online induction user agrees to terms and conditions;
(iv) how a user enters mobile phone number;
(v) how a user purchases a token to make use of the system;
(vi) how a user goes to a page which confirms their identity;
(vii) how a user requests a secure code;
(viii) how a user code is sent to the user's mobile phone;
(ix) how a user enters code within 5 minutes;
(x) how a user is granted access to system
as described in detail in Confidential Affidavit of Mr PC Culbert dated 21 December 2012 at paragraphs 24-57);
(xi) the process of the information management system, i.e. the sequential steps of the information management system as described in Confidential Affidavit of Patrick James Culbert dated 21 December 2012 at paragraphs 58-59);
(xii) the process of the plant management module, i.e. the sequential steps of the plant management module, as described in Confidential Affidavit of Patrick James Culbert dated 21 December 2012 at paragraphs 60 - 65);
(xiii) the process of the access control module, namely the sequential steps of the access control module, as set out in Confidential Affidavit of Patrick James Culbert dated 21 December 2012 at paragraphs 75 - 77); and
(xiv) the eInduct source code; and
(c) [The databases that formed part of the eInduct System and contained company, user and plant information and documents.]
Mr Corsaro submitted that the circumstances that could be taken into account in considering whether an equitable duty of confidence existed included the contractual relationship between the parties and the terms of that contract (specifically, the "contract" said to have existed in relation to the joint venture and the "contracts" said to have come into existence upon acceptance by Messrs Conacher and Morrow of the terms of use), and taking into account the representations said to have been made at the outset and during the course of the joint venture.
Mr Corsaro submitted, further, that the acknowledgment of 15 December 2011, following the termination of the meeting of directors of Group that took place on that date, recognised that a relationship of confidence existed.
Mr Andronos accepted that EIFY's source code for the e-Induct system was confidential (and, as will become apparent, that it was the subject of copyright). That does not take the matter much further because, as Mr Andronos submitted, it was common ground that the defendants had never had access to the source code.
As to the balance of the identified information, Mr Andronos submitted that:
1. the description of the allegedly confidential information did not show, nor did the evidence otherwise illuminate, why each piece of information (apart from source code) was confidential to EIFY;
2. the description of the allegedly confidential pieces of information was not sufficiently precise to enable any judgment to be made that it was confidential at all, let alone confidential to EIFY;
3. the way in which EIFY marketed the e-Induct system to potential customers deprived the system of the degree of relevant secrecy necessary to ensure protection [74] ;
4. following on from the previous submission, the question was not whether it had been disclosed to the public at large but, rather, whether it had been disclosed to what might be called "the relevant public" [75] ;
5. the "relevant public" consisted of users and potential users of the e-Induct system; and
6. neither the nature of the steps within or forming part of the systems themselves nor the restrictions on access to the system were such as to indicate the existence of any equitable duty of confidence.
As to para (c) - the databases - Mr Andronos submitted, correctly, that no claim in relation to the databases (also referred to as "relational databases" because of the way that one database could access and take information from another) had been pleaded. In those circumstances, he submitted, the claim should not be entertained.
As to induction programs that were created for Thiess and Mirvac, pursuant to a contract between Group and Thiess or Group and Mirvac, Mr Andronos submitted that if there were any confidentiality in the induction material, it was the confidence of Thiess or Mirvac, as the case might be. He submitted that the inductions were prepared for the relevant user pursuant to a contract between that user and Group, incorporated or were based on material supplied by the user, and were paid for by the user.
I start with the description of the confidential information given by Mr Corsaro, which I have set out at [355] above. On the face of it, that description might appear to convey some degree of particularity. However, when one reads it carefully, it is plain that EIFY is claiming that its confidential information comprises the whole of the e-Induct system.
First, para (a), although it starts off by referring to "the graphical and textual elements of each of the" webpages, concludes by stating "(in short - the induction content or webpages)". This appears to extend the ambit of the information said to be confidential from the purely graphic or textual elements to the whole of the content of the webpages that constitute the online induction system that in turn is part of the e-Induct system.
That impression is confirmed by paras (b)(i)-(x). The claim there made is for confidentiality in the sequence of steps that are described: again, steps that are integral parts of the e-Induct online induction system.
Paragraph (b)(xi)-(xiii) extend the claim, it seems, to the other functional elements of the e-Induct system: namely, the information management system, plant management module and access control module.
I pass over source code, as to which there is no dispute, and the claim in respect of the databases, which was not pleaded and which was referred to for the first time only in Mr Corsaro's opening.
To my mind, this is a very problematic way of advancing a claim for confidence in equity. To show why, I shall look at the evolution of the online induction system: specifically, those described in the list statement as the Version 5, Version 6 and Version 7 series (see para 33H, set out at [160] above). Version 5 was the online induction system that EIFY prepared for LORAC. It was based on information and instructions provided by LORAC. Version 6 was the online induction system prepared by Group for Thiess. It was based on the LORAC Version 5 induction, but incorporated specific information and instructions supplied by Thiess. Version 7 was prepared by Group for Mirvac. It was based on the Thiess Version 6, but incorporated specific information and instructions supplied by Mirvac.
Mr Culbert said, and I am prepared to assume, that the graphic design work for Versions 5, 6 and 7 was done to some extent by him but substantially by Mr Quicke, and that the coding work was done by himself or by Mr Birmingham. That may very well mean that such of the information comprised in Version 5 as is confidential, but not the confidential information of LORAC, is the confidential information of EIFY. That conclusion does not help, because it does not demonstrate:
1. what (if any) part of that information is truly confidential in the relevant sense;
2. of the information that is truly confidential in the relevant sense, what is confidential to LORAC; and
3. of the information that is truly confidential in the relevant sense, what is confidential to EIFY.
Those problems do not disappear with Versions 6 and 7 but, rather, are overlaid by a further and to my mind insurmountable problem. That further problem is that the contractual relationship for the preparation of the online inductions was between Group and Thiess, or Group and Mirvac, as the case may be. To the extent that the online induction system that Group prepared for Thiess or Mirvac contained information that was confidential, but was not the confidential information of the customer, it would be confidential information of Group rather than of EIFY.
To put the problem slightly differently, it does not follow, simply because (and to the extent that they did) Mr Quicke, Mr Culbert or Mr Birmingham worked on Version 6 or Version 7, that any information in those versions that is confidential in the relevant sense is the property of EIFY.
It is unnecessary to consider whether the coding that Messrs Culbert and Birmingham did was done for EIFY, or for Group, or for Thiess or Mirvac as the case may be. That is because, as I have said more than once, there is no evidence that the defendants had access to or copied the source code.
To the extent that Mr Culbert did graphic design work, he did it in his capacity as a director of Group. Group was the counter-party to the contracts with Thiess and Mirvac to develop Versions 6 and 7 respectively. If any of the images that Mr Culbert prepared were properly to be regarded as confidential information, they would be the property either of Group or of the customer (Thiess or Mirvac, as the case may be) for whom they were prepared.
That leaves the graphic design work done by Mr Quicke. The evidence was that the work was done on Mr Culbert's instructions, on the basis that Clearsite would invoice Group for the work. In fact, Clearsite mistakenly invoiced EIFY for some work. At Mr Culbert's request, Clearsite cancelled the invoice to EIFY and invoiced Group instead. It was paid by Group. On that basis, the content of Mr Quicke's graphic design work on Versions 6 and 7 cannot be the confidential information of EIFY. Mr Culbert must be regarded as having acted in his capacity as a director of Group when he instructed Mr Quicke to undertake that work.
To my mind, the problem that faces EIFY is similar to that dealt with by Mason J (with whom Murphy, Aickin, Wilson and Brennan JJ agreed) in O'Brien v Komesaroff [76] . At 327, Mason J referred to the judgment of Brightman J in Amway Corporation v Eurway International Ltd [77] , where his Lordship distinguished [78] between confidential information that was protectable in equity (for example, by injunctive relief) and know-how, which was not.
At 328, Mason J said that the information in question represented the "accumulated knowledge, skill and experience in a particular field" of the respondent. His Honour said that this could not all be confidential information. Mason J then said [79] :
Even so, if the respondent were able to identify some particular pieces of information and show that they were confidential or that an obligation of confidence had arisen with respect to them he would be entitled to protection of them. But this is just what the respondent has failed to do. He has persisted in making a global claim for protection that covers the entirety of the schemes that evolved and the entirety of the documentation by which they were implemented. He is not entitled to that protection and, accordingly, his claim must fail. My conclusion is that in the circumstances he is not entitled to any greater protection than that given to him in respect of his ownership of copyright.
That is the essential problem that EIFY faces in this case. By making a claim that, on analysis, extends to the whole of its online induction system, it is effectively combining a claim to protect know-how with a claim to protect information that may or may not be confidential. It has failed to separate out the information that is said to be confidential, and to demonstrate why it is. And it has failed to demonstrate (source code excepted) what information that is confidential is its own, and not that of someone else.
Because the claim is expressed in a global way, it is enough to point to particular aspects of the subject matter for the purpose of saying that, on the assumption that they are or embody confidential information, they or it cannot be the confidential information of EIFY. That must be so in respect of Version 6 and Version 7. To the extent that those versions of the online induction system embody confidential information, it must be confidential information either of the customer for whom it was prepared or, if not, of Group.
That is enough to dispose of the equitable confidential information claim in the online induction system.
I should mention that Mr Corsaro submitted that even if the information had been derived from other or publicly available sources, nonetheless the work done on it by EIFY was sufficient to invest the result with the appropriate degree of confidentiality. He referred to cases such as Exchange Telegraph v Central News [80] and Bates and Partners Pty Ltd v The Law Book Company [81] . That submission goes nowhere. Even if the analogy established by those cases was relevant for Version 5 of the online induction system, it can have no application to Versions 6 and 7, for the reasons I have indicated.
To the extent that Mr Corsaro called in aid either the contract case (in any of its manifestations) or the representation case, they do not help. As to the supposed contract relating to the formation of the joint venture (and this applies also to the representation case), I have concluded [82] , that I am not satisfied that the relevant promissory statements or representations were made. Equally, I have concluded [83] that no contract can be inferred because a suite of documents was prepared which, if executed, would have given rise to legal relations.
As to the contract that is said to have come into existence on acceptance of the terms of use, it is enough to say that nothing in those terms identified what was the confidential information of EIFY. Such contracts as were so brought into existence might protect whatever information might be held to be confidential. They do not, of themselves, describe or prescribe that any particular information is confidential.
Nor can the fact that the parties operated, in fact at least if not in law, as joint venturers for a period of time assist EIFY. The conclusion that joint venturers owe obligations of a fiduciary nature to each other must be one that follows from, and takes into account, the terms of the joint venture agreement: United Dominions Corporation Ltd v Brian [84] .
In this case, no terms have been proved. All that has been proved is that the parties tried for a time to work together to promote jointly a system that comprised and maximised the utility of their several products. There is nothing in that circumstance to justify the proposition that one party owed any obligations of a fiduciary nature to the other.
The key to the existence of a fiduciary relationship is the subordination of self-interest to joint interest (Grimaldi v Chameleon Mining NL (No 2) [85] ). In this case, the joint venture, to the extent that it went beyond some vague arrangement, was no more than an association for a commercial purpose, with the hope of gaining profit [86] . No doubt, the parties placed trust and confidence in each other, if only because of the familial relationship. But that is not enough, of itself, to create a fiduciary relationship [87] .
Equally, it may be said that EIFY was dependent on Group, in that Group invoiced customers for the total cost of work done, and received payment of the total amount. Group was required to pass on to EIFY the latter's share of, or entitlement to, payments made. EIFY depended on Group doing this, and doing it honestly. But it can hardly be said that EIFY was in any relevant sense [88] "vulnerable".
EIFY was not "a remote principal lacking the capacity to observe what was happening…". It was, instead, "in constant contact with" events, and "in an excellent position to … protect its interests …. There was no entrustment or custodianship to be abused". It knew what its share of revenues was. It knew when any particular project was delivered. It was in a position to see that its share of any payment was passed onto it.
Mr Corsaro did not submit that the arrangements in some way constituted Group as the agent of EIFY, for the purpose of receiving and accounting for payments. If it were, then it might be possible to argue that, at least for that limited purpose, there was a fiduciary relationship. But this was not put.
Finally, the acknowledgment signed on 15 December 2011 reflects the fact that some of the information given by each party to the other was confidential. It does not specify what, from either source, was confidential. Nor do the minutes of the directors' meeting (of Group) held immediately before that acknowledgment was signed shed any light on this subject, because "the framework for the Plant Module" and the "Framework for the Procurement Portal" (the only things identified as "the property of" EIFY) seem to have very little to do with the categories of confidential information that are the subject of the claim to protection in equity.
I conclude that EIFY has not made good its claim to protection in equity.
[13]
Breach
This issue can be relevant only to the contractual claim against Messrs Conacher and Morrow [89] . The only evidence of suggested breach is:
1. that (as is uncontentious) 3D Safety used the online induction prepared by Group for Mirvac as the basis for an online system that 3D Safety itself proposed to provide to Mirvac, offering both online induction and online safety management functionality; and
2. Mr Culbert's assertions that on 4 September 2012, someone from an IP address associated with 3D Safety accessed the e-Induct system and during that time "visited 12,562 URLs within the system", in the course of doing so "viewing individual record details… of which there were many hundreds" [90] .
The first complaint goes nowhere, because it has not been shown that any of the information that was utilised was information of, let alone confidential to, EIFY. Further, the web pages or slides in question were based substantially on images and text provided by Mirvac for the purpose of preparing the online induction. To the extent that Mr Quicke added anything (apart from rearranging colours, positions on the page, format and the like), he used stock images that he obtained at little or no cost from external sources.
As to the second matter, the number of URLs visited does not seem to me to be significant. There may be many URLs embodied in any single webpage. A visit to that webpage will be recorded as a visit to each of those URLs. More substantively, there is no evidence to support that proposition, that such information as may have been gathered was put to any improper use. To put it another way, there is no evidence that the usage to which Mr Culbert referred was usage for anything other than the purposes of the joint venture, which had not been terminated at that time.
[14]
Copyright
Resolution of the issues relating to copyright has not been assisted by the lack of correspondence between EIFY's pleaded case and the submissions (in particular, the closing submissions) that were put. Accordingly, I propose to start by setting out the way in which the case was pleaded.
[15]
The pleaded case
In Part A of the list statement (setting out the nature of the dispute) something called EIFY's "personnel management, induction, access control and plant management system" was defined as "the e-Induct system". It was said to take the form of a website and other hardware and software elements. The website was said to include a series of web pages "primarily used for online inductions by construction companies to create a system whereby they can undertake an online worker induction process".
Paragraph 8 of Part C (the statement of contentions) "pleads" some features of the e-Induct System. Somewhat confusingly, those features are themselves described as the "e-Induct system". I set out para 8:
8. The eIniduct System provides users with a particular experience, which arises through a combination of:
(a) the physical appearance of the user interface, chiefly comprising text, images and sounds, which allow users to enter, use, exit from and otherwise interact with the eInduct System;
(b) the controls, underlying logic, business rules, structure, processes and user flow of the eInduct System;
(c) the plaintiff's business model, including the way in which the plaintiff engages with customers and users and generates revenue from the eInduct System; and
(d) the way in which the eInduct System incorporates and interacts with other technologies and hardware, such as mobile devices, scanning software and third party security systems.
The pleading of the copyright case commences with a statement of "the Concept" said to underly the e-Induct System or alternatively the e-Induct Online Induction System. That concept (which is pleaded in para 33AA) is said in para 33AB to be expressed by a structure which is referred to as "the e-Induct Structure". I set out para 33AB:
33AB The plaintiff's expression of the Concept is by means of the following structure (or sequence or organisation):
(a) the preparation of a data base structure to cater to the requirements of the system;
(b) the creation of a system of modules and elements written in computer code to produce object code which creates the user interface in the appropriate sequence for the logical process;
(c) the inclusion in the user interface of digitized images to either provide information to the user for the particular stage of the induction process or to illustrate or enhance the induction procedure;
(d) a user registration process by the user entering personal information into a web interface backended by a data base to store the information, to link the employeed to an employer;
(e) the acquisition of an access code (token) by the user or their employer;
(f) the collection of data and other information particular to the user as required for access to the workplace site to which the induction refers;
(g) the validation of the user's ability to undertake the induction by verifying the existence of a pre-existing access code (token) and verification of the user's identity;
(h) the commencement of the induction process once the token or access code is verified;
(i) a two factor authentication to confirm the user's identity, via text message to a mobile phone or mobile device;
(j) the inclusion of user selectable actions to permit the user to move through the induction process and voiceover with relevant controls;
(k) the inclusion of safeguards at each stage of the induction process to ensure the user has correctly assessed the information, risks and requirements of each stage of the induction process, and to prohibit the user moving forward from one stage to the next without successfully completing a prior stage; and
(l) a final result screen to illustrate the final result of the induction procedure undertaken by the user, and including an option such as printing out a certificate or induction card
(the eInduct Structure)
The contentions then plead the way in which the "Concept" was conceived and the way in which the various iterations of it were created. That pleading culminates in para 33H, which I have set out already but for convenience repeat:
33H The structure (or sequence or organisation) of the eInduct System, layout, format and look of the eInduct Induction Web Pages and the eInduct Source Code and Object Code Associated with those eInduct Induction Web Pages of each of, or alternatively one or more of:
(a) the 2007 System;
(b) the Version 1 Series;
(c) the Version 2 Series;
(d) the Version 3 Series;
(e) the Version 4 Series;
(f) the Version 5 Series;
(g) the Version 6 Series;
(h) the Version 7 Series
(collectively the "Works") are original literary works within the meaning of the Copyright Act, 1968 (Cth).
The response to para 33H reads:
33H. In answer to paragraph 33H:
(a) Deny that the layout, format and look of any of the eInduct Induction Web Pages are original literary works within the meaning of the Copyright Act 1968 and deny that any copyright subsists in the layout, format and look of any of the eInduct Induction Web Pages;
(b) Deny that the structure or sequence or organisation of the eInduct System is an original literary work within the meaning of the Copyright Act 1968 and deny that any copyright subsists in the structure or sequence of organisation of the eInduct System;
(c) Admit that the eInduct Source Code associated with the eInduct Induction Web Pages of each of the 2007 System and the Version 1 through to the Version 7 Series is a literary work within the meaning of the Copyright Act 1968;
(d) Deny that the Object Code associated with the eInduct Induction Web Pages of each of the 2007 Systems and the Version 1 through to the Version 7 Series is an original literary work within the meaning of the Copyright Act 1968; and
(e) Otherwise deny the allegations in paragraphs 33H.
It is not necessary to set out the balance of the pleading.
The key paragraph is thus para 33H. It appears to describe some 32 "Works", which are said to be "original literary works". Those Works are, for each iteration of what for convenience I will call the e-Induct System:
1. its structure or sequence or organisation;
2. the layout, format and look of the e-Induct Induction Web Pages;
3. the e-Induct Source Code associated with those Web Pages; and
4. the e-Induct Object Code associated with those Web Pages.
If this is not the correct understanding of para 33H then EIFY can hardly complain. It alone is responsible for the opacity of its pleaded case. As I have said, EIFY's submissions did not trouble to cross-refer to the pleadings.
The pleadings makes no reference to any claim to copyright in an artistic work. Nonetheless, as I have indicated already, the defendants accept that, in respect of the 34 images [91] , the particulars effectively notified them of a claim for copyright in those images on the basis that they were artistic works.
[16]
The Copyright Act 1968 (Cth)
The Copyright Act provides for copyright to subsist in "works" and in subject-matter other than works. The latter category may be put to one side for the purposes of this case.
It is necessary to pay attention to some of the definitions in s 10 of the Copyright Act. I set out the definitions of "work", "literary work", "artistic work", and "computer program":
"work " means a literary, dramatic, musical or artistic work.
"literary work" includes:
(a) a table, or compilation, expressed in words, figures or symbols; and
(b) a computer program or compilation of computer programs.
"artistic work" means:
(a) a painting, sculpture, drawing, engraving or photograph, whether the work is of artistic quality or not;
(b) a building or a model of a building, whether the building or model is of
artistic quality or not; or
(c) a work of artistic craftsmanship whether or not mentioned in paragraph (a) or (b);
but does not include a circuit layout within the meaning of the Circuit Layouts Act 1989 .
"computer program" means a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.
It is clear, in particular from s 21(5) of the Copyright Act, that a computer program may include both source code and object code.
Section 32 provides for copyright to subsist in original unpublished and published works. Section 35(2) provides that, subject to s 35, the author of a work is the owner of any copyright subsisting in that work. Section 35(6) provides that where a work has been made by its author in pursuance of the author's terms of employment, the employer owns any copyright in the work.
Section 196 of the Copyright Act deals with assignments and licences. By s 196(3), an assignment of copyright does not have effect unless it is in writing signed by or on behalf of the assignor.
[17]
Source code and object code
There was a vigorous dispute as to whether EIFY was the owner, either as author or as employer for whom the work was created or by assignment, of any copyright that subsists in the source code or object code for any of the eight versions of the e-Induct System referred to in para 33H of the list statement. It is unnecessary to resolve that dispute, because there is no evidence whatsoever that any of the defendants had access to the source code or the object code, or that they copied it. Nor has there been any analysis of the source code and object code of any of those versions of the e-Induct System, comparing them to the source code and object code of any allegedly infringing work produced by 3D Safety.
The high point of the evidence is an assertion by Professor Braun that "[i]n cases where the screens are very similar, the underlying Object Code in the Video RAM is also very similar" [92] . Even assuming the requisite degree of similarity (and Professor Braun's evidence, to the extent it was admitted, does not prove this), it does not follow that the object code underlying the screens in the 3D Safety online induction system (or any other functional part of that system) results from any act that could constitute an infringement of any copyright that subsists in the object code underlying the screens in any versions of the e-Induct System.
[18]
Structure, sequence or organisation
Those words in para 33H were presumably intended to refer back to, so as to pick up, the defined term "e-Induct Structure" found in para 33AB. I say that because the reference in para 33H to "[t]he structure (or sequence or organisation) of the e-Induct System" picks up the chapeau to para 33AB, read in conjunction with the defined term at the end of that paragraph.
It may be accepted, at least for the purposes of argument, that the structure, sequence or organisation of a computer program may be the subject of copyright. Arnold J said as much in SAS Institute Inc v World Programming Ltd [93] . His Lordship said [94] :
[232] Even leaving aside the decision of the Court of Appeal in Nova, I am not persuaded that Pumfrey J was wrong to hold that it is not without more an infringement of the copyright in a computer program to create another computer program which has the same functionality. I accept that copyright protection is not limited to the text of the source code of the program, but extends to protecting the design of the program, that is, what has been referred to in some cases as its "structure, sequence and organisation". If there were any doubt about this, then the conferring of protection on "preparatory design material" confirms it. But there is a distinction between protecting the design of the program and protecting its functionality. It is perfectly possible to create a computer program which replicates the functionality of an existing program, yet whose design is quite different.
The distinction that his Lordship drew between the design of the program on the one hand and its functionality on the other is critical. Mr Andronos submitted that EIFY's case appeared to confuse the two concepts. I agree.
The significance of the distinction is shown by the decision of Pumfrey J in Navitaire Inc v Easyjet Airline Co [95] . In that case, Easyjet commissioned an online booking system specifically to replicate the functionality and ease of use of the Navitaire "OpenRes" system. Pumfrey J stated Navitaire's contention at [2], [3] and set out the issue at [5]. I set out those paragraphs:
[2] The case is factually and technically complex and has taken a considerable amount of time in court. It raises starkly an issue of considerable importance in the law of copyright. While there are comparatively minor allegations of infringement by copying of certain code and an allegation in relation to the databases that I summarise below the striking feature of this action is that Navitaire does not suggest that easyJet or BulletProof ever had access to the source code of the OpenRes system. What is alleged, and not disputed, is that easyJet wanted a new system that was substantially indistinguishable from the OpenRes system, as easyJet used it, in respect of its "user interface". This term is used to denote the appearance the running software presents to the user, who may be an agent in a call centre or a private individual seeking to make a booking by use of the World Wide Web. It substantially achieved this far from simple goal. It is not in dispute that none of the underlying software in any way resembles that of OpenRes, save that it acts upon identical or very similar inputs and produces very similar results, but it is said that the copyright in OpenRes is infringed by what was called "non-textual copying".
[3] In its context in this action, "non-textual copying" had three aspects. The first was the adoption of the "look and feel" of the running OpenRes software. The second, not always clearly distinguished from the first during the trial, was a detailed copying of many of the individual commands entered by the user to achieve particular results. The third was the copying of certain of the results, in the form of screen displays and of "reports" displayed on the screen in response to prescribed instructions. In other words, as used by easyJet the systems are very similar in use. Internally, it is correct to say that they are completely different, subject to a point on the names used to identify certain data in the databases in eRes. Given that near-identity in appearance and function could not have been achieved without a close analysis of the OpenRes system in action, Navitaire say that there is here "non-textual" reproduction of either the whole of the OpenRes software considered as a single copyright work or alternatively of the various copyrights subsisting in "modules" going to make up the system.
…
[5] There is here an issue of general importance. To emulate the action of a piece of software by the writing of other software that has no internal similarity to the first but is deliberately designed to "look" the same and achieve the same results is far from uncommon. If Navitaire are right in their most far-reaching submission, much of such work may amount to the infringement of copyright in the original computer program, even if the alleged infringer had no access to the source code for it and did not investigate or decompile the executable program.
Navitaire contended that the case was analogous to taking the plot of a book. As Pumfrey J said [96] , "an author who takes the plot of another work and copies nothing else will still infringe copyright if a substantial part of the earlier author's work is represented by the plot". Navitaire submitted "and the same goes for computer programs" [97]
Pumfrey J rejected the analogy, saying [98] :
[125] This does not answer the question with which I am confronted, which is peculiar, I believe, to computer programs. The reason it is a new problem is that two completely different computer programs can produce an identical result: not a result identical at some level of abstraction but identical at any level of abstraction. This is so even if the author of one has no access at all to the other but only to its results. The analogy with a plot is for this reason a poor one. It is a poor one for other reasons as well. To say these programs possess a plot is precisely like saying that the book of instructions for a booking clerk acting manually has a plot: but a book of instructions has no theme, no events, and does not have a narrative flow. Nor does a computer program, particularly one whose behaviour depends upon the history of its inputs in any given transaction. It does not have a plot, merely a series of pre-defined operations intended to achieve the desired result in response to the requests of the customer.
Pumfrey J then referred to the settled (although difficult to identify) distinction between an idea and its expression. He referred to observations in the speech of Lord Hoffman in Designers Guild Ltd v Russell Williams (Textiles) [99] . Lord Hoffman said [100] :
My Lords, if one examines the cases in which the distinction between ideas and the expression of ideas has been given effect, I think it will be found that they support two quite distinct propositions. The first is that a copyright work may express certain ideas which are not protected because they have no connection with the literary, dramatic, musical or artistic nature of the work. It is on this ground that, for example, a literary work which describes a system or invention does not entitle the author to claim protection for his system or invention as such. The same is true of an inventive concept expressed in an artistic work. However striking or original it may be, others are (in the absence of patent protection) free to express it in works of their own: see Kleeneze Ltd. v. D.R.G. (U.K.) Ltd. [1984] F.S.R. 399 . The other proposition is that certain ideas expressed by a copyright work may not be protected because, although they are ideas of a literary, dramatic or artistic nature, they are not original, or so commonplace as not to form a substantial part of the work. Kenrick & Co. v. Lawrence & Co. (1890) 25 Q.B.D. 99 is a well known example. It is on this ground that the mere notion of combining stripes and flowers would not have amounted to a substantial part of the plaintiff's work. At that level of abstraction, the idea, though expressed in the design, would not have represented sufficient of the author's skill and labour as to attract copyright protection.
Generally speaking, in cases of artistic copyright, the more abstract and simple the copied idea, the less likely it is to constitute a substantial part. Originality, in the sense of the contribution of the author's skill and labour, tends to lie in the detail with which the basic idea is presented. Copyright law protects foxes better than hedgehogs. In this case, however, the elements which the judge found to have been copied went well beyond the banal and I think that the judge was amply justified in deciding that they formed a substantial part of the originality of the work.
Applying those principles, Pumfrey J concluded that Navitaire's claim failed. His Lordship said [101] :
…
Navitaire's computer program invites input in a manner excluded from copyright protection, outputs its results in a form excluded from copyright protection and creates a records of a reservation in the name of a particular passenger on a particular flight. What is left when the interface aspects of the case are disregarded is the business function of carrying the transaction and creating the record, because none of the code was read or copied by the defendants. It is right that those responsible for devising OpenRes envisaged this as the end result for their program: but that is not relevant skill and labour.
The reasoning of Pumfrey J in Navitaire was considered in Nova Productions Ltd v Mazooma Games Ltd [102] . In the Court of Appeal, Jacob LJ (with whom Sir Andrew Morritt Ch and Lloyd LJ agreed) said that:
…
Pumfrey J was quite right to say that merely making a program which will emulate another but which in no way involves copying the program code or any of the program's graphics is legitimate. [103]
In StatusCard Australia Pty Ltd v Rotondo [104] , the defendant created a computer program to replicate many of the functions of the plaintiff's program and the manner in which the plaintiff's program displayed information. The defendant did not copy the plaintiff's source or object codes in doing so. Chesterman J held that the defendant had not breached the plaintiff's copyright. His Honour identified the plaintiff's argument as follows [105] :
[82] The plaintiff does not allege that the first defendant has copied its computer codes, source or object codes, or the sequence or patterns of bits which cause the plaintiff's computer program to function. The plaintiff's case is that the first defendant set out to replicate the functions of the plaintiff's program and did so by means of a different computer program. In doing so the plaintiff alleges that the first defendant's program reproduced the computer screen display I have described. That screen display is said to be a literary or artistic work, copyright in which subsists in the plaintiff.
[83] The source codes and object codes (machine language) of the two programs are not the same. The programs, Delphi and Visual Basic, are different. The plaintiff's case is that the first defendant set out to replicate the operation and functionalities of its program, utilising commercial software for the purpose. The plaintiff's case is not that Mr Rotondo engaged in reverse engineering to work back from the functions of the program to its codes, but that, using different codes and software, it duplicated the manner in which the plaintiff's program processes the BettorData and displays it. I have no doubt that this is what the first defendant did with some success. The evidence of Mr Weber and Mr Braidotti point inexorably to that conclusion.
[84] The plaintiff's case is that the visual depiction of the data produced by its program is original, artistic or literary work as defined by the Act and that the first defendant's program produces a copy of the same visual depiction thereby infringing its copyright in the work.
Chesterman J pointed out [106] that "the functionality of a computer program, its behaviour, is not the subject of copyright protection". He referred [107] first to the decision of the High Court in Autodesk Inc v Dyason (No.2) [108] , and then (with apparent approval) to the decision of Pumfrey J in Navitaire.
Chesterman J noted [109] that the case was one not of copying but of replication. He said that it was common ground, and rightly so, that there is no copyright in the functionality, or the "look and feel" of a computer program. In my respectful view, that is correct. His Honour then turned to the question, whether the plaintiff's screen display was a table or a compilation, so as to fit within the definition of literary work. It is not necessary to go to that aspect of his Honour's reasons.
Returning to the distinction that Arnold J drew in SAS Institute at [232] [110] , 3D Safety's online induction programs for Thiess and Mirvac may well have replicated the functionality of EIFY's existing online induction program. It does not follow that 3D Safety has thereby copied the design of EIFY's program, and such other evidence as there is does not prove copying of design as opposed to replication of functionality.
The case based on structure, sequence or organisation fails.
[19]
Layout, format and look
As I understand EIFY's case, these words refer to the "look and feel" of EIFY's online induction program. EIFY's case, on that understanding, is that because (EIFY says) the online induction programs prepared by 3D Safety for Thiess and Mirvac have the same look and feel as EIFY's existing online induction program, copyright in that existing program has been breached. For the reasons that follow, I do not agree.
I have referred already [111] to Australian authority that holds there is no copyright in the "look and feel" of a computer program. Mr Corsaro contended, however, that there was American authority to support that proposition. He referred to Whelan Associates Inc v Jaslow Dental Laboratory, Inc [112] . Mr Andronos submitted that the American authorities must be considered with some care, for two reasons. The first was that the structure of the American legislation is substantially different to the Australian legislation, because it does not limit copyright protection to (relevantly) works. The other reason was that the American authorities do not speak with one voice. Those submissions are correct.
As to the first submission, the relevant statute is the Copyright Act of 1976, 17 USC ss 101 - 810 (2016). Section 102 provides:
s102 Subject matter of copyright: In general
Copyright protection subsists, in accordance with this title, in original works of authorship fixed in any tangible medium of expression, now known or later developed, from which they can be perceived, reproduced, or otherwise communicated, either directly or with the aid of a machine or device. Works of authorship include the following categories:
(1) literary works;
(2) musical works, including any accompanying words;
(3) dramatic works, including any accompanying music;
(4) pantomimes and choreographic works;
(5) pictorial, graphic, and sculptural works;
(6) motion pictures and other audiovisual works;
(7) sound recordings; and
(8) architectural works.
In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.
The obvious point is that it is not necessary for a work to be categorised as "literary", "artistic", etc before copyright can subsist. Copyright will subsist in an "original work of authorship fixed in any tangible medium of expression". In contrast to the position in this country, the statutory examples of "works of authorship" are illustrative, not exhaustive.
The American authorities make it clear that the concept of "tangible medium of expression" may range well beyond "works" as that expression is used in this country. See for example, Tetris Holding LLC v Xio Interactive Inc [113] , a case dealing with video games.
As to the second submission, the court in Tetris made it clear at 401-403 that the reasoning, although not the result, of the decision in Whelan has been criticised by other courts and in standard texts. Further, the decision in Media.net advertising FZ - LLC v Netseer Inc [114] at 1062 holds that copyright protection does not extend to "look and feel".
When one turns to the structure of the e-Induct System, as it is described in para 33AB of the list statement, it is apparent immediately that what is described is not the expression of any idea but the functionality, or output, or result, of the ideas that are embodied in the source code and converted into object code. There is no literary work in the conventional sense: nothing in writing (whether having a "literary" character or not). Nor is there a "computer program": a set of statements or instructions that are used, directly or indirectly, by a computer to bring about a result. The structure is the result (or part of it), not the means - the program - whereby that result is achieved.
EIFY's case conflates the structure, sequence or organisation of the e-Induct System with the structure, sequence or organisation of the underlying computer program. It is the latter, not the former, in which copyright may subsist.
[20]
Source code and object code
I have already dealt with this topic to some extent. [115] As I have said more than once, there is no evidence comparing the source or object codes of EIFY's online induction system with the source or object codes of 3D safety's allegedly infringing online induction systems. Thus, the case of breach of copyright based on source or object code must depend on inferences drawn from other evidence. That was made clear in EIFY's closing submissions in reply at para 230:
The plaintiff's case in relation to infringement of the copyright in the source code is put on the basis that the "look and feel" and/or the structure, sequence or organisation may be subject to copyright. A further or alternative way of putting this is to say that the defendants have copied the object code of the eInduct system. That argument is set out in detail by the expert appointed by the plaintiff, Professor Braun. In short, the argument is this: whenever a computer generates an image in the screen, regardless of which source code language is employed, if the image is the same the same object code will be generated to produce that image.
For the reasons I have given, insofar as the submission depends on structure, sequence or organisation, or on look and feel, it is not made good. And to the extent that the submission depends on some inferences that are said to have been available from Professor Braun's evidence, the relevant paragraphs were objected to and rejected [116] .
EIFY has not made good its case for breach of such copyright as may subsist in the source or object codes of its online induction program.
[21]
The 34 images
EIFY's case, as to copyright in these images, is as follows:
1. it contracted with Clearsite for Mr Quicke, in his capacity as an employee of Clearsite, to produce the images;
2. there was an oral agreement or arrangement between Clearsite and EIFY that for all images so produced, Clearsite would (and did) assign copyright to EIFY;
3. that oral assignment was confirmed, with retrospective effect, by deed made on 14 May 2015;
4. each of the 34 images comprises an original artistic work in which copyright subsists; and
5. accordingly, EIFY holds the copyright in each of those images.
The defendants contest almost every step of that argument, save that they accept that a deed of assignment was made between Clearsite and EIFY on 14 May 2015. The defendants do not however accept that the deed had the full effect that EIFY attributes to it.
There was a considerable amount of evidence devoted to the disputed steps; much ink was spilled in setting out the respective positions of the parties in writing; and considerable breath was expended in elaborating those submissions orally. There does not seem to me to be any point in resolving many of the disputed questions. There are two reasons.
First, it is clear that, whatever the deed did, it did not assign to EIFY any causes of action that Clearsite might have had for any breach of copyright up until 14 May 2015. As Besanko J pointed out in Insight SRC IP Holdings Pty Ltd v Australian Council for Educational Research Ltd (No 2) [117] , an assignee can only sue for breaches of the assigned copyright prior to the date of assignment if those rights of action, as well as the copyright, were assigned to it. Although an appeal from his Honour's decision succeeded, it did not disturb the essential point (and with respect, the point must be correct in any event).
EIFY has not proved any breach of copyright occurring after 14 May 2015 (or if there is any evidence of such a breach, I was not taken to it in the course of submissions). It follows, in the absence of breach since the assignment was perfected, that there is no entitlement to damages vested in EIFY. Any compensable breach prior to 14 May 2015 remains vested in Clearsite, and Clearsite is not a party to these proceedings.
The second reason (for restricting consideration of the construction and effect of the deed of assignment) relates to the nature of the breach that EIFY asserts. EIFY's case, as to the 34 images, is that 3D Safety infringed EIFY's copyright by utilising those images for the purpose of preparing its own version of the Mirvac online induction program in 2012.
As an aside, I note that this cannot involve any allegation of breach of copyright in the source code of EIFY's online induction program, because the evidence of Mr Malthus, which was essentially unchallenged and which I accept, was to the effect that he himself developed the source code, on the instructions of Mr Morrow. He did so either in his capacity as an employee of McGirr (which in turn had a contractual relationship with 3D Safety, the effect of which was to give the latter the benefit of copyright in code written by McGirr), or in his capacity as an employee of 3D Safety.
Returning to the 34 images: it may be accepted that 3D Safety used them in the preparation of its online induction program for Mirvac. However, the images that it used were taken from the Mirvac online induction program that Group prepared for Mirvac, which in turn was based on the Thiess online induction program that Group prepared for Thiess.
To the extent that Mr Culbert played any part in the production of those images, he did so in his capacity as a director of Group. It follows that, to the extent Mr Culbert was an "author" for the purposes of copyright, any copyright arising from his efforts was held by him on trust for Group. That was common ground between the parties, and rightly so. See A-One Accessory Imports Pty Ltd v Off Road Imports Pty Ltd & King [118] .
To the extent that the work was done by Mr Quicke, the position is a little more complicated. I have referred earlier to the way in which and the basis on which (as he understood it) Mr Quicke did that work [119] . If Mr Quicke did the work in his capacity as an employee of Clearsite, any copyright may subsist in Clearsite. If he did it in his capacity as a director of Clearsite, any copyright might subsist in him but would be held in trust for Clearsite, for the reasons I have given earlier. Clearsite is not a party to these parties and does not assert any claim of breach.
EIFY relies on the deed of assignment between it and Clearsite made on 14 May 2015, to which I have referred already. The subject of that deed, as both the recitals and the operative provisions make clear, is "Intellectual Property Rights", including copyright, created by Clearsite pursuant to or in the course of providing "Consultancy Services" to EIFY. The expression "Consultancy Services" is not defined but, by reference to the recitals, is apparently intended to denote "intellectual property services and other services" provided by Clearsite to EIFY from time to time.
Such services as Clearsite provided for the Thiess and Mirvac inductions were provided, as directed by Mr Culbert, to Group. I repeat that Clearsite invoiced Group (after an initial mistaken invoice to EIFY, which was cancelled at Mr Culbert's direction) and was paid by Group. Mr Culbert must have been acting as a director of Group when he instructed Clearsite to provide those services, and directed it to invoice Group.
In those circumstances, the work done by Mr Quicke on the Thiess and Mirvac inductions cannot be regarded as falling within the scope of the "Consultancy Services" from time to time provided by Clearsite to EIFY. Thus, to the extent that there is any copyright in those works (that is to say, in so much of the 34 images as were the subject of Mr Quicke's creative labours), it is not vested in EIFY by virtue of the deed of assignment.
In those circumstances, there is no point seeking to disentangle further the confusing and inconsistent evidence, and the submissions based upon it.
[22]
Text
EIFY's particulars asserted that the text [120] on one page taken from an induction prepared by 3D Safety for Thiess breached EIFY's copyright in the text of two or three slides forming part of the induction that EIFY prepared for LORAC. It is not clear whether this claim was pressed. It does not appear to have been addressed separately in EIFY's closing submissions (written or oral, or in reply). Perhaps it is a chunk of EIFY's case that fell between the gaps [121] .
The short answer (if answer be required) is that although the text of the allegedly offending slide expresses the same idea as did the allegedly copyright text in the LORAC slides, the language is not the same. In the absence of submissions from EIFY on this aspect of its case, I do not propose to say anything more.
[23]
Conclusion on copyright case
However it is put, EIFY's case based on breach of copyright must fail.
[24]
Misleading or deceptive conduct
EIFY's case to misleading or deceptive conduct appears to be another chunk that has fallen between the gaps. I address it only because it is pleaded (and included in the stated issues) and has not been expressly withdrawn.
[25]
The pleaded case
The pleaded case as to misleading or deceptive conduct is stated at paras 14 to 19 of the list statement. I set out those paragraphs:
14. Between February 2011 and May 2011, the first and/or fourth defendants made representations to the plaintiff that it would not develop software having the same or similar functionality to the software or systems of the plaintiff ("Pre-commencement Representations").
Particulars
The Pre-commencement Representations were made during discussions between Mr Culbert of the plaintiff and the second defendant on behalf of the first and fourth defendants which occurred in the first half of 2011.
15. The Pre-commencement Representations were made in trade and commerce.
16. The Pre-commencement Representations were made in connection with the supply or possible supply of goods or services to others.
17. The Pre-commencement Representations were misleading and deceptive within the meaning of section 18 of the Australian Consumer Law.
Particulars
The Pre-commencement Representations were made either knowing them to be false or were not made on reasonable grounds, and the plaintiff in this respect relies upon section 4 of the Australian Consumer Law. The representations were promissory in quality and were unqualified, and the true position was that the first and/or fourth defendants might develop software having the same or similar functionality to the software or systems of the plaintiff.
18. The plaintiff relied upon the Pre-commencement Representations.
Particulars
But for the Pre-commencement Representations, the plaintiff would not have:
(a) proceeded with the joint venture or, alternatively, have allowed it to continue; or
(b) given the defendants the level of access they were given (they already had access, just to the level that the plaintiff subsequently provided) to the eInduct System and confidential information.
19. Further or in the alternative, it was misleading and deceptive for the first and fourth defendants to proceed with the joint venture in circumstances where they knew that the plaintiff believed that the defendants would not develop software having the same or similar functionality to the software or systems of the plaintiff, notwithstanding the first and/or fourth defendant's intention to do so.
[26]
The parties' submissions
The topic was not addressed (in terms, at least) in the closing oral submissions for EIFY. It was referred to briefly in EIFY's closing written submissions, and in EIFY's closing written submissions in reply. Those submissions stated, at paras 75 and 68 respectively:
MISLEADING & DECEPTIVE CONDUCT
[75] The evidence shows that prior to the commencement of the joint venture, Mr Anthony Conacher, on behalf of the first and fourth defendants, represented to the plaintiff that the defendants would not develop software having the same or similar functionality to the software or systems of the plaintiff. The plaintiff relied upon those representations in proceeding with the joint venture and giving the defendants a level of access to its software or systems. The plaintiff will assert that the representations were made either knowing them to be false, or were not made on reasonable grounds, and that they were accordingly misleading and deceptive within the meaning of section 18 of the Australian Consumer Law.
Misleading or deceptive conduct
[68] The defendants' assertion in relation to the plaintiff's case for misleading or deceptive conduct is that it depends on an oral representation which Mr Culbert asserts Mr Conacher made and which Mr Conacher denies. The plaintiff asserts that if there is any contest between the truthfulness of Mr Conacher and Mr Culbert, the Court would comfortably accept Mr Culbert's evidence.
The defendants' submissions were that:
1. there was no evidence at all of any representation made (as the pleading asserted) between February and May 2011;
2. although Mr Culbert gave evidence of a representation said to have been made in July 2011, that evidence was uncorroborated and should be rejected; and
3. there was ample evidence that Mr Culbert had been told from time to time during the life of the joint venture that if the two systems could not be integrated, 3D Safety would develop its own online induction system.
[27]
Decision
The first submission put for the defendants is correct. There is no evidence of any representation made between February and May 2011. On that basis, the pleaded case based on misleading or deceptive conduct must fail.
As to the conversation that Mr Culbert alleged took place on 25 July 2011, there is no corroboration. Mr Conacher denies that the conversation took place. Although I put no more weight on Mr Conacher's denial than I do on Mr Culbert's assertion, the inevitable outcome, bearing in mind my view as to Mr Culbert's credibility and the absence of corroboration, is that I am not satisfied, let alone actually persuaded, on the balance of probabilities that the alleged representation was made.
Even if the alleged representation were made, it is difficult to see how Mr Culbert could have placed any reliance on it. He had been told 20 days earlier, in an email of 5 July 2011, that if the integrated system could not be completed in time, 3D Safety might implement its own online induction system. The point was essentially repeated in an email from Mr Conacher to Culbert dated 13 July 2011, and again in the "Schedule Three" document signed by Messrs Conacher and Culbert on 20 July 2011.
As to this last document (signed five days before the date of the alleged representation), Mr Culbert accepted that it suggested to him that Mr Conacher might be intending or desiring to develop a competing product [122] .
The case based on misleading or deceptive conduct is not made out on the evidence.
[28]
Remedies
EIFY has failed. It has not made good any claim to relief. I see no point in assessing what remedies (whether by way of damages, account of profits, equitable compensation or otherwise) might have been available. Any attempt to decide the question of remedies would require very different factual findings from those I have made. In effect, the exercise would require alternative hypothetical factual findings, and consideration of the results that, based on those hypothetical findings, might follow.
I add that even with the extended time allowed for the hearing, there was not enough time to consider the expert evidence on question of damages and other monetary relief. For those reasons, upon the defendants' accepting (as they did) that if the plaintiff succeeded, it had suffered some loss (to the extent necessary to perfect its cause of action), I directed that all questions of quantification of loss and other monetary remedies be dealt with separately from and after the determination of all other issues in the proceedings.
[29]
Conclusion and orders
However it is put, EIFY's case fails. The result is that there should be judgment for the defendants.
1. Since there will no doubt be an argument as to the costs orders that should be made, I propose to direct that the parties provide written submissions (and with them any evidence on which they intend to rely as to costs), and written submissions in reply. Unless the parties persuade me otherwise, I propose to deal with the questions of costs on the papers once submissions are complete.
I make the following orders:
1. direct entry of judgment for the defendants on the plaintiff's claim.
2. Direct the parties, by 19 October 2017, to serve on each other and deliver to my Associate a draft of the costs orders that each seeks, any evidence in support of those orders, and written submissions not exceeding 10 pages in length in support of such orders.
3. Direct the parties, by 16 November 2017, to serve on each other and deliver to my Associate any evidence in reply on costs, and written submissions in reply not exceeding ten pages in length.
4. Unless the court otherwise orders, direct that the question of costs be dealt with on the papers.
5. Direct that the exhibits be handed out.
[30]
Endnotes
Report dated 4 November 2016, para 72.
Report dated 4 November 2016, para 61.
Paras 64 to 69 and Figure 6.
(2014) 253 CLR 122.
At [16] above.
(2011) 243 CLR 588.
At [37].
(2001) 52 NSWLR 705 at [85].
At [42].
[2017] NSWCA 168 at [34].
See at [26] and following above.
Honeysett at [43].
Compare Honeysett at [45].
Compare Rolleston at [36].
At para 11.
At para 72.
At [24], [25] above.
At [102] and following below.
Affidavit made on 2 July 2015, para 2.
That reading appears at T617-619, and is summarised at [97] below.
I accept that, at the linguistic and philosophical levels, a "text" may include (although it need not be limited to) both images and words. For convenience, and reflecting the usage commonly adopted in the course of the evidence in this case, I shall use the word "images" to denote pictorial material and the word "text" to denote written language.
T604.18-.38.
T604.40-.44.
T605.6-.37.
T607.19-.42.
T618.7-.9.
See at [129] below.
At [71] above.
At [123], [124] above.
T952.9-.20.
Referring to the second of the three questions set out in the extract above.
See T1498.30-.40.
T1123.33-.41.
Expressed in the course of submissions at T1497.19-.29.
See also at [401] below.
As I shall explain at [173] and following below, there is a limited exception as to the 34 images.
At [92] to [98] above, and elsewhere.
At [14].
See generally T444-449.
T445.38.
At para 78.
See generally T239-240.
See generally T213-220, 242-244.
(1995) 49 NSWLR 315.
At 318-319.
See for example T1020-1021 in conjunction with exhibit PX15.
See generally T923-924, T934.
See generally T1058-1060.
At [271] to [313] below.
Briginshaw v Briginshaw (1938) 60 CLR 336.
At [193] to [196].
See generally T390-392.
See generally T397-400.
See at [145] and following above.
The written submissions were provided only after the oral submissions had been delivered.
Affidavit sworn 31 May 2017, para 116, corrected in part at T1217.44-.45.
At [281] above.
T1237.35-.43.
T1238.32-.34.
T123.36-.37.
See at [281] above.
See at [279] above.
See T905.35-906.19
T906.14-.26.
T906.41-907.7.
T908.6, 909.3.
After an opportunity to take instructions.
T910.39-911.5.
Fourth further amended commercial list statement at para 13.
T255.31-256.36.
T1281.1-.19.
See Megarry J in Coco v AN Clarke (Engineers) Ltd [1969] RPC 41 at 47.
See Gummow J in Corrs Pavey Whiting and Byrne v Collector of Customs for Victoria (1987) 14 FCR 434.
He referred to Artedomus (Aust) Pty Ltd v Del Casale 68 ISR 577 at [25]-[28] and Brand v Monks [2009] NSWSC 1454 at [184].
He referred to (although the phrase in quotation marks does not come from) the judgment of Megarry J in Coco at 47.
(1982) 150 CLR 310.
[1974] RPC 82.
At 86-87.
Again at 328.
[1897] 2 Ch 48.
(1994) 29 IPR 11.
At [342].
At [343], [344].
(1985) 157 CLR 1 at 11.
(2012) 200 FCR 296 at [177] (Finn, Stone and Perram JJ).
See John Alexander's Clubs Pty Ltd v White City Tennis Club Ltd (2010) 241 CLR 1 at [93].
See at [340] above.
Affidavit affirmed 21 December 2012, para 174.
See at [175] above.
Report dated 4 November 2016, para 61.
[2010] EWHC 1829 (Ch).
At [232].
[2004] EWHC 1725 (Ch).
At [73].
Ibid.
At [125].
[2000] 1 WLR 2416.
At 2423.
At [129].
[2007] EWCA Civ 219.
At [52].
[2009] 1 Qd R 559.
At [82] - [84].
At [85].
At [86].
(1993) 176 CLR 300.
At [87].
See at [412] above.
At [422].
797 F 2d 1222 (1986).
863 F Supp 2d 394 (2012).
156 F Supp 3d 1052 (2016).
See at [409], [410] above.
See at [256] above.
(2012) 211 FCR 563 at [105].
(1996) 65 FCR 478.
See at [374] above.
Meaning words.
See at [253] above.
Affidavit affirmed 21 December 2012, para 114.
DISCLAIMER - Every effort has been made to comply with suppression orders or statutory provisions prohibiting publication that may apply to this judgment or decision. The onus remains on any person using material in the judgment or decision to ensure that the intended use of that material does not breach any such order or provision. Further enquiries may be directed to the Registry of the Court or Tribunal in which it was generated.
Decision last updated: 28 September 2017
Navitaire Inc v Easyjet Airline Co [2004] EWHC 1725 (Ch)
Nova Productions Ltd v Mazooma Games Ltd [2007] EWCA Civ 219
O'Brien v Komesaroff (1982) 150 CLR 310
Rolleston v Insurance Australia Ltd [2017] NSWCA 168
SAS Institute Inc v World Programming Ltd [2010] EWHC 1829 (Ch)
StatusCard Australia Pty Ltd v Rotondo [2009] 1 Qd R 559
Tetris Holding LLC v Xio Interactive Inc 863 F Supp 2d 394 (2012)
United Dominions Corporation Ltd v Brian (1985) 157 CLR 1
Watson v Foxman (2000) 49 NSWLR 315
Whelan Associates Inc v Jaslow Dental Laboratory, Inc 797 F 2d 1222 (1986)
Category: Principal judgment
Parties: EIFY Systems Pty Ltd (Plaintiff)
3D Safety Services Pty Ltd (First Defendant)
Anthony Ian Conacher (Second Defendant)
Simon Paul Morrow (Third Defendant)
3D Safety Systems Pty Ltd (Fourth Defendant)
Wishbone Consulting Pty Ltd (Fifth Defendant)
Representation: Counsel:
F Corsaro SC / S Baron-Levi (Plaintiff)
K Andronos SC / S Keizer (Defendants)