Description
The "comment" object type represents a textual response to another object. For the spec on this section http://martin.atkins.me.uk/specs/activitystreams/activityschema#comment
Properties
Property name | Type | Required | Property Description | JSON field | Atom field | RSS field |
---|
title |
string |
yes |
The subject of the comment -- not common
|
displayName |
atom:title |
|
content |
string |
no |
The entire comment
|
content
|
atom:content |
|
owner |
object |
no |
Entity who wrote the comment if different than actor. Usually the object type is a person |
?? |
atom:author |
|
id |
string |
yes |
Unique id for the object. Must be different than the activity id |
id |
atom:id |
|
url |
URI |
yes |
Permalink to an html containing the comment
|
permalinkUrl |
atom:link rel="alternate" |
|
published |
W3CDTF timestamp |
no |
Time the object was created |
published |
atom:published |
|
related links |
array |
no |
Related links |
links |
atom:link rel="related"
|
|
Verbs
Does this object relate to only certain kinds of verbs? If so, please list them and link to the appropriate page on the wiki.
URI
What is the URI for the object? Most URIs will be in the form:
http://activitystrea.ms/schema/1.0/comment
Examples
Provide examples of the object being used in context.
Notes
Provide any useful notes or hints about this object.
Implementations
Where is this object implemented? Please list all known implementations with links to the relevant API documentation.
Maintainers
Who maintains this page, or should be contacted if there are questions or feedback?
User Interface Examples
- What are the best of breed user interfaces / experiences that existing sites use to show a specific "comment" activity along with any context, e.g. possibly:
- what the comment was in-reply-to
- follow-ups to the comment
- how does the permalink for the comment represent the comment itself rather than the thing the comment was about (or follow-ups)
- current examples as a basis for discussion
- Twitter: @-reply to a previous tweet
- ...
Comments (0)
You don't have permission to comment on this page.