diff --git a/docs/01-introduction/standoff-rdf.md b/docs/01-introduction/standoff-rdf.md index 8aba511349..e732815ea4 100644 --- a/docs/01-introduction/standoff-rdf.md +++ b/docs/01-introduction/standoff-rdf.md @@ -19,7 +19,7 @@ License along with Knora. If not, see . # Standoff/RDF Text Markup -[Standoff markup](http://uahost.uantwerpen.be/lse/index.php/lexicon/markup-standoff/) +[Standoff markup](https://lexiconse.uantwerpen.be/index.php/lexicon/markup-standoff/) is text markup that is stored separately from the content it describes. Knora's Standoff/RDF markup stores content as a simple Unicode string, and represents markup separately as RDF data. This approach has some advantages over commonly used markup systems diff --git a/docs/03-apis/api-v1/authentication.md b/docs/03-apis/api-v1/authentication.md index 2fad561944..7c718546fd 100644 --- a/docs/03-apis/api-v1/authentication.md +++ b/docs/03-apis/api-v1/authentication.md @@ -48,7 +48,7 @@ There are two possibilities to do so: when doing a HTTP request to the API When using Python's module `requests`, the credentials (email / password) can simply be submitted as a tuple with each request using the param `auth` ([python - requests](http://docs.python-requests.org/en/master/user/authentication/#basic-authentication)). + requests](https://2.python-requests.org/en/v2.8.1/user/authentication/#basic-authentication)). An alternative way for accessing all routes is to simply supply the *email* and *password* credentials on each request either as URL diff --git a/docs/05-internals/design/principles/design-overview.md b/docs/05-internals/design/principles/design-overview.md index c4ab8ce856..64009b7b81 100644 --- a/docs/05-internals/design/principles/design-overview.md +++ b/docs/05-internals/design/principles/design-overview.md @@ -69,7 +69,7 @@ API v2, but API v2 does not depend on API v1. ### HTTP Module -- `org.knora.webapi.routing`: Knora's [Akka HTTP](https://akka.io/akka-http/) routes. +- `org.knora.webapi.routing`: Knora's [Akka HTTP](https://doc.akka.io/docs/akka-http/current/index.html) routes. Each routing class matches URL patterns for requests involving some particular type of data in the repository. Routes are API-specific. For example, `ResourcesRouteV2` matches URL paths starting with `/v2/resources`, which