yurucommu Data Vocabulary

Published JSON-LD contexts for yurucommu. A published term is not, by itself, evidence that the current federation output uses it.

Contexts

Context	URL	Current status
Combined	`https://yurucommu.com/ns/context.jsonld`	Contains both current Story terms and proposed APC terms
Story	`https://yurucommu.com/ns/story/context.jsonld`	Used by the current Story object model
APC	`https://yurucommu.com/ns/apc/context.jsonld`	Proposed vocabulary. Current community Group actors do not emit these properties

Current Story terms

Story objects use the https://yurucommu.com/ns/story# namespace for:

Story — a type emitted together with Note
displayDuration — an xsd:duration
overlays — an ordered list of overlay objects
position — normalized x, y, width, and height values from 0 to 1

Current outbound Story objects inline these mappings, so consumers do not have to dereference this site to understand the term IRIs.

Proposed APC terms

The APC context publishes rooms, joinPolicy, postPolicy, and visibility. The current per-community Group actor does not emit these values. Treat them as reserved proposals, not a supported federation contract.

Current community federation instead relies on ActivityStreams Group, Follow, Accept, Reject, Undo, and Announce.

Example

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://yurucommu.com/ns/story/context.jsonld"
  ],
  "type": ["Story", "Note"],
  "displayDuration": "PT5S",
  "overlays": [
    {
      "type": "Note",
      "name": "Hello",
      "position": {
        "x": 0.5,
        "y": 0.8,
        "width": 0.6,
        "height": 0.1
      }
    }
  ]
}

Interoperability

A JSON-LD processor may ignore terms it does not understand, but that does not guarantee another ActivityPub product will reproduce yurucommu's Story or community behavior. Verify the receiving implementation's supported types and properties separately.

Data vocabulary guide (JA) · All documentation