Centre for Internet and Society

CIS RTI REQUEST TO DIPP - NUMBER 2 - FEBRUARY, 2015

nehaa — 2015-04-14T17:22:37Z

For more details visit https://cis-india.org/a2k/blogs/cis-rti-request-to-dipp-number-2-february-2015

CIS RTI REQUEST TO DIPP - NUMBER 1 - FEBRUARY, 2015

nehaa — 2015-04-14T17:17:53Z

For more details visit https://cis-india.org/a2k/blogs/cis-rti-request-to-dipp-number-1-february-2015

Patterns of Gender Aggression and Harassment in Open Tech and Open Culture Communities Online

rohini — 2015-06-01T02:13:14Z

Report on the talk delivered by me at Adacamp held in Montreal, Canada on April 13-14, 2015.

Link to the original blog post published on Wikimedia blog can be accessed here.

I received a grant from the Wikimedia Foundation to participate in Adacamp. While the talk was pegged on my experience of working on Wikipedia's Gender gap in India, the content is equally relevant for other, open online projects, especially those that value the anonymity of its users. The talk ended with a discussion on how to identify and combat these patterns. It was a collaborative talk delivered along with Gretchen McCulloch who spoke on Wikipedia's Gender gap and Fandom. Credits to session rapporteur and participant Maja Frydrychowicz.

Gender disparity among Wikipedia's editors is well-known and well-documented.[1] [2] A survey conducted by the Wikimedia Foundation in 2011 pegged the number of female contributors to the English-language Wikipedia at 9%.[3] Several outreach, advocacy, and capacity-building efforts have been made to bridge Wikipedia's glaring gender imbalance. In the openness domain, other projects and initiatives have been making similar efforts to bring more women into the fold. To cite an example, the Outreach Program for Women endeavours to recruit more female coders in the world of open source software.

While the narrative of few women being online has changed, more in some parts of the world than in others, the next barriers of making them stay online and establishing an active presence, remain. Wikipedia, like many other open communities, has a high drop-out rate of female contributors. Many female contributors maintain identities that do not give away their gender or practise self-censorship in order to continue to be a part of the community. Several studies conducted in the past few years have attributed the gender gap to numerous reasons -- women have less time left after fulfilling their tasks at home and work; antagonistic exchanges are emotionally draining; in households where there is only one Internet-enabled device, women have access to it for a shorter time; and so on. A blog post by Sue Gardner former executive director of the Wikimedia Foundation, pithily lays out why women don't edit Wikipedia.

One of the ways that outreach and advocacy can work towards retaining more contributors and enabling them to participate more fruitfully is by identifying patterns of aggression and harassment that are directed, subtly or otherwise, at them owing to their gender or sexual orientation.

What are some of the significant patterns that cause a contributor to censor themselves or leave, even if they have just joined?

Hostile environment, antagonistic exchanges: These word clouds[4][5] display name-calling experienced by female users on Wikipedia. Wikipedia's editorial model stands on building consensus and collaboration but the spirit of debate often gives way to slings and arrows, many of which would violate Wikipedia's policy of being civil to other contributors (WP:Civil) and one of the five pillars of the crowdsourced encyclopedia. Facing hostility can be emotionally draining, especially for a new contributor, and reason enough for them to avoid contributing to certain topics, to censor themselves, or to leave the platform. Verbal violence and use of language considered unacceptable as per the community rules, is one form of harassment/ violence that is relatively easy to spot and call out, and is not uncommon.
Mansplaining: is more insidious than outright hostile behaviour. The intent is not constructive criticism but to humiliate the recipient, make them feel that do not belong in the space, or drive them underground. It involves the use of what Wikipedia terms "weasel words", and dismissive and condescending speech. It is difficult to address because it is less perceptible, difficult to differentiate from advise or feedback given in good faith (WP: AssumeGoodFaith), and does not violate the guideline of not attacking newbies but explaining the matter to them (WP:DontBiteTheNewbies).
Deletionism: is the practice of reverting edits or deleting/ nominating for deletion entire pages, projects, or other content out of relatively strict adherence to policies. Deletionism is often difficult to tell apart from very strict adherence to standards. Policies are open to interpretation, and deletionists justify their position by applying certain policies and contexts that favour their stance. In the context of issues pertaining to gender or sexuality, a pattern to look out for is the same user, IP address, or an apparent sockpuppet reverting edits, making edits, and defending them in a way that makes the article less gender-sensitive and disproportionately skewed away or towards a certain gender or orientation.
Subtle Powerplay/ Microaggressions: find their way into discussion boards, mailing lists and other areas of debate and discussion. A study done by the Internet Democracy Project in India documents some of the remarks that leave women feeling they are unwelcome, that do not belong in the space, or that they are an 'imposter'. "People will not be outright abusive towards you, which is a lot I face in my job. When someone does not want you to be a part of their community, they will not abuse you because they get banned for it. They will goad and nudge you in ways to tell and make sure that you are not welcome. So they will ask you, 'Oh, so when did you learn JavaScript?' knowing that you don’t know JavaScript. Just to make you feel that only those who have learnt JavaScript have the right to be there [in the forum].”

One of the factors that inadvertently aids some of these patterns is the kind of sources that are considered reliable on Wikipedia (WP:RS). Newspapers, magazines, websites, books, and journals are considered acceptable references. These sources tend to reflect existing gender biases and structures of power. Studies conducted on the content published by newspapers, for example, have shown that news coverage about men is much higher than that about women.

As most of the attendees of the talk were not very well-acquainted with the intricacies of Wikipedia's Gender gap, I went on to explain some topics that were not explicitly related to the subject of the talk.

Initiatives to improve diversity and encourage new contributors on Wikipedia

Beginner-friendly groups such as The Tea House and the Welcoming Committee
Special Interest Groups (SIGs)
The Gender gap project
Edit-a-thons geared towards increasing gender-sensitive content on Wikipedia and correcting content with gender bias
Wikipedia tries to foster positive feedback through barnstars, Wikilove, and marking a good edit with a “thank you” or a heart icon.

How existing editors can work towards increasing diversity and encouraging new editors

Help get more women mentioned in references or citations in Wikipedia articles.
Add information about women in biographies (e.g. add the mother's name or female spouse's name in a biography article.)
One of the traits of communities that do have many women on them is that a lot of positive interaction happens in response to contributions.
Teachers can obtain support for getting students to edit Wikipedia as part of a class project.

Strategies to recruit more women editors (individuals who self-identify as women, transwomen, genderqueer, genderfluid)

Aim outreach efforts towards women who blog, or already have a presence online.
Persuade existing editors to encourage women in their family and social groups to start contributing. In the case of existing male editors, it works as the two-pronged strategy of sensitising men while empowering women.
Organise outreach events where the organisers and participants are all women/ individuals who largely self-identify as women.
Organise outreach events with gender-sensitive male editors.

Questions-Answers

What is needed to meet Wikipedia's notability criterion?

A: There are different requirements depending on the subject of the article: a book, a work of art, a public figure, an artist, a writer, and so on. There are stricter requirements for biography articles, especially those of living people. Being famous does not necessarily mean being notable in the Wikipedia context. Notability requirements end up being gendered; Wikipedia replicates the biases that are present in the offline world due to its reference structure (WP:RS)

There were several general questions from the attendees about editing Wikipedia, and about Wikipedia policies and best practices. These were answered by McCulloch and me in the last 15 to 20 minutes of the talk.

References

[1]. Define Gender Gap? Look Up Wikipedia's Contributor List, Naom Cohen, January 30, 2011.

[2]. WP:Clubhouse? An Exploration of Wikipedia's Gender Imbalance, Shyong (Tony) K. Lam, Anuradha Uduwage, Zhenhua Dong, Shilad Sen, David R.Musicant, Loren Terveen, John Riedl, 2011

[3]. Women and Wikimedia survey, 2011

[4]. Research: Communicating on Wikipedia while female

[5]. Women and Wikimedia survey, 2011, Name-calling on English Wikipedia

[6]. Women and Online Abuse, Internet Democracy Project, 2013

For more details visit https://cis-india.org/openness/blog-old/patterns-of-gender-aggression-and-harassment-in-open-tech-and-open-culture-communities-online

One reason startups are moving out of India

praskrishna — 2015-05-08T01:46:01Z

Prime Minister Narendra Modi says Make in India. But anyone who wants to, finds that their intellectual property is valued much more if the patent is filed in the US, or anywhere else, but India.

The article by Evelyn Fok and Varun Aggarwal was published in the Times of India on April 10, 2015. Sunil Abraham gave his inputs.

Take the case of BITS Pilani graduate Sriram Kanuni, for instance, who decided to come back to India after spending 12 years with SAP in Germany. His family thought he was out of his mind, but he wanted to work for India and primarily serve Indian clients.

His core vision hasn't wavered five years down the line, but he has been forced to move a large part of his company's intellectual property (IP) to the US, just to get a better valuation for his next round of funding. And his is not an isolated case.

"Global investors seem to value companies with patents in the US much higher. Therefore, it makes more sense to shift patents out of India, in case you're looking to raise money or exit the company," Kanuni, who is the CEO and co-founder of Arteria Technologies, said.

Major Indian startups such as Flipkart, Myntra and ZipDial, which have either raised over a billion dollars or exited, already have their IPs outside the country. Experts say that is one of the reasons that attracted investors.

"If a company with its IP in India is acquired by an international firm, and post acquisition the buyer wishes to transfer the IP to a different jurisdiction, such transfer would need to be at a fair value decided by the government and the company is taxed at the rate of 34% on that," one of the bankers who was part of a large exit told ET.

"For tech-centric companies where the value of IP would comprise over 70-80% of their value, such high taxes can possibly make them unattractive for potential investors," they added.

With better valuation and exits in mind, startups are moving out their innovation to countries such as Singapore and the US, leaving behind very little intellectual property that the country can proudly call its own.

"You would want to incorporate somewhere with a respected reputation for maintaining legal protection when it comes to copyright and trademarks, especially with global licensees or partners," said Sharad Devarajan, co-founder and CEO of character entertainment company Graphic India, which is incorporated in Singapore.

"Incorporation in a country like the US where potential for M&A is higher, especially for core technology startups, will generally make it more attractive to potential buyers as it avoids a lot of legal and financial paperwork," said Brij Bhasin, India investment lead of Japanese venture capital firm Rebright Partners.

Investor concerns over IP are well founded. "Indian courts aren't uniform when it comes to developing jurisprudence around copyright and patent infringement," explained Sunil Abraham, executive director of Bengaluru-based research organization Centre for Internet and Society.

"There is a high chance that a judge who doesn't understand the details would give an injunction. Then the loss of six months, etc, can be quite expensive, because in six months' time your competitor might eat into all of your market," he said.

For more details visit https://cis-india.org/a2k/news/the-times-of-india-april-10-2015-evelyn-fok-and-varun-aggarwal-one-reason-startups-are-moving-out-of-india

Odia waits for Google Translate debut - Nine Indian languages available

praskrishna — 2015-05-08T01:27:21Z

Odia getting the "classical" status last year was certainly a proud moment for the people of the state, but, it is yet to feature among the languages available in Google's popular translation service.

The article by Anwesha Ambaly was published in the Telegraph on April 6, 2015. Subhashish Panigrahi was quoted.

Over 90 languages, including nine from India (Bengali, Gujarati, Hindi, Kannada, Marathi, Malayalam, Punjabi, Tamil, and Telugu) are part of the service.

Odia, which is spoken by over 45 million people globally, is yet to debut here.

Techies working in the field attribute the reason to the lack of web presence of the language.

"Google has set parameters on the basis of which translations are available. Only those languages that have a wide use on the Internet and have enough online content are included in the list. The online presence of Odia is quite insignificant," said Subhashish Panigrahi, programme officer at Centre for Internet and Society and a regular contributor to Odia Wikipedia.

Among the limited data in Odia available online, Odia Wikipedia and Odia Wikisource have emerged as important reference sources for all kinds of information.

The Odia Wikipedia serves as an online encyclopaedia that was initiated in 2002 and hosts over 8,000 articles in Odia. The Odia Wikisource was launched in the state last year and is run by volunteers and communities. It is a sister concern of Odia Wikipedia that makes rare Odia books available on the Internet.

However, a Google spokesperson said: "We value all Indic languages and search and Gmail are available in 16 Indian languages with more languages to follow"

Recently, the entire Odia Bhagbata by Jagannath Das was made available on Wikisource. Also, Bhubaneswar-based organisation Srujanika, in collaboration with NIT, Rourkela, has digitized over 750 books. But these apart, there are no major online portals available in Odia.

Panigrahi and his contributor friends are presently working at promoting the Google Translate community, which is a platform for language enthusiasts and volunteers interested in improving translation quality for their language or help Google add it to translate.

"To ensure more availability of online content, people should be encouraged to share information on the web. More Odia content on the web will get a wider reach," said the techie.

"We are quite hopeful that the translator would be available in Odia soon."

The universal web-compatible Unicode font for Odia language was developed in 2000. Despite the Unicode standard having been made available over a decade ago, Odia language is not used actively on the Internet.

"We are still stuck to using outdated fonts such as Akruti and Sreelipi for typing text in Odia and most of these are not compatible for using on the Internet. There are thousands of book and articles available in these fonts. Most of the important content available on the government portals also uses the older fonts. Unless content is available in Unicode, it will not be searchable, sharable and reusable on the Internet," said Panigrahi.

One of the earliest websites in Odia was developed by Ganesh Mishra in 1999 for a popular Odia daily. But the website was shut down after six years when the concept of e-paper came into being.

"These days, most of the publishers of Odia newspapers and magazines have come up with e-papers which are nothing but the scanned images of the original pages. But an online search won't display them as results. Online content in Unicode is accessible through search engines," said the website developer.

He said that people have so many alternatives on the Internet that the absence of Odia language is not felt. "Customers often initiate commercial websites in Odia but soon request us to change it to English because it was inconvenient for users," said Mishra.

Some youngsters in the state are coming up with online portals to promote Odia literature. Jyoti Prasad Patnaik, a doctor by profession, has been running an online Odia literary magazine since 2006.

"The Internet is the most powerful medium of communication these days and there could be no better way to popularise our language other than this. When I started out, there were hardly any readers. Today my website has around 5,000 visitors every month. The number is growing slowly and I hope it will increase in the future," said Patnaik.

For more details visit https://cis-india.org/openness/news/the-telepgrah-april-6-2015-anwesha-ambaly-odia-waits-for-google-translate-debut-nine-indian-languages-available

Conference on Standards Settings Organizations (SSO) and FRAND, NLSIU

rohini — 2016-04-02T18:12:41Z

Rohini Lakshané attended the Conference on Standards Settings Organizations (SSO) and FRAND held at NLSIU, Bengaluru on March 21 and 22, 2015. It was organised by the MHRD Chair on Intellectual Property Rights, Centre for Intellectual Property Rights and Advocacy (CIPRA), National Law School of India University, Bengaluru in association with Intel Technology India. This post is a compilation of notes from the conference.

Programme Schedule

Significant Takeaways
It is anti-competitive to seek to exclude competitors from the market by seeking injunctions on the basis of SEPs, if the licensee is willing to take a license on FRAND terms. In these circumstances, the seeking of injunctions can distort licensing negotiations and lead to unfair licensing terms, with a negative impact on consumer choice and prices. -- EU Competition Policy Brief, Issue 8, June 2014. This is a very important issue for India as it thinks about how it can attract foreign investments. India has a unique opportunity to learn from these lessons from around the globe and craft India-specific solutions. India has the intellectual capability and the institutions capable of crafting these solutions, and in doing that we can support Make In India. India needs to be mindful about what is happening in the [South Asian] region. China has moved aggressively to try to curb FRAND abuse. The People's Court in China ruled in Huawei vs. InterDigital that for 2G, 3G, and 4G patents, the license fees of royalties should not exceed 0.019% of the actual sale price. Apple also stated that Ericsson was calculating royalties on the sale price of the iPhone or iPad, whereas the royalty should be calculated on the value of the baseband chip that runs this technology in the mobile device. If such litigation occurs in India, what would be India's position? If a building block contains the technology pertaining to a patent, then royalty should be calculated on the smallest possible patent practising unit and not the entire product. The government of India has adopted a royalty free (RF) approach to licensing open standards. Non-essential claims are excluded from disclosure. Pending patent applications are not. Only 16% patents declared as SEPs are actually SEPs, according to a study. The Delhi High Court has passed interim orders restraining the CCI from deciding these cases. Our appeal to the courts is that these patent infringement lawsuits should not be viewed in isolation. They should not be viewed as merely contractual issues between the licensor and the licensee. They should be seen in the context of their economic effects and their adverse effect on competition. The CCI should be enabled to deal with such cases. Matheson: The phrase "compulsory license" sends a shiver down every corporate's spine every time it is used. International experience is that the judicial system has been the only forum where we have been able to have due process to enable us to construct cases properly in order to explain to the judge or to the jurors how the system works. That has produced very sensible solutions to this problem. Handing it off to the government to institute a compulsory license wouldn't be fair to the SEP holders.

SSOs and FRAND: Licensing issues

John Matheson, Director of Legal Policy (Asia Pacific), Intel

The role of licensing policy

Ensuring market access
Standards often depend on patented technology, which is accessed through the Promise to License on FRAND terms.
It is equally critical to ensure that standards can be implemented without unfair legal games.
It is essential to prevent patent hold-up.
Reasonable compensation

Patent holders remain entitled to fair compensation and benefit from the proliferation of their technologies via standardisation.

Why FRAND?

A FRAND commitment embodies certain fundamental principles that have been recognised widely by the courts and regulators.

The fundamental purpose of a FRAND commitment is widespread adoption of the standard.

Because of the peculiar nature of SEPs, the process is open to abuse.

A FRAND commitment is aimed at preventing patent holders from exploiting a hold-up value and extracting unreasonable royalties and concessions that could otherwise follow from being in a very unique position. Often, the holders of the IP have a single solution to an interoperability or connectivity conundrum that technology is facing.

Why are SEP license negotiations different from Non-SEP ones?

In the context of non-SEPs, one may be negotiating to obtain a license to a patent for a particular feature. If the licensor is being difficult, one can discard the feature to include something else. In a competitive market, this negotiation is focused on the value of the invention to be licensed. Thus one can redesign to avoid a particular claim and, in turn, avoid injunction.

On the other hand, it is necessary to either obtain a license for or infringe an SEP to manufacture the mobile device. There is no workable alternative or workaround to obtaining a license for the desired technology. With the threat of an injunction looming over the negotiations, the prospective licensee is under pressure to obtain a license. So the market negotiations for SEPs and non-SEPs are very different. One-way negotiations raise the possibility of a patent hold-up, and abuse of the standard implementer.

IP policies inevitably involve compromise.

Common areas of misunderstanding include:

