 Thank you everyone for coming this late hour on a work day. I am just starting my fourth month in Qatar, so I'm fairly new to the community, but I am not new to this particular area. I've been involved in startup activities for about 25 years. In the course of my career, I've been involved in helping start 20 companies, primarily from a legal perspective, but also involved in raising monies and that sort of thing. Typically, when folks are speaking to a room of digital entrepreneurs, if anyone's wearing a suit, they're either an account executive for a large company or a lawyer, so I'm going to be playing the lawyer tonight. And I'm going to be talking about a subject that, at its core, is very broad, very complex, and it would be very difficult in just 30 minutes to really dive into the subject matter in any great depth. So I'm going to pretend to be sort of a falcon flying very high in the air. I'm going to kind of swoop down and attack, a prey, some subjects. And I'm going to focus on subjects that are of particular interest, I hope, to digital entrepreneurs. And you will see them as I proceed through my presentation. One of the questions that I'm often asked is, how do I define entrepreneurship? And I've spent a lot of my career working with medical centers like Sidra, but I've also worked in software companies in the digital world. And it's been my experience that entrepreneurship really is a state of mind. It's kind of a feeling, a thing that you do. And it's built on the desire to serve the greater good, and I would say the greater good of humanity. But it's fueled by a sense of wonder and a sense of urgency, a sense of wonder in the sense that technology is fascinating and things are moving very fast in the world, but there's also a sense of urgency. We need to do things now. This is particularly the case in an academic medical center setting. There is really a sense of urgency for the development of new technologies to help patients. Now, if you consider that a sense of wonder, sometimes maybe you think of that as children, but in adults that equates to passionate curiosity about technology. The famous physicist Albert Einstein once said, I have no special gifts, I am just passionately curious. And unlike Albert Einstein, I think you all have special gifts and you're also passionately curious. So that is how I define entrepreneurship in my experience. Now, I'm going to be talking primarily about the Internet of Things very broadly and how at certain points it connects to social media, which was the focus of today's discussion. And I'm going to talk about some key legal items, first intellectual property, data security, and data privacy. Really those three subjects, although very, very broad, are likely in the front of everyone's mind in the digital entrepreneurship world for a variety of reasons, and I'll touch on a few of them. Now, copyrights are one of the intellectual properties and there are others that you certainly are familiar with, trade secrets, trademarks, patents, and I put them in this particular order because those of you who work in the digital field will likely interface with these types of legal protections, likely in this order. Copyrights because they come into being automatically. You don't really have to do anything, you just have them. Trade secrets, which is confidential information, everyone works with confidential information. A little bit more formalistic, you get to trademarks, which identify goods, and then finally patents are an entirely different area of complexity that is constantly changing. I'm not going to spend a lot of time with patents because of time constraints, but I'm going to focus my talk on kind of a basic understanding of these types of intellectual properties very quickly so we all have a common understanding and then I'll talk about some more specific issues. Copyrights protect original expression of an idea that's fixed in a tangible meaning of expression. Now, if you notice in the common definition of copyrights, expression appears twice, so expression is important. It's how things are expressed. Now, when someone says I have a copyright, what does that mean exactly? I have a copyright. Well, copyright is really a bundle of rights. A copyright gives you the ability to reproduce a work, the ability to adapt a work, which we call creation of derivative works. You have the right to distribute the copyrighted work. You can display it and you can perform it. So when someone says I have a copyright, they have this list of rights that they could utilize in their activities. Now, in the digital world, copyrights last a very, very long time. In most instances, it's the life of the author plus 70 years. In an employment context, that could be as long as 100 years. That's like a million years in the digital world, so it lasts a very long time, essentially forever if you're thinking of it in those terms. Now, trade secrets are really anything that is kept confidential, but they can provide the owner of that information with a competitive business advantage. And you can imagine a lot of different types of information that would fall into that category lists of customers, ways of doing business, source code for your programs, for instance. And if you maintain them, if you keep them secret, they could possibly last forever. However, the challenge is keeping them secret. How about trademarks? A trademark simply identifies a product and it distinguishes it from other products, like Microsoft versus Apple or Samsung versus Nokia. And the core idea is that it's identifying the source, so when you see the Apple logo, you know it's from Apple or you know it's from Microsoft if it's a Microsoft logo. And like trade secrets, if you maintain them appropriately and that's essentially paying money to keep them going with the various offices that maintain trademarks, they could really last forever if you want them to. Now patents are a little bit different in that if you notice in my first sentence, I'd say the patents are used to prevent others from doing something. You can prevent others from making, using or selling. One of the things that folks don't realize often about patents is having a patent doesn't necessarily mean that you can practice your patent. Right? You can prevent others from practicing it, but you may not be able to practice it. You may need a license for say background art or competing technologies or other technologies. So it's a little different than the other areas of intellectual property. And patents are only good or only valid out to the borders of the country in which they were filed. So you have a U.S. patent and you have a European patent, you have an Australian patent and so on. Those patents will last 20 years from the date of their filing. So they're not essentially forever like perhaps copyrights or trademarks or trade secrets. They do have a finite life. Now just as a summary, copyrights protect the form of expression of the ideas. Remember expression is the key. Trademarks protect the identification of the sources of these ideas. And patents and trademarks protect the application of the ideas. So I think hopefully we're all on a common understanding about intellectual property. Now let's talk about a hot legal issue. And this is becoming more and more prevalent from a litigation point of view and from a strategic management point of view. And that's the use of free and open source software. And I abbreviated it FOSS, which I think is what you folks call it. And because of the prevalence of free and open source software in the marketplace, there is sort of becoming a situation where a FOSS is starting to give rise to litigation. How can that be? When people see the word free, they think unfettered, right? It's free from perhaps a money point of view. You're not paying for the software. But underlying it, remember we talked about all these copyrights and all this other stuff kind of existing. That is not free from the perspective of obligation. So what is happening is that technologies are being developed and they are incorporating FOSS into their products. And as they are marketing them, they are what? Infringing the copyright of the FOSS holder. And there's been litigations, particularly in the United States, that have resulted in very, very large damages. So the whole issue of what do you do with free and open source software if you are utilizing it in your products? Now, if you are a digital company and you are distributing a software product, you definitely want to identify the presence of FOSS within your product. You want to be able to manage how it's utilized. And if there are licenses attached to that free and open source software, you want to make sure that you're complying with it. Because if you're going to be marketing a product, those obligations flow through to whatever license you are granting to your customers. So hence, it's really about the obligation flow through to other users that you have to be concerned about. Now, what if you're using it simply within your company for specific purposes? It's more an issue of compliance. There are probably restrictions associated with the use of that technology as far as propagation and distribution. And you need to be aware of them. Now, a lot of software is available under what they call public licenses. But if you read through all of the verbiage, the legal verbiage of these licenses, there's usually a section that talks about potential commercial use. So if you are a commercial company, you have to pay particular attention to those particular clauses because they are likely to be restrictive and you have to be aware of them. So identifying and managing and then complying I think is the key when it comes to free and open source software. It's kind of interesting because when I way back when when I was young and software was very new, sort of everything was proprietary at that point. It was only much later in the process that this free and open source software came into being. And there's also in some instances been kind of a cycling of it. There was a time when Linux was competing with Unix and then along came Red Hat. If you've heard of the company Red Hat. So they're taking Linux and they're making money from Linux, which is a free and open source software. So there's kind of this recycling of ideas along the way. And I think it's likely going to accelerate. Now, I had mentioned the basis of copyright and how does that impact on FOS? Why should you be concerned about it? If you think you link back to the bundle of rights, what would you be doing with that software in your own product? Well, you would likely be reproducing it. You could be adapting it, creating a derivative work or distributing it. So you would have impacted those at least those three of the bundle of rights of copyright. That's why you need to be thinking about it. Now, I spoke to some of the programmers at Sidra and I asked about this because that's what I need to do as the council. How do you find out whether or not the software is embedded in what you're using? And they gave me these names. So maybe you are familiar with them as tools to scan your programs to see if there's FOS included. Now, another subject that is particularly important for social media-based companies, but probably all companies that deal with digital information is the idea of data security. Now, the interconnectedness of the Internet of Things, and if you think about all the things that are being connected now, you know, scannables and wearables and anything that you attach the word smart to, you know, is sending information someplace and you're being tracked and all that information is being generated. So things are connecting things all over and that information has value to someone or a lot of folks. So as a part of your plan, your development of your products or your company, you need to come up with a way to ensure that there is security in this information. And I've turned it security by design. You really have to think about security from the very beginning of developing the technology. Now, what are the key issues as far as data security? Well, connecting intelligently for one. Is it really necessary for, say, my device to connect it to this device or that device, you know, should your phone connect to your refrigerator? Is there a reason for that? Maybe there is. Maybe there isn't. But if it does connect, it's going to have an impact. Ensuring that the software remains up to date over its life. There are certainly issues in the area of medical applications of social media where keeping things up to date is absolutely critical. And finally maximizing data protection as a part of your overall security plan. And obviously that's a technological type of activity, but it has to be a part of your strategy as well. Now, the last issue I wanted to raise is data privacy. And I contrast data security, which I view more as a technological process. But data privacy is kind of a business strategy. You choose what information that you want to gather from your customers as a part of your business plan. Now, obviously this information is going to have value. Knowledge is power. Knowledge is value. And there's going to be lots and lots of individuals and companies that want to have access. Now, the key is to approach this issue very proactively. You want to approach privacy of data. And I've kind of focused it more. It's not as much data, is it? It's really about privacy of the user. So there is a person behind that information. So really when you're protecting data, you're protecting people, protecting individuals. Think of it that way. Now, there's been a lot of talk about a way of doing this called data minimization. It's essentially only collecting as much information as you need to fulfill the purposes of what your program is going to do. And you'll only keep that information for as long as you need to keep it. In the medical application area, this is a significant issue because you are collecting information about a person's health. Now, what happens if that information is kept forever and ever? Some place, you know, in the cloud or where it might be. Someone could get to it. You know, someone could break the security and get to that medical information. It could be very difficult and very challenging. So kind of minimizing the danger, you know, the impact of a security breach by only collecting as much information as you need to collect to do what you want to do. My employer requires me to say that I am not authorized to practice law and cutter. So I can't provide legal advice to you related to private matters. A lot of times when I give talks, I get calls afterwards and I get very, very detailed hypothetical situations that people talk about. I know it's coming because that's how they start. Hypothetically, if this. But I'm happy to talk about these topics in general, particularly from a legal perspective, especially intellectual property. It's kind of my area. So thank you. Thanks.