A terminology issue exists in a contract if key terms are not defined or are poorly defined. Terminology issues are commonplace in technology and intellectual property (IP) agreements. To be meaningful these types of agreements require good situation-specific definitions.
This Mumbrella video on YouTube (http://www.youtube.com/user/TheMumboReport#p/u/7/TD153sb6SVg) illustrates that the practice of imitating popular supermarket products is rife at Coles. Coles no doubt checks the legality of each of its imitations.
Here's a few suggestions on how manufacturers and product originators can improve their legal protection. Each involves being a futurist in use of intellectual property law. Each involves the principle that it's better to design your IP than IP your design.
To prepare a letter of demand to protect a name you have two main tasks. Assume you claim ownership to the name and today discover a competitor using an identical or similar name. It might be for a similar business or for comparable products or services.
Task 1: First, gather facts by listing registrations you have for any relevant trade marks, company names, domain names or business names. You're sure to have some evidence here, maybe even if it is a product name or brand.
Task 2: Next, gather facts by listing your evidence of use of the name or brand in the course of trade. This task is difficult for many businesses.
One is for an established wealth management consultancy. Another for a supplier of hosted customised software.
Both require us to design and test like an engineer designing a car of the future.
The relatively easy bit is drafting legal wording for compliance with law and making legally effective agreements.
The hard bit is finessing and designing when and how each client will deal with its business tasks. That's the work that minimise the most risks. They are the client's practical tasks of writing business proposals, project plans, scope of work or specifications, and setting price expectations.
A prospective client this week sought to register a name as a business name or company name. He did his own online name availability search... or so he thought.
On seeing an identical name on a business name register in another state he wondered if he should still proceed with the target name. It was still available as a domain name and trade mark... or so he thought.
I wrote on this topic in What trade mark professionals do. Today I had to be blunt. Here's what I wrote.
1. Do people love work at your place?
2. Do people at your place feel their careers and the business is developing?
3. Are they trained to take both to the next level?
4. Are the paths for that clear to all?
5. Do the employment contracts align with those paths?
6. Is there credible evidence for your answers to these questions?
These question are focused on people. My personal experience points to people as the top priority. As further evidence let's see what two great inventors working with teams have said.
We've all learned a lot from Steve Jobs (1955-2011).
He's inspired a great deal of thought and writing on this Lightbulb law blog.
In memory of his unforgettable life and work, below is a list of my articles about him or shaped around his work.
He won't stop inspiring. Great people never do. Each time I look up at the clouds, he'll be beaming down.
Mobility and mobile device screens (smartphones, tablets, e-readers) make possible new functionality and uses for devices.
For example it would be useful to know how readers of The Australian Financial Review use their iPads, about 30% of them have iPads! It's a niche, and there are others hiding in research data.
What's exciting about facts like that is that for developers and their investors mobile device app, content or services development provides a point of market entry.
Software development is a field with many myths.
Here's three, following by a myth busting extract from an application development tasks list.
There's the myth of a first mover advantage. Very few successful IT companies were first in their field. Not Google for search engines, not Microsoft for PC operating systems, not Apple for phones or digital music players, and the list goes on.
As our firm is currently working on many contracts for client cloud projects, I listened to this long video and recommend it: The Future of Cloud Computing.
It's a panel presentation held at The Commonwealth Club in California. Some very interesting points are made by the first two speakers.