Plain activity event with no specific content; the activity is defined by the event’s stream, time and duration, and possibly description.

An attribute type for the user’s sex

An attribute type for the user’s blood type

An attribute type for the user’s skin type

The audio source is the file attached to the event (no explicit content defined). You can use the event’s duration to mirror the recording’s duration.

A reference to an audio file online.

The blood pressure measurement. Pressures are stored in mmHg and the heart rate in bpm

An attribute type for true or false

A single iCalendar VEVENT mapped to a Pryv event. The well-known fields are kept here for queryability; the verbatim VEVENT block is preserved in the event’s clientData._raw for lossless round-trips. The event’s own time / duration carry the canonical instant; dtstart / dtend mirror it as ISO 8601 strings.

The contact’s name (or a free-form identifier)

The Skype id

The phone number

Type to record the clinical information, including an attachment, corresponding to the data of the fhir resource.

Cross-account consent request issued by a requester (cmc/request-v1 lineage). The plugin mints a single-use capability access from this trigger, embeds the URL in content.capabilityUrl, and delivers the request to the recipient.

Cross-account consent accept (cmc/accept-v1 lineage). Has two shapes: LOCAL TRIGGER (carries capabilityUrl, written by the accepter’s app to start the accept flow) OR PEER-DELIVERED (carries grantedAccess.apiEndpoint + server-stamped from, written by the accepter’s plugin to the requester’s responses stream / inbox).

Cross-account consent refuse (cmc/refuse-v1 lineage). Carries the capability URL of the request being refused + an optional localised reason.

Cross-account consent revoke (cmc/revoke-v1 lineage). Either party tears down an established access pair by writing this with the local data-grant access id + an optional localised reason.

Post-acceptance handshake step (cmc/back-channel-v1 lineage). Delivered from the requester to the accepter’s :_cmc:inbox via the data-grant URL, carrying the requester’s back-channel apiEndpoint + remote stream-ids so the accepter can later POST chat / system messages back to the requester.

Collector-proposed scope change on an established consent (cmc/system-scope-request-v1 lineage). The collector writes a proposal carrying the desired new permissions; the user-side app accepts or refuses by writing a corresponding consent/scope-update-cmc event.

User-side scope change apply / notify (cmc/system-scope-update-v1 lineage). Has two shapes: response-to-request (carries scopeRequestEventId + accept) OR self-initiated (carries newPermissions). The plugin updates the local data-grant access permissions and notifies the peer.

Requester-side invalidation of an open-link consent capability (cmc/invalidate-link-v1 lineage). The plugin flips the capability access state to 'invalidated' so further accepts are rejected. Already-established data-grant + back-channel relationships are UNTOUCHED — use consent/revoke-cmc for per-relationship teardown. Single-use capabilities are auto-consumed on first accept; calling invalidate on a single-use capability is a no-op.

A Facebook user as specified in the Graph API: https://developers.facebook.com/docs/reference/api/user/

A business card in vCard 2.0-3.x format. See: rfc2425, rfc2426.

Necessary information to access a Pryv.io account. Url in the format of http(s)://{token}@{apiEndpoint}

The ISO 8601 format

AES-256-GCM encrypted payload. payload is Base64( iv || ciphertext || tag ) where iv is a random 96-bit (12-byte) nonce generated per encryption, ciphertext is the AES-256-GCM encryption of the UTF-8 JSON plaintext, and tag is the 128-bit (16-byte) GCM authentication tag. The key is 256 bits (32 bytes). Standard (non-URL-safe) Base64.

Asymmetric (ECIES-style) encrypted payload for a NIST P-256 (secp256r1) recipient key pair. Encryption: generate an ephemeral P-256 key pair; compute the ECDH shared secret with the recipient’s public key (the 32-byte X coordinate); derive the content key with HKDF-SHA-256 (salt: empty, info: the ASCII string encrypted/ecies-aes-256-gcm, output: 32 bytes) and use it as an AES-256-GCM key with a random 96-bit IV. payload is Base64( ephemeralPublicKey || iv || ciphertext || tag ) where ephemeralPublicKey is the 65-byte uncompressed SEC1 point (0x04 || X || Y), iv is 12 bytes and tag is the 16-byte GCM authentication tag. Decryption requires the recipient’s private key. Standard (non-URL-safe) Base64.

DEPRECATED — prefer encrypted/aes-256-gcm. AES encrypted payload, with a text key and a Base64 payload; the exact cipher parameters (mode, key derivation, IV handling) were never fully specified, so implementations may not interoperate.

The file is attached to the event

A set of file attached. Structure can be declared in the filenames.

A reference to a file hosted elsewhere

An e-mail message.

A Facebook post. See Facebook’s API docs for reference. Facebook properties message and created_time map to event description and time respectively. Facebook attached pictures can be directly mapped to attachments. Other Facebook properties such as link, source, privacy are allowed.

A Twitter post. Twitter property created_at maps to event time. Other Twitter properties (see Twitter’s API docs) are allowed.

Chat message exchanged on a CMC consent’s per-counterparty chat stream (cmc/chat-v1 lineage). Plain string up to 10 KB; the plugin handles delivery to the peer’s matching chat stream.

Rating of mood (float value) 0:worst -> 1:best

ASCII Art emoticon

Inspired from id3 key/pair

See Soundcloud track properties.

An HTML-formatted note.

A plain-text note.

An HTML-formatted note associated to its source URL.

CMC system alert (cmc/system-alert-v1 lineage). Sent on the per-counterparty collectors stream of an established CMC consent. Carries an alert level, localised title + body, and an optional ack request (ackRequired / ackId).

CMC system alert acknowledgement (cmc/system-ack-v1 lineage). The recipient of a notification/alert-cmc writes one of these back referencing the original alert via alertEventId + ackId.

The format key is freely defined.

For example, a heart measurement with type numset/heart and content:

{ 
  "systolic": { "pressure/mmhg": 105 },
  "diastolic": { "pressure/mmhg": 64 },
  "rate": { "frequency/bpm": 88 }
}

The picture is caried in base64 (utf-8) encoded in string

The picture is the image file attached to the event (no explicit content defined). TODO: list accepted formats.

A reference to a picture file online.

The latest revision of the World Geodetic System (used by GPS).

Generic ratio.

A percentage value.

A type to record sexual activity

A type to record the menstrual cycles

A type to record the quality of the mucus

A type to record the result of an ovulation test

One shared secret. Lives under the reserved :_shared-secrets:<accessId> stream of the access that created it. The event’s own time + duration carry the lifetime — expiry is exactly now > time + duration — and trashed marks an item that has left the pending state.

A type to record severity of a symptom such as bloating or abdominal cramps.

A type to represent change in appetite.

An HTTP or HTTPS resource.

The video is the file attached to the event (no explicit content defined). TODO: list accepted formats.

A reference to an video file online.

A Vimeo video ID.

A YouTube video ID.