Podcasts & Interviews

Podcast with Chetan Sikarwar, FOSS Compliance Legal Counsel, Bosch (Part-2)

Join host Avinash Tripathi as he engages in a thought-provoking conversation with Chetan Sikarwar, FOSS Compliance Legal Counsel at Bosch. In this illuminating podcast, Chetan shares his expertise on open-source software, patents, and the legal intricacies of the tech world.

Key Discussion Points:

FOSS Compliance Unveiled

Chetan demystifies the day-to-day responsibilities of a FOSS (Free and Open Source Software) Compliance officer, shedding light on their crucial role in ensuring that software used and developed by companies complies with various open source licenses and legal requirements.

Free vs. Open Source

Addressing a common misconception, Chetan explains why free software isn’t necessarily open source and vice versa. He elaborates on the different philosophies and licensing implications that distinguish these two types of software.

Creative Commons Explained

Chetan breaks down Creative Commons licenses for our audience, emphasizing their impact on content sharing. He discusses the various types of Creative Commons licenses and how they allow creators to share their work with specific permissions.

Software Patents Today

A comparison of the current software patent landscape with that of 5-10 years ago. Chetan highlights the evolution of software patenting practices and the shifting attitudes toward software patents in the tech industry.

Patents vs. Copyright

Why do companies lean toward software patents over copyright protection? Chetan explores the strategic advantages of patents in providing robust protection for software innovations and deterring infringement.

Patenting Software in India

Insights into the feasibility and challenges of obtaining software patents in India. Chetan discusses the legal framework, procedural hurdles, and practical considerations for patenting software in the Indian context.

Startup Dilemma

Should young startups invest in patenting their software or technology? Chetan provides guidance for startups on the cost-benefit analysis of pursuing patents and alternative intellectual property strategies.

Google’s Early Days

An intriguing hypothetical—would Chetan have advised Google to patent their groundbreaking technology in their early days? He delves into the strategic decisions surrounding IP protection for disruptive technologies.

Generative AI in Law

Chetan explores the best use cases of generative AI within the legal profession. He discusses how AI can enhance legal research, contract analysis, and streamline various legal processes.

Research Strategies

Discover the steps Chetan follows while researching legal cases. He shares his methodology for conducting thorough and effective legal research, leveraging both traditional resources and advanced technology tools.


This podcast promises valuable insights for tech enthusiasts, legal professionals, and startup founders alike! 🎙️🔍💡

Don’t miss this enlightening episode! Subscribe to our channel for more discussions on technology, law, and innovation.


1
00:00:00,000 --> 00:00:11,600
Hey guys, welcome back to another episode of LexDiscuss Cafe.

2
00:00:11,600 --> 00:00:17,900
Today, we are thrilled to continue our insightful conversation with Mr. Chetan.

3
00:00:17,900 --> 00:00:21,440
He is a FOSS Compliance Counsel at Bosch.

4
00:00:21,440 --> 00:00:27,800
For people who may not know what FOSS means, it is actually an abbreviation that stands

5
00:00:27,800 --> 00:00:31,040
for Free and Open Source Software.

6
00:00:31,040 --> 00:00:36,160
If you missed the part 1 of our conversation with Chetan, make sure to catch up on our

7
00:00:36,160 --> 00:00:42,160
fascinating discussion about intellectual property law and open source software compliance.

8
00:00:42,160 --> 00:00:44,800
Now let me tell you a little bit about Chetan.

9
00:00:44,800 --> 00:00:47,180
He is an alum of IIT Kharagpur.

10
00:00:47,180 --> 00:00:52,200
He has an impressive background that spans from software engineering, patent analysis

11
00:00:52,200 --> 00:00:53,560
to legal research.

12
00:00:53,760 --> 00:00:59,200
Today, we dive deeper into his experiences and his thoughts on the evolving landscape

13
00:00:59,200 --> 00:01:01,840
of software licensing and compliance.

14
00:01:01,840 --> 00:01:09,880
Stay tuned for a compelling dialogue.

15
00:01:09,880 --> 00:01:16,940
So Chetan, welcome again, and please go ahead and appear on the second part of the podcast.

16
00:01:16,940 --> 00:01:17,940
Thank you.

17
00:01:17,940 --> 00:01:18,940
Thank you for having me.

18
00:01:19,420 --> 00:01:24,220
So for the listeners who don't know Chetan, please go and listen to the part 1.

19
00:01:24,220 --> 00:01:28,540
We have given an amazing introduction to what Chetan does and what kind of things he does

20
00:01:28,540 --> 00:01:29,940
on a day-to-day basis.

21
00:01:29,940 --> 00:01:35,980
Just a quick refresher, he is FOSS Compliance Officer at Bosch, right?

22
00:01:35,980 --> 00:01:41,380
Do you want to just give a quick explanation of what does a FOSS Compliance Officer do?

23
00:01:41,380 --> 00:01:46,860
As a FOSS Compliance Officer, my part of the job is to ensure that whatever software component

24
00:01:46,860 --> 00:01:51,580
we are using in our product, they are compliant with the open source licenses.

25
00:01:51,580 --> 00:01:54,020
Can you please tell us what FOSS stands for?

26
00:01:54,020 --> 00:01:56,900
So FOSS stands for Free and Open Source Software.

27
00:01:56,900 --> 00:02:01,860
So there are two major organizations which deal with the open source in general.

28
00:02:01,860 --> 00:02:09,220
One is Open OSI, that is Open Source Initiative, and another one is Free and Open Source Software,

29
00:02:09,220 --> 00:02:10,380
FSF.

30
00:02:10,380 --> 00:02:14,060
So the FOSS is basically a combination of both these two.

31
00:02:14,060 --> 00:02:20,500
So OSI has a different understanding of what open source means, whereas Free Software Foundation

32
00:02:20,500 --> 00:02:22,260
have a different understanding to me.

33
00:02:22,260 --> 00:02:27,500
So any application which is licensed and developed by Free Software Foundation are considered

34
00:02:27,500 --> 00:02:30,100
to be a free software.

35
00:02:30,100 --> 00:02:35,620
And anything which is licensed under Open Source Initiative licenses are known as open

36
00:02:35,620 --> 00:02:37,460
source licenses.

37
00:02:37,460 --> 00:02:40,380
So collectively, they are known as FOSS.

38
00:02:40,380 --> 00:02:41,380
Right.

39
00:02:41,380 --> 00:02:42,380
That's great.

40
00:02:42,700 --> 00:02:46,980
In the last podcast, you explained it really well, just because something is available

41
00:02:46,980 --> 00:02:48,340
on the internet for free.

42
00:02:48,340 --> 00:02:50,740
It's open source.

43
00:02:50,740 --> 00:02:54,860
And because you have to pay for some software, it doesn't mean that the software is not open

44
00:02:54,860 --> 00:02:55,860
source.

45
00:02:55,860 --> 00:02:56,860
Yes.

46
00:02:56,860 --> 00:02:58,740
Want to repeat that for our listeners?

47
00:02:58,740 --> 00:02:59,740
Yes.

48
00:02:59,740 --> 00:03:01,820
So the best example is Wikipedia.

