Knora API Server Design Documentation

• Knora API Server Design Overview
  • Introduction
  • Design Diagram
  • Modules
  • Actor Supervision and Creation
  • Concurrency
  • What the Responders Do
  • Store Module (org.knora.webapi.store package)
  • Triplestore Access
  • Error Handling
  • API Routing
  • JSON
• Futures with Akka
  • Introduction
  • Handling Errors with Futures
  • Using recover on Futures
  • Designing with Futures
  • Mixing Futures with non-Futures
  • How to Write For-Comprehensions
  • Execution Contexts
• HTTP Module
• Responders Module
  • Version 1.0 Responders
• Store Module
  • Overview
  • Lifecycle
  • HTTP-based Triplestores
  • Embedded Triplestores
• Shared Packages
• How to Add an API Route
  • Write SPARQL templates
  • Write Responder Request and Response Messages
  • Write a Responder
  • Write a Route
• Triplestore Updates
  • Requirements
  • Design
  • SPARQL Update Examples
• Consistency Checking
  • Requirements
  • Design
• Authentication in the Knora API Server
  • Scope
  • Implementation
  • Usage
• Administration (Users, Projects, Groups, Institutions, Permissions)
  • Scope
  • Implementation
  • Overview
  • Permissions
  • Implicit Permissions
  • Permission Templates
  • Default Permissions Matrix for new Projects
  • Basic Workflows involving Permissions
  • Implementation
  • Use Cases
  • Webapi Components
  • Redesign / Questions June 2016
• Plans for Knora API v2
  • Naming
  • Structure
  • Redundancy
  • Efficiency
  • Suitability for non-GUI applications
  • Working with multiple projects
  • Annotating values
  • Typing
  • JSON-LD