The mystream from akarakoc

Eliminating duplicate tags from tags list

Preparing a research document

Research document will be prepared about
W3C Activity Stream
W3C Web Annotation Data Model
Wikidata

Adding Useful Resources to the Wiki Home Page

Useful resources that are used and will be used will be added to the Wiki Home page.

Wikidata Research Revision

Wikidata Research paper will be reviewed.

Creating user scenario for Web annotation

User scenarios for web annotation will be created.
Be aware of the templated provided for professor on Assignment 3 .

Creating Use Case Diagrams 2

Use case diagrams will be created for the requirements for requirements between 16 and 29

Activity items, discussions and agenda will be put together in first meeting report

Annotation Creation Front End Design

Creatng annotation popup and saving basic annotation object via Rest API

Mockup designs

We will create mockups to understand whether our understandigs meet the expectations or not.

Creating Use Case Diagrams 1

Use case diagrams will be created for the requirements for requirements between 1 and 16

Activity items will be added to the first meeting report

Deploy annotation web service to remote server

Prepare a remote server in heroku or aws, deploy web service and make it runnable via http requests from django web project.

Creating Requirements.txt

Requirements.txt will be created and committed and updated for each new library added in the project and installed in project environment.

Solve Cross Origin Problem between Annotation server and front-end

Software Requirement Specification Review

Software requirements and mockups would be reviewed and enhanced based on the feedbacks from last week.
More detailed version of the mockups ( previous screen and last screen parts will be prepared ).

Creating Sequence Diagrams 3

Creating Sequence Diagrams between requirements 28 and 37.

Create new project for annotation server

Create new project for annotation server on github. Add Ali Karakoç, Tutku Bayrı and Suzan Üsküdarlı on this project.

Convert annotation search as like search

Creating scenarios

We need to create 3 scenarios for doing mockups according to them.

Complaint type posts

People can enter complaint type posts

Creating Sequence Diagrams 2

Creating Sequence Diagrams between requirements 16 and 27.

Creating user scenario for Activity Stream

User scenarios for web activity stream will be created.
Be aware of the templated provided for professor on Assignment 3 .

Creating a new branch for activity stream

Searching for django activity stream

Searching for implementation of django activity stream

Research on W3C Web Annotation Data Model

W3C Web Annotation Data Model will be investigated and the idea behind it will be understood to proceed on project.

Activity Stream Structure

I searched about django.actstream but it uses a library called "django.utils.six" and it is not supported in Django 3.

I found an alternative way that has these steps:

Creating a table that has an integer field as primary key and a JSON field.
In backend, in every action like create, join, follow and likewise will save to the table that is mentioned above by using W3C structure of activity stream.

Is it correct to follow this way? If not which way I can follow to create activity streams?

Creating Sequence Diagrams 1

Creating Sequence Diagrams between requirements 1 and 15.

Creating Class Diagram

Class diagram for the project will be created.

Search post & posttype utility

Search utility will be implemented on posttypes and posts

Research on W3C Activity Stream

There will be a research activity to understand how Activity Stream works.

Completing supported types of posts

The posts will support w3c primitive types

Prepare search operations for annotation service

Make search n postgre db for annotations via web service takin json input and returning response as json document

Creating Use Case Diagrams 3

Use case diagrams will be created for the requirements for requirements between 30 and 37

Creating user scenario for Wikidata

User scenarios for wikidata will be created.
Be aware of the templated provided for professor on Assignment 3 .

Research on Wikidata

Wikidata will be used in the project and its need to be make a research about it!

Discussion about policy for closing an issue

Discussion about policy for closing an issue will be held under this issue.

Prepare remote database for annotation server

Postgre database will be used in annotation server, remote service will be prepared and configured.

Search Community Utility

Community search feature will be implemented

Discussion about working principles

Discussion about working principles will be held under this issue.

Project kick-off meeting and planning

To determine the path that will be followed during the project initial short kick-off meeting will be set Thursday 13 Feb 2020

Preparing software requirement spesifiction

We will prepare software requirement spesification document.

List Requirements of the Project

Listing functional and non-functional requirements of the project.

Fixing properties of Annotation in json-ld

Hello @uskudarli ,

We prepare a sample json-ld structure in order to save annotation.

Based on the W3C standards, we have to define a list of properties, but I could not clearly understand the required value types for the properties on json-ld.

"textAnno" :  {
    "id": "http://example.org/anno1",
    "type": ["Annotation"],
    "motivation": ["tagging", "commenting"],
    "annotatedBy": {
      "id": "http://example.org/agent1",
      "type": "Text",
      "name": "A. Person",
      "nick": "agent1"
    },
    "body": [
      {
        "type": "Text",
        "related": "http://dbpedia.org/resource/London"
      },
      {
        "type": "Text",
        "value": "One of my favorite cities",
        "format": "text/plain",
        "language": "en"
      }
    ],
    "target": [{
      "id": "http://example.org/sptarget1",
      "type": "Text",
      "source": "http://example.org/source1",
      "selector": {
        "id": "http://example.org/selector1",
        "type": "Text",
        "start": 4096,
        "end": 4104
      }
    }]
  }

Have some questions based on the w3c documentation.

Q1- Should we store class names in Type parameter ? May these class names custom defined classes in our project ? Should we provide a web IRI for them ?

Q2 - Will these be changed for type in each property ie. type of annotation, type of annotatedBy ? Should we limit class names for each property on backend?

Q4 - How should we interpret the explation below ? It is quoted from w3c documentation. I try to look at each parameter of each property ( id of annotation is different than id of body ).

Is it nullable or not ? Is is variable or list ?
format
Property
The format of the Web Resource's content.
The Body or Target should have exactly 1 format associated with it, but may have 0 or more.
The value of the property should be the media-type of the format, following the [rfc6838] specification.

Q5 - How could we set value to id properties ? These should be IRI value.

I annotate a "cat" word with an image on the web.
Target would be like below.

"target": [{
      "id": "???????", ------------------- May it be Url locating the word "cat" ? 
      "type": "Text",
      "source": "???",------------------- May it be  same with id value ?
      "selector": {
        "id": "???",----------------------- I think I could use predefined selector class name ?
        "type": "Text",
        "start": 4096,
        "end": 4104
      }
    }]

Q6 - Is there any difference between storing id property as "id" and "@id" ? This changes for each property of json-ld and stated differently in different samples.

These are the questions arising during development.

fyi : @akarakoc and @tutkubayri

Regards,

Melike,