Do a SWOT analysis of the product

[satazor]

No description provided.

[marcooliveira]

I put this under https://github.com/ipfs-shipyard/discussify/blob/master/doc/project/design/planning/swot.md, but it's still not complete.

What's missing:

1. Fill opportunities.
2. Weight each factor (give it some numerical weight).
3. Map Opportunities/Threats to our Strenghts/Weaknesses.
4. Draw conclusions from this analysis.

[marcooliveira]

I'll take care of filling the missing info, we need to get our conclusions very soon.

[lidel]

Hi, I just noticed this repo, not sure if timing is right or if its useful at all, but below are some additional data points for SWOT Threats/Opportunities sections:

• Open Annotation Collaboration community created some W3C Drafts relevant to this endeavor around 2013.
• W3C Web Annotation Working Group was created, improved on drafts and published as Recommendations in 2017:

  • Web Annotation Data Model—specification describes a structured model and format, in JSON, to enable annotations to be shared and reused across different hardware and software platforms. Common use cases can be modeled in a manner that is simple and convenient, while at the same time enabling more complex requirements, including linking arbitrary content to a particular data point or to segments of timed multimedia resources.
  • Web Annotation Vocabulary—specifies the set of RDF classes, predicates and named entities that are used by the Web Annotation Data Model. It also lists recommended terms from other ontologies that are used in the model, and provides the JSON-LD Context and profile definitions needed to use the Web Annotation JSON serialization in a Linked Data context.
  • Web Annotation Protocol—describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.

• W3C also produced two additional Working Group Notes relevant to the problem space:

  • Embedding Web Annotations in HTML—describes and illustrates potential approaches for including annotations within HTML documents. Examples also are included illustrating the use within an HTML document of annotation Selectors as fragment identifiers.
  • Selectors and States—selecting part of a resource on the Web is an ubiquitous action. This document does not define any new approach to selection; instead, it relies on the formal specification and the semantics in the Web Annotation Data Model. The current document only “extracts” Selectors and States from that data model; by doing so, it makes their usage easier for applications developers whose concerns are not related to annotations.

• Hypothes.is is probably the most relevant entity in open annotation space today
  • it is based on the Annotator project and annotation standards mentioned above
  • model is similar to Discussify: web + browser extension, but is based on centralized services for annotation storage and identity management

I imagine the biggest innovation IPFS can bring is in data and identity decentralization, providing alternative to REST-based "The Web Annotation Protocol".

That being said, we might want to look into "Web Annotation Data Model" and linked Working Group Notes and see if it makes sense to adopt existing standards or at least provide a compatible import/export.
I would love to have ability to export my annotations from centralized hypothes.is into IPFS-based alternative :)

[ghost]

@lidel Thanks for this! Me and @satazor went back from vacations today, I'll have a look on these examples. Actually I was already using Hypothes.is as the main competitor, @diasdavid mentioned it before once we looked at it as a new feature for the app.