Patents are a complicated subject, and there are a lot of questions that come up about them. The World Intellectual Property Organization (WIPO) has published a list of the most frequently asked questions about patents, with answers from experts. Here are some of the highlights:
Q: What is a patent?
A: A patent is an exclusive right granted for an invention, which is a product or a process that provides a new way of doing something, or offers a new technical solution to a problem. To get a patent, you must file a patent application with a patent office.
Q: How long does a patent last?
A: The term of a patent is 20 years from the date of filing the patent application.
Q: What is the difference between a patent and a trademark?
A: A patent protects an invention, while a trademark protects a brand name or logos.
Q: Can I get a patent for my software?
A: Yes, you can get a patent for software, provided that it meets the requirements for patentability.
Q: I have invented a new medical treatment. Can I get a patent for it?
A: Yes, you can get a patent for a new medical treatment, provided that it meets the requirements for patentability.
Q: What are the requirements for patentability?
A: The requirements for patentability are that the invention must be new, inventive, and capable of industrial application.
This is just a small selection of the questions and answers available on the WIPO website. For more information, please visit the website or contact a patent office.
Patents are a type of intellectual property that can provide protection for an invention. An invention is a unique or novel device, method, composition or process. The invention must have a practical application and be capable of being made or used in some kind of industry. To get a patent, you must file a patent application with the United States Patent and Trademark Office.
There are many different types of patents, but they all serve the same purpose: to protect an invention. A patent can be obtained by filing a patent application with the appropriate government agency. The process can be complex, but it's important to understand the basics before you get started.
First, you need to decide which type of patent you need. There are three main types of patents: utility patents, design patents, and plant patents. Utility patents are the most common type of patent. They protect the function of an invention. Design patents protect the way an invention looks. Plant patents protect new plant varieties.
Once you know which type of patent you need, you can start the application process. The first step is to file a patent application with the United States Patent and Trademark Office (USPTO). The USPTO is the government agency that grants patents.
The patent application must include a detailed description of the invention. It must also include one or more claims. Claims define what the invention is and what it does. They're important because they determine the scope of the patent.
After the patent application is filed, the USPTO will review it to make sure it meets all the requirements. If it does, the USPTO will issue a patent. Once you have a patent, you have the exclusive right to make, use, or sell the invention for a set period of time.
Obtaining a patent can be a complex process, but it's important to protect your invention. A patent gives you the exclusive right to make, use, or sell your invention for a set period of time. This can give you a competitive edge in the marketplace and help you generate revenue from your invention.
If you've ever wondered what the difference is between a utility patent, a design patent, and a plant patent, you're not alone. These are three of the most common types of patents, but they each provide different types of protection.
A utility patent is the most common type of patent. It covers products and processes that are new and useful. Utility patents can be issued for products, processes, machines, chemicals, and other things.
A design patent covers the look of a product. Design patents can be issued for products, packaging, and graphics.
Finally, a plant patent covers a new kind of plant that has been created through human intervention. Plant patents are relatively rare, but they provide protection for the maker of the new plant.
Each of these types of patents provides different types of protection. If you're looking to patent something, you'll need to determine which type of patent is right for you.
A: A patent generally lasts for 20 years from the date the patent application was filed.
Once the term expires, the invention becomes public domain.
Q: The term “mol Graph-based quantum mechanics” is cited in a patent application. I have never heard this term. What does it mean?
A: Mol Graph-based quantum mechanics (MGQM) is a quantum mechanical method that defines molecules in terms of atomic orbitals. The orbitals are represented by directed lines with nodes (“molecular graphs”). The method is used for solving the time-independent Schrödinger equation for molecules. Operations on molecular graphs generate closed form expressions for energies, densities and wavefunctions.
back to top
Remember, Too Much Knowledge May Actually be Dangerous!
Knowledge can be both a blessing and a curse—that is, it can provide an advantage (blessing) or a disadvantage consisting of problems and consequences (curse). For example, if you don’t know where local libraries are, you must find such a reference facility by asking questions (“Where are the local libraries?”) or by seeking help from a reference librarian. Knowing the locations and hours of operation of the two local libraries saves you time by allowing you to visit the library even if it isn’t on your regular route. Knowing the understanding-level of a patron allows a reference librarian to offer the correct type of information (i.e., more depth or shallower), which vastly improves the speed with which the reference need is met. Knowing that The Catcher in the Rye by J.D. Salinger is a “Banned Book from being taught” in the local school district would alert librarians that such a book should not be available for purchase as a new addition to the local high school library. Learning that a particular book is unavailable in the local public library collection due to the re-implementation of a long-outdated censorship policy is clearly a curse, not a blessing. Many of us understand how blessing and curse take form in our personal lives; in some functional areas, people granted application privileges may be less fortunate (blessing) or may be the only knowledge worker required to address a unique work activity (curse). Either way, architecture planners who are form buyers and implementers must understand all functional user roles.
A Blessing, a Curse, an Adventure
If you don’t know where the terrain is in a mountain range, your adventure may be brief and out of necessity, quite abrupt in its ending. Knowing where the difficult terrain is located and having planned accordingly, all members of your expedition could arrive at the ridge line. The other factor to consider is common sense! If you should know about a hazard but don’t and this overwhelming knowledge disadvantage leads to your demise, winning a posthumous award for “Dumbness” isn’t likely to satisfy your remaining relatives.
The term “Dumbness” does not represent a curse in the traditional sense of the word. Rather, ignorance may be considered a curse. Ignorance is related to the quality and aspects of existence expressed by “Dumb”—that is, refusing or unable to speak. The impact of ignorance is significant in the context of Information Architecture. How can an architect fully realize requirements if stakeholders don’t know enough about the system to express these requirements in the first place? Obviously, the personnel who create requirements during project Initiate should be knowledgeable about the context and the systems and architecture for the particular industry domain in which the business endures. Officials participating in the requirements gathering activities should first address “Dumbness.” First, the context should be debated, followed by major and minor system components. As architects and business requirements writers raise valid issues and questions during Initiate, these questions and comments will cause participants to recognize and consider other issues. If a business requirements writer overhears questions whether a proposed behavior makes sense, then the writer should question the business requirement. “Dumbness” often stems from an inadequate or outdated understanding of the environment. When the context is less than completely understood, the business requirements will likely be inappropriate and unusable.
“Dumbness” is a curse in an additional context. How many doomed projects of the past decade failed because architects failed to understand the context in which their architecture would reside? How much business wreckage was caused by architects who joined a project resulting from horizontal integration at the wrong time, because they didn’t understand the business situation, In addition, how many architects have served in the wrong business context for so long that their “Dumbness” is evident? Where are architects from 2009 who are not yet aware of their own “Dumbness”? How many architects’ tools, processes, and even assumptions will jeopardize efforts in 2010 because architects will repeat the nine deadly sins of software architecture?
Solutions for the Curse of