Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Adding New Dimension by Including Patents in My DNS API Research

DZone's Guide to

Adding New Dimension by Including Patents in My DNS API Research

When you lay API information side-by-side, you begin to see a more complete picture of what is really going on in the API space.

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

I have been tracking on API related patents for some time. I regularly pull XML dumps from the U.S. Patent Office, a process in which I am getting more refined, so that I am able to easily tag and organize them alongside the rest of my research. I spent some time this last week diving into my DNS API research, and after updating the rest of the data behind, I added some DNS-related patents.

The patent information is already available in my API monitoring system. I just needed to be able to tag the patents and write a script to publish the tagged patents to each of my GitHub projects. Now that I have this in place, it is pretty easy for me to spend an hour or two looking through the patents that come each week and putting them into each area of the API space I study (which is why I have organized my API research the way that I have).

The patent information provides shines another light on each layer of the space for me. Understanding the companies, tools, and individual API endpoints provide me with important insight on what is going on, but the patents being submitted are an extremely important indicator of what is actually going on behind the curtain within industries, and companies. With this addition, my research is finally reaching the levels I originally envisioned when I first began organizing my work in this way, going beyond what is available on the "features" page for each company, organization, institution, or government agency is doing with APIs.

I can extract a lot of information from the product pages of the companies who are doing APIs, but these pages are designed to tell a specific story. I find that API definitions, press releases, and patent filings often tell a different story than the company's main product page. I would say that all these areas lie, but marketing, API definitions, press releases, and patent filings are all designed to tell specific untruths designed for different masters. When you lay them side-by-side, you begin to see a more complete picture of what is really going on in the API space.

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:
apis ,patents ,integration

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}