LogoLogo
  • 🔮DeSci Codex
    • 🕊️Overview
    • 🏁Design goals
  • Data layer definition
    • 🌳Introduction to Sidetree
    • 👾Entities
      • 🧑‍🔬Profiles
      • 📗Research object
      • 📄Research component
      • 🏅Claim
      • 📯Attestation
      • 💬Annotation
      • 🔁Relational information
        • 💫Research field
        • 🤝Contributor
        • 👉Reference
    • 🏷️Metadata
  • Protocol operation
    • 🎣Deterministic resolution
    • 🧑‍🤝‍🧑Participation
      • 📚Network operators
      • 🔮Gateway providers
      • 📦Data services
      • 🧲Advanced indexing
      • 🗺️dPID resolvers
      • 🛂Identity verifiers
      • 🏷️Legacy PID mapping
  • Implementation
    • 🌊Ceramic & ComposeDB
    • 🛠️Reference implementation
    • ⚠️Current limitations
      • 🤞Mutability quirks
      • 🧐Invalid data
      • ⌛Timestamps
      • 🎟️Delegation of permissions
  • Future work
    • 🧩Feature wishlist
    • 🛣️Roadmap
Powered by GitBook
On this page
  • Schema
  • Revocation
  1. Data layer definition
  2. Entities
  3. Relational information

Reference

Directional link between two publications indicating scientific dependence

Last updated 1 year ago

Relates a research object with another, indicating that the result depend on or is related to the target publication. The exact meaning of this relation depends on the author intention, in the same way as a reference in a classical paper does.

Having dedicated entities for references, instead of text based equivalents in the paper, enables querying the scientific record based on direct or transient reference relations.

Since any actor can create these relations, a gateway operator may choose to only show such indications created by the publication author or an otherwise trustworthy actor.

Schema

Field
Type
Description

fromID

ID

Research object at the source of the reference

fromVersion

Commit

Version indicator of the same

toID

ID

Research object at the target of the reference

toVersion

Commit

Version indicator of the same

revoked

Boolean

Revokation status

Revocation

Since entity instances can be updated, but not deleted, the way to recall a contributor indication is by updating this field to true. Gateways should respect this and mark it as revoked from the version where it happened.

👾
🔁
👉
Reference relations, showing transient references between three publications