Weekly Lecture Notes - SWE-574-Spring-2018/LinkyWay GitHub Wiki

Week 2

Coherent issue tags can be grouped using prefixes (bug-wontfix, priority-high etc.).
Assignee list should be kept as short as possible (to ease up status tracking).
References for external resources should be stated explicitly.
Deadlines should be made clear for issues and action items.
Query language is proposed by Suzan Üsküdarlı. (SparkQl)

Discover isn't enough to define functionality of the application.
Give a shot to Slack??
Multiple deliverables can be gathered in single milestone.
Tweets or pictures also shall be able to be annotated by user. (W3J specification standards are crucial)
Node character count must be constrainted.
Nodes must be unique and splitted.
Moderator system can be used.
Multiple wiki annotations should be possible on single node.
Anno4J - Java library / Triplet <Subject, Predicate, Object>
Everyone should research about web annotation.
There must be seperate DBs for web application and annotations. (LD protocol)
Edges cannot be annotated via tweets. (Requirement 5.1 has to be changed)
Next week's tasks: 1) to prepare user scenarios. 2) Finalize project plan.

Tweets don't have to be annotations.
Body : content; Target: tweets or nodes
WikiData annotation is user's job.
Properties will be searched from WikiData.
Mockup process should be started.
A text may be notated at simple HTML page. (Suzan Üsküdarlı sends practice material to Piazza)
Selector standards (both for image andf text) must be researched W3C standards.
Web Annotation Vocabulary must be studied.