Valuations or meaning of "reasonable". Valuations of IP under consideration.
Injunctive relief or exclusion orders
Discrimination or refusal to license
Patent transfer (It requires a continuation of the FRAND commitment, and shouldn't get differential treatment in the IP policy.)

Competition authorities in the US and EU have asked SSOs to reconsider policies to reduce ambiguity in the context of these areas of misunderstanding.

The ex-ante or the incremental value of the SEPs before the standard is set needs to be understood. The SSOs look at several different ways to solve a connectivity problem. The patent owners bring their patents into the standards body and claim that theirs is the best way to solve that problem. The market and consumers want an uncomplicated solution which works and is as cheap as possible. In many cases, there is one single winner, simply because we need one solution. In exchange for being the winner, the FRAND discipline is quid pro quo.

European Commission's response to two different patent lawsuits:

In the Samsung and Motorola cases, the Commission clarifies that in the standardisation context where the SEP holders have committed to:

License their SEPs
Do so on FRAND terms

It is anti-competitive to seek to exclude competitors from the market by seeking injunctions on the basis of SEPs, if the licensee is willing to take a license on FRAND terms.

In other words, if there is a bona fide commitment on the part of the licensee to agree to that test, then it is anti-competitive to seek an injunction.

In these circumstances, the seeking of injunctions can distort licensing negotiations and lead to unfair licensing terms, with a negative impact on consumer choice and prices. -- EU Competition Policy Brief, Issue 8, June 2014.

Anyone who needs access to connectivity or needs interoperability requires to get a SEP license, and if that license is required to be obtained within a time limit, it almost -- by definition -- is not going to work. Patent licenses take years to negotiate, and they're incredibly complex. For example, a patent policy may offer up to 12 months to agree on a license, but that is not the way the market works. So we cannot expect policies that put forth time limits to work in the SEP arena. What we can expect is that the implementers make a bona fide commitment to seek a license.

Motorola vs. Microsoft, Germany:

Motorola sought injunctive relief against Microsoft in Germany. Microsoft moved its distribution centre from Germany to the Netherlands. This resulted in loss of jobs, relocation costs ($11.6 million), and annual increased operating costs of $5 million for Microsoft.

Samsung vs. Apple, Germany

Similarly, on the basis of one patent, a temporary injunction was granted on the sale of the Apple iPad and iPhone. Apple was forced to agree to terms it didn't want to agree to, so that the sale of its products would resume.

This is a very important issue for India as it thinks about how it can attract foreign investments. India has a unique opportunity to learn from these lessons from around the globe and craft India-specific solutions. India has the intellectual capability and the institutions capable of crafting these solutions, and in doing that we can support Make In India.

SEP holders that make FRAND commitments should not be allowed to obtain injunctions against alleged infringers, except in limited circumstances. This formula has been adopted by the IEEE, which has solved this problem. India has the opportunity to leapfrog a lot of patent litigation by adopting the IEEE test.

Learn from what happened with Microsoft in Germany. What kind of message do you want to send to the foreign community about investing in India? Do you want to use the scare tactics of injunctions or do you want to adopt a policy that will avoid litigation?

India needs to be mindful about what is happening in the [South Asian] region. China has moved aggressively to try to curb FRAND abuse. The People's Court in China ruled in Huawei vs. InterDigital that for 2G, 3G, and 4G patents, the license fees of royalties should not exceed 0.019% of the actual sale price.

Reasonable Compensation Considerations

Royalty based on the smallest unit that practices the standard.
Technical value of patented technologies vs. alternatives.
Overall royalty that could reasonably charged for all SEPs.

Non-discrimination

A commitment to license every implementer of the relevant standard.

Transfer

FRAND commitments follow the transfer of a patent to subsequent proprietors.

Dr. Krishna Sirohi, Impact Innovator, GISFI, President, I2TB

As per the Make in India programme, we have to achieve zero imports by 2020. Product development in India by Indian companies will happen with collaborative research and development and IPR sharing through licenses. We are looking at national capacity building through product development and patent uses.

Global Information and Communication Technology Forum for India (GISFI) is a standards setting body involved with standardisation and research. It is a telecommunications standards development body (TSDO) set up with the approval of the DoT. It has peer relationships with ITU, OMA, TTC and a bunch of other SDOs. Internet of Things (IoT), mobility and security are its three major research programmes.

GISFI is working towards defining 5G in India. The 5G standardisation theme in India is called WISDOM (Wireless Innovative System for Dynamic Operating Mega Communications). GISFI is considering the perspective of the Indian user, the network capability, the network architecture, network development and the Indian revenue model, strategic and special purpose networks, inclusive growth, and network security.

However, some India-specific aspects such as illiteracy and lack of basic civic infrastructure need to be considered in the standardisation process.

GISFI plans and stages for 5G definition and adoption

Stage 1 (2014-2018): National agenda for strategic research, innovation and experimentation

Focus on Digital India and Make in India programmes.

Stage 2 (2016-2019): Standardisation

Stage 3 (2017-2021): Product Development

Stage 4 (2019-2023): Early Development

Technical understanding required for IPR issues

Enhancement applicable to general scenarios
- Traffic capacity
- Cell coverage
- Edge cell performance
- Intercell interference
- Network congestion
- Mobility
- Energy consumption
Enhancements targeting new use cases
- machine-type communication
- national security
- public safety services
Carrier aggregation
- Higher throughput owing to intra and inter-band transmission bandwidth of more than 20 MHz.
- Reduced network congestion owing to load-balancing across multiple carriers.
- Improvement in mobility and reduction in inter-cell interference.
Enhanced MIMO
- Improved spatial diversity and multiplexing
- Improved beam-forming
- Multiple access with multi-antenna transmission
Coordinated Multi-Point Operation (CoMP)
- Reduction in intercell interference owing to coordinated scheduling or beamforming (CS/CB)
- Transmission from multiple distribution points (base stations, RRH) in a coordinated way (Dynamic point selection, and Joint transmission)

What do SSOs handle IPR in different parts of the world and what are the issues they face?

GISFI has adopted ITU's IPR policy.

In SSOs, the FRAND principle works well only when participating entities have equal or almost equal IPR clout, and can reciprocate with their own patents every time other entities share their patents. It is difficult to create a balance between entities that only own IPR and those that only consume IPR.

Most of the members of SSOs are IPR owners. The entities that develop [technological] solutions without owning the IPRs are usually not a part of SSOs. However, additional strategies need to be implemented for realising the "Make in India" goal. The goal of zero imports by 2020 can only be achieved if a large number of small companies use these standards to develop products locally. So small manufacturers should be represented even at the highest levels of the standards development body. An IPR policy should be defined/ modified to factor in these needs.

Evaluation of LTE essential patents declared by ETSI

Cyber Creative Institute, June 2013: http://www.cybersoken.com/research/pdf/lte03EN.pdf

A large number of LTE patents are held by a handful of companies. There is no Indian owner of any LTE SEP.

Ericsson sued Apple in the US over infringement of its LTE patents. As of January 2015, Apple countersued Ericsson in a federal court in California and claimed that it did not owe any royalties to the latter.

Apple also stated that Ericsson was calculating royalties on the sale price of the iPhone or iPad, whereas the royalty should be calculated on the value of the baseband chip that runs this technology in the mobile device. If such litigation occurs in India, what would be India's position? If a building block contains the technology pertaining to a patent, then royalty should be calculated on the smallest possible patent practising unit and not the entire product.

Dr. Kumar N. Shivarajan, CTO, Tejas Networks

TSDSI's (Telecommunications Standards Development Society of India) IPR policy states that a member's technology will become a part of a standard as long as the member licenses it on FRAND terms to other members.

By 2017, 70% of the global equipment spend will be on LTE.
TD-LTE subscriber base in India has been projected to reach 67 million by 2017.
Most of the data connections in India are still on 2.5G.
Smartphones have become affordable but 3G continues to languish in India; 4G yet to take off.
The number of 3G connections in India grew from 30 million to 33 million from 2013 to 2014.

Is 5G the answer to India's access problems?

The mobile industry is aiming to go beyond traditional 4G LTE in 2015 and there is increasing focus on adding new bells and whistles to 4G and realise 4G+.

LTE Licensed-assisted access (formerly LTE-Unlicensed)
LTE Direct/ Peer-to-peer
LTE-M for machine to machine communication
CoMP

Countries forming 5G groups to take an early lead:

China: IMT-2020 (5G) Promotion Group
Korea: 5G Forum
EU: 5G Public Private Partnership (5G-PPP)

5G in its current form is souped-up 4G.

Key India-specific requirements for 5G standard development

5G must factor in the Indian requirement for DSL-like connectivity: Always ON, low latency, affordable cost
To minimise costs, 5G must minimise the use of BTS sites and focus on spectral efficiency.
5G should allow virtual network operations enabling multiple operators to use the same physical network infrastructure.
5G must work well in Indian propagation environments: concrete buildings blocking signals, dense barriers.
5G infrastructure should be green as electricity shortfall is a problem. India has 400,000 cell towers. 10% of them are not connected to the electricity grid. More than 70% experience power outages longer than 8 hours per day, and work on diesel-powered generators. As a result, 25% of the operational costs of telcos are their energy bills. India imports 3 billion litres of diesel annually to run these cell sites.

India can try to get a headstart in owning the IPR that would eventually go into the 5G standard.

Prof. Ramakrishna, MHRD Chair, NLSIU, Bengaluru

The attitude of an SSO towards patented technology determines the objective of its IPR policy. For example, an SSO may want to:

Promote widespread implementation of a standard without unnecessary IPR implications.
Ensure transparency and certainty about the declaration of patents and patents' claims as SEPs.
Ensure that every patented technology is available at a reasonable fee, comparable to the value of the technology.

What happens when IP ownership is transferred to another owner? It continues to be a part of the SSO but things get complicated.

New owners, third parties, subsidiaries, and affiliates fall under the purview of the IPR policy, by extension.

IP and Disclosure policies of Indian SDOs

BIS (Bureau of Indian Standards) and TEC (Telecommunication Engineering Centre) do not have IP policies of their own. TEC refers to the ISO/IEC IP policies wherever the technology is equivalent or the same.
GISFI disclosure requirement: Each member is required to inform GISFI in a timely manner of essential IPRs. But members are not under any obligation to conduct IP searches. GISFI's IPR policy is based on that of ETSI.
DOSTI (Development Organization of Standards for Telecommunications in India) is not functional.

IPR policy for open standards in e-governance

The government of India has adopted a royalty free (RF) approach to licensing open standards.

Mandatory Characteristics of Open Standards:

The patent claims necessary to implement the standard should be made available royalty free for the lifetime of the standard.
The standard shall be adapted and maintained by a not-for-profit organisation.
The standard shall have a technology-neutral specification.

The RF approach and the maintenance by a non-profit may be a disincentive for IP owners.

IEEE patent policy:

IEEE invites participants to disclose patent claims essential to a standard under development. Upon disclosure, the patent holder needs to submit a letter of assurance that states:

License(s) will be made available without compensation or at a RAND rate.
A commitment to enforce the essential patent claims against any entity complying with the standard.
Or state its unwillingness or inability to license its essential patent claims.

Common patent policy for ITU-T/ ITU-R/ ISO/ IEC

Recommendations/ deliverables are non-binding -- ensure compatibility of technologies and systems on a worldwide basis.

The "code of practice":

It is desirable that the fullest available information should be disclosed although ITU, ISO or IEC are unable to verify the validity of any such information.

Major types of IPR policies:

Participation-based IPR policies

These are common in small, informal bodies such as consortia.
Members are bound by the terms of membership to commit to licensing SEPs on RAND or RF terms.
SEP holders notify the standards body in case RAND or RF licenses are not available after the draft standard has been published.

Commitment-based IPR policies
- These are commonly followed large, standards setting bodies.
- These bodies identify SEPs to a draft standard through disclosure and submission of licensing commitment.
- Parties may seek alternative solutions or work on a withdrawn standard is the the alternative solutions don't work out.

Basic building blocks of commitment-based IPR policies

Disclosure policies:

Disclosure is important for
- sending requests to SEP holders to make licensing commitments
- ensuring that experts' groups make informed decisions on inclusion of patented technologies
- providing information to prospective standards implementers about the SEP owners

Two forms of disclosure:

A call for patents is made at the start of meetings. This is more informational than binding.
Later, the member states its intentions regarding licensing the patent on RAND terms.

How disclosure obligations arise (and commitments are binding):

IEEE has by-laws that are binding on members.
ITU, IEC, and ISO: It is via a resolution or recommendation.

(Indicative list)

General disclosure procedure:

The nature of disclosure rules concerning self-owned patents depends on the status or the role of the entity.

A "submitter" is a participant in the working group making a conscious decision to submit its technology to the SSO for a license or free of royalty.
A participant in a working group may submit its technology to the SSO free of royalty, on RAND terms, on RAND terms with the right to charge a fee, or with a refusal to license it. (A working group participant who discloses technology is usually a technology expert. When someone who does not have adequate knowledge of patents discloses technology, it has complicated implications.)
A non-working group participant (third-party) may also submit its technology.

ANSI has left it to the accredited SSO to decide the terms of disclosure for participants of working groups. It has not laid out a policy in this regard. Other organisations have laid out obligations on the submitter to disclose SEPs.

Nature of disclosure terms for patents owned by third-parties:

ETSI: It is obligatory.

ITU/ ISO: Obligatory only for participants of the working groups.

IEEE: Entirely voluntary

Non-essential claims are excluded from disclosure. Pending patent applications are not.

Working groups prefer early disclosure so that they may adopt or discard the claim as early as possible in the standard setting process.

ITU: Disclosure from the outset

IEEE: During meetings of the working group

ETSI: "Timely manner"

AFSI: At a sufficiently mature level

There is no mandate for updating the disclosure in case a standard evolves.

Most SSOs make disclosed patents public. Failure to disclose patents may result in accusations of abuse of monopoly or anti-trust/ anti-competitive activities.

It is difficult to identify all potentially essential patents due to the complexity of specifications.

Some SSOs don't require IP disclosure at all. The obligations to license on FRAND terms would be sufficient.

Only 16% patents declared as SEPs are actually SEPs, according to a study.

It makes sense for rightsholders to go for blanket disclosures instead of disclosure of specific patents.

Vinod Dhall, ex-chairperson of the Competition Commission of India (CCI):

Our competition law is new, so there aren't any cases pertaining to patent litigation and involving the competition law, which we can treat as precedents. In one of the mobile phone patent litigation cases in India, the implementer has approached the CCI claiming that the licensor has been abusing its dominant position in the market by charging unreasonable royalties.

The Delhi High Court has passed interim orders restraining the CCI from deciding these cases. Our appeal to the courts is that these patent infringement lawsuits should not be viewed in isolation. They should not be viewed as merely contractual issues between the licensor and the licensee. They should be seen in the context of their economic effects and their adverse effect on competition. The CCI should be enabled to deal with such cases.

Questions-answers round:

What are the criteria for declaring a patent an SEP?

T. Ramakrishnan: SSOs have no role in declaring that a patent is an SEP. The SEP holder declares that their patent is essential to a technical standard. Most of the time, the SEP may turn out to be a non-SEP at a later stage. Statistically, 16 out 100 claimed SEPs are actually SEPs. There is no way for SSOs to tell if a patent is an SEP. IP policies of most SSOs state that they don't search [if a patent is an SEP]. The members of SSOs are under no obligation to search.

The commitment to license an SEP on FRAND terms is more important to an SSO [than determining if the patent is indeed an SEP].

Can compulsory licensing be implemented with government intervention in India so that the Central Government can fix a royalty and put an end to patent litigation?

Matheson: The phrase "compulsory license" sends a shiver down every corporate's spine every time it is used. International experience is that the judicial system has been the only forum where we have been able to have due process to enable us to construct cases properly in order to explain to the judge or to the jurors how the system works. That has produced very sensible solutions to this problem. Handing it off to the government to institute a compulsory license wouldn't be fair to the SEP holders.

With respect to the "safe harbour" approach towards SEP-based injunctions, what does the licensee need to do to prove to the courts that it is a willing licensee, in the event that licensing negotiations fail or take a long time?

Matheson: It gets down to the licensee showing its willingness to negotiate. The licensee cannot make a half-hearted attempt and decline to negotiate or decline the licensor's offer and then disappear. They should physically engage in the negotiation. If and when it gets to a judicial environment, the judges know when people are telling stories and when parties are bona fide. They can tell a ruse when they see one, and I think it is one of the things you observe in practice.

Ramakrishnan: The licensee should be able to demonstrate that it is willing to pay the royalty and should deposit an amount towards royalty. One recommendation from AIPP states that instead of using the terms "willing licensee" and "willing licensor", use "good faith response". For "good faith" we have very well established criteria. The entire licensing process should end within 12 months of starting. If the negotiations fail or if the process takes longer, then they should agree upon an arbitrator to fix FRAND terms. These are indicators that demonstrate the licensee being a "willing licensee" or a "good faith" licensee.

Often technology changes before the legal action can be taken or the lawsuit completed, and the patent over which litigation has happened may no longer be relevant to the technology. How do patent holders deal with this situation?

S.K. Murthy, Research Scholar, NLSIU: Even if the technology becomes obsolete, damages can be claimed retrospectively.

Matheson: You have a commitment to a FRAND solution, so that when you enter the protracted negotiation, you know that at the end of it you will get a fair solution. That's not always the case when you are dealing outside the FRAND world. You're dealing with a FRAND incumbent, not with unlicensed patents.

Why is putting a time limit to negotiations not a good idea? Also, IEEE seems to have done well by taking the threat of negotiations out of its way. Is it practical in India, because injunction is still the most potent weapon to protect intellectual property rights in India currently?

Matheson: Licensing is incredibly complex. There can be claims to the validity of the patent, there are claim charts to be drawn, there is expert evidence to be put together. Litigation over patents can take 2 to 3 years. To say that there must be a solution [arrived at] within a smaller framework gives the licensor the opportunity to wait around till the end of that period and assert its patents through an injunction. If you're leaving injunction at the table, you will not have a fair solution. The licensee will always be at a major disadvantage. The IEEE solution is a good one because it has taken the time limit away, but at the same time the policies that would adopt that solution need to include the discipline to ensure that the negotiations are bona fide.

What percentage of the sale price should be provisioned by a product developer for royalties? Can a mechanism be drawn up for this purpose?

Justice Ratnakala: Definitely. Such a mechanism should be drawn up in the near future.

For more details visit https://cis-india.org/a2k/blogs/conference-on-standards-settings-organizations-sso-and-frand-nlsiu

2nd National Language Conference, Bhubaneswar

subha — 2015-04-10T15:23:02Z

Institute of Odia Studies and Research organised 2nd National Language Conference beginning on Monday, March 30, 2015 and ending on April 2, 2015 at the Institute of Physics, Bhubaneswar. This conference was organised in collaboration with the Department of Tourism and Culture. I presented a paper in Odia language in this conference as part of a panel discussion related to Odia language computing.

I spoke briefly about the issues with Odia being used massively on the Internet and gaining popular with Odia speaking netizens. Odia Wikimedia community and CIS-A2K's efforts has resulted growth in online Odia content. I also shared the potential projects that people could get involved and how collective effort will yield more diversification of the language and its use by today's generation.

The talk is available on Wikimedia Commons under a Creative Commons Share-Alike 4.0 license.

Video

For more details visit https://cis-india.org/openness/blog-old/second-national-language-conference-bhubaneswar

Bangla Wiki turns 10

praskrishna — 2015-04-04T16:10:12Z

The 10th anniversary of Bengali Wikipedia was marked with a a gathering of Wikipedians of vernacular languages from across the country and beyond at Jadavpur University. Bengali is one of 20 Indian languages to have a Wikipedia presence. The event also celebrated 14 years of the mother edition in English of the open-access, crowd-sourced online encyclopaedia.

Contributed by Sudeshna Banerjee, Showli Chakraborty and Abhinanda Datta the story published in the Telegraph on March 29, 2015 quotes T. Vishnu Vardhan.

"We hear of digital divide all the time. Here it is about digital inclusiveness. The University Grants Commission talks of four factors to make a good university - access, equity, quality and employability. What a teacher cannot give in class, he can offer on the world wide web. The question of quality in Wikipedia can be addressed through workshops like this," said Calcutta University registrar Basab Chaudhuri.

Wikimedia Foundation trustee Bishakha Datta spoke of the uneasy relationship between Wikipedia and academia, especially over authenticity.

"Yes, we do not use original research. So our articles are not admissible as primary sources. At the same time, every piece of information in a Wikipedia article has to be cited and annotated. It is great that an institution like JU has come forward to host us," said Datta, thanking the university's School of Languages and Linguistics.

Joint registrar Sanjay Gopal Sarkar argued in favour of the existence of Wikipedia articles in the vernacular. "It is a part of the empowerment of my mother tongue."

Quantity was a problem, he said. "It is not enough to have 33,000 articles (the English version has 4.7 million). Workshops need to be held in Bengal and Assam on how to write articles. If Wikipedia and the universities join hands, a battalion of writers and editors can be created."

The Bangladeshi delegates revealed how Wikipedia's mission of making knowledge free was getting a technological boost back home. "Grameenphone and Bangla Link, two of our biggest mobile service providers, have made Facebook and Wikipedia free. Subscribers just have to log on to specific domains (0.facebook.com and zero.wikipedia.org) to see picture-less texts," said Ankan Ghosh Dastidar, a Class XI student from Dhaka.

Vishnu Vardhan from the Centre for Internet and Society, Bangalore, urged for more institutional tie-ups so that instead of stopping students from going to Wikipedia, teachers would integrate their contributions to Wikipedia in the course. "Andhra Loyola College is the largest contributor to Telegu Wikipedia," he said. Hindi, he added, has the maximum articles among Indian languages, followed by Tamil and Telugu. "But Malayalam has the most active Wikipedians - around 100."

A workshop was held to teach how to type in Bengali and edit the Bengali Wikipedia. Techno India student Ayan Chaudhury addressed queries on downloading the Avro font and typing tricky conjoined letters in Bengali, as also how to create cross references and highlight terms. "Ask yourself two questions when you want to add any information: Is it relevant? Can it be verified? Also do not blindly turn on Google Translate. The quality of its translation is such that a word like 'swipe' becomes ' dhum dhadakka'."

A group editing session took place on the second day with 15 volunteers translating articles from the English Wikipedia and adding new articles in Bengali. Some also worked on Wiktionary, an online dictionary, and others on Wikisource, typing out pages of seminal texts outside copyright.

Crafts for a cause

Artisans from Bengal and Bangladesh joined hands to participate in a handcrafted jewellery and handloom exhibition organised by WIIN (Women and Infants in Need) at Shree Art Gallery in Ballygunge on March 25 and 26.

"The proceeds will be donated to Paripurnata, a home for women with mental disabilities (off EM Bypass). We emphasise on mental health awareness programmes and try and create job opportunities for the residents at Paripurnata. This helps in building their confidence and creates a sense of social acceptance," said Nilanjana Mukherjee, the general secretary of WIIN and Paripurnata.

The exhibition was inaugurated by actress Sonali Gupta, who plays Satyabati to Dhritiman Chaterji's Byomkesh Bakshi in Sajarur Kanta. "This cause is close to my heart. We must come together to help women and infants in need," said Gupta.

The exhibition showcased a collection of saris and jewellery from the Rajshahi district in Bangladesh, quirky handbags, hand-painted mugs, kurtas and dupattas.

Trilingual road trip

An independent film - or indie - by two graduates of the Satyajit Ray Film and Television Institute (SRFTI) has hit theatres this Friday. Titled Yahan Sabki Lagi Hai (Everybody Gets Screwed Here), the 100-minute trilingual (English, Hindi and Bengali) black comedy is directed by Calcutta girl Tina A. Bose and Mumbai boy Cyrus R. Khambata.

Produced by Vibrant Works, the film revolves around Kesang and Bharat, who are on their way to a birthday party but their road trip soon turns into a disaster as they find themselves in the middle of a jungle, robbed of all their belongings.

Road trip gone wrong has been done before, but according to the young film-makers, "while most of them have been horror or slasher films, ours travels the philosophical path and focuses on the issues we face in life."

The lead actress is a Tibetan girl, Eden Shyodhi. "We wanted to cast a girl from a minority community. We needed someone who was weird and interesting as the character of Kesang is very unusual. And when we met Eden, she had flaming red hair, just like how we had envisioned Kesang!" said Tina, who has studied in Lady Brabourne College and Jadavpur University. The cast also includes stand-up comedian Varun Thakur and Bengali actor Heerok Das, previously seen in Egaro.

For more details visit https://cis-india.org/openness/news/the-telegraph-march-29-2015-bangla-wiki-turns-ten

4th IPR Researchers Confluence

praskrishna — 2015-04-04T06:15:08Z

Maggie Huang attended the event organized by Shailesh J. Mehta School of Management, Indian Institute of Technology Bombay, Mumbai and National Institute of Industrial Engineering, Mumbai with support from Ministry of Human Resource Development, New Delhi on March 27 and 28, 2015.

Maggie Huang presented intermediary findings of the research entitled "India’s Music Copyright Management in the Age of Music Streaming" positing streaming services as the 'frugal innovation' due to its low price tier. See Maggie's presentation here. For more information on the event, click here.

For more details visit https://cis-india.org/a2k/news/fourth-ipr-researchers-confluence

Hindustani Language: We Are Wikipedia

syed — 2015-04-10T16:20:07Z

In 2014, the Centre for Internet and Society's Access to Knowledge team (CIS-A2K) embarked on a new social media-based initiative - WeAreWikipedia. The aim of the project was "One Wikimedian every week to tell untold community stories on Twitter".

Read the original published on Wikipedia page here.

Although CIS-A2K has the mandate of promoting Wikimedia Projects only in India, by virtue of the inherent power of Twitter and Internet, the project was able to attract Wikipedians from virtually all parts of the world - India, Cambodia, Israel, USA, and a number of other countries for curating WeAreWikipedia account on Twitter. The enriching outcome was these Wikipedians' expression of community views and as well as their own editing and Wiki World experiences in the form of short and succinct tweets. These messages give a more clear pictures of happenings than tons of blogposts, videos and lengthy articles which we find today scattered over the internet.

In February 2015, I attended the first Hindi Wiki Sammelan Meet in Delhi. This event was also supported by CIS-A2K. It was attended by 15 people, including three administrators of the Hindi Wikipedia: Ashish Bhatnagar, Aniruddha Kumar and Sanjeev Kumar. Also present were two reviewers: Piyush Maurya and my humble self. During the meet, one of the participants, Manish Panday, demonstrated the massive reach and impact of "Twittercasting" the event proceedings. This drew a keen interest from the Hindi Wikipedians with the Hindi Wikipedia admin Ashish Bhatnagar taking the lead in curating the "WeAreWikipedia" shortly after the meet. As his one week of curation came to end, he asked as to who would curate next. I volunteered to be part of this exercise. My CIS ex-colleague Subhashish Panigrahi informed about allocating the week March 2-9 for me, which I agreed.

As a Wikimedian, I made it a point to first showcase the developments within Hindi Wikipedia such as the notable articles written during the week, the discussions on the Hindi transliteration of non-Hindi names/ titles, village pump discussions, etc.I also shared suggestions with some of the Hindi Wikipedians on editing aspects.

A remarkable development during the week was publication of my report on Hindi Wiki Sammelan Meet in Delhi and its Hindi translation by Ashish Bhatnagar on Wikimedia Foundation Blog. I was delighted to post the information of both these developments on Twitter. In fact, Ashish Bhatnagar favorited my Twitterpost about the Hindi translation. . In addition to Hindi Wikipedia, I was also vocal on the developments at the language front such as Kavita Path Pratiyogita (Poetry Competition) by HindiUSA, Unicode converters, Hindi blogs, developments in Urdu and other Indian languages. I also highlighted some of the projects such as Speedydeletion Wikia, Manypedia, blogpost/ online forum discussions on Wikipedia as well as the rise of mobile edits on Indian Wiki projects.

Since March 8 or Women's Day happened during the week, I made many tweets during the week about the commemorative Wikipedia Editathons both in India and abroad, including those in places like Latin America. I also tweeted about important events such GLAM-WIKI 2015 conference, Erasmus Prize 2015 for Wikipedia, Howard University's efforts to fill in Wikipedia’s gaps in Black History, etc.

I was glad to highlight many important issues during my week as a curator. This included the special media attention abroad given to people who edit Wikipedia or Wikimedia projects such as the featured interview of Bryan Henderson in the The Independent. I suggested that there is a need for such an encouraging gesture to the contributors of Wikimedia projects. I remember some of the Wikipedians favoriting this message as they concurred with me. I also stressed on the need to reinforce fresh lease of life in projects such as Devanagari Wikis Monitoring Team as an active team will benefit not just Hindi but all Wiki Projects in Devanagari-based languages.

The most pleasing aspect of my curator experience were the proactive discussions, retweets, favoriting, of many of my messages. I witnessed an instant response when I mentioned how beautifully the bot-assisted Twitter account "PakistanEdits" posts about anonymous edits from Pakistan on English Wikipedia and the need for a similar tool for India. One Wikipedian promised to work on finding a similar solution to this idea. Similarly, my Twitterpost on the time-barred "Hindi Wiki Sammelan" message notification on every page of Bhojpuri Wikipedia was removed instantly. A still surprising reaction was seen only a few days back when a gentleman enquired about how he can contribute to fill the need for Sanskrit text in the online Vietnamese Wikipedia guestbook page - this response comes after a fortnight of my tweet, and two persons had curated the Twitter account during this period.

Thus, I believe that my messages were well received and my interactions with other Twitter-users were friendly, informative and extremely fruitful. A summary of my curator experience is as follows:

Description of Tweets	Number
No of Unique Tweets	148
My Tweets Retweeted	53
My Tweets Favorited	63
My Discussed Tweets	12
Others Tweets I Retweeted	27
Followers+	34
Following+	17
Image Uploads	5

For more details visit https://cis-india.org/openness/blog-old/hindustani-language-we-are-wikipedia

Interviews with App Developers: Open Source, Community, and Contradictions – Part III

samantha — 2015-04-03T08:15:25Z

The following is a third post within a series reporting on interviews conducted with 10 of Bangalore's mobile app developers and other industry stakeholders. Through this research, CIS attempts to understand how the developers interviewed engage with the law within their practice, particularly with respect to IP. Here we examine different attitudes and perspectives towards themes related to open software, as well as contract agreements.

While interviewing 10 of Bangalore's mobile app developers, the conversations that proceeded the immediate responses to our questions posed proved to be the most insightful. Previously, we examined responses surrounding different views on intellectual property rights (IPR) and potential factors influencing these individuals' attitudes and practices within their work. Within these preceding blog posts reporting on our interviews, a prevalent device we have made reference to is the dichotomy across positions that app developers take at polar ends of various spectrums. Here are some examples of the ways we have observed individuals to have opposing standpoints:

To work within a large corporate body	versus for a small startup enterprise
To develop mobile apps as one's own product	versus to develop apps as a service for another
To be familiar with intellectual property	versus to disregard intellectual property
To desire protection for one's intellectual property	versus not to care about protection for one's intellectual property

Contrary to some pro-IPR stances, several of our app developers strongly opposed notions of strict IPR regimes (patents, especially) and advocated on behalf of the open source community. And yet, others expressed their appreciation for open source software (OSS), all the while pursuing their own IP protection—a contradiction?

But is it really so cut and dry? Must an individual represent one side or the other? And if he or she does straddle the line that divides these opposing stances, is it by choice? Or necessity?

And what other dichotomies exist for the mobile app developer?

Open values and open source

Those interviewed who spoke highly of open source software often did so in referring to personal values of openness and the ability to share and use others' code freely within their work. One developer within a nonprofit enterprise explained that he would not want to restrict the future development and utilization of their idea, and would only consider licensing his source code under open source licensing, and not copyright.

Another common claim across developers is their involvement within the developer community, and contributions to open source libraries—and not only as a hobby. Large software development social enterprise, Mahiti, along with other interviewees representing social or nonprofit enterprises exhibited a particular interest in the use of and contributions to open source libraries.

Sreekanth S. Rameshaiah, cofounder and CEO of Mahiti explains that they “require all software to be GNU licensed, unless decided otherwise by the clients.” GNU General Public License (GPL) is considered a free software license—one that allows the licensed works to be freely accessible to all and to be used, copied, and altered as desired—as well as copyleft—in requiring all users of any component of the previous work to license their succeeding work under the same license as well. Some clients for Mahiti, of course, wouldn't find such conditions desirable, if they are ever to profit off or retain full ownership over their products and services.

Open source for future protection

One designer from a services SME enlightened us of a different reason for doing so: to guarantee their ability to use their work again. “Since we use a bunch of templates and things like that, those we license using a non-exclusive license, because we reuse those elements on different bits of code in different projects,” he explains, “so there are bits of it which is used over multiple projects and there are stuff that is built exclusively for the client.”

Here we are given some insight, that perhaps developers do not necessarily license for community values primarily, but for the ability to use their own work across clients. That being said, we begin to wonder what the possibility that open source code may serve as a loophole for work-for-hire contracts, which require the developer to assign all written intellectual property to whoever is commissioning the project. If the code happened to “already be available by open source,” a developer may still be honouring any restrictive agreements with clients, and ensuring their ability to use their code in this future again.

Such a strategy complies with the advice of Jayant Tewari of Out Sourced CFO & Business Advisory Services. Some advice Tewari has for startups is to first and foremost protect themselves by making wiser choices related to code in order to prevent being litigated against by others—such as using an open source equivalent to a piece of code that one does not have the rights to, or instead putting the extra time in to develop it from scratch.

Conflicting perspectives: hypocrisy or realism?

Of those who expressed an interest in the open source movement, not all had said that their products were to be open licensed as well. One developer explicitly stated: “I like the idea of open source, and building upon others' work...but our app is not open source, it's proprietary.” It may be a given, then, that all or most developers within our interview sample rely on open source code within their practice, but not all may contribute their resulting product's source code back.

Vivek Durai, from Humble Paper says that despite the fact that “open source has really taken route... on the smaller levels, people will come to a point when philosophies begin to change the moment you start seeing commercial.”

In our first blog post, we established the tendency for startup app developers to move away from the services model towards a product-oriented business model. If app developers most often contribute back to open source libraries when they do not have any mobile app products of their own to protect, I begin to wonder if we would see any change to the levels of content generation across open source libraries if, hypothetically speaking, all services app development enterprises began to solely develop their own products.

Which brings us to an additional mobile app ecosystem dichotomy:

To license mobile app code as proprietary VS to license mobile app code as open source

As individuals move away from the services model to focus their energy and investments on their own products, I begin to wonder if there is a tendency for them to also move away from the open source model as well...

Although perhaps irrelevant, we also consider the question concerning the reasons mobile app developers moving away from the services model to begin with. In the first part of this series, we heard from industry consultants of the little financial incentive the services sector has to offer, but can that be all there is to it?

Join us in our next post as we look closer at the mobile app ecosystem's business model trends, as well as its startup culture with regards to contracts and copyright.

For more details visit https://cis-india.org/a2k/blogs/interviews-with-app-developers-open-source-community-and-contradictions-iii

Interviews with App Developers: Name of the Game (Part IV)

samantha — 2015-04-03T08:58:27Z

The following is a concluding piece in a series reporting on interviews conducted with 10 of Bangalore's mobile app developers and other industry stakeholders. Within this research, CIS attempts to understand how they engage with the law within their practice, particularly with respect to IP. Here we examine responses given across interviews regarding instances of infringement of IP within their work.

Before commencing our interviews with India's mobile app developers and other industry players, a small series of questions had been devised in hopes of enabling us a glimpse at the facets of the picture of our main interest: those related to intellectual property. What we soon came to find, was that these questions may have too bluntly stated, producing hesitant and wary responses from those interviewed. After breaking this immediate ice, however, we often were given the privilege of hearing from these talented and thoughtful individuals several times over. And it is through this set of questions that the space was created for us to work together to reach an understanding of how different types of players orient themselves within the industry, in relation to their practices, policies, and business relationships, and voice any concerns or questions of their own.

The last of these questions to look at, is arguably the most sensitive in nature, asking whether one has ever had their works infringed upon, or has been accused for infringement upon those of others. In asking this question, we had hoped to gain some insight about occurrences of infringement taking place within the mobile app ecosystem, how this occurs, and in what sort of context.

Preceding conversations revealed differing experiences related to infringement; some experiences common across most, while others limited to one or two individuals. What these experiences, in turn, revealed, is what seems to be polarized stances on the very notion of infringement, reflecting personal histories and differing interests.

But what even is “infringement?” The term may be generally defined as:

infringement

noun

The action of breaking the terms of a law, agreement, etc.; a violation

But what exactly does this mean for a mobile app developer? Having not been previously defined or explained to those interviewed, the term had been used across responses in reference to various instances of infringement, spanning across many areas related to mobile app development. These instances will be looked at to follow.

Mobile app content (i.e. logos, pictures, etc.)
Pirated apps in app stores
“Dummy apps” or imitations of another's app
Breaching app stores user agreement
License agreements of code created by another
Open source licenses
Breaching of terms of agreement for by commissioning clients
Breaching of terms of agreement for by those hired

Not a threat to the threatening

After implying that his enterprise uses components that are owned by another without the proper permission to do so (whether source code or visual components was not specified), one developer simply stated that “no one would come after us—we have no money!” IP Strategy Consultant, Arjun Bala, explained to us that “here, developers do not need to worry about being sued. The big companies do not go after small developers; it depends on how much money they're making.” Bala continues in saying that, “Patent lawsuits can cost something like millions of dollars, so unless they're going to get more back, they wouldn't go throught the trouble of doing so... but that is true even in the US.”

This soon revealed to be a demonstrated theme known across those within the developer ecosystem. Developer, Aravind Krishnaswamy stated that the “startup mentality is to break all of the rules first, then concern themselves with IP as a means of covering their own tracks.” There is a perceivable difference, he says in their motives regulating their behaviours that differ from “I shouldn't do this because I can get caught vs. I shouldn't do this because it's against the law.”

Towards being infringed upon

For those within service agreements, this was generally so due to the fact that one does not own their works and instead assigns ownership to their mobile apps to clients. Rahul of Uncommon explains that any cases of infringement upon their work is unconcerning to his team: “Because once we hand it off [to clients], it's their issue,” he says.

Contrasting to this perspective, however, is the apprehension exhibited by some towards not clearly knowing whether they are incidently infringing upon others people's work. Because of this unknowing, however, others are indifferent. "There's a few people who I think looked at what we're doing and tried to copy some of the features or just the positioning,” Krishnaswamy suspects, “but, ultimately there are some things you can be bothered about as a small company.” He continues in saying that those suspects to be copying you “could have been working on their product independently—it's quite possible.”

Sree of Mahiti, on the other hand is not too concerned about others infringing upon their products or copying them as such is “irrelevant to their business model.” In making their software products open source, Sree explains, that they do not care how people use it, but if he were to come across infringement, he would likely act upon it.

But how can one be indifferent to infringement while licensing under GNU, a perpetual copyleft license?

Name of the game

Perhaps one could even go a step further in arguing that being a developer (a startup developer, especially) necessitates bending the rules at some point. Of all of the bits of open source code used, how many of the licenses are actually considered and complied to in their entirety? As stated by Vivek Durai of Humble Paper: “In a mobile app where you're producing software, you could potentially be violating the terms of OS licenses.” Tewari argues that this actually occurs in pretty much all cases.

“Everyone is in non-compliance. That is a given,” Tewari asserts. However, the distinction he makes is that more corporate players are in non-compliance knowingly than not, where is more SMEs infringe upon others without being aware that they are. Just as well, the degree to which infringement takes place may differ between the two types of industry players: “At the corporate level, where they know they are not in compliance, the degree of non-compliance might be very small or specific, but it still exists.” On the other hand, for startup developers, a substantial amount of their code may not comply with the licenses and agreements they are obliged to—something that could pose problems for them later down the road if left unfixed.

“Everyone is in non-compliance. That is a given... It is similar to asking 'do I know anyone who has never paid a bribe?' My answer is no.”

To put simply, Tewari draws the following comparison “It is similar to asking 'do I know anyone who has never paid a bribe?' My answer is no.” Here, he suggests that non-compliance to legal agreement, although technically unjust, is as tacit to the software sector as bribes are to the justice sector. Although perhaps not a perfect comparison, it definitely helps to put things into perspective.

Mope App Matrix

After speaking with numerous mobile app developers, lawyers, and other community players, it is difficult to say whether our findings have brought clarity to the nature the problem at hand, or if our research has, instead, shed light on additional problems within our realm of vision—at varying heights and depths, cutting across one another to form a matrix of indivisible linkages, or just plain chaos.

In the next of our exercises, we hope to comprehensively illustrate this matrix, by categorizing the different stakeholders across this ecosystem according to their interests and the ways in which they operate, and in turn, affect each other.

We look forward to bringing to completion (even if only to return to later) the first of our stages within this chapter of the Pervasive Technologies Project, which, to recap, had initially been to understand the mobile app ecosystem in light of India's IP regime. But what we are arriving at may be regarded, instead, as an understanding of the ecosystem informed by the stories and experiences of the ecosystem's central organisms: its developers. Perhaps it can only be here, at the intersection of stories—whether complementary or contradictory in nature—where the intricacies of processes deeply-embedded and their implications begin to reveal themselves.

For more details visit https://cis-india.org/a2k/blogs/interviews-with-app-developers-name-of-the-game-part-iv

Internet becomes vernacular with relaunch of e-bhasha

praskrishna — 2015-04-03T05:49:42Z

With the relaunch of e-bhasha as a mission mode project, there is a fresh urgency to create content and technical solutions in Indian languages.

The article by Ankita Lahiri was published in Governance Now on March 23, 2015. Sunil Abraham is quoted.

Computer literacy is often linked to the knowledge of English. With the launch of the e-bhasha project, the government is hoping to make the internet more accessible. The project aims at providing computing tools in Indian languages, thus making government services available to a substantial part of India. These tools were developed more than a decade ago, but sadly remained non-utilised. However, the government has now decided to bring in the e-bhasha project under the umbrella of the national e-governance plan (NeGP) as a mission mode project (MMP).

The project that is being jointly driven by the department of electronics and information technology (DeitY) and technology development for Indian languages (TDIL), will be implemented in all departments across states and promises to provide all government services in 22 scheduled Indian languages. It will also provide a range of technical solutions, browsers and content in local languages. The multilingual aspect will ensure that government services have a wider reach and are accessible to citizens in local languages. The department hopes to get approval for the MMP by early next year.

Although TDIL has been finalised as the nodal implementing agency, the idea is to create a separate body, the centre of excellence (CoE) for localisation of Indian languages that will do the actual implementation on the ground level. Discussing the wing’s role, Swaran Lata, officer-in-charge, human-centred computing division, TDIL, told Governance Now: “We are like the backbone MMP. We will provide tools and solutions that can be used to generate the content in Indian languages. We will also provide standards and guidelines for the electronic governance domain. The final service delivery will be the responsibility of the various departments.”

Elaborating on how this platform can potentially transform the lives of the common citizen, Rajat Moona, director general, centre for development of advanced computing (C-DAC), said, “More people will get connected to government services now. It will bring the government closer to the citizen. The platform will change the way people carry out government services.” C-DAC has been working on local language computing and has been a key player driving the initiative on the technology front.

As an MMP, e-bhasha will have two main components: productisation and capacity building. The first step towards creating the e-bhasha platform will be the productisation. As Rajendra Kumar, joint secretary, DeitY, pointed out, “E-bhasha is all about the use of computing tools in Indic languages. It is about the productisation of these software tools, which means the ultimate utilisation of these tools for the end user.” In order to fully implement the MMP, proper training as to how to implement it at the ground level has to be given. The capacity building module of the MMP aims to train both the government departments as well as their technical teams. The training will be implemented jointly by DeitY and TDIL.

Commenting on the need for capacity building Lata said, “People still don’t have the skills to develop applications in multilingual or bilingual languages.” The training will be given through classroom sessions and various trouble shooting groups. Lata explained that applications will be classified in two groups – new projects and continuing projects. For each group the challenges will be different. For pre-existing applications, the entire application might have to be rewritten since the application as such might not have any provision for local languages. “The localisation of applications will vary according to the existing applications,” she said.

After this, content in these languages will be generated by various institutes and research and development organisations. Explaining that the service delivery framework for the MMP has already been designed, Rajendra Kumar said that the centre will extend total support to all the states in implementing the project.

Where India stands

Work to provide support in the form of tools and content in Indic languages has been going on in the country for more than two decades. C-DAC has been involved in this since 1988. The centre has been working towards developing tools that support Indic languages. Moona said, “We have been supporting Indic languages since 1988, whether it is from left to right or vice versa and languages with multiple fonts, like Konkani.

“As an integral part of the e-bhasha MMP, the centre will provide software tools that will facilitate the citizen in accessing government services in the local languages,” Moona said adding that, “Through the tools, we provide localisation support of government services. We provide government frontend in local languages. That is what the e-bhasha MMP is all about.”

C-DAC has already developed a number of solutions that support the Indic languages including a mobile touch keypad that can be downloaded from its website. Further a screen reader and various templates are also available. “The keyboard is slowly disappearing. We have a touchscreen that supports 27 Indic languages,” Moona said.

One of the key initiatives by TDIL has been in the form of the Sakal Bharti font, a type of open font format (OFF). It is a standard font, applicable to all the 22 schedule languages, irrespective of the platform, programme and language. It allows one to view and edit any document without any loss of data. Similar efforts have also been made by private players in creating the required tools to increase the reach the Indian languages. The Centre for Internet and Society (CIS) has launched several initiatives, including translating Wikipedia in regional languages and creating screen readers that support indigenous languages.

With the increase in internet penetration and the resulting increase in demand, private players, including digital giants Google and Microsoft, have joined hands to promote content in Indian languages. The initiative called the Indian languages Internet Alliance (ILIA) was launched by Google to cater to the Hindi-speaking population by providing content and solutions. Launched around the same time as the e-bhasha project, the two projects are expected to complement each other.

“It is heartening to see support from the government for this initiative. The initiative would shape the thinking around the government’s e-bhasha initiative and we are happy to partner with the government around the three pillars of e-bhasha: e-governance, e-education and culture,” said a Google spokesperson.

In support of the private initiatives that are coming up, Lata explained that an ecosystem has been built. “What happens is that in areas where it is not commercially beneficial, it has to be the government which steps in first. I think the government has received a wake-up call in terms of both e-governance as well as languages.”

The chicken or the egg?

The resources have been available with the government for the last two decades, yet it is only now that the push for local languages has got the attention it much needed. According to Kumar, while C-DAC has been involved in developing these tools and their language department, GIST, has been around for at least 15 years the implementation in e-governance did not happen.

Lata further elaborated, “It is not the correct perspective to say that the localisation of languages is just a frontend issue. It is an architectural issue and a language solution should enable people to search access and retrieve data in the local languages.”

The surge in the number of users as well as the new government’s heightened interest in electronic governance has created an increased demand. “The push for Indian languages has been there for a long time. Many government websites are bilingual (English and Hindi). However, with the introduction of electronic governance a lot of activities have been happening. The need for Indian languages has become much higher,” Moona said. “It is an evolutionary process. Internet governance is still a new thing in India, it is only after its introduction that the tools and support for local languages has been required.”

Sunil Abraham, executive director, CIS, said, “Creation of Indic content cannot be left to a single government entity. It needs massive effort from all concerned stakeholders. The reason that there is very little Indic content online is because most internet users today either are comfortable using English or don’t have sufficient purchasing power to sustain different business models. As more and more Indians come online, more and more businesses will begin to leverage Indic content. However, focused and enlightened investments by the government would be very useful in helping Indic languages catch up on the internet.”

With Indic languages receiving a push from both the government and private players, it might just be time that the internet really becomes a tool for everyone.

For more details visit https://cis-india.org/internet-governance/news/governance-now-march-23-2015-ankita-lahiri-internet-becomes-vernacular-with-relaunch-of-e-bhasha

Mobile App Developer Series: Terms of Agreement – Part IV

samantha — 2015-04-03T08:26:27Z

The following is Part Four in a series reporting on interviews conducted with 10 of Bangalore's mobile app developers and other industry stakeholders. Through this research, CIS attempts to understand how the developers interviewed engage with the law within their practice, particularly with respect to IP. Here we examine different attitudes and work practices related to contracts agreements and developer culture in the legal realm.

We left off in our blog series considering the reported reasons why one would protect their mobile app by intellectual property means and how they relate back to (or contradict) their values as a mobile app developer in India. Here, we would like to get into more of the nitty gritty of contracts—which clauses are most important to mobile app developers, and what they think of them—followed by a cultural interpretation of the dynamics of this developer community with respect to contracts, and then lastly, a look at copyright, more generally.

Contracts in mobile app developing services

Previously, we shed light on the tendency for mobile app developers, in India particularly, to create mobile apps or mobile app components for clients, often overseas, within a work-for-hire agreement. Within such an agreement, the rights to (or ownership over) one's work is generally handed over to the client the moment the code comes into creation. Simply put, if paid to carry out a particular project, whatever is created within the project belongs to the client.

This is not the only instance where we encounter contract agreements in the mobile app ecosystem, however. For startups where team players are small in number, it is likely that all will have access to any contract agreements entered into with clients. For larger corporate software developer firms, there may be a specialized department for legal-related matters. In such cases, the mobile app developers themselves would seldom lay eyes on the legalese of contracts, for the primary reason being that it doesn't concern them. Instead, the terms of agreement more familiar to them would be those that they obliged to upon working for their employer.

However, after conversing with multiple stakeholders within India's mobile app space, what we came into understanding is that the importance of contract agreements for mobile app developers may be generally underestimated by the developers—both from within the startup to the corporate employer.

Clauses of caution

Within a work-for-hire agreement, it is commonplace for developers to enter into restrictive agreements that obstruct the freedoms of what they can do with the code created for the client. Across interviews with developers in startups and SMEs working for clients, this seemed to be a prevalent problem. Problematic areas proved to be those related to the time periods in which the developer was not allowed to take up future work for competing clients (i.e. the non-compete clause), or could not talk about their work for the client at all (the “quiet period”).

Designer, Rahul Gonsalves explains how these areas of their contracts with clients may impact his team at Uncommon: “The non-compete and the quiet periods are the two bits which are most germane to us, because if I can’t do work for a year in the same area, that impacts my ability to run my company.” Fortunately, Gonsalves says that less frequently are they obliged into quiet periods—in which they would not be able to talk about the work they do for their clients—as this poses an even bigger problem when trying to keep a portfolio for prospective clients, or when writing or speaking on behalf of their experience at conferences.

On several occasions Gonsalves and his team have tried to license their work to clients while retaining ownership... without much luck. “Clients typically do not want a perpetual license, but complete ownership.” Gonsalves goes on in explaining that, “this means they could make a derivative work or use it for another project. Depending on how bad we want the project, we'll work out some middle ground.” But it does not seem to be so easy for he and his SME to do so: “The thing about contracts is it’s all about a sort of differential bargaining power that the two parties have... you’ll have very little control about what happens once you’ve got paid.”

“The thing about contracts is it’s all about a sort of differential bargaining power that the two parties have... you’ll have very little control about what happens once you’ve got paid.”

Contract confusion

To have any sort of bargaining power within a work-for-hire arrangement requires a lot of time for negotiating, and the space for communication to begin with. In many cases, contracts may not even be introduced into a work agreement, leaving a lot of intricacies to the unknown.

“Getting these things down in a legal document is a big deal. It matters,” says Aravind Krishnaswamy of Levitum. The topic came up while speaking about the process of creating the content for one of his startup's apps, which entailed arranging contracts with several third parties involved in. Krishnaswamy and his team did so to ensure that they retained ownership (or co-ownership) over all of the content featured within their app, which features instructional videos on Indian music.

Another developer interviewed, Naveen*, shared with us his experience coming out of college and into employment. Upon joining his first employer, who happened to be a large company, he along with the new “batch” of employees attended a legal session within their training, “but that was Greek and Latin to us then,” he jokes. “We were fresh out of college and had no idea what a software license was... and it was after lunch, so everyone was sleeping.”

Lucky for Naveen, he didn't need to deal with that area too much, as his employer had a legal team to take care of such matters when it came to transactions with clients or third parties. For his current employer, on the other hand, Naveen explained that he could not recall the terms of his employment, as it had been a very long time ago when he signed his employment contract.

Not a contract culture?

Naveen suggests that the problem is one of contract-illiteracy, or simply not having the background knowledge to truly understand the legal facets of the industry, especially as you move away from India's entrepreneurial hubs: “In tier 1 cities, like Bangalore or Chennai, the colleges and students do have some knowledge about open source, licensing and terms, but when you go to tier 2 cities, that's where the problem is.”

But is anyone contract-literate anyway? With the exception of lawyers or legal departments, of course, don't we all have the immediate impulse to click “Next” or sign our signature as soon as we see the words “User Agreements” followed by infinite paragraphs in the smallest font?

However, for the developer in the increasingly-complex mobile app space with numerous parties and transactions involved, terms of contractual agreements may dictate everything from whether one can develop for competing clients, to whether an employee can contribute to open source projects on their own time. Still think that reading those clauses are a waste of time?

We are not arguing that the fact that the developer community seems to be far removed from “contract culture” is in itself a bad thing. As Jayant Tewari of Outsourced CFO & Business Advisory Services asserts: “How mobile app developers regard IP laws—or better yet, disregard—is fine for their sake.” What they must instead learn is to maneuver the landscape to avoid troubles as best as possible.

A good way of going about it, however, may be to begin with the agreements that a developer is already committed to—with clients, employers, and third parties, alike. One should be able to articulate: What is expected of me? Within what limitations? What am I not allowed to do?

Better familiarizing oneself with one's own responsibilities and commitments may be the first step for a mobile app developer to educating him- or herself and become aware of what sort of choices could stir about conflicts in the future, potentially threatening their relationships, reputation, or even livelihood.

But is it even possible to comply to all of the rules of the game?

Within such an overcrowded industry, creation and innovation does not occur in a vacuum, and as a result, many may adjust their own creations as they see fit, according to whatever ways are most convenient and carry out the best function. But at what cost—or more appropriately, what risk?

The next, and final of this blog series will shed light on responses given across interviews to the question of infringement. Here, we intend to connect the dots between the legal practices of mobile app developers and cases of infringement. We hope that after examining such numerous and wide sweeping—yet interconnected—facets of how mobile app developers in India engage with the law within their work, we will be able to comprehensively illustrate the role that these developers play in this economy, and ultimately, pass judgement on the laws that govern this space.

For more details visit https://cis-india.org/a2k/blogs/mobile-app-developer-series-terms-of-agreement-iv

Conference on Standards Setting Organisations (SSOs) and FRAND

praskrishna — 2015-04-10T15:07:38Z

Rohini Lakshané participated in this event organised by MHRD Chair on Intellectual Property Rights, Centre for Intellectual Property Rights and Advocacy (CIPRA), National Law School of India University, Bangalore, in association with Intel Technology India Pvt. Ltd on March 21 and 22, 2015.

Concept Note

There is a relentless effort among public and private companies to build products that conform to national and international Standards. Among several advantages of standardization, seamless interoperability between devices from several manufacturers play an important role. Standards play an important role in spurring the Innovation culture of a country and contribute to consumer benefits. Members of the Standards Setting Organizations (SSOs) may contribute their inventions/technology while forming a Standard. Needless to say, the members of the SSOs may have chosen to procure patents for their inventions/technology, which are contributed to formation of Standards. Further, one among (i.e., winning technology) the several available technologies may be chosen as a Standard and the patents covering such winning technology is generally termed as “Standard Essential Patents” (SEPs).

Generally, SSOs have their IPR policies to (a) enable disclosure of such SEPs to the SSOs; and (b) ensure that licenses are available to standards implementers to practice such SEPs. A commonly used model or principle to ensure that licenses are available to standards implementers is generally referred to as FRAND (Fair, Reasonable and Non-discriminatory). Even though FRAND is a widely accepted model there have been at least some genuine legal issues related to practice of FRAND in the SSOs. Legal systems, legal fraternity, and the businesses around the world are attempting to resolve these legal issues related to practice of FRAND.

Issues related to practice of FRAND are equally important to India as we are moving up the innovation value chain and embarking on a “Make in India” journey. This Conference is designed to enhance awareness on issues related to practice of FRAND and probable solutions thereof. This Conference is aimed to bring together honourable members of the judiciary, members of the law firms, legal fraternity, law students, and premier educational institutions to increase the awareness on FRAND related issues in SSOs.

Click to download the Programme Schedule

For more details visit https://cis-india.org/a2k/news/conference-on-standards-setting-organisations-and-frand