Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Julian Fietkau boosted
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp 3 days ago

The @w3c #Publishing Maintenance #WorkingGroup issues EPUB Annotations 1.0 as #FPWD, enabling richer reading and improved interoperability #timetogiveinput
▶️ https://www.w3.org/TR/epub-anno-10/

This document defines a profile of the Web Annotation Data Model for #EPUB publications, enabling annotations such as highlights, notes, and bookmarks to be expressed using embedded #JSON-LD. The spec. also introduces Annotation Sets for packaging and sharing annotations.

Feedback welcome: https://github.com/w3c/epub-specs/issues?q=is%3Aissue%20state%3Aopen%20label%3ASpec-Annotations

 Example 1: Core structure of an EPUB annotation

{
    "@context": "https://www.w3.org/ns/epub-anno.jsonld",
    "id": "urn:uuid:123-123-123-123",
    "type": "Annotation",
    "created": "2023-10-14T15:13:28Z",
    "modified": "2024-01-29T09:00:00Z",
    "target": {
        …
    },
    "body": {
        …
    }
}
Example 1: Core structure of an EPUB annotation { "@context": "https://www.w3.org/ns/epub-anno.jsonld", "id": "urn:uuid:123-123-123-123", "type": "Annotation", "created": "2023-10-14T15:13:28Z", "modified": "2024-01-29T09:00:00Z", "target": { … }, "body": { … } }
Example 1: Core structure of an EPUB annotation { "@context": "https://www.w3.org/ns/epub-anno.jsonld", "id": "urn:uuid:123-123-123-123", "type": "Annotation", "created": "2023-10-14T15:13:28Z", "modified": "2024-01-29T09:00:00Z", "target": { … }, "body": { … } }

EPUB Annotations 1.0

This document defines a profile of the Web Annotation Data Model [annotation-model] by specifying a subset of the terms, and adding terms deemed useful to satisfy the entries in the EPUB Annotations Use Cases and Requirements [epub-anno-ucr] document.
  • Copy link
  • Flag this post
  • Block
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp 3 days ago

The @w3c #Publishing Maintenance #WorkingGroup issues EPUB Annotations 1.0 as #FPWD, enabling richer reading and improved interoperability #timetogiveinput
▶️ https://www.w3.org/TR/epub-anno-10/

This document defines a profile of the Web Annotation Data Model for #EPUB publications, enabling annotations such as highlights, notes, and bookmarks to be expressed using embedded #JSON-LD. The spec. also introduces Annotation Sets for packaging and sharing annotations.

Feedback welcome: https://github.com/w3c/epub-specs/issues?q=is%3Aissue%20state%3Aopen%20label%3ASpec-Annotations

 Example 1: Core structure of an EPUB annotation

{
    "@context": "https://www.w3.org/ns/epub-anno.jsonld",
    "id": "urn:uuid:123-123-123-123",
    "type": "Annotation",
    "created": "2023-10-14T15:13:28Z",
    "modified": "2024-01-29T09:00:00Z",
    "target": {
        …
    },
    "body": {
        …
    }
}
Example 1: Core structure of an EPUB annotation { "@context": "https://www.w3.org/ns/epub-anno.jsonld", "id": "urn:uuid:123-123-123-123", "type": "Annotation", "created": "2023-10-14T15:13:28Z", "modified": "2024-01-29T09:00:00Z", "target": { … }, "body": { … } }
Example 1: Core structure of an EPUB annotation { "@context": "https://www.w3.org/ns/epub-anno.jsonld", "id": "urn:uuid:123-123-123-123", "type": "Annotation", "created": "2023-10-14T15:13:28Z", "modified": "2024-01-29T09:00:00Z", "target": { … }, "body": { … } }

EPUB Annotations 1.0

This document defines a profile of the Web Annotation Data Model [annotation-model] by specifying a subset of the terms, and adding terms deemed useful to satisfy the entries in the EPUB Annotations Use Cases and Requirements [epub-anno-ucr] document.
  • Copy link
  • Flag this post
  • Block
Sabrina Web :privacypride: 📎 boosted
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp last month

The @w3c Security #InterestGroup proposes to make systematic use of threat modeling in W3C to identify potential #threats, vulnerabilities, and safeguards in web specifications.
This guide is designed to help standards #developers make informed decisions about #security and #privacy risks from the beginning of standard development #timetogiveinput

▶️ https://www.w3.org/TR/threat-modeling-guide/

Feedback wlc: https://github.com/w3c/threat-modeling-guide/issues

Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.
Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.
Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.

Threat Modeling Guide

  • Copy link
  • Flag this post
  • Block
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp last month

The @w3c Security #InterestGroup proposes to make systematic use of threat modeling in W3C to identify potential #threats, vulnerabilities, and safeguards in web specifications.
This guide is designed to help standards #developers make informed decisions about #security and #privacy risks from the beginning of standard development #timetogiveinput

▶️ https://www.w3.org/TR/threat-modeling-guide/

Feedback wlc: https://github.com/w3c/threat-modeling-guide/issues

Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.
Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.
Data Flow Diagram for Minimalist Web Threat Model with 3 entities (user, network operator, website admin), linked by 7 flows to 3 processes (DNS, browser, server), as described in section A1.3 of the guide.

Threat Modeling Guide

  • Copy link
  • Flag this post
  • Block
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp 3 months ago

The @w3c SHACL 1.2 Rules specification is an addition to the Shapes Constraint Language (SHACL) family of documents. It provides a standardized way to express and evaluate declarative rules that generate new data (as #RDF triples) by inference on existing RDF data. #FPWD #timetogiveinput
▶️ https://www.w3.org/TR/shacl12-rules/

Feedback welcome: https://github.com/w3c/data-shapes/issues/

SHACL 1.2 Rules

This document describes Shapes Constraint Language (SHACL) Rules.
  • Copy link
  • Flag this post
  • Block
W3C Developers
W3C Developers
@w3cdevs@w3c.social  ·  activity timestamp 8 months ago

Government-approved digital credentials (driver license, etc.) are becoming more commonly used online. The @w3c Digital Credentials #API enables websites to request credentials, and for users to consent to return credentials that they carry around in #DigitalWallets
▶️ https://www.w3.org/TR/digital-credentials/
#FPWD #timetogiveinput

@simone explains how this API advances #privacy-preserving Web identities: https://www.w3.org/blog/2025/w3c-digital-credentials-api-publication-the-next-step-to-privacy-preserving-identities-on-the-web/ #gdc25

Feedback welcome: https://github.com/w3c-fedid/digital-credentials/

  • Copy link
  • Flag this post
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.34 no JS en
Automatic federation enabled
Log in
Instance logo
  • Explore
  • About
  • Members
  • Code of Conduct