W3C home > Mailing lists > Public > public-schemaorg@w3.org > August 2019

Re: Using Comment to indicates comments

From: Benjamin Young <byoung@bigbluehat.com>
Date: Wed, 21 Aug 2019 13:51:04 +0000
To: Mark Nottingham <mnot@mnot.net>, Marijane White <whimar@ohsu.edu>
CC: schema.org Mailing List <public-schemaorg@w3.org>
Message-ID: <DM5PR06MB3401AC59F734189DFE3318B2B2AA0@DM5PR06MB3401.namprd06.prod.outlook.com>
Hey Mark,

Would something like this work for your use case?

"""
<html>
<body itemscope itemtype="http://schema.org/WebPage">
<div>
  <h3>Comments</h3>
  <div class="comment_css" itemprop="comment">
  [ first comment ]
  </div>
  <div class="comment_css" itemprop="comment">
  [ second comment ]
  </div>
  <div class="add_comment_css">
  [ add a comment UX ]
  </div>
 </div>
</body>
</html>
"""

If the repetition is bothersome, you could use `itemprop="comment"` for styling and get rid of the `class="comment_css"`.

That works fine in the Structured Data Testing Tool, fwiw https://search.google.com/structured-data/testing-tool


However, if you're wanting a list of comments that's a distinct thing separate from the thing being commented upon (i.e. not expressed as a property, but as it's own collection), then using something like CreativeWorkSeries could work...but the markup would certainly be more "chatty."

Hope that helps!
Benjamin



--

http://bigbluehat.com/


http://linkedin.com/in/benjaminyoung


________________________________
From: Mark Nottingham <mnot@mnot.net>
Sent: Tuesday, August 20, 2019 11:08 PM
To: Marijane White <whimar@ohsu.edu>
Cc: schema.org Mailing List <public-schemaorg@w3.org>
Subject: Re: Using Comment to indicates comments

Hi Marijane,

I'm trying to avoid requiring people to mark up each individual comment; that might be seen as onerous.

Conversation is very close to what I'm looking for -- thanks for that reference!  It seems, however, that it is intended to hold Message, whereas there's no equivalent container for Comment. On the face of it, it seems odd to put Comment inside of Conversation -- at least as things are currently defined.

Cheers,


> On 21 Aug 2019, at 9:31 am, Marijane White <whimar@ohsu.edu> wrote:
>
> Mark,
>
> Since a Comment is a CreativeWork, could you use Comment to mark up each individual comment and then use hasPart/isPartOf to relate them to a set of comments as a CreativeWorkSeries?  Or, since CreativeWorkSeries is kind of an abstract class used to organize its subtypes, perhaps a set of comments could be a Conversation, which also can be used with hasPart/isPartOf?
>
>
> Marijane White, M.S.L.I.S.
> Data Librarian, Assistant Professor
> Oregon Health & Science University Library
>
> Phone: 503.494.3484
> Email: whimar@ohsu.edu
> ORCiD: https://orcid.org/0000-0001-5059-4132
>
>
> ´╗┐On 2019/08/19, 4:12 PM, "Mark Nottingham" <mnot@mnot.net> wrote:
>
>    Hello,
>
>    Is this community alive?
>
>    Cheers,
>
>
>> On 28 Jun 2019, at 2:22 pm, Mark Nottingham <mnot@mnot.net> wrote:
>>
>> Hi schema folk,
>>
>> I've been looking for a way to indicate what parts of a Web page are comments; see <https://discourse.wicg.io/t/proposal-comments-element/3483> for the use case.
>>
>> I see that something in this area is already defined at <https://schema.org/Comment>, but it's not quite what I'd like; I want to mark the *set* of comments + commenting UX, not just an individual comment.
>>
>> Would it be horribly abusive if a page were to do something like:
>>
>> """
>> <div itemscope itemtype="http://schema.org/Comment">
>>
>> <h3>Comments</h3>
>>
>> <div class="comment_css">
>> [ comment ]
>> </div>
>>
>> <div class="comment_css">
>> [ comment ]
>> </div>
>>
>> <div class="add_comment_css">
>> [ add a comment UX ]
>> </div>
>>
>> </div>
>> """
>>
>> ?
>>
>> Is there a better way to do this (including defining a new type)?
>>
>> Cheers,
>>
>>
>> --
>> Mark Nottingham   https://www.mnot.net/

>>
>>
>
>    --
>    Mark Nottingham   https://www.mnot.net/

>
>
>
>

--
Mark Nottingham   https://www.mnot.net/



Received on Wednesday, 21 August 2019 13:51:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:48 UTC