Open trieloff opened 6 years ago
@trieloff Nino Walker and I have been talking about this in email and it's a complex problem since in some systems a comment's body can have any type of UGC present - and then how is it not an asset (or something large in itself). Definitely glad you put this back in play...but I don't see us resolving this one soon.
Also DC has chosen to punt on these for our June release (for this and other reasons)
Summoning @ninowalker
in some systems a comment's body can have any type of UGC present - and then how is it not an asset (or something large in itself).
I'd see two ways to start here:
author + time + comment + extra
and we gradually let extensions define extra
, starting without any extra
s like attachments, links, etc.author + time + content
, and we start by defining different types of content
, including plain comment, file, etc.the problem that @ninowalker and I identified is that comment/content is the same thing, since even just supporting "rich text markup" (eg. bold, italics) on your comments - which some might say is table stakes - makes it content and not comment (in your definition). The W3C has great work here on schemas for comments and it is what I plan to use as the basis - but as it is general purpose, it needs some tightening into our usage...
From the discussion in #53 an important side-track has spun up:
This is coming just at the right time, because the type of comment that I had in mind when I suggested
/content/usergenerated-comment.schema.json
is a type of user generated content that you would make as a reader in response to a blog post or facebook post. (the stuff that people refer to when they say "always skip the comments")The type of comment that @lrosenth seems to have in mind is more an editorial comment that is part of the production of an asset (but can also be applied to content, as illustrated by annotations in AEM).
It is clear that we have another example of the duality that we've already seen between @noahe's collaboration profile and @kstreete's customer/visitor profile.
Let's identify the commonalities and differences between the approaches taken in collaboration systems and moderation systems and define a schema for user-generated content comments, as opposed to the collaboration comments defined in #65 – but ideally with enough overlap and use of a common base model like the W3C Annotation Model