49
00:03:01,820 --> 00:03:06,400
So if you look into the Wikipedia and go scroll down, you'll see a creative common attribution

50
00:03:06,400 --> 00:03:08,280
share a license.

51
00:03:08,280 --> 00:03:12,960
So what it means is that although you have right to use this particular work, reproduce

52
00:03:12,960 --> 00:03:16,920
that work in your whatever the thing that you are doing, but that does not mean that

53
00:03:16,920 --> 00:03:20,680
particular piece of work do not have copyright of someone.

54
00:03:20,680 --> 00:03:25,160
It is still copyrighted by someone, somebody owns that piece of work, he can change, he

55
00:03:25,160 --> 00:03:30,160
can do whatever he wants to do with this piece of work, but out of his goodwill, he has given

56
00:03:30,160 --> 00:03:36,600
you the right to use, reproduce, create derivative works out of it, but with certain conditions.

57
00:03:36,600 --> 00:03:41,380
Now those condition are under creative common attribution share alike licenses that whenever

58
00:03:41,380 --> 00:03:46,040
you're using work, which is under this particular license, you need to give attribution.

59
00:03:46,040 --> 00:03:50,480
Now attribution is nothing but the copyright notice means the name of the author, copyright

60
00:03:50,480 --> 00:03:52,920
sign here and then all right received it.

61
00:03:52,920 --> 00:03:58,880
So whatever second share alike, what it basically mean is the way you received it, you shall

62
00:03:58,880 --> 00:04:00,700
reproduce it in the exact manner.

63
00:04:00,700 --> 00:04:02,860
You cannot make modification to that work.

64
00:04:02,860 --> 00:04:08,860
So for example, if I downloaded an article from Wikipedia and I want to republish it,

65
00:04:08,860 --> 00:04:12,300
I cannot make changes in that work as per the license agreement.

66
00:04:12,300 --> 00:04:16,660
Apart from that, there are various licenses which says that you cannot charge for the

67
00:04:16,660 --> 00:04:21,980
application itself, but if you want to give maintenance and support, you can charge it

68
00:04:21,980 --> 00:04:22,980
for that.

69
00:04:22,980 --> 00:04:28,540
Or if you are distributing a conventional manner, for example, CD DVD and all, you can

70
00:04:28,540 --> 00:04:29,540
charge it for that.

71
00:04:29,740 --> 00:04:33,700
Or if you are adding your own application along with it, then you can charge it for

72
00:04:33,700 --> 00:04:38,340
your application, but not for the something that you have received from us.

73
00:04:38,340 --> 00:04:43,880
So this is what a lot of lawyers say to me that they say like, okay, we were just starting

74
00:04:43,880 --> 00:04:46,420
to understand what is an open source software.

75
00:04:46,420 --> 00:04:51,460
You brought in the concept of free software and then you create a distinction in that.

76
00:04:51,460 --> 00:04:54,340
You brought in the concept of creative commons, right?

77
00:04:54,340 --> 00:04:57,260
So thanks for the stuff to meet you.

78
00:04:57,260 --> 00:05:00,340
You are right now.

79
00:05:00,340 --> 00:05:04,300
Now you have like, let me just rephrase what you have just said and correct me if I'm

80
00:05:04,300 --> 00:05:05,300
wrong.

81
00:05:05,300 --> 00:05:09,220
An open source software essentially means that the source code, like you know that the

82
00:05:09,220 --> 00:05:14,540
thing that coders have actually written that is available, open to everyone, right?

83
00:05:14,540 --> 00:05:15,540
Yes.

84
00:05:15,540 --> 00:05:16,540
Yes.

85
00:05:16,540 --> 00:05:22,060
Just because it is open to everyone, it doesn't mean that you can do anything with it, right?

86
00:05:22,060 --> 00:05:26,500
You can open source your software under two frameworks.

87
00:05:26,500 --> 00:05:29,860
First is software initiative and the second one works.

88
00:05:29,860 --> 00:05:36,380
Second one is OSI, open source initiative, software foundation, and the other one is

89
00:05:36,380 --> 00:05:39,100
open source initiative, right?

90
00:05:39,100 --> 00:05:46,220
So you can know these and they have to be detached with it, right, as a legal audience

91
00:05:46,220 --> 00:05:48,460
who really understand copyright.

92
00:05:48,460 --> 00:05:49,460
This is not for you.

93
00:05:49,500 --> 00:05:52,260
For a general audience, copyright is like a bundle of rights.

94
00:05:52,260 --> 00:05:54,980
So you have rights, right?

95
00:05:54,980 --> 00:05:55,980
Yes.

96
00:05:55,980 --> 00:05:58,180
Which one do you want to access?

97
00:05:58,180 --> 00:06:03,660
Right to ownership, right to reproduce, right to accreditation, right?

98
00:06:03,660 --> 00:06:04,980
There are so many rights.

99
00:06:04,980 --> 00:06:10,980
So in these, what is happening is these foundations and these organizations are standardizing

100
00:06:10,980 --> 00:06:15,780
these licensing terms essentially, according to their own interpretation.

101
00:06:15,780 --> 00:06:20,620
Now, there is another thing that comes in, which is Creative Commons, which is nothing

102
00:06:20,620 --> 00:06:25,500
else but a standardized version of licensing terms.

103
00:06:25,500 --> 00:06:27,260
And what is exactly Creative Commons?

104
00:06:27,260 --> 00:06:30,620
I will let Shetan explain a little more.

105
00:06:30,620 --> 00:06:37,740
So Creative Commons is a set of licenses, which is basically designed to cater the requirement

106
00:06:37,740 --> 00:06:39,020
of artistic work.

107
00:06:39,020 --> 00:06:45,820
So if let's say I have a sound recording or an image or a text, and I want this piece

108
00:06:45,820 --> 00:06:48,780
of work to be protected under copyright information.

109
00:06:48,780 --> 00:06:56,100
So now under open source, whatever the licenses we have, whether MIT, BSD, GPL, so all these

110
00:06:56,100 --> 00:06:59,860
licenses are designed for software specific in nature, right?

111
00:06:59,860 --> 00:07:03,820
So you will find some technical information there as well.

112
00:07:03,820 --> 00:07:08,420
But Creative Commons is designed in a way that it only caters to your artistic work,

113
00:07:08,660 --> 00:07:15,220
like, for example, an image or a text, which is Wikipedia or any sound recording.

114
00:07:15,220 --> 00:07:18,020
But during my course of work, I found out a lot of authors.

115
00:07:18,020 --> 00:07:21,940
They have also licensed their work under Creative Commons as well.

116
00:07:21,940 --> 00:07:28,060
Now Creative Commons comes in a way, when you say authors, authors of software or authors?

117
00:07:28,060 --> 00:07:29,060
Yes.

118
00:07:29,060 --> 00:07:30,060
No, no, authors of software.

119
00:07:30,060 --> 00:07:33,700
So these licenses are there on their website.

120
00:07:33,700 --> 00:07:38,380
So Creative Commons have a huge website where they give you a variety of licenses.

