Skip to content

Latest commit

 

History

History
68 lines (48 loc) · 3.91 KB

File metadata and controls

68 lines (48 loc) · 3.91 KB

Activity Content Specification

Version 1.3.0

Content references shared via the DSNP consist of URLs pointing to documents containing Activity Streams JSON objects. For the purposes of the DSNP, restrictions are placed on the Activity Streams 2.0 specification.

JSON-LD and Activity Streams

All DSNP Activity Content is compatible with the Activity Streams 2.0 specification. While there are some DSNP extensions, they are guaranteed to use non-colliding terms. Therefore, the JSON-LD @context field is set to https://www.w3.org/ns/activitystreams according to Activity Streams 2.0 §2.1.

Core Activity Content Types

DSNP uses only the following content types at the root level:

Name Description DSNP Announcements
Note standard user content Broadcast, Reply, Update
Profile user profile content Profile

Associated Types

Name Description Specification
Location add a location to content Activity Vocabulary
Tag add a tag to content Activity Vocabulary
Attachments supported attachment types Activity Vocabulary
Hash content validation hash DSNP Extension

Supported URL Schema

URLs in DSNP-compatible Activity Content MUST use one of the following URL schemes:

Scheme Description Reference DSNP Version Added
HTTPS Hypertext Transfer Protocol Secure RFC2818 1.0
HTTP Hypertext Transfer Protocol RFC2616 1.0

Libraries

Name Language(s)
LibertyDSNP/activity-content JavaScript/TypeScript
LibertyDSNP/activity-content-java Java/Kotlin
LibertyDSNP/activity-content-swift Swift

Releases

Version Description Release Date Changelog
1.3.0 DIP-257 2024-09-17 Changelog
1.2.0 DIP-210 2023-04-11 Changelog
1.1.0 DIP-158 2022-05-05 Changelog
1.0.0 Initial Release 2021-09-09 Changelog

Non-Normative

Additional Fields

Implementers may choose to support more of the Activity Streams standard as long as it does not conflict with this specification, but should note that other implementations may not recognize those additions. Implementers who extend their support for Activity Streams objects beyond the subset defined here do so at their own risk.