pyvideo.org: Videos of Van Lindberghttp://www.pyvideo.org/speaker/226/van-lindberg/rssen-usSun, 13 Apr 2014 00:00:00 -0500500Keynote - Van Lindberghttp://www.pyvideo.org/video/2688/keynote-van-lindbergVan LindbergSun, 13 Apr 2014 00:00:00 -0500http://www.pyvideo.org/video/2688/keynote-van-lindbergPyCon 2014 Awardshttp://www.pyvideo.org/video/2702/pycon-2014-awards<p>Abstract</p>
The awards portion of Van Lindberg's keynote at PyCon 2014.Van LindbergSun, 13 Apr 2014 00:00:00 -0500http://www.pyvideo.org/video/2702/pycon-2014-awardsKeynotehttp://www.pyvideo.org/video/1666/keynote-0<p>Abstract</p>
Van Lindberg is a software engineer and practicing attorney. What he does most, though, is translate - from "lawyer" to "engineer" and back. He likes working with both computer code and legal code to get things done.Van LindbergSun, 17 Mar 2013 00:00:00 -0500http://www.pyvideo.org/video/1666/keynote-0Graph Processing in Pythonhttp://www.pyvideo.org/video/627/graph-processing-in-python<p>Abstract</p>
Graphs are everywhere - from your distributed source code control to Twitter
analytics. This session presents a set of three problems and shows how they
can be decomposed into operations on graphs, and then demonstrates solutions
using the various graph libraries available for (or accessible to) Python.
Van LindbergFri, 09 Mar 2012 00:00:00 -0600http://www.pyvideo.org/video/627/graph-processing-in-pythonHow to kill a patent with Pythonhttp://www.pyvideo.org/video/425/pycon-2011--how-to-kill-a-patent-with-python<p>Description</p>
How to kill a patent with Python
Presented by Van Lindberg
Finding the right piece of "prior art" - technical documentation that
described a patented piece of technology before the patent was filed - is like
finding a needle in a very big haystack. This session will talk about how I am
making that process faster and more accurate through the use of natural
language processing, graph theory, machine learning, and lots of Python.
Abstract
From my work consulting on a number of patent cases, I am frequently asked to
find "prior art" - patents and publications that describe a technology before
a certain date. The problem is that the indexing mechanisms for patents and
publications are not as good as they could be, making good prior art searching
more of an art than a science. When I decided to do better, I reached for
Python.
* Part I (5 mins): The USPTO as a data source.* The full-text of each patent is available from the USPTO (and now from Google.) What does this data look like? How can it be harvested and normalized to create data structures that we can work with?
* Part II (15 mins, in two parts):* Once the patents have been cleaned and normalized, they can be turned into data structures that we can use to evaluate their relationship to other documents. This is done in two ways - by modeling each patent as a document vector and a graph node.
* Part IIA (7 mins): Patents as document vectors.* Once we have a patent as a data structure, we can treat the patent as a vector in an n-dimensional space. In moving from a document into a vector space, we will touch on normalization, stemming, TF/IDF, Latent Semantic Indexing (LSI) and Latent Dirichlet Allocation (LDA).
* Part IIB (7 mins): Patents as technology graphs.* This will show building graph structures using the connections between patents - both the built-in connections in the patents themselves as well as the connections discovered while working with the patents as vectors. We apply some social network analysis to partition the patent graph and find other documents in the same technology space.
* Part III (5 mins): What have we built?* Now that we have done all this analysis, we can see some interesting things about the patent database as a whole. How does the patent database act as a map to the world of technology? And how has this helped with the original problem - finding better prior art?
Van LindbergFri, 11 Mar 2011 00:00:00 -0600http://www.pyvideo.org/video/425/pycon-2011--how-to-kill-a-patent-with-python