121
00:07:38,380 --> 00:07:44,540
Similarly, Free Software Foundation has their own list of licenses, General Public License

122
00:07:44,540 --> 00:07:48,900
1, General Public License 2, General Public License 3, which is their latest version.

123
00:07:48,900 --> 00:07:55,900
They also have something known as Lesser General Public License, LGPL 2.1 and 3.

124
00:07:55,900 --> 00:08:01,180
Then they also have Afro General Public License, Faro General Public License, that is AGPL.

125
00:08:01,420 --> 00:08:06,180
Similarly, Open Source Initiative, what they do is they look at the license text, which

126
00:08:06,180 --> 00:08:11,660
is designed by a specific author, go through the license text, determine whatever the principle

127
00:08:11,660 --> 00:08:16,020
they have enshrined in a license, whether those principles are there or not.

128
00:08:16,020 --> 00:08:20,140
If they found those principles in that particular license, they certify it.

129
00:08:20,140 --> 00:08:25,660
So OSI is sort of a certification body which certifies the licenses, whereas Free Software

130
00:08:25,660 --> 00:08:29,820
Foundation is something which drafts their own licenses.

131
00:08:29,820 --> 00:08:34,320
Let's talk about the Creative Commons or Creative Commons in general comes in a various flavor.

132
00:08:34,320 --> 00:08:36,060
So they have four or five terms.

133
00:08:36,060 --> 00:08:39,340
So first term is Creative Commons Attribution.

134
00:08:39,340 --> 00:08:43,820
Now Creative Commons Attribution is something where you can use the work, do whatever you

135
00:08:43,820 --> 00:08:48,380
want to do with the work, just attribution is required.

136
00:08:48,380 --> 00:08:52,980
Now with the same thing, they add another term that is Creative Commons Attribution

137
00:08:52,980 --> 00:08:54,380
and Share Alike.

138
00:08:54,380 --> 00:09:00,020
Now the moment I add Share Alike, it becomes a sort of strong copy left, although the term

139
00:09:00,020 --> 00:09:05,700
is not correct to use here, but in a way it becomes the strong copy left means you need

140
00:09:05,700 --> 00:09:08,180
to distribute the work in a same manner.

141
00:09:08,180 --> 00:09:14,180
Now it's up to a person who is licensing his work under Creative Commons to either choose

142
00:09:14,180 --> 00:09:16,860
this Share Alike or not.

143
00:09:16,860 --> 00:09:21,020
Then third thing comes, let's say for example, I wrote a novel and I do not want commercial

144
00:09:21,020 --> 00:09:22,420
people to utilize it.

145
00:09:22,420 --> 00:09:26,200
So I can do Creative Commons Attribution non-commercial.

146
00:09:26,200 --> 00:09:31,920
So the moment I do this, what happens is you cannot use my work for commercial purposes.

147
00:09:31,920 --> 00:09:34,160
So Creative Commons have various things.

148
00:09:34,160 --> 00:09:37,820
So one is Share Alike, another is your non-commercial.

149
00:09:37,820 --> 00:09:42,420
I think these are the two major ones where you can customize your license as per your

150
00:09:42,420 --> 00:09:48,380
requirement and you can release your work under these requirements.

151
00:09:48,380 --> 00:09:52,700
Now apart from that, they also come up with the various jurisdiction specifics.

152
00:09:52,700 --> 00:09:58,540
So for example, I am the person who wrote some article in US and I want that article

153
00:09:58,540 --> 00:10:00,420
to be just in the US jurisdiction.

154
00:10:00,420 --> 00:10:05,200
So I can go with Creative Commons, Share Alike or whatever, USA.

155
00:10:05,200 --> 00:10:10,140
So now by that what happens is whatever the list of rights, obligations and restrictions

156
00:10:10,140 --> 00:10:16,020
are there in the license, they shall be interpreted in terms of United States of America or Canada

157
00:10:16,020 --> 00:10:17,740
or anywhere else.

158
00:10:17,740 --> 00:10:23,340
So Creative Commons, I would say, is sort of a la carte basket where you choose rights

159
00:10:23,340 --> 00:10:27,060
and obligations as per your requirement and then release it to the public.

160
00:10:27,060 --> 00:10:34,380
It essentially makes the job of lawyers redundant, like you do not have to consult a lawyer every

161
00:10:34,380 --> 00:10:36,900
time you are doing a licensing of your software, right?

162
00:10:36,900 --> 00:10:40,300
And this is a very boring and mundane topic as to what these are.

163
00:10:40,300 --> 00:10:45,180
So we will not go into the detail of this in this podcast, but a friend of mine has

164
00:10:45,420 --> 00:10:47,340
written a very extensive article on this.

165
00:10:47,340 --> 00:10:51,940
So some, again, will be interested in understanding the nuances of each and every license.

166
00:10:51,940 --> 00:10:53,540
I'll put a link in the description.

167
00:10:53,540 --> 00:10:56,060
You go and read that, right?

168
00:10:56,060 --> 00:11:00,420
Now moving on to the next very interesting question because we are talking about softwares.

169
00:11:00,420 --> 00:11:02,540
Patent for software, right?

170
00:11:02,540 --> 00:11:09,580
Current scenario versus how things were 5 years, 10 years back or patents of software

171
00:11:09,580 --> 00:11:13,380
in India compared to software patents in the US.

172
00:11:13,540 --> 00:11:16,420
Do you want to give a comparative analysis on this?

173
00:11:16,420 --> 00:11:24,860
Okay, so patent, if I talk about patent in general, USA versus India, so patent grant

174
00:11:24,860 --> 00:11:28,460
in USA is more easier when it comes to these things.

175
00:11:28,460 --> 00:11:32,180
So they more or less give everything patent, right?

176
00:11:32,180 --> 00:11:34,140
Because they are more market driven economy.

177
00:11:34,140 --> 00:11:37,940
When we talk about India, we more or less follow the approach of UK or Europe, where

178
00:11:37,940 --> 00:11:42,260
we are very selective in order to give exclusive right to anyone.

179
00:11:42,260 --> 00:11:47,060
Now coming to the software part, in USA you can get a patent for more or less anything

180
00:11:47,060 --> 00:11:50,580
as long as it is not computer program per se.

181
00:11:50,580 --> 00:11:55,900
So now per se can be interpreted as in you have an algorithm, you convert that algorithm

182
00:11:55,900 --> 00:12:01,300
into a machine readable language, either in Java, C, C++, whatever.

183
00:12:01,300 --> 00:12:05,860
Now in India, what basically happens is that you will not get patent for that particular

184
00:12:05,860 --> 00:12:06,860
code itself.

185
00:12:06,860 --> 00:12:11,220
Rather, you'll get the patent for functionality it achieves.

186
00:12:11,220 --> 00:12:16,620
So if I take an example here, let's say I am developing a washing machine, right?

187
00:12:16,620 --> 00:12:18,780
Now this washing machine has certain features.

188
00:12:18,780 --> 00:12:23,860
Feature as in you press a button, it will wash your delicate clothes in a certain manner

189
00:12:23,860 --> 00:12:27,300
or you press a button, it will wash your woolens.

