3

I am doing research on how to build an open data platform with a web portal and a REST interface without relying on a turnkey solution.

I found different solutions: CKAN, Socrata, OpenDataSoft and Junar.

But they all lack documentation regarding the different technologies they use in order to have such system working, and why they used them. Also, Twitter documentation is very detailed, but obviously I can't find anything about their Rest API architecture.

Only CKAN has good documentation, but their architecture description doesn't go much into details of the different software stacks it uses, because I guess I need more than a front end, a load balancer, a backend and a database to make it work.

closed as unclear what you're asking by Jan Doggen, nmtoken, Jeanne Holm Jul 8 '17 at 13:46

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    super unpopular opinion in this space: but simply publishing data in HTML properly goes a very long way. – albert Jun 7 '17 at 20:34
  • 3
    Somehow, I don't get your question, as I literally can't find it (no question mark). What are you looking for? Advice on REST architecture? Use another stackexchange Plattform. How to publish? Look here: w3.org/TR/dwbp – Grimaldi Jun 9 '17 at 20:04
  • 1
    Use hypermedia and established protocols, don't go down the route of defining URL structures... – nmtoken Jun 10 '17 at 21:05
  • 1
    why would you not define URL structures? – albert Jun 16 '17 at 2:29
  • Defining URL structure is not flexible to changes in your application. It is not a requirement of REST architecture to define ANY URL structure. – nmtoken Jun 19 '17 at 11:55