https://github.com/xrstf/oeis-api

ABANDONED project to provide a RESTful, JSON-based OEIS API
https://github.com/xrstf/oeis-api

Last synced: about 6 hours ago
JSON representation

ABANDONED project to provide a RESTful, JSON-based OEIS API

• Host: GitHub
• URL: https://github.com/xrstf/oeis-api
• Owner: xrstf
• License: other
• Created: 2015-12-20T15:07:18.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2015-12-20T15:07:34.000Z (about 9 years ago)
• Last Synced: 2024-12-17T13:52:28.357Z (6 days ago)
• Language: PHP
• Size: 60.5 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
OEIS API

========

This is an **ABANDONED** project that was supposed to build a nice, RESTful API around the

OEIS, but as the maintainers proved to not understand their own license and to be unwilling to

let others spread their data, I decided to not finish it.

In its current state, the crawling/importing code mostly works for things. It's based on parsing the

HTML instead of the internal, text-based format (yes, I knew about that one), because extracting

usernames and links is *much* easier that way. Some things are left unfinished, though.

The goal was to provide semantic JSON for each sequence. My attempt eventually lead to the OEIS

offering a JSON version themselves, which unfortunately completely misses the point (as you still

have to parse the basically line-based format) of my project.

Take from this what you want. The parsing code is pretty good, the rest is just a stub for a Silex

app with MariaDB in the background for indexing purposes. There's also some crawling code in

``www/``, where I spread the crawling throughout 3 VMs. It's all pretty hackish, though.

**DO NOT use this in production, as you will make people at the OEIS sad.**

Even though this package has a ``composer.json``, it's not registered on packagist. It jsut

documents the dependencies.