190
00:12:27,300 --> 00:12:30,120
Now this functionality is achieved by a software, right?

191
00:12:30,120 --> 00:12:37,100
So when I press delicate, it will give certain inputs to the hardware and then hardware function

192
00:12:37,100 --> 00:12:38,420
in certain manner.

193
00:12:38,420 --> 00:12:43,800
Now I can get patent on this particular software along with the functionality.

194
00:12:43,800 --> 00:12:48,620
If I go and say, okay, this is my software and give me patent for this software, I will

195
00:12:48,620 --> 00:12:49,620
not receive it.

196
00:12:49,620 --> 00:12:55,820
I have to show how it is functioning and how it is enhancing the, either the monetary way

197
00:12:55,820 --> 00:12:58,860
or enhancing the life of the people in general.

198
00:12:58,860 --> 00:13:03,580
So in India, if you want to get your software patented, you need to show the functionality

199
00:13:03,580 --> 00:13:06,340
associated to the application.

200
00:13:06,340 --> 00:13:13,060
Hence there has to be some hardware and software linkage and how this software is controlling

201
00:13:13,060 --> 00:13:17,980
that hardware to either assisting people or reducing money.

202
00:13:17,980 --> 00:13:25,020
Wow, great explanation and you know, do you want to delve into why inventors or companies

203
00:13:25,020 --> 00:13:29,140
love software patents versus copyright?

204
00:13:29,140 --> 00:13:35,500
Like just FYI, for people who don't know, copyright software or source code is created

205
00:13:35,500 --> 00:13:41,820
as a literary work and by the virtue of Berne Convention and the Indian Populite Act, you

206
00:13:41,820 --> 00:13:47,900
get automatic or protection of it as soon as it is put in a tangible form.

207
00:13:47,900 --> 00:13:55,220
There is a perception that, you know, if you don't register, it would be, it's not enforceable.

208
00:13:55,220 --> 00:13:59,300
No, if you don't register, it is harder to enforce.

209
00:13:59,300 --> 00:14:03,280
But the moment you put it in a tangible format, it is protected.

210
00:14:03,280 --> 00:14:04,780
It is protected, yes.

211
00:14:05,660 --> 00:14:11,020
Now, why they love software patents versus software copyright?

212
00:14:11,020 --> 00:14:17,020
Okay, so it's almost two years since I'm working in this industry and I read a lot of research

213
00:14:17,020 --> 00:14:20,860
paper and I also work with these software developers.

214
00:14:20,860 --> 00:14:27,900
So one thing which I found out after this year of experience is that software is something

215
00:14:27,900 --> 00:14:30,500
which is very functional in character, right?

216
00:14:30,500 --> 00:14:35,340
So whenever I want a protection, I want the protection for the functionality, not the

217
00:14:35,340 --> 00:14:37,180
expression, right?

218
00:14:37,180 --> 00:14:41,000
I am least bothered about my expression because there are n number of ways someone can copy

219
00:14:41,000 --> 00:14:45,740
that expression and still that expression is different from mine, right?

220
00:14:45,740 --> 00:14:51,540
Now copyright is designed in a way that it only protects the expression, not the functionality.

221
00:14:51,540 --> 00:14:54,900
Whereas patent is something which protects your functionality, they are least concerned

222
00:14:54,900 --> 00:14:57,280
about the expression, how you are expressing it.

223
00:14:57,280 --> 00:15:01,120
So I think this is one of the reason because of which companies are preferring to go for

224
00:15:01,120 --> 00:15:04,400
a software patent rather than copywriting.

225
00:15:04,400 --> 00:15:10,600
Now if I deep dive into this, then I would say in copyright what happens is if you have

226
00:15:10,600 --> 00:15:16,400
multiple ways to express certain things, right, then your expression is protected, right?

227
00:15:16,400 --> 00:15:21,120
So for example, I'm developing a software for scientific calculator, let's say.

228
00:15:21,120 --> 00:15:25,840
Now in developing that scientific calculator, no matter how well I have written that piece

229
00:15:25,920 --> 00:15:31,320
of code, but if it's the only way to achieve the addition of two numbers, someone else

230
00:15:31,320 --> 00:15:34,400
can copy it, right?

231
00:15:34,400 --> 00:15:36,240
Either I have a copyright over it.

232
00:15:36,240 --> 00:15:41,040
Now because of this particular reason, people are preferring patents.

233
00:15:41,040 --> 00:15:43,240
Now in patents, there is nothing like such.

234
00:15:43,240 --> 00:15:47,800
So if I am the first inventor of an application and file the patent for my software, nobody

235
00:15:47,800 --> 00:15:49,200
can touch me.

236
00:15:49,200 --> 00:15:50,920
Nobody can touch my product.

237
00:15:50,920 --> 00:15:53,720
Nobody can even use it or import it.

238
00:15:53,720 --> 00:15:55,840
Certain sort of things are not available in the copyright.

239
00:15:55,840 --> 00:15:57,680
So copyright is designed in this way.

240
00:15:57,680 --> 00:16:02,320
There is one beautiful paper written by, I'm not sure who's the author of it, known as

241
00:16:02,320 --> 00:16:03,320
spillover.

242
00:16:03,320 --> 00:16:07,080
So he basically discuss about the fallacies of the copyright law.

243
00:16:07,080 --> 00:16:12,360
He said the copyright is designed in a way so that it has a lot of fallacy in it.

244
00:16:12,360 --> 00:16:18,000
Apart from that, I also believe that comparing a novel with the software is not the right

245
00:16:18,000 --> 00:16:19,000
thing.

246
00:16:19,000 --> 00:16:23,000
It's like comparing Apple with, I would say a potato.

247
00:16:23,000 --> 00:16:26,920
They are not even a same family all together.

248
00:16:26,920 --> 00:16:30,840
Apart from that, one more reason because of which I believe copywriting software is not

249
00:16:30,840 --> 00:16:35,400
well protected is if you look into the time period.

250
00:16:35,400 --> 00:16:40,200
So copyright is given for the author's life, 60 years, right?

251
00:16:40,200 --> 00:16:45,920
And nowadays the technology is fasting such a way that today my software is in market

252
00:16:45,920 --> 00:16:48,560
tomorrow something new comes and it becomes obsolete.

253
00:16:48,560 --> 00:16:52,640
Now what will I do for that particular prediction?

254
00:16:53,560 --> 00:16:56,000
And there are a lot of research papers written by a lot of people.

255
00:16:56,000 --> 00:17:04,520
I think Pamela Samuelson, she's a well-renowned professor in UC Berkeley, if I'm not wrong.

256
00:17:04,520 --> 00:17:09,720
She has written a fantastic paper where she has discussed that why copyright is not right

257
00:17:09,720 --> 00:17:11,680
legislation to protect software.

258
00:17:11,680 --> 00:17:12,680
Right.

259
00:17:12,680 --> 00:17:17,000
And you know, from a practical perspective, a lot of people who are writing software,

260
00:17:17,000 --> 00:17:22,240
they come to me and say like, if I want to register a software, I have to submit a copy

