[wp-trac] [WordPress Trac] #40031: Consider Adding Web Annotations to WordPress

[WordPress Trac]

#40031: Consider Adding Web Annotations to WordPress
-----------------------------+------------------------------
 Reporter:  MikeSchinkel     |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Comments         |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui
-----------------------------+------------------------------

Comment (by MikeSchinkel):

 Replying to [comment:3 dshanske]:
 > ''"Annotation to me sounds like a type of comment where you are
 specifying a specific part of a post to comment on. It would therefore not
 be displayed at the bottom, but inline in some fashion."''

 Annotations can be either of those.  And they can be many other things
 too.  Highly recommend reading about the [https://www.w3.org/TR/2017/REC-
 annotation-model-20170223/ Annotations Data Model] if this ticket
 continues to interest you.

 > ''"I think this is the wrong approach for WordPress Core in the short
 term. if WordPress wants to start with annotations, how about we enhance
 the comment system to support annotations?"''

 I am assuming you made this comment because of an assumption that Web
 Annotations refers to being able to select a section of content and then
 comment on that content?

 Yes, that use-case is addressed by Web Annotation, but Web Annotations is
 ''(IMO at least)'' more about establishing a JSON format for linking
 between annotation and the subject of the annotation, and thus about
 enabling additional storage '''the fact that such an annotation exists'''
 in a location different than where the annotations or the subject of the
 annotation is currently stored.

 Or in less abstract terms, Web Annotations is about enabling a website to
 serve a feed of Web Annotations one of which might look like this:

 {{{
 {
   "@context": "http://www.w3.org/ns/anno.jsonld",
   "id": "https://david.shanske.com/annotation-3264",
   "type": "Annotation",
   "motivation": "replying",
   "body": "https://david.shanske.com/2016/11/28/cbss-elementary-gets-
 kosher-wrong/",
   "target": [
     "https://david.shanske.com/2016/11/28/cbss-elementary-gets-kosher-
 wrong/#comment-3264",
 "https://www.facebook.com/dshanske/posts/1188775184544354?comment_id=1188793234542549"
   ]
 }
 }}}

 > ''"While support for custom comment types is a 'blessed' task, we still
 don't have that."''

 No reason this ticket could not be the catalyst to make that blessed task
 a higher priority.  It might even inform the design of comment types by
 providing some insight into use-cases.

 > ''"So, having annotations as a built-in comment type would allow someone
 to annotate a post/page/etc. Now, that's initially a local implementation,
 not a distributed one. But from the perspective of site owners, you should
 always have a local implementation of a feature before you start fetching
 stuff from other sites. A base feature should be built in, and only
 enhanced by an outside site or service."'' ... I may be on a completely
 different line of thought than the initial proposal, but I feel strongly
 about local first as a building philosophy.

 You have made an philosophical argument but it is too abstract to prove or
 disprove. And thus I think debating it distracts from the specific use-
 cases and requirements we could be discussing.

 Let us first make sure we all understand what is being proposed and what
 the goals of the proposal are and then discuss if those goals are
 appropriate before we debate philosophy of implementation? The former
 really should inform the latter.  Otherwise we'll just be talking past
 each other.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40031#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform