Socialwg/Social syntax requirements
< Socialwg
Requirements for a social syntax
- Represent entities such as
- People
- Groups / Organizations
- Projects
- Events
- Places
- Applications
- Relationships / Affiliations (interpersonal, organizational)
- Roles (social, organizational)
- Activity / Action ( "{agent} {verb} {object}" )
- Completed / On-going Activity ("John uploaded a photo", "Sally is watching a movie")
- Potential Actions (like, share, pin, save, approve, reject )
- Ability to Represent a wide range of content such as
- Text
- Images
- Video
- Sound
- Ability to Represent "semantic content" such as
- Articles
- Badges
- Status Updates
- Albums
- etc..
- Represent a wide range of social activities, such as
- CRUD for content (create, upload, update, delete)
- Response-To/Promotion-of content (comments, likes, recommends, shares)
- Relationship management (follow, friend, join/leave group)
- Workflow (submit, approve, reject, review)
- Event RSVP
- Abuse/inappropriate reporting
- Extensible for
- new types / specializations of agents
- new types / specializations of content
- new types / specializations of activities
- domain or application specific requirements
- Universal identifiers
- Preferably URIs/IRIs
- Use JSON primarily or have a JSON encoding
- Re-use of existing "paved roads" (leveraging existing work)
- Support for both Syntax and Semantics-based processing
- Geosocial support
- Location of objects
- Location of agents
- Location of activity
- Royalty-free license
Non-Requirements for a social syntax
- Non-JSON encodings
- "Kitchen Sink" entity schema definition
- (please list others)