261
00:17:22,240 --> 00:17:23,240
of it, right?

262
00:17:23,240 --> 00:17:24,240
Yes.

263
00:17:24,240 --> 00:17:25,240
Yes.

264
00:17:25,240 --> 00:17:31,880
I agree that to me, to an author of a software, that seems more risky because I'm sharing

265
00:17:31,880 --> 00:17:34,620
my copy and I'm making it public domain.

266
00:17:34,620 --> 00:17:40,680
If I'm so secretive about it, I'd rather just keep it a closed source and keep it as

267
00:17:40,680 --> 00:17:47,520
a trade secret in protecting it in the copyright, right?

268
00:17:47,520 --> 00:17:54,480
I also believe that proving patent infringement is comparatively easier than proving the copyright

269
00:17:54,480 --> 00:17:55,480
infringement.

270
00:17:55,480 --> 00:17:56,480
Right.

271
00:17:56,480 --> 00:17:59,600
So when you go for a copyright infringement, a lot of things, firstly, you need to show

272
00:17:59,600 --> 00:18:04,600
that whatever you have done, this is the fact part of it.

273
00:18:04,600 --> 00:18:06,160
And these are the expression.

274
00:18:06,160 --> 00:18:10,080
Now in that expression, they will look into the substantial similarity, right?

275
00:18:10,080 --> 00:18:14,160
So whatever the work I have in whatever the work infringer have, they will look for the

276
00:18:14,160 --> 00:18:15,960
substantial similarity in that.

277
00:18:15,960 --> 00:18:21,680
So the design in such a way that at last, whatever is left, most of the time it is not

278
00:18:21,680 --> 00:18:23,220
considered as infringement.

279
00:18:23,220 --> 00:18:28,160
So I don't think so copyright is doing any help to the software industry.

280
00:18:28,160 --> 00:18:33,260
It's a high time that we look for some new legislature, which is more stronger and stringent.

281
00:18:33,260 --> 00:18:35,680
On the same time, give protection for a limited period.

282
00:18:35,680 --> 00:18:39,880
I mean, don't give us a protection for 20 years because technology will be obsolete

283
00:18:39,880 --> 00:18:40,880
in 20 years.

284
00:18:40,880 --> 00:18:45,880
Give us for five or seven years and has to be a stronger one.

285
00:18:45,880 --> 00:18:52,640
And then copyright is specifically expedite the process, a patent granting process.

286
00:18:52,640 --> 00:19:01,400
And a couple of years back, I think still 2015, 16, when I was actively practicing IP, right?

287
00:19:01,400 --> 00:19:07,880
At that time, the position of government of India was that we will not grant just the

288
00:19:07,880 --> 00:19:08,880
software patents.

289
00:19:08,880 --> 00:19:13,680
We will grant patents if a software is attached with a novel hardware.

290
00:19:13,680 --> 00:19:16,520
That was the exact term these guys were using.

291
00:19:16,520 --> 00:19:21,720
Now a lot of that what is happening is that for yourself, imagine that I want to get a

292
00:19:21,720 --> 00:19:28,200
patent for a software to help people in restaurants order their stuff right from the table that

293
00:19:28,200 --> 00:19:29,700
they are eating at, right?

294
00:19:29,700 --> 00:19:32,680
So like me, I want to create a software like that.

295
00:19:32,680 --> 00:19:35,440
Now in India, I can't get a patent for that software, right?

296
00:19:35,440 --> 00:19:39,680
So what I'll do, I'll just, just for the sake of getting a patent, I'll attach a software,

297
00:19:40,680 --> 00:19:46,600
I'll attach a basic computer, which is not novel in any way, and try to get a patent

298
00:19:46,600 --> 00:19:47,600
that way.

299
00:19:47,600 --> 00:19:49,440
So do you have any latest updates on it?

300
00:19:49,440 --> 00:19:53,680
Is this stance has changed or are they still following it?

301
00:19:53,680 --> 00:19:55,120
No, I don't think so.

302
00:19:55,120 --> 00:19:57,600
They have changed anything on this particular matter.

303
00:19:57,600 --> 00:20:04,280
And to be honest, and it won't be an exaggeration to say that we basically wait for US or UK

304
00:20:04,280 --> 00:20:07,960
to do something and then we implement that in our legislation.

305
00:20:07,960 --> 00:20:12,300
So although they have changed the rule, but I don't think so they have made any changes

306
00:20:12,300 --> 00:20:17,000
so far as granting the patent for the software in general.

307
00:20:17,000 --> 00:20:21,640
Software patents are usually granted in India, it's all about the way you are drafting it.

308
00:20:21,640 --> 00:20:26,440
A very previous drafter can get you a patent on any piece of software.

309
00:20:26,440 --> 00:20:30,960
Just a misnomer now that software patents are not there in India, it's all about the way

310
00:20:30,960 --> 00:20:32,680
you are drafting it.

311
00:20:32,680 --> 00:20:39,200
If I can recall correctly, a friend of mine, she used to work in one of the industry and

312
00:20:39,200 --> 00:20:47,240
she drafted a patent and the functionality for which she got the patent was very naive.

313
00:20:47,240 --> 00:20:51,340
They have a drop down menu initially, I mean, they had a ribbon initially and then they

314
00:20:51,340 --> 00:20:55,640
converted that ribbon into a drop down menu and they drafted in a way that it reduces

315
00:20:55,640 --> 00:20:59,380
the time for the consumer, it is easier to see and so on and so forth.

316
00:20:59,380 --> 00:21:01,240
And they received the patent for it.

317
00:21:01,240 --> 00:21:07,960
So nowadays, I mean, you are getting a patent for anything and everything, it's just how

318
00:21:07,960 --> 00:21:14,480
you are drafting it, thus there shall not be any prior art.

319
00:21:14,480 --> 00:21:19,920
It brings us to a very interesting concept as to what should young startups at this stage

320
00:21:19,920 --> 00:21:20,920
do.

321
00:21:20,920 --> 00:21:27,160
So to be honest, as a startup, a lot of times you come up with new ways of doing stuff,

322
00:21:27,160 --> 00:21:29,640
especially when there is an emerging technology.

323
00:21:30,560 --> 00:21:33,080
Now the question comes, what should they do?

324
00:21:33,080 --> 00:21:39,720
Should they invest 2.5 lakhs, this is the minimum amount a decent patent specification

325
00:21:39,720 --> 00:21:42,880
drafter would charge, right?

326
00:21:42,880 --> 00:21:49,560
Get that and just for the sake of as a competitive advantage, or sorry, should I say as a more

327
00:21:49,560 --> 00:21:55,520
to sell depends, we could just get that patent in India, get it in the US and other, or should

328
00:21:55,520 --> 00:22:01,040
we ignore the patent part of it, focus on the building product?

329
00:22:01,040 --> 00:22:06,280
So I would say that if a startup is in a very nascent phase, and whatever the technology

330
00:22:06,280 --> 00:22:10,840
they have come up with is not so revolutionary, I believe that keep on working on it rather

331
00:22:10,840 --> 00:22:13,280
investing their time on patent.

332
00:22:13,280 --> 00:22:17,040
The best way is if they have something which is like revolutionary, nobody has thought

333
00:22:17,040 --> 00:22:20,960
of it before, then of course you should go for a patent.

334
00:22:20,960 --> 00:22:24,000
Otherwise you would have no point of going for the patent, right?

335
00:22:24,000 --> 00:22:29,040
So let's say I develop something and somebody develop the same thing, now question comes

336
00:22:29,040 --> 00:22:33,280
whether I'll go for a patent infringement there or not, right?

337
00:22:33,280 --> 00:22:38,820
If they develop more or less the same thing, do my purse allow me to go for a patent infringement?

338
00:22:38,820 --> 00:22:42,800
So all of these things do come in picture, whether to go for a patent or not, I would

339
00:22:42,800 --> 00:22:48,040
say it's best suited on the either the purse or there, I mean how much money they have

340
00:22:48,040 --> 00:22:53,400
in their bank account plus the nature of technology they want to protect, like if it is something

341
00:22:53,400 --> 00:22:58,800
which is very unique, then of course they should go for, I mean it's all up to the

342
00:22:58,800 --> 00:23:01,520
money they have in their bank account.

343
00:23:01,520 --> 00:23:05,840
People often file patents just for the to file case against other people.

344
00:23:05,840 --> 00:23:13,720
So by these people called patent trolls, that they will have a company who is not doing

345
00:23:13,720 --> 00:23:22,680
any business, just hold on to a lot of patents and just go and filing cases against them.

346
00:23:22,680 --> 00:23:29,080
And because litigation and IP litigation is quite and specifically IP litigation is quite

347
00:23:29,080 --> 00:23:34,400
expensive in the US, what lawyers what they what end up happening that majority of the

348
00:23:34,400 --> 00:23:36,080
cases are settled.

349
00:23:36,080 --> 00:23:41,080
Yeah, so that is what is the case I've seen even in the open source as well.

350
00:23:41,080 --> 00:23:47,560
So there are a lot of companies who had to settle their cases outside the court and paying

351
00:23:47,560 --> 00:23:51,480
a hefty sum of money for something which is very, very small.

352
00:23:51,520 --> 00:23:55,760
I mean, they're not supposed to pay that much, they could have done it in the initial phase,

353
00:23:55,760 --> 00:23:59,280
but because of lack of information, they have not.

354
00:23:59,280 --> 00:24:04,480
So for patents, I believe, as I said earlier, if you're post support, then of course go

355
00:24:04,480 --> 00:24:06,080
for a patent.

356
00:24:06,080 --> 00:24:11,000
If your technology is very unique and have a distra could have a disruptive effect on

357
00:24:11,000 --> 00:24:13,240
the market, then of course go for a patent.

358
00:24:13,240 --> 00:24:18,280
But if it is something which is like, in general, like general in nature, then I would say there

359
00:24:18,320 --> 00:24:22,440
is no point of wasting your money when getting the patent because you're not anyways going

360
00:24:22,440 --> 00:24:27,920
for the patent infringement or anything else because litigation in India is still a very

361
00:24:27,920 --> 00:24:29,560
expensive and a tough job.

362
00:24:29,560 --> 00:24:31,200
But for all reasons, right.

363
00:24:31,200 --> 00:24:35,120
And see, that's what that's exactly was experience of one of my friends.

364
00:24:35,120 --> 00:24:40,240
And she was sued by a company which is offering an open source solution.

365
00:24:40,240 --> 00:24:44,080
Right. So that's a misnomer that people don't believe that, you know.

366
00:24:44,120 --> 00:24:49,000
And that's why in the in the last podcast, I was like, you know, trying to tell you as

367
00:24:49,000 --> 00:24:53,040
to how, like, you know, young startups can make sure that, you know, they're not infringing

368
00:24:53,040 --> 00:24:55,560
the open source licenses for the.

369
00:24:57,400 --> 00:25:01,960
So if you like end up in a problem and like they are asking for an FTA money, try to get

370
00:25:01,960 --> 00:25:06,280
in touch with us. We will probably try to help you as much as we can.

371
00:25:06,560 --> 00:25:07,560
Yeah.

372
00:25:07,720 --> 00:25:13,320
Our listeners that now they see that's now coming back to your question as to what

373
00:25:14,160 --> 00:25:18,240
you said that they should get a patent if the technology is revolutionary.

374
00:25:18,240 --> 00:25:22,440
Right. At the earliest, it's hard to guess that.

375
00:25:22,440 --> 00:25:23,880
Right. Imagine this, right.

376
00:25:23,880 --> 00:25:29,320
Imagine this. We have to let's let's go back 20 years or 20, 25 years back in time.

377
00:25:29,320 --> 00:25:35,800
Right. Now, the imagine the founders of Google is sitting in front of you and they're

378
00:25:35,800 --> 00:25:41,240
asking. Now, what we have done is that getting inspiration

379
00:25:41,240 --> 00:25:47,400
from academic papers, where it is a very good indicator of the fact that how credible

380
00:25:47,560 --> 00:25:50,480
a scientific paper is taking inspiration from that.

381
00:25:50,760 --> 00:25:54,920
We have tried to implement that this concept in the web itself.

382
00:25:55,200 --> 00:26:00,600
So now we are going to categorize or rank a web page based upon the fact how many

383
00:26:00,600 --> 00:26:03,560
backlinks and what is the quality of those backlinks is coming.

384
00:26:03,600 --> 00:26:06,320
Right. Now, they come to you.

385
00:26:06,320 --> 00:26:08,560
Right. And what would you say to them?

386
00:26:09,560 --> 00:26:14,440
I mean, Google didn't go for a patent for it anyways, and still they're doing absolutely

387
00:26:14,440 --> 00:26:19,680
fine. That's luckily true.

388
00:26:19,680 --> 00:26:21,560
But, yeah, there is no necessity.

389
00:26:21,560 --> 00:26:27,760
Right. Right now, the thing is, when Google was trying to do, IBM wasn't trying to

390
00:26:28,040 --> 00:26:29,640
enter into the search engine market.

391
00:26:29,640 --> 00:26:34,440
Right. Yeah. What is happening is that because a lot of people, in respect of generative

392
00:26:34,520 --> 00:26:38,920
AI is coming to me and saying that, you know, this is the thing we should we get a patent

393
00:26:38,920 --> 00:26:44,080
or not. But the problem right now is all the existing incumbents, whether it's Google,

394
00:26:44,080 --> 00:26:50,000
whether it's Microsoft, it's Apple, all of them are trying to enter into the even NVIDIA.

395
00:26:50,120 --> 00:26:53,440
Right. So now, like I give you a very practical example.

396
00:26:53,440 --> 00:26:58,680
Couple of days back, very good friend of mine came to me and he these guys have come

397
00:26:58,680 --> 00:27:04,400
up with the method or process through which they can substantially reduce the

398
00:27:04,400 --> 00:27:07,880
hallucination problem in the large language models.

399
00:27:07,880 --> 00:27:12,000
Obviously, I would not go into that because then it will become part of prior art and

400
00:27:12,000 --> 00:27:16,320
it will invalidate their patent application if they decide to file.

