Developer Hub
Relation ProtocolRelation ONE APIRelation Graph API
English
English
  • Overview
  • QUICK START
    • Deploy a Semantic SBT contract leveraging Relation Protocol
    • Deploying query services using Graph Indexer
  • KEY CONCEPTS
    • RDF
    • Semantic SBTs
    • Social Graph
  • Architecture
  • Schema Standard
    • Overview
    • How schemas limit smart contracts
    • Store schema
    • List of schemas
  • Contract Open Standard
    • Overview
    • Identity
      • Name Service
    • Relationship
      • Follow
      • Dao
    • Publication
      • Content
      • Privacy Content
  • Open Standard API
    • Introduction
    • EIP-6239
    • Business Interface
      • Identity
      • Relationship
      • Publication
  • Graph Indexer
    • Definition and usage
    • Listen to events
    • To parse RDF data
    • To build a social graph
  • Integrations
    • Quick start
    • Construct a social graph with Relation Protocol
    • List of resources
    • NameService contract guide
    • Follow contract guide
    • Dao contract guide
    • Content contract guide
    • PrivacyContent contract guide
  • Relation Name Service
    • Name Service Api
  • Use Case
  • APPENDIX
    • Deploy a contract using Hardhat
    • SemanticSBT Deployment tool
Powered by GitBook
On this page
  • Identity
  • Relationship
  • Publication
  • Scenario Extension
  1. KEY CONCEPTS

Social Graph

Last updated 2 years ago

Social Graph refers to a graph that represents social relationships between entities, which is a model of a social network. In the Relation Protocol, the Social Graph is composed of social data stored in numerous Semantic SBTs in a graph database. The Social Graph in the Relation Protocol has the following predefined scenarios:

  • Identity

  • Relationship

  • Publication

Identity

In the Relation Protocol, identity is composed of a Relation Name Service and several Semantic SBTs used to describe identity.

The identity design of the Relation Protocol is scalable. In the Relation Protocol, all contracts that conform to the Contract Open Standard and describe identity will have their RDF data parsed as part of user identity. In this way, we hope that all developers can participate in the construction of the decentralized network's identity system.

Relationship

In the Relation Protocol, relationships represent social connections between entities. In certain specific scenarios, relationships will be used to define permissions, such as only those who follow me can view the content I publish.

The Relation Protocol has two predefined relationship scenarios:

Follow: The follow relationship between addresses. When a user follows another user, they will receive an SBT marked as "follow".

DAO: DAO expresses group relationships, and users can grant SBTs as DAO membership by creating a DAO entity.

Publication

Publication is a module for various types of content publishing in the Relation Protocol. It is original content published by creators and can be in the form of text, images, videos, or other formats. Publication contains two types:

Content: Public content publishing that can be read by everyone.

Privacy Content: Content publishing with privacy, where creators can set visibility to allow only specific objects to read the content. The specific objects can be specified addresses, NFT holders, and so on.

Scenario Extension

In addition to the above scenarios, the Relation Social Graph also supports the extension of scenarios. Developers can submit schemas that conform to the specified standards to cover scenarios that are not yet covered in the current social graph and define initial RDFs.

Figure 2-6 Socially Programmable Identity