- Loosening restrictions when using /argument POST route
- :text is now only needed when an :identifier is not provided
- :identifier can be used to create an argument with an existing statement. All other fields of premise or conclusion are ignore when :identifier is present
- Change versioning scheme. Semantic is bad style
- Rework API to be easier to use when adding stuff
- Tags are now supported as special data on statements
- New route
statements/by-tag
enables searching for statements by tag strings
- Adding a reference per API now only requires a text. If host and/or path are not given, the data sent via referer is added.
- Return all links instead of local ones for /links
- Use all links instead of local ones for arguments
- Refactor statements to have a list of
:references
instead of a single one. - Correctly handle
:predecessors
inside statements now - Automatically fetch
:references
if statements are coming from D-BAS
- Fix wrong adding of arguments
- Add route to fetch all arguments
- Add route to get arguments by a certain author (by name)
Major Changes with 0.3
- The user is not a simple String anymore. The user is now a map containing the public Screenname (
:name
), the:id
and thedgep-native
flag which is set when the user is native to the aggregator stated inidentifier.aggregator-id
. - Shorthands for adding statements and whole arguments just by text all accept a author-id and assume the author is local to the current DGEP instance.
- Shorthands for adding arguments and statements now accept additional fields trhough the
additional
map. You can add any custom field there. Attributes added here will be first-class on the resulting statements. This means that addingadditional: {"foo" "bar"}
will add a field:foo
with the valuebar
to the resulting statement. - Added support for first-class reference search.
- A
reference
field is expected to contain a:text
,:host
and:path
- References can be searched by host- and text-content in the corresponding routes (See
/index.html#!/statements
for an overview)
- A
- Other custom fields can be searched via
/statements/custom
- A bug with the DBAS-Connector has been fixed and now again produces correct links.