DOC: fix urls

README_SETUP.md

@@ -211,7 +211,7 @@ Stand-alone documentation is built using Sphinx: `make doc`
     (`l_` not found):
 
 ```sh
-git clone git@github.com:simgrid/javasphinx.git
+git clone https://github.com/simgrid/javasphinx.git
 cd javasphinx
 git checkout 659209069603a
 pip3 install .

src/doc/CaosDB-Query-Language.md

@@ -120,11 +120,11 @@ Examples:
 
 ##### `d1>d2`: Transitive, non-symmetric relation.
 Semantics depend on the flavors of d1 and d2. If both are... 
-###### [UTCDateTime](Datatype#datetime) 
+###### [UTCDateTime](specification/Datatype.html#datetime) 
 * ''True'' iff the time of d1 is after the the time of d2 according to [UTC](https://en.wikipedia.org/wiki/Coordinated_Universal_Time).
 * ''False'' otherwise.
 
-###### [SemiCompleteDateTime](Datatype#datetime)
+###### [SemiCompleteDateTime](specification/Datatype.html#datetime)
 * ''True'' iff `d1.ILB>d2.EUB` is true or `d1.ILB=d2.EUB` is true.
 * ''False'' iff `d1.EUB<d2.ILB}} is true or {{{d1.EUB=d2.ILB` is true.
 * ''Undefined'' otherwise.
@@ -142,11 +142,11 @@ Examples:
 
 ##### `d1<d2`: Transitive, non-symmetric relation.
 Semantics depend on the flavors of d1 and d2. If both are... 
-###### [UTCDateTime](Datatype#datetime)
+###### [UTCDateTime](specification/Datatype.html#datetime)
 * ''True'' iff the time of d1 is before the the time of d2 according to [UTC](https://en.wikipedia.org/wiki/Coordinated_Universal_Time)
 * ''False'' otherwise.
 
-###### [SemiCompleteDateTime](Datatype#datetime)
+###### [SemiCompleteDateTime](specification/Datatype.html#datetime)
 * ''True'' iff `d1.EUB<d2.ILB` is true or `d1.EUB=d2.ILB` is true.
 * ''False'' iff `d1.ILB>d2.EUB}} is true or {{{d1.ILB=d2.EUB` is true.
 * ''Undefined'' otherwise.
@@ -164,7 +164,7 @@ Examples:
 
 ##### `d1 IN d2`: Transitive, non-symmetric relation.
 Semantics depend on the flavors of d1 and d2. If both are... 
-###### [SemiCompleteDateTime](Datatype#datetime)
+###### [SemiCompleteDateTime](specification/Datatype.html#datetime)
 * ''True'' iff (`d1.ILB>d2.ILB` is true or `d1.ILB=d2.ILB` is true) and (`d1.EUB<d2.EUB` is true or `d1.EUB=d2.EUB` is true).
 * ''False'' otherwise.
 
@@ -177,7 +177,7 @@ Examples:
 
 ##### `d1 NOT IN d2`: Non-symmetric relation.
 Semantics depend on the flavors of d1 and d2. If both are... 
-###### [SemiCompleteDateTime](Datatype#datetime)
+###### [SemiCompleteDateTime](specification/Datatype.html#datetime)
 * ''True'' iff `d1.ILB IN d2.ILB` is false.
 * ''False'' otherwise.
 

src/doc/roles.md

@@ -32,4 +32,4 @@ There are some special roles, which are automatically assigned to users:
 
 Except for the `anonymous` role, these special roles are not returned by the
 server, but can nevertheless be used to define
-[permissions](permissions).
+[permissions](permissions.html#permissions).

src/doc/specification/AbstractProperty.md

@@ -132,14 +132,13 @@ Any xml representation of an `AbstractProperty` that is to be posted to the Caos
 #### Get all
 *Request:*
 
-        GET http://localhost:8122/mpidsserver/AbstractProperty/
-        GET http://localhost:8122/mpidsserver/AbstractProperty
+        GET http://localhost:8122/server/AbstractProperty/
+        GET http://localhost:8122/server/AbstractProperty
 
 *Response:*
 
         <?xml version="1.0" encoding="UTF-8"?>
         <Response />
-[View Ticket #2](http://dev.bmp.ds.mpg.de/heartdb/ticket/2)
 #### Erroneous Requests
 ##### Non-existing
 *Request:*

src/doc/specification/Datatype.md

@@ -43,7 +43,7 @@
 ----
 
 ## DATETIME
-The DateTime data type exists in (currently) three flavors which are dynamically chosen during parsing on the the serverside. The flavors have different ranges, support of time zones and intended use cases. Only the first two flavors are actually implemented for storage and queries. The third one is implemented for queries exclusively.
+The DateTime data type exists in (currently) three flavors which are dynamically chosen during parsing on the serverside. The flavors have different ranges, support of time zones and intended use cases. Only the first two flavors are actually implemented for storage and queries. The third one is implemented for queries exclusively.
 
 ### UTCDateTime
 * Description: This DATETIME flavor stores values which represent a single point of time according to [UTC](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) with the format specified by [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) (Combined date and time). It does support [UTC Leap Seconds](https://en.wikipedia.org/wiki/Leap_second) and time zones.
@@ -55,7 +55,7 @@ The DateTime data type exists in (currently) three flavors which are dynamically
   * It is allowed to ommit the nanosecond part of a UTCDateTime (`2016-01-01T13:23:00CEST`). This indicates a precision of seconds for a UTCDateTime value.
 
 ### Date
- Description:: This DATETIME flavor stores values which represent a single date, month or year according to the [gregorian calendar](https://en.wikipedia.org/wiki/Gregorian_Calendar). A month/year is conceived as a single date with the presion of a month/year. This concept is useful if you try to understand the query semantics which are explained [elsewhere](./QueryLanguage#POVDateTime).
+ Description:: This DATETIME flavor stores values which represent a single date, month or year according to the [gregorian calendar](https://en.wikipedia.org/wiki/Gregorian_Calendar). A month/year is conceived as a single date with the presion of a month/year. This concept is useful if you try to understand the query semantics which are explained [elsewhere](../CaosDB-Query-Language.html#pov-property-operator-value).
  Format:: `Y[YYY][-MM[-dd]]` (where square brackets mean that the expression is optional).
  Range:: Any valid date according to the gregorian calendar from `-9999-01-01` to `9999-12-31` (and respective dates with lower precision. E.g. the year `-9999`). There is no year `0`.
 * Note: Date is a specialization of [#SemiCompleteDateTime]. 
@@ -73,7 +73,7 @@ Please file a new feature request as soon as you need them.
 ----
 
 ## REFERENCE
-* Description: REFERENCE values store the [Valid ID](./Glossary#valid-id) of an existing entity. The are useful to establish links between two entities. 
+* Description: REFERENCE values store the [Valid ID](../Glossary#valid-id) of an existing entity. The are useful to establish links between two entities. 
 * Accepted Values: Any [Valid ID](./Glossary#valid-id) or [Valid Unique Existing Name](./Glossary#valid-unique-existing-name) or [Valid Unique Temporary ID](./Glossary#valid-unique-temporary-id) or [Valid Unique Prospective Name](./Glossary#valid-unique-prospective-pame).
 * Note:
   * After beeing processed successfully by the server the REFERENCE value is normalized to a [Valid ID](./Glossary#valid-id). I.e. it is guaranteed that a REFERENCE value of a valid property is a positive integer.

src/doc/specification/RecordType.rst

@@ -190,8 +190,6 @@ Get all
    <?xml version="1.0" encoding="UTF-8"?>
      <Response />
 
-[View Ticket #2](http://caosdb.example.com/caosdb/ticket/2)
-
 
 POST Requests
 ~~~~~~~~~~~~~