401
00:27:16,320 --> 00:27:22,400
Right. So people from non-legal background, you have certain idea about the

402
00:27:22,400 --> 00:27:25,280
patents. You can definitely discuss this internally.

403
00:27:25,280 --> 00:27:31,080
You can definitely discuss it with your lawyers or loyal friends, but never put it

404
00:27:31,200 --> 00:27:35,000
whenever publish it, because the moment you publish it, it becomes part of the prior

405
00:27:35,000 --> 00:27:41,960
art. And that is a very and if that happens, it's almost invalidate your own

406
00:27:41,960 --> 00:27:47,040
invention. I mean, yeah, there are anticipation clauses there.

407
00:27:47,040 --> 00:27:49,560
But then, again, unnecessary hassle will be there.

408
00:27:50,400 --> 00:27:52,640
That's against the complication. So don't publish it.

409
00:27:52,880 --> 00:27:54,880
Don't publish it. That's the end line.

410
00:27:54,880 --> 00:28:01,280
Yes, right. So now the thing is now a person like Moom is like, you know, these

411
00:28:01,280 --> 00:28:04,120
guys are doing hard work. They are obviously on a shoestring budget.

412
00:28:04,360 --> 00:28:09,400
They have done a really good job at reducing the hallucination problem, which is a very

413
00:28:09,640 --> 00:28:12,480
fundamental problem of large language models.

414
00:28:13,200 --> 00:28:15,800
So what should I say to those guys?

415
00:28:16,520 --> 00:28:21,920
So if the application which they have developed is actually affecting the means

416
00:28:21,920 --> 00:28:24,840
of reducing the hallucination in a large language model, I believe this is a

417
00:28:24,840 --> 00:28:28,240
revolutionary technology. They should go for a patent for this particular

418
00:28:28,520 --> 00:28:33,960
application. Now, when I say general in nature means, let's say I develop a new

419
00:28:34,160 --> 00:28:37,880
device which use AI to do specific tasks.

420
00:28:38,040 --> 00:28:40,880
Now, this is something which is very general and very specific.

421
00:28:40,880 --> 00:28:43,480
I shall not waste my time to get a patent for this.

422
00:28:44,160 --> 00:28:47,840
Now, the example which we have given is resolving a very technical problem, which

423
00:28:47,840 --> 00:28:51,520
is there and most of the AI model are suffering from it.

424
00:28:51,960 --> 00:28:56,480
Now, this is a revolutionary technology, I believe, and they should go for the patent

425
00:28:56,480 --> 00:29:03,520
for this one. So you need to identify and determine the or rather, I should say, weight

426
00:29:03,800 --> 00:29:09,520
your own invention on one end and the amount of money that you are willing to spend on

427
00:29:09,520 --> 00:29:14,920
the other end. Now, if you find that money is well spent, then yes, go for it.

428
00:29:15,240 --> 00:29:20,880
But if you see it is not and you are running low on the budget, I would say save your

429
00:29:20,880 --> 00:29:22,920
money. That is the best way to go forward.

430
00:29:23,480 --> 00:29:26,000
But this technology, I would say, of course, you should go for it.

431
00:29:27,400 --> 00:29:30,440
See, that was that's exactly was my advice as well.

432
00:29:30,600 --> 00:29:31,960
So that's pretty interesting.

433
00:29:31,960 --> 00:29:35,520
And now we're talking about larger English models, chat, GPT.

434
00:29:36,160 --> 00:29:41,600
What is in your opinion as a ex-ingineer and the current lawyer, what is the best

435
00:29:41,600 --> 00:29:44,440
use case for generative AI in legal profession?

436
00:29:45,400 --> 00:29:52,920
In the legal profession, see, interpretation is a major role that lawyers do, right?

437
00:29:53,240 --> 00:29:58,760
And I don't think so the current AI or the generative AI that we have is sufficient or

438
00:29:58,760 --> 00:30:00,720
capable enough to do the interpretation.

439
00:30:01,160 --> 00:30:06,720
As one of our law professors put it in a very well-mannered statement is that that

440
00:30:06,720 --> 00:30:10,480
these generative AI are nothing but text prediction, right?

441
00:30:10,480 --> 00:30:14,200
So what I have in my mobile is more or less the same thing, but on a larger scale.

442
00:30:14,680 --> 00:30:19,280
The right quote is they're over glorified autocorrect.

443
00:30:19,840 --> 00:30:21,640
Yes, over glorified autocorrect.

444
00:30:21,640 --> 00:30:22,160
Exactly.

445
00:30:22,880 --> 00:30:28,640
So as of now, with the current state of the generative AI, what the assistant they can

446
00:30:28,640 --> 00:30:33,440
do in the legal field is the drafting of the contracts, especially the normal contracts,

447
00:30:33,440 --> 00:30:35,800
for example, rental agreement or the sale deed.

448
00:30:36,280 --> 00:30:39,320
They also can help you in analyzing these agreements.

449
00:30:39,440 --> 00:30:44,880
I mean, if I want to get the summary of an agreement, I can go through, but then again,

450
00:30:44,880 --> 00:30:49,000
I would highly recommend not to rely completely on the summary provided.

451
00:30:49,880 --> 00:30:56,040
So on the drafting part, I would say that yes, generative AI can assist a lot, but still

452
00:30:56,080 --> 00:31:01,880
there are a lot of areas where, especially in the legal domain, AI is still not on the

453
00:31:02,280 --> 00:31:04,120
even the closest pedestal, I believe.

454
00:31:04,720 --> 00:31:10,640
So the reason I believe is when we talk about law and core law in general, it's more about

455
00:31:10,640 --> 00:31:11,440
the interpretation.

456
00:31:11,560 --> 00:31:14,880
If I take an example of a criminal law, let's say somebody stabbed me.

457
00:31:15,320 --> 00:31:18,640
Now here, the question is not that person has stabbed me and that's why I'm a murderer.

458
00:31:18,720 --> 00:31:25,080
The point comes into what pressure, where I put the knife into, whether that knife hitting

459
00:31:25,080 --> 00:31:30,200
the vital parts of my body or not, how much I twisted the knife, right?

460
00:31:30,240 --> 00:31:35,240
So evidence comes into a picture and I believe current state of the AI is not able to handle

461
00:31:35,240 --> 00:31:41,200
all of these things and is not able to predict the answers or determine whether the person

462
00:31:41,200 --> 00:31:44,560
is guilty or not of the crime he is accused of.

463
00:31:45,200 --> 00:31:47,920
So in drafting part, I would say yes, AI can assist.

464
00:31:48,680 --> 00:31:53,840
On the analysis part, of course, AI can assist, but still a lot of work is still lawyers need

465
00:31:53,840 --> 00:31:54,080
to do.

466
00:31:54,840 --> 00:31:55,240
Right.

467
00:31:55,320 --> 00:31:55,880
Absolutely.

468
00:31:56,120 --> 00:32:00,880
So this is like in a sense, you're saying the interpretation is a use case where I feel

469
00:32:00,880 --> 00:32:03,520
that AI is really lagging and there's a lot of yes.

470
00:32:05,040 --> 00:32:08,920
That's completely, completely, I completely concur with you on that topic.

471
00:32:09,600 --> 00:32:09,880
Right.

472
00:32:09,920 --> 00:32:14,080
But in addition to these general use cases, like contract drafting, contract analysis or

473
00:32:14,080 --> 00:32:19,280
contract review, do you have anything specific to the kind of problems that you are facing,

474
00:32:19,280 --> 00:32:19,600
right?

475
00:32:19,600 --> 00:32:25,720
Very specific to professors who are doing your kind of work, where you feel generally

476
00:32:25,800 --> 00:32:27,280
I can make a huge difference.

477
00:32:28,040 --> 00:32:32,400
I mean, I would, I won't say that I'm working into this particular area, but yes, there

478
00:32:32,400 --> 00:32:36,560
are a lot of people who are doing the drafting part of the agreement or the analysis part

479
00:32:36,560 --> 00:32:37,240
of the agreement.

480
00:32:37,480 --> 00:32:38,680
I'm also over there.

481
00:32:40,040 --> 00:32:40,440
Yeah.

482
00:32:40,800 --> 00:32:43,280
So for them, it's really helpful.

483
00:32:43,960 --> 00:32:49,800
Just for the fun sake, I try to create a question answering model to see whether they are

484
00:32:49,800 --> 00:32:54,440
functioning, they are sufficient, whether they will assist me or not, although it's

485
00:32:54,440 --> 00:32:55,640
not my part of job.

486
00:32:56,440 --> 00:33:00,920
So I was able to determine exactly what are the rights and liabilities of the obligation,

487
00:33:00,920 --> 00:33:08,040
at least where it is stated, or classify the entire license agreement into the pre-informed

488
00:33:08,800 --> 00:33:09,320
clauses.

489
00:33:09,720 --> 00:33:12,800
So yes, on that particular part, of course, the AI can help you.

490
00:33:14,320 --> 00:33:18,600
But then I would say a second reading is still required because there are a lot of things

491
00:33:18,600 --> 00:33:22,040
which even in my model that AI left.

492
00:33:22,720 --> 00:33:27,880
So if I asked on the right, there are certain things it provided, then certain things I

493
00:33:27,880 --> 00:33:30,600
still have to go through the entire license agreement and then look into.

494
00:33:32,240 --> 00:33:34,440
Have you used any AI for legal research?

495
00:33:35,200 --> 00:33:37,720
No, no, I don't rely on AI for legal research.

496
00:33:37,720 --> 00:33:44,000
I go for both on ICSRN, look for a legal research and then start reading into it.

497
00:33:44,480 --> 00:33:45,000
That's true.

498
00:33:45,000 --> 00:33:50,360
But just to remember that the lawyers before your generation used to say the thing about

499
00:33:50,360 --> 00:33:51,320
Google, right?

500
00:33:52,080 --> 00:33:53,680
Yeah, I remember that.

501
00:33:53,960 --> 00:33:57,760
Yeah, I still believe that books are a better way to go forward.

502
00:33:57,760 --> 00:34:01,560
I have a lot of legal books which are kept outside.

503
00:34:05,920 --> 00:34:07,880
Even if I have to, sorry to cut you a bit.

504
00:34:08,360 --> 00:34:10,760
No, no, books, I completely agree.

505
00:34:10,760 --> 00:34:19,000
But imagine today, I have this question, whether having an indemnity clause with 3x

506
00:34:19,000 --> 00:34:24,840
liability or something of that sort, where would I go and do the research on this?

507
00:34:24,840 --> 00:34:29,760
If I would have to go to the old school and do the research just by using books, how would

508
00:34:29,760 --> 00:34:30,280
I go about that?

509
00:34:31,520 --> 00:34:33,640
Mean drafting an indemnity clause or?

510
00:34:34,800 --> 00:34:36,840
Legal research using just using books.

511
00:34:37,280 --> 00:34:42,560
And I have a legal question, whether this indemnity clause is valid or not.

512
00:34:43,040 --> 00:34:44,000
How would I go about it?

513
00:34:45,000 --> 00:34:49,600
I think for contracts, specifically, there are a lot of good commentaries available.

514
00:34:49,880 --> 00:34:58,880
I believe, I think, OLA or OLA, OLA in OLA, I believe, not OLA, there's some books from

515
00:34:58,880 --> 00:35:06,160
Nexus, Lexis Nexus is there, which has a huge commentary on contract law.

516
00:35:06,560 --> 00:35:09,840
And those commentaries are given on the section specific.

517
00:35:09,880 --> 00:35:12,400
So you go and find the indemnity section.

518
00:35:13,320 --> 00:35:15,200
What is the section number for the indemnity?

519
00:35:15,760 --> 00:35:20,680
Open that book, go to that particular section and go to the entire case laws, whatever is

520
00:35:20,680 --> 00:35:20,920
there.

521
00:35:21,360 --> 00:35:29,920
And I believe if you read five, six, seven research paper, after seventh, you develop

522
00:35:29,920 --> 00:35:36,080
this ability to read few lines and determine whether this particular paper will be helpful

523
00:35:36,080 --> 00:35:36,880
to you or not.

524
00:35:37,760 --> 00:35:43,760
So once you do that research, you will be able to develop this this capacity that after

525
00:35:43,760 --> 00:35:46,960
reading few lines, you will determine, OK, this is not useful for me.

526
00:35:46,960 --> 00:35:47,760
I can move forward.

527
00:35:48,800 --> 00:35:50,800
So, yeah, that's what it is.

528
00:35:51,040 --> 00:35:54,440
And I still believe that is the best way to go forward.

529
00:35:55,720 --> 00:35:56,280
Makes sense.

530
00:35:57,000 --> 00:36:00,080
So, Chetan, thanks a lot for coming on the podcast today.

531
00:36:00,440 --> 00:36:04,440
Are you interested to have your theory or insights?

532
00:36:04,960 --> 00:36:05,400
Yep, sure.

533
00:36:05,520 --> 00:36:06,040
No issues.

534
00:36:06,600 --> 00:36:07,040
Thank you.

535
00:36:08,200 --> 00:36:11,080
That wraps up our enriching discussion with Chetan.

536
00:36:12,080 --> 00:36:17,880
From navigating the complexities of open source software compliance to sharing his personal

537
00:36:17,880 --> 00:36:23,160
journey and hardships, Chetan's insights have been nothing short of enlightening.

538
00:36:23,600 --> 00:36:28,920
If you found this episode valuable, don't forget to subscribe and share it within your

539
00:36:28,920 --> 00:36:29,320
network.

540
00:36:29,880 --> 00:36:34,040
Thanks again to our listeners for joining us on LexDiscuss Cafe.

541
00:36:34,360 --> 00:36:40,200
And a special thanks to Chetan for his time, expertise and sharing his side of story.

542
00:36:40,520 --> 00:36:43,040
This is your host, Avinash Tepati, signing off.

543
00:36:43,280 --> 00:36:46,320
Until next time, stay curious, stay caffeinated.

 

Shares:
Show Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *