<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>standard</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/27/feed"/>
    <updated>2026-04-23T09:08:18+00:00</updated>
    <id>https://links.biapy.com/guest/tags/27/feed</id>
            <entry>
            <id>https://links.biapy.com/links/12458</id>
            <title type="text"><![CDATA[Open Cybersecurity Schema Framework (OCSF)]]></title>
            <link rel="alternate" href="https://ocsf.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12458"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Open Cybersecurity Schema Framework (OCSF) is an open standard for cybersecurity event logging and data normalization. The framework is made up of a set of categories, event classes, data types, and an attribute dictionary. It is not restricted to cybersecurity nor to events, however the initial focus of the framework has been a schema for cybersecurity events.

- [Open Cybersecurity Schema Framework @ GitHub](https://github.com/ocsf/ocsf-schema).

Related contents:

- [OCSF explained: The shared data language security teams have been missing @ Venture Beat](https://venturebeat.com/security/ocsf-explained-the-shared-data-language-security-teams-have-been-missing).
- [What is OCSF and How Do You Implement It? @ Datadog](https://www.datadoghq.com/knowledge-center/ocsf/).]]>
            </summary>
            <updated>2026-04-08T06:10:12+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12274</id>
            <title type="text"><![CDATA[cq]]></title>
            <link rel="alternate" href="https://github.com/mozilla-ai/cq" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12274"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open standard for shared agent learning. Agents persist, share, and query collective knowledge so they stop rediscovering the same failures independently. 

cq is derived from colloquy (/ˈkɒl.ə.kwi/), a structured exchange of ideas where understanding emerges through dialogue rather than one-way output. It reflects a focus on reciprocal knowledge sharing; systems that improve through participation, not passive use. In radio, CQ is a general call (&amp;quot;any station, respond&amp;quot;), capturing the same model: open invitation, response, and collective signal built through interaction.

Related contents:

- [cq: Stack Overflow for Agents @ Mozilla.ai](https://blog.mozilla.ai/cq-stack-overflow-for-agents/).]]>
            </summary>
            <updated>2026-03-24T13:25:02+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12184</id>
            <title type="text"><![CDATA[Machine Payments Protocol]]></title>
            <link rel="alternate" href="https://mpp.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12184"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The open protocol for machine-to-machine payments. Charge for API requests, tool calls, or content—agents and apps pay per request in the same HTTP call.]]>
            </summary>
            <updated>2026-03-19T12:56:28+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12146</id>
            <title type="text"><![CDATA[GitAgent]]></title>
            <link rel="alternate" href="https://www.gitagent.sh/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12146"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[your repository becomes your agent.
The Open Standard for Git-Native AI Agents.
The open standard for defining, versioning, and running AI agents natively in git.

A git-native, framework-agnostic, open standard for defining AI agents. Version-controlled config that exports to Claude Code, OpenClaw, Lyzr Agent, Chimera, NanoBot, CrewAgent, and Agents SDK.

- [GitAgent @ GitHub](https://github.com/open-gitagent/gitagent).]]>
            </summary>
            <updated>2026-03-16T12:24:17+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12076</id>
            <title type="text"><![CDATA[The human.json Protocol]]></title>
            <link rel="alternate" href="https://codeberg.org/robida/human.json" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12076"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A lightweight protocol for humans to assert authorship of their website content and vouch for the humanity of others. 

human.json is a lightweight protocol for humans to assert authorship of their site content and vouch for the humanity of others. It uses URL ownership as identity, and trust propagates through a crawlable web of vouches between sites.]]>
            </summary>
            <updated>2026-03-10T12:12:26+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12010</id>
            <title type="text"><![CDATA[DORA]]></title>
            <link rel="alternate" href="https://dora.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12010"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Get Better at Getting Better.

 DORA is the largest and longest running research program of its kind, that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance. 

Related contents:

- [DORA’s software delivery performance metrics @ DORA](https://dora.dev/guides/dora-metrics/).
- [GitOps architecture, patterns and anti-patterns @ Platform Engineering](https://platformengineering.org/blog/gitops-architecture-patterns-and-anti-patterns).]]>
            </summary>
            <updated>2026-03-04T12:44:26+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/12008</id>
            <title type="text"><![CDATA[Open Container Initiative]]></title>
            <link rel="alternate" href="https://opencontainers.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/12008"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Open Container Initiative is an open governance structure for the express purpose of creating open industry standards around container formats and runtimes.

Established in June 2015 by Docker and other leaders in the container industry, the OCI currently contains three specifications: the Runtime Specification (runtime-spec), the Image Specification (image-spec) and the Distribution Specification (distribution-spec). The Runtime Specification outlines how to run a “filesystem bundle” that is unpacked on disk. At a high-level an OCI implementation would download an OCI Image then unpack that image into an OCI Runtime filesystem bundle. At this point the OCI Runtime Bundle would be run by an OCI Runtime.

Related contents:

- [GitOps architecture, patterns and anti-patterns @ Platform Engineering](https://platformengineering.org/blog/gitops-architecture-patterns-and-anti-patterns).]]>
            </summary>
            <updated>2026-03-04T12:39:02+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11913</id>
            <title type="text"><![CDATA[RFC 9842 - Compression Dictionary Transport]]></title>
            <link rel="alternate" href="https://datatracker.ietf.org/doc/rfc9842/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11913"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[This document specifies a mechanism for dictionary-based compression
in the Hypertext Transfer Protocol (HTTP).  By utilizing this
technique, clients and servers can reduce the size of transmitted
data, leading to improved performance and reduced bandwidth
consumption.  This document extends existing HTTP compression methods
and provides guidelines for the delivery and use of compression
dictionaries within the HTTP protocol.

- [Compression dictionary transport @ GitHub](https://github.com/WICG/compression-dictionary-transport).

Related content:

- [Dictionary Compression is finally here, and it&amp;#039;s ridiculously good @ HTTP Toolkit](https://httptoolkit.com/blog/dictionary-compression-performance-zstd-brotli/).]]>
            </summary>
            <updated>2026-02-24T12:31:32+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11847</id>
            <title type="text"><![CDATA[ActivityPub Rocks!]]></title>
            <link rel="alternate" href="https://activitypub.rocks/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11847"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[ActivityPub is a decentralized social networking protocol based on the ActivityStreams 2.0 data format. ActivityPub is an official W3C recommended standard published by the W3C Social Web Working Group. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and subscribing to content.

Related contents:

- [Use Protocols, Not Services @ ~~p](https://notnotp.com/notes/use-protocols-not-services/).]]>
            </summary>
            <updated>2026-02-17T12:57:36+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11715</id>
            <title type="text"><![CDATA[Semantic Service Naming]]></title>
            <link rel="alternate" href="https://semserv.org/en/1.0.0/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11715"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Create meaningful service names that are unlikely to change over time by composing the name from elements that describe what the service does.

- [SemServ @ GitHub](https://github.com/spandigital/semserv).]]>
            </summary>
            <updated>2026-02-05T16:19:57+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11543</id>
            <title type="text"><![CDATA[Universal Commerce Protocol (UCP)]]></title>
            <link rel="alternate" href="https://ucp.dev/#" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11543"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The common language for platforms, agents and businesses.

UCP defines building blocks for agentic commerce—from discovering and buying to post purchase experiences—allowing the ecosystem to interoperate through one standard, without custom builds. 

- [Universal Commerce Protocol (UCP) @ GitHub](https://github.com/Universal-Commerce-Protocol/ucp).

Related contents:

- [Under the Hood: Universal Commerce Protocol (UCP) @ Google for Developers](https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/).
- [Google lance un protocole qui va transformer l&amp;#039;achat en ligne, Carrefour fait partie des premiers à l&amp;#039;adopter @ Clubic :fr:](https://www.clubic.com/actualite-594658-google-lance-un-protocole-qui-va-transformer-l-achat-en-ligne-carrefour-fait-partie-des-premiers-a-l-adopter.html).]]>
            </summary>
            <updated>2026-01-20T09:20:59+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11470</id>
            <title type="text"><![CDATA[Agent Skills]]></title>
            <link rel="alternate" href="https://agentskills.io/home" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11470"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A simple, open format for giving agents new capabilities and expertise.
Agent Skills are folders of instructions, scripts, and resources that agents can discover and use to do things more accurately and efficiently.

- [Agent Skills @ GitHub](https://github.com/agentskills/agentskills).

Related contents:

- [Vercel&amp;#039;s Agent Skills @ GitHub](https://github.com/vercel-labs/agent-skills).
- [MCP, Skills, and Agents @ cramr](https://cra.mr/mcp-skills-and-agents/).
- [Agent Skills vs. Rules vs. Commands @ builder.io](https://www.builder.io/blog/agent-skills-rules-commands).
- [3 Principles for Designing Agent Skills @ Block Engineering Blog](https://engineering.block.xyz/blog/3-principles-for-designing-agent-skills).]]>
            </summary>
            <updated>2026-03-02T06:56:42+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11386</id>
            <title type="text"><![CDATA[Language Server Protocol]]></title>
            <link rel="alternate" href="https://microsoft.github.io/language-server-protocol/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11386"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Language Server Protocol (LSP) defines the protocol used between an editor or IDE and a language server that provides language features like auto complete, go to definition, find all references etc. The goal of the Language Server Index Format (LSIF, pronounced like &amp;quot;else if&amp;quot;) is to support rich code navigation in development tools or a Web UI without needing a local copy of the source code. 

- [Language Server Protocol @ GitHub](https://github.com/microsoft/language-server-protocol).

Related contents:

- [Claude Code Sees Like A Software Architect Dancing with Robots: A Software Architect&amp;#039;s Journey @ Dancing with Robots: A Software Architect&amp;#039;s Journey](https://davegriffith.substack.com/p/claude-code-sees-like-a-software).]]>
            </summary>
            <updated>2026-01-06T07:04:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11314</id>
            <title type="text"><![CDATA[model.yaml]]></title>
            <link rel="alternate" href="https://modelyaml.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11314"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Open Description Standard for AI Models.

An open description standard for defining cross-platform, multi-format AI models.

- [model.yaml @ GitHub](https://github.com/modelyaml/modelyaml).]]>
            </summary>
            <updated>2025-12-29T07:33:21+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11278</id>
            <title type="text"><![CDATA[TRON]]></title>
            <link rel="alternate" href="https://github.com/fastserial/lite3" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11278"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Tree Root Object Notation.

A JSON-Compatible Zero-Copy Serialization Format.]]>
            </summary>
            <updated>2025-12-22T13:17:01+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11277</id>
            <title type="text"><![CDATA[JSON Structure]]></title>
            <link rel="alternate" href="https://json-structure.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11277"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[JSON Structure is a data structure definition language that enforces strict typing, modularity, and determinism.

JSON Structure is a schema language that can describe data types and structures whose definitions map cleanly to programming language types and database constructs as well as to the popular JSON data encoding. The type model reflects the needs of modern applications and allows for rich annotations with semantic information that can be evaluated and understood by developers and by large language models (LLMs).

Related contents:

- [JSON Structure: A JSON schema language you&amp;#039;ll love @ Messaging on Azure Blog](https://techcommunity.microsoft.com/blog/messagingonazureblog/json-structure-a-json-schema-language-youll-love/4476852).]]>
            </summary>
            <updated>2025-12-22T13:14:44+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11122</id>
            <title type="text"><![CDATA[Kubernetes Container Storage Interface (CSI)]]></title>
            <link rel="alternate" href="https://kubernetes-csi.github.io/docs/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11122"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[This site documents how to develop, deploy, and test a Container Storage Interface (CSI) driver on Kubernetes.

The Container Storage Interface (CSI) is a standard for exposing arbitrary block and file storage systems to containerized workloads on Container Orchestration Systems (COs) like Kubernetes. Using CSI third-party storage providers can write and deploy plugins exposing new storage systems in Kubernetes without ever having to touch the core Kubernetes code.

- [Container Storage Interface (CSI) Specification @ GitHub](https://github.com/container-storage-interface/spec).]]>
            </summary>
            <updated>2025-11-28T12:51:01+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11120</id>
            <title type="text"><![CDATA[Dotprompt]]></title>
            <link rel="alternate" href="https://google.github.io/dotprompt/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11120"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Executable GenAI Prompt Templates.

Dotprompt is an executable prompt template file format for Generative AI. It is designed to be agnostic to programming language and model provider to allow for maximum flexibility in usage. Dotprompt extends the popular Handlebars templating language with GenAI-specific features.

- [Dotprompt @ GitHub](https://github.com/google/dotprompt).
- [runprompt @ GitHub](https://github.com/chr15m/runprompt).]]>
            </summary>
            <updated>2025-11-28T12:45:11+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11096</id>
            <title type="text"><![CDATA[Matter]]></title>
            <link rel="alternate" href="https://csa-iot.org/all-solutions/matter/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11096"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Foundation for Connected Things. Smart Home Device Solution.

One protocol to connect compatible devices and systems with one another. Smart home devices should be secure, reliable, and seamless to use. And with Matter, they are.

- [The Matter Specifications @ Build with Matter](https://handbook.buildwithmatter.com/specification/).

Related contents:

- [Episode \#118: NOT a swarm! @ Changelog &amp;amp; Friends](https://changelog.com/friends/118).]]>
            </summary>
            <updated>2025-11-25T07:41:26+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11087</id>
            <title type="text"><![CDATA[Darwin Information Typing Architecture (DITA)]]></title>
            <link rel="alternate" href="https://www.oxygenxml.com/dita/1.3/specs/index.html" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11087"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types.

Related contents:

- [Issue 45 - Markdown is Holding You Back @ Code, Content, and Career with Brian Hogan](https://newsletter.bphogan.com/archive/issue-45-markdown-is-holding-you-back/).]]>
            </summary>
            <updated>2025-11-24T13:05:28+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11086</id>
            <title type="text"><![CDATA[DocBook]]></title>
            <link rel="alternate" href="https://docbook.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11086"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[DocBook is a schema (available in several languages including RELAX NG, SGML and XML DTDs, and W3C XML Schema) maintained by the DocBook Technical Committee of OASIS. It is particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). 

Related contents:

- [Issue 45 - Markdown is Holding You Back @ Code, Content, and Career with Brian Hogan](https://newsletter.bphogan.com/archive/issue-45-markdown-is-holding-you-back/).]]>
            </summary>
            <updated>2025-11-24T13:04:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11085</id>
            <title type="text"><![CDATA[reStructuredText]]></title>
            <link rel="alternate" href="https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11085"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[reStructuredText (reST) is the default plaintext markup language used by both Docutils and Sphinx. Docutils provides the basic reStructuredText syntax, while Sphinx extends this to support additional functionality.

Related contents:

- [Issue 45 - Markdown is Holding You Back @ Code, Content, and Career with Brian Hogan](https://newsletter.bphogan.com/archive/issue-45-markdown-is-holding-you-back/).]]>
            </summary>
            <updated>2025-11-24T13:03:10+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11037</id>
            <title type="text"><![CDATA[OpenSpec]]></title>
            <link rel="alternate" href="https://openspec.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11037"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A lightweight spec‑driven framework.

OpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. No API keys required.

- [OpenSpec @ GitHub](https://github.com/Fission-AI/OpenSpec).

Related contents:

- [Spec-driven development doesn&amp;#039;t work if you&amp;#039;re too confused to write the spec @ deontologician](https://publish.obsidian.md/deontologician/Posts/Spec-driven+development+doesn&amp;#039;t+work+if+you&amp;#039;re+too+confused+to+write+the+spec).
- [The uncomfortable truth about vibe coding @ RedHat Developer](https://developers.redhat.com/articles/2026/02/17/uncomfortable-truth-about-vibe-coding).
- [What spec-driven development gets wrong @ augment code](https://www.augmentcode.com/blog/what-spec-driven-development-gets-wrong).]]>
            </summary>
            <updated>2026-02-24T07:52:44+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11030</id>
            <title type="text"><![CDATA[Keep a Changelog]]></title>
            <link rel="alternate" href="https://keepachangelog.com/en/1.1.0/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11030"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[If you build software, keep a changelog.
Don’t let your friends dump git logs into changelogs.

- [Keep a Changelog @ GitHub](https://github.com/olivierlacan/keep-a-changelog/).

Related contents:

- [The importance of a good changelog @ WordPress Developer Blog](https://developer.wordpress.org/news/2025/11/the-importance-of-a-good-changelog/).]]>
            </summary>
            <updated>2025-11-21T12:36:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10802</id>
            <title type="text"><![CDATA[IPCrypt]]></title>
            <link rel="alternate" href="https://ipcrypt-std.github.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10802"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A Common Approach to IP Address Encryption

IPCrypt is a simple, open specification for encrypting and obfuscating IP addresses, balancing privacy considerations with practical network operations.

- [Methods for IP Address Encryption and Obfuscation @ GitHub](https://github.com/ipcrypt-std/draft-denis-ipcrypt).

Related contents:

- [Why IP address truncation fails at anonymization @ Frank DENIS random thoughts](https://00f.net/2025/10/27/ip-anonymization/).]]>
            </summary>
            <updated>2025-10-28T11:03:24+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10734</id>
            <title type="text"><![CDATA[GraphQL]]></title>
            <link rel="alternate" href="https://graphql.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10734"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A query language for your API.

GraphQL is an open‑source query language for APIs and a server‑side runtime. It provides a strongly‑typed schema to define relationships between data, making APIs more flexible and predictable. And it isn’t tied to a specific database or storage engine — it works with your existing code and data, making it easier to evolve APIs over time.

Related contents:

- [GraphQL Myths @ Jovi De Croock](https://jovidecroock.com/blog/graphql-myths/).
- [GraphQL: the enterprise honeymoon is over @ john james.](https://johnjames.blog/posts/graphql-the-enterprise-honeymoon-is-over).]]>
            </summary>
            <updated>2025-12-16T13:01:05+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10647</id>
            <title type="text"><![CDATA[CycloneDX]]></title>
            <link rel="alternate" href="https://cyclonedx.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10647"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[CycloneDX Bill of Materials Standard.

CycloneDX is a modern standard for the software supply chain.

The International Standard for Bill of Materials (ECMA-424)
The OWASP Foundation and Ecma International Technical Committee for Software &amp;amp; System Transparency (TC54) drive the continued advancement of the specification.

- [CycloneDX BOM Standard @ GitHub](https://github.com/CycloneDX).

Related contents:

- [CycloneDX PHP Composer Plugin @ GitHub](https://github.com/CycloneDX/cyclonedx-php-composer).]]>
            </summary>
            <updated>2025-10-14T09:44:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10545</id>
            <title type="text"><![CDATA[Abilities API]]></title>
            <link rel="alternate" href="https://github.com/WordPress/abilities-api" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10545"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A WordPress API for declaring and discovering plugin, theme, and core abilities in a human- and machine-readable way. 

Related contents:

- [ Abilities API  @ Wordpress AI](https://make.wordpress.org/ai/2025/07/17/abilities-api/).
- [API Abilities - Le langage universel de Wordpress pour unifier les composants IA @ Korben :fr:](https://korben.info/wordpress-ia-native-abilities-api-open-source.html).]]>
            </summary>
            <updated>2025-10-06T09:23:01+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10478</id>
            <title type="text"><![CDATA[JSON]]></title>
            <link rel="alternate" href="https://www.json.org/json-en.html" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10478"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.

JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

Related contents:

- [JSON is not JSON Across Languages @ dochia.dev blog](https://blog.dochia.dev/blog/json-isnt-json/).]]>
            </summary>
            <updated>2025-10-01T12:01:28+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10367</id>
            <title type="text"><![CDATA[Cap&amp;#039;n Web]]></title>
            <link rel="alternate" href="https://github.com/cloudflare/capnweb" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10367"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[JavaScript/TypeScript-native, low-boilerplate, object-capability RPC system.

Cap&amp;#039;n Web is more expressive than almost every other RPC system, because it implements an object-capability RPC model.

Related contents:

- [Cap&amp;#039;n Web: a new RPC system for browsers and web servers @ Cloudflare](https://blog.cloudflare.com/capnweb-javascript-rpc-library/).]]>
            </summary>
            <updated>2025-09-23T11:34:20+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10325</id>
            <title type="text"><![CDATA[AsciiDoc]]></title>
            <link rel="alternate" href="https://asciidoc.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10325"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Publish presentation-rich content from a concise and comprehensive authoring format.

AsciiDoc is a plain text markup language for writing technical content. It’s packed with semantic elements and equipped with features to modularize and reuse content. AsciiDoc content can be composed using a text editor, managed in a version control system, and published to multiple output formats.

Related contents:

- [Issue 45 - Markdown is Holding You Back @ Code, Content, and Career with Brian Hogan](https://newsletter.bphogan.com/archive/issue-45-markdown-is-holding-you-back/).]]>
            </summary>
            <updated>2025-11-24T13:01:42+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10299</id>
            <title type="text"><![CDATA[KSON: Kson Structured Object Notation]]></title>
            <link rel="alternate" href="https://kson.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10299"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A 💌 to the humans maintaining computer configurations.

KSON combines the best aspects of JSON and YAML—robust and efficient like JSON, clean and readable like YAML. KSON is designed to be toolable and has a flexible syntax that is usually auto-formatted to look like this:

- [KSON: Kson Structured Object Notation @ GitHub](https://github.com/kson-org/kson).

Related contents:

- [Configuration files are user interfaces @ Adolfo Ochagavía](https://ochagavia.nl/blog/configuration-files-are-user-interfaces/).
- [Abstraction, not syntax @ Ruud van Asseldonk](https://ruudvanasseldonk.com/2025/abstraction-not-syntax).]]>
            </summary>
            <updated>2025-10-14T12:15:07+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10269</id>
            <title type="text"><![CDATA[WebAssembly]]></title>
            <link rel="alternate" href="https://webassembly.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10269"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications.

Related contents:

- [What Happened To WebAssembly @ emnudge.dev](https://emnudge.dev/blog/what-happened-to-webassembly/).
- [10 Years of Wasm: A Retrospective @ Bytecode Alliance](https://bytecodealliance.org/articles/ten-years-of-webassembly-a-retrospective).
- [Making WebAssembly a first-class language on the Web @ moz.://a Hacks](https://hacks.mozilla.org/2026/02/making-webassembly-a-first-class-language-on-the-web/).
- [Notes on Writing Wasm @ Monad Nomad](https://notes.brooklynzelenka.com/Blog/Notes-on-Writing-Wasm).
- [Why is WebAssembly a second-class language on the web? @ moz://a hacks](https://hacks.mozilla.org/2026/02/making-webassembly-a-first-class-language-on-the-web/).
- [Rewriting our Rust WASM Parser in TypeScript @ OpenUI](https://www.openui.com/blog/rust-wasm-parser).]]>
            </summary>
            <updated>2026-03-23T14:55:46+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10251</id>
            <title type="text"><![CDATA[The /llms.txt file]]></title>
            <link rel="alternate" href="https://llmstxt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10251"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A proposal to standardise on using an /llms.txt file to provide information to help LLMs use a website at inference time.

We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content. This file offers brief background information, guidance, and links to detailed markdown files.

llms.txt markdown is human and LLM readable, but is also in a precise format allowing fixed processing methods (i.e. classical programming techniques such as parsers and regex).

- [llms.txt @ GitHub](https://github.com/answerdotai/llms-txt).
- [MCP LLMS-TXT Documentation Server @ GitHub](https://github.com/langchain-ai/mcpdoc).

Related contents:

- [Firecrawl LLMs.txt Generator @ GitHub](https://github.com/firecrawl/create-llmstxt-py).
- [A proposal for inline LLM instructions in HTML based on llms.txt @ Vercel](https://vercel.com/blog/a-proposal-for-inline-llm-instructions-in-html).
- [\#119: Les news sur le développement web et l&amp;#039;IA pour septembre 2025 RC2 @ Double Slash :fr:](https://double-slash.dev/podcasts/news-sept25-rc2/).
- [A fun trick for getting discovered by LLMs and AI tools @ Cassidy Williams](https://cassidoo.co/post/ai-llm-discoverability/).]]>
            </summary>
            <updated>2026-02-02T10:24:56+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10246</id>
            <title type="text"><![CDATA[Agent Payments Protocol (AP2)]]></title>
            <link rel="alternate" href="https://ap2-protocol.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10246"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Building a Secure and Interoperable Future for AI-Driven Payments. 

- [Agent Payments Protocol (AP2) @ GitHub](https://github.com/google-agentic-commerce/AP2).

Related contents:

- [ Google&amp;#039;s new open protocol secures AI agent transactions - and 60 companies already support it  @ ZDNET](https://www.zdnet.com/article/googles-new-open-protocol-secures-ai-agent-transactions-and-60-companies-already-support-it/).]]>
            </summary>
            <updated>2025-09-17T11:23:10+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10227</id>
            <title type="text"><![CDATA[Agent Client Protocol]]></title>
            <link rel="alternate" href="https://agentclientprotocol.com/overview/introduction" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10227"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A protocol for connecting any editor to any agent.

The Agent Client Protocol standardizes communication between code editors (IDEs, text-editors, etc.) and coding agents (programs that use generative AI to autonomously modify code).

- [Agent Client Protocol @ GitHub](https://github.com/zed-industries/agent-client-protocol).

Related contents:

- [Bring Your Own Agent to Zed — Featuring Gemini CLI @ Zed](https://zed.dev/blog/bring-your-own-agent-to-zed).
- [Episode \#112: A new direction for AI developer tooling @ Changelog &amp;amp; Friends](https://changelog.com/friends/112).]]>
            </summary>
            <updated>2025-10-14T05:49:41+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10167</id>
            <title type="text"><![CDATA[Really Simple Licensing (RSL)]]></title>
            <link rel="alternate" href="https://rslstandard.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10167"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The open content licensing standard
for the AI-first Internet

Really Simple Licensing (RSL) is an evolution of the early ideas behind the widely adopted RSS standard, which provided a machine-readable framework for publishers to syndicate content to third-party clients and crawlers in exchange for traffic.

- [RSL Collective homepage](https://rslcollective.org/).

Related contents:

- [Pay-per-output? AI firms blindsided by beefed up robots.txt instructions. @ Ars Technica](https://arstechnica.com/tech-policy/2025/09/pay-per-output-ai-firms-blindsided-by-beefed-up-robots-txt-instructions/).]]>
            </summary>
            <updated>2025-09-12T12:33:43+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10018</id>
            <title type="text"><![CDATA[Media over QUIC]]></title>
            <link rel="alternate" href="https://moq.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10018"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Media over QUIC is a live media protocol powered by QUIC: a super-charged TCP/UDP replacement that powers HTTP/3. It’s being developed by the IETF and your favorite big tech companies such as Cloudflare, Google, Meta, Cisco, Akamai, etc.

- [Media over QUIC @ GitHub](https://github.com/kixelated/moq).

Related contents:

- [MoQ: Refactoring the Internet&amp;#039;s real-time media stack @ Cloudflare](https://blog.cloudflare.com/moq/).]]>
            </summary>
            <updated>2025-09-04T17:12:55+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/7</id>
            <title type="text"><![CDATA[AGENTS.md]]></title>
            <link rel="alternate" href="https://agents.md/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/7"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A simple, open format for guiding coding agents,
used by over 20k open-source projects.

Think of AGENTS.md as a README for agents: a dedicated, predictable place to provide the context and instructions to help AI coding agents work on your project.

- [AGENTS.md @ GitHub](https://github.com/openai/agents.md).

Related contents:

- [Improve your AI code output with AGENTS.md (+ my best tips) @ builder.io](https://www.builder.io/blog/agents-md).
- [\#118 - Les news sur le développement web et l&amp;#039;IA pour septembre 2025 RC1 @ Double Slash :fr:](https://double-slash.dev/podcasts/sept25-rc1/).
- [Optimizing repos for AI @ Tom Bedor&amp;#039;s Blog](https://tombedor.dev/optimizing-repos-for-ai/).
- [How to write a great agents.md: Lessons from over 2,500 repositories @ GitHub Blog](https://github.blog/ai-and-ml/github-copilot/how-to-write-a-great-agents-md-lessons-from-over-2500-repositories/).
- [Writing a good CLAUDE.md @ humanlayer](https://www.humanlayer.dev/blog/writing-a-good-claude-md).
- [Streamlining my user-level CLAUDE.md @ chris dzombak](https://www.dzombak.com/blog/2025/12/streamlining-my-user-level-claude-md/).
- [The Complete Guide to CLAUDE.md @ builder.io](https://www.builder.io/blog/claude-md-guide).
- [How to build self-improving coding agents - Part 1 @ Eric J Ma&amp;#039;s Website](https://ericmjl.github.io/blog/2026/1/17/how-to-build-self-improving-coding-agents-part-1/).
- [AGENTS.md outperforms skills in our agent evals @ Vercel](https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals).
- [Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents? @ arXiv](https://arxiv.org/abs/2602.11988).
- [Knowledge Priming @ martinFowler.com](https://martinfowler.com/articles/reduce-friction-ai/knowledge-priming.html).
- [J&amp;#039;ai mis deux IA en code review l&amp;#039;une contre l&amp;#039;autre — voici ce que ça donne @ Maxence Maireaux :fr:](https://maxence.maireaux.fr/fr/blog/mon-workflow-ia-claude-code-codex/).
- [Filesystems are having a moment @ madalitso.me](https://madalitso.me/notes/why-everyone-is-talking-about-filesystems/).
- [Your Docs Directory Is Doomed @ Jim Yagmin&amp;#039;s Blog](https://yagmin.com/blog/your-docs-directory-is-doomed/).
- [Stop Wasting Hours Writing Unit Tests: Use GitHub Copilot to Explode Code Coverage Fast @ Build5Nines](https://build5nines.com/stop-wasting-hours-writing-unit-tests-use-github-copilot-to-explode-code-coverage-fast/).]]>
            </summary>
            <updated>2026-04-20T05:45:41+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/115</id>
            <title type="text"><![CDATA[YAML: YAML Ain&amp;#039;t Markup Language]]></title>
            <link rel="alternate" href="https://yaml.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/115"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[YAML is a human-friendly data serialization
  language for all programming languages.

Related contents:

- [YAML Multiline](https://yaml-multiline.info/).
- [ohyaml.wtf](https://www.ohyaml.wtf/).
- [The yaml document from hell @ Ruud van Asseldonk](https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell).]]>
            </summary>
            <updated>2025-11-20T13:24:35+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/128</id>
            <title type="text"><![CDATA[POML (Prompt Orchestration Markup Language)]]></title>
            <link rel="alternate" href="https://microsoft.github.io/poml/latest/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/128"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[POML (Prompt Orchestration Markup Language) is a novel markup language designed to bring structure, maintainability, and versatility to advanced prompt engineering for Large Language Models (LLMs). It addresses common challenges in prompt development, such as lack of structure, complex data integration, format sensitivity, and inadequate tooling. POML provides a systematic way to organize prompt components, integrate diverse data types seamlessly, and manage presentation variations, empowering developers to create more sophisticated and reliable LLM applications.

- [POML (Prompt Orchestration Markup Language) @ GitHub](https://github.com/microsoft/poml).]]>
            </summary>
            <updated>2025-10-16T09:05:41+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/193</id>
            <title type="text"><![CDATA[A Vocabulary For Expressing AI Usage Preferences]]></title>
            <link rel="alternate" href="https://ietf-wg-aipref.github.io/drafts/draft-ietf-aipref-vocab.html?cf_target_id=_blank" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/193"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[This document proposes a standardized vocabulary for expressing preferences related to how digital assets are used by automated processing systems. This vocabulary allows for the creation of structured declarations about restrictions or permissions for use of digital assets by such systems.

Related contents:

- [Perplexity is using stealth, undeclared crawlers to evade website no-crawl directives @ Cloudflare Blog](https://blog.cloudflare.com/perplexity-is-using-stealth-undeclared-crawlers-to-evade-website-no-crawl-directives/).]]>
            </summary>
            <updated>2025-09-18T15:26:23+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/352</id>
            <title type="text"><![CDATA[The Web Robots Pages]]></title>
            <link rel="alternate" href="https://www.robotstxt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/352"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Web Robots (also known as Web Wanderers, Crawlers, or Spiders), are programs that traverse the Web automatically. Search engines such as Google use them to index the web content, spammers use them to scan for email addresses, and they have many other uses.

Related contents:

- [I was wrong about robots.txt @ Evgenii Pendragon](https://evgeniipendragon.com/posts/i-was-wrong-about-robots-txt/).
- [Fix Your robots.txt or Your Site Disappears from Google @ alanwsmith.com](https://www.alanwsmith.com/en/37/wa/jz/s1/).]]>
            </summary>
            <updated>2026-01-22T12:47:53+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/407</id>
            <title type="text"><![CDATA[OpenCLI]]></title>
            <link rel="alternate" href="https://opencli.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/407"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The OpenCLI specification (OCS) defines a standard, platform and language agnostic interface to CLI applications which allows both humans and computers to understand how a CLI tool should be invoked without access to source code or documentation.

An OpenCLI Description can be used by documentation software to display usage of a tool, or code generation tools to create clients for interoping with a CLI tool.

- [OpenCLI @ GitHub](https://github.com/spectreconsole/open-cli).

Related contents:

- [Introducing OpenCLI @ Patrik Svensson](https://patriksvensson.se/posts/2025/07/introducing-open-cli).]]>
            </summary>
            <updated>2025-08-28T17:05:51+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/716</id>
            <title type="text"><![CDATA[Event Destinations Initiative]]></title>
            <link rel="alternate" href="https://eventdestinations.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/716"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A model for event interoperability between event producers and their consumers to favor better developer experience, robust integration, and infrastructural efficiency. 

- [Event Destinations Initiative @ GitHub](https://github.com/hookdeck/event-destinations).]]>
            </summary>
            <updated>2025-08-28T17:58:14+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/928</id>
            <title type="text"><![CDATA[12 Factor Agents]]></title>
            <link rel="alternate" href="https://github.com/humanlayer/12-factor-agents" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/928"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Principles for building reliable LLM applications.

What are the principles we can use to build LLM-powered software that is actually good enough to put in the hands of production customers?]]>
            </summary>
            <updated>2025-08-28T18:32:33+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/936</id>
            <title type="text"><![CDATA[SustainableIT.org]]></title>
            <link rel="alternate" href="https://www.sustainableit.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/936"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Advancing Global Sustainability through Technology Leadership

For too long, sustainability has been someone else’s problem to solve. It’s time for technology leaders to take a stand for sustainability, as one. Together we can drive digital transformation programs that unlock the art of the possible.

Related contents:

- [Making the Internet Sustainable— Starting from Its Infrastructure @ fastly](https://www.fastly.com/blog/making-the-internet-sustainable-starting-from-its-infrastructure).]]>
            </summary>
            <updated>2025-08-28T18:34:37+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/945</id>
            <title type="text"><![CDATA[ts-rest]]></title>
            <link rel="alternate" href="https://ts-rest.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/945"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Incrementally adoptable type-safety for your new and existing APIs.
 RPC-like client, contract, and server implementation for a pure REST API 

ts-rest offers a simple way to define a contract for your API, which can be both consumed and implemented by your application, giving you end to end type safety without the hassle or code generation.

- [ts-rest @ GitHub](https://github.com/ts-rest/ts-rest).]]>
            </summary>
            <updated>2025-08-28T18:35:34+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1001</id>
            <title type="text"><![CDATA[Agent2Agent Protocol (A2A)]]></title>
            <link rel="alternate" href="https://google.github.io/A2A/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1001"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open protocol enabling communication and interoperability between opaque agentic applications.

One of the biggest challenges in enterprise AI adoption is getting agents built on different frameworks and vendors to work together. That’s why we created an open Agent2Agent (A2A) protocol, a collaborative way to help agents across different ecosystems communicate with each other.

- [Agent2Agent Protocol (A2A) @ GitHub](https://github.com/google/A2A).

Related contents:

- [Announcing the Agent2Agent Protocol (A2A) @ Google for Developers](https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/).
- [MCP vs. A2A: Friends or Foes? @ SwirlAI Newsletter](https://www.newsletter.swirlai.com/p/mcp-vs-a2a-friends-or-foes).]]>
            </summary>
            <updated>2025-08-28T18:44:39+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1028</id>
            <title type="text"><![CDATA[The Update Framework (TUF)]]></title>
            <link rel="alternate" href="https://theupdateframework.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1028"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A framework for securing software update systems.

The Update Framework (TUF) maintains the security of software update systems, providing protection even against attackers that compromise the repository or signing keys. TUF provides a flexible framework and specification that developers can adopt into any software update system.

- [The Update Framework specification @ GitHub](https://github.com/theupdateframework/specification).
- [python-tuf @ GitHub](https://github.com/theupdateframework/python-tuf).

Related contents:

- [Episode \#497: sécurisation de la chaîne d’approvisionnement logicielle (software supply chain) @ NoLimitSecu :fr:](https://www.nolimitsecu.fr/).
- [Secure publication of Datadog Agent integrations with TUF and in-toto @ Datadog](https://www.datadoghq.com/blog/engineering/secure-publication-of-datadog-agent-integrations-with-tuf-and-in-toto/).]]>
            </summary>
            <updated>2025-08-28T18:48:41+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1055</id>
            <title type="text"><![CDATA[SimpleFIN]]></title>
            <link rel="alternate" href="https://www.simplefin.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1055"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[SimpleFIN (also SFIN) stands for Simple Financial Interchange and makes read-only financial interchange simple. It’s like RSS for financial information.

SimpleFIN is like a window on a safe: it lets people look at, but not touch your financial information. And you control who can look through the window!

Related contents:

- [Episode 627: The 2 a.m. Rescue @ Linux Unplugged](https://linuxunplugged.com/627).]]>
            </summary>
            <updated>2025-08-28T18:52:44+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1064</id>
            <title type="text"><![CDATA[FOCUS™ - FinOps Open Cost &amp;amp; Usage Specification]]></title>
            <link rel="alternate" href="https://focus.finops.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1064"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The FinOps Open Cost and Usage Specification (FOCUS™) is an open-source specification that defines clear requirements for billing data generators to produce consistent cost and usage datasets.

Related contents:

- [Simplify multi-cloud cost management with FOCUS and Datadog @ Datadog](https://www.datadoghq.com/blog/focus-and-datadog/).
- [The FOCUS Problem Nobody Talks About (Until It Breaks Your Data) @ FinOps: Zero to Hero](https://finopszerotohero.substack.com/p/the-focus-problem-nobody-talks-about).]]>
            </summary>
            <updated>2026-02-20T16:40:49+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1184</id>
            <title type="text"><![CDATA[Vibe Coding Manifesto]]></title>
            <link rel="alternate" href="https://vibemanifesto.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1184"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[We are uncovering a new way of building software by embracing AI, iteration, and human intuition.

- [Vibe Coding Manifesto Landing Page @ GitHub](https://github.com/przadka/vibemanifesto-lp/).]]>
            </summary>
            <updated>2025-08-28T19:14:54+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1369</id>
            <title type="text"><![CDATA[agents.json]]></title>
            <link rel="alternate" href="https://docs.wild-card.ai/agentsjson/introduction" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1369"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The agents.json Specification is an open specification that formally describes contracts for API and agent interactions, built on top of the OpenAPI standard.

- [agents.json @ GitHub](https://github.com/wild-card-ai/agents-json).]]>
            </summary>
            <updated>2025-08-28T19:44:10+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1393</id>
            <title type="text"><![CDATA[MessagePack]]></title>
            <link rel="alternate" href="https://msgpack.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1393"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[MessagePack is an extremely efficient object serialization library. It&amp;#039;s like JSON, but very fast and small.

It&amp;#039;s like JSON. but fast and small.
MessagePack is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it&amp;#039;s faster and smaller. Small integers are encoded into a single byte, and typical short strings require only one extra byte in addition to the strings themselves.

- [MessagePack @ GitHub](https://github.com/msgpack/msgpack).

Related contents:

- [Begrudgingly choosing CBOR over MessagePack @ taylor.town](https://taylor.town/flat-scraps-001).]]>
            </summary>
            <updated>2025-08-28T19:48:12+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1550</id>
            <title type="text"><![CDATA[Citation Style Language]]></title>
            <link rel="alternate" href="https://citationstyles.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1550"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Welcome to the open source Citation Style Language (CSL) project! Our goal is to facilitate scholarly publishing by automating the formatting of citations and bibliographies. We develop the Citation Style Language and maintain a crowdsourced repository with over 10,000 free CSL citation styles.

- [Schemas describing the Citation Style Language @ GitHub](https://github.com/citation-style-language/schema).]]>
            </summary>
            <updated>2025-08-28T20:15:28+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1762</id>
            <title type="text"><![CDATA[OAuth]]></title>
            <link rel="alternate" href="https://oauth.net/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1762"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open protocol to allow secure authorization in a simple and standard method from web, mobile and desktop applications.

Related contents:

- [What&amp;#039;s OAuth2 Anyway? @ Roman Glushko Blog](https://www.romaglushko.com/blog/whats-aouth2/).
- [What is OAuth? @ leaflet](https://leaflet.pub/p/did:plc:3vdrgzr2zybocs45yfhcr6ur/3mfd2oxx5v22b).]]>
            </summary>
            <updated>2026-02-23T13:13:36+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1838</id>
            <title type="text"><![CDATA[The Seven-Action Documentation model]]></title>
            <link rel="alternate" href="https://passo.uno/seven-action-model/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1838"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[I think all technical writers, at some point or another, feel the urge to base their work on something more systematic than “it’s just the way folks documented stuff since forever”. Toolkits and frameworks provide content types, which is immensely valuable when you know what you want to write, but starting from there is like buying a hammer without knowing that half of the work you’ll do is turning screws. As I find the lack of deeper conversation around this topic rather unsettling, I decided to contribute some verses.]]>
            </summary>
            <updated>2025-08-28T21:03:57+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1964</id>
            <title type="text"><![CDATA[RomVer]]></title>
            <link rel="alternate" href="https://github.com/romversioning/romver" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1964"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Romantic Versioning Specification.

You are given a version number HUMAN . MAJOR . MINOR, increment the:

- HUMAN version when you make any conceptual change, major rewrite, major documentation change, or any other change which requires additional HUMAN involvement.
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backward-compatible manner or fix with backward-compatible bug fixes.]]>
            </summary>
            <updated>2025-08-28T21:24:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/1965</id>
            <title type="text"><![CDATA[Epoch Semantic Versioning]]></title>
            <link rel="alternate" href="https://antfu.me/posts/epoch-semver" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1965"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[In an ideal world, I would wish SemVer to have 4 numbers: EPOCH.MAJOR.MINOR.PATCH. The EPOCH version is for those big announcements, while MAJOR is for technical incompatible API changes that might not be significant. This way, we can have a more granular way to communicate changes. Similarly, we also have Romantic Versioning that propose HUMAN.MAJOR.MINOR.]]>
            </summary>
            <updated>2025-08-28T21:24:19+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2194</id>
            <title type="text"><![CDATA[Feature-Sliced Design]]></title>
            <link rel="alternate" href="https://feature-sliced.design/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2194"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Architectural methodology for frontend projects.

Feature-Sliced Design (FSD) is an architectural methodology for scaffolding front-end applications. Simply put, it&amp;#039;s a compilation of rules and conventions on organizing code. The main purpose of this methodology is to make the project more understandable and structured in the face of ever-changing business requirements.

- [Feature-Sliced Design @ GitHub](https://github.com/feature-sliced/documentation).

Source: [Architectures of modern Front-end applications @ BRACKETS&amp;#039; Medium](https://blog.meetbrackets.com/architectures-of-modern-front-end-applications-8859dfe6c12e).]]>
            </summary>
            <updated>2025-08-28T22:01:34+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2609</id>
            <title type="text"><![CDATA[JSON Lines]]></title>
            <link rel="alternate" href="https://jsonlines.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2609"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[This page describes the JSON Lines text format, also called newline-delimited JSON. JSON Lines is a convenient format for storing structured data that may be processed one record at a time. It works well with unix-style text processing tools and shell pipelines. It&amp;#039;s a great format for log files. It&amp;#039;s also a flexible format for passing messages between cooperating processes.]]>
            </summary>
            <updated>2025-08-28T23:11:07+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2714</id>
            <title type="text"><![CDATA[PCI Security Standards Council]]></title>
            <link rel="alternate" href="https://www.pcisecuritystandards.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2714"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Protect Payment Data with Industry-driven Security Standards, Training, and Programs.

- [Échange avec un ancien RSSI. Aujourd&amp;#039;hui auditeur PCI DSS (QSA) | \#6 @ Cybersécurité All Day :fr:](https://cybersecuriteallday.fr/episode/echange-avec-un-ancien-rssi-aujourdhui-auditeur-pci-dss-qsa-61).]]>
            </summary>
            <updated>2025-08-28T23:29:19+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2765</id>
            <title type="text"><![CDATA[BSON (Binary JSON) Serialization]]></title>
            <link rel="alternate" href="https://bsonspec.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2765"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[BSON, short for Bin­ary JSON, is a bin­ary-en­coded seri­al­iz­a­tion of JSON-like doc­u­ments. Like JSON, BSON sup­ports the em­bed­ding of doc­u­ments and ar­rays with­in oth­er doc­u­ments and ar­rays. BSON also con­tains ex­ten­sions that al­low rep­res­ent­a­tion of data types that are not part of the JSON spec. For ex­ample, BSON has a Date type and a BinData type.]]>
            </summary>
            <updated>2025-08-28T23:37:31+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/2775</id>
            <title type="text"><![CDATA[Plus Codes]]></title>
            <link rel="alternate" href="https://maps.google.com/pluscodes/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/2775"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Plus Codes are like street addresses for people or places that don’t have one. Instead of addresses with street names and numbers, Plus Codes are based on latitude and longitude, and displayed as numbers and letters. With a Plus Code, people can receive deliveries, access emergency and social services, or just help other people find them. 

- [Open Location Code @ GitHub](https://github.com/google/open-location-code).
- [Open Location Code @ Wikipedia](https://en.wikipedia.org/wiki/Open_Location_Code).]]>
            </summary>
            <updated>2025-08-28T23:39:20+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3042</id>
            <title type="text"><![CDATA[Open Podcast API]]></title>
            <link rel="alternate" href="https://openpodcastapi.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3042"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A new API for podcast synchronization.

The Open Podcast API is an initiative aiming to provide a feature-complete synchronization API specification for podcast (web) apps and user-focused servers.

- [Open Podcast API specification @ GitHub](https://github.com/OpenPodcastApi/api-specs).]]>
            </summary>
            <updated>2025-08-29T00:24:22+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3099</id>
            <title type="text"><![CDATA[TypeSchema]]></title>
            <link rel="alternate" href="https://typeschema.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3099"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[TypeSchema is a JSON specification to describe data models.

TypeSchema is a JSON format to describe data models in a language neutral format. A TypeSchema specification can be easily transformed into code for almost any programming language. This helps to reuse core data models in different environments.

- [TypeSchema @ GitHub](https://github.com/apioo/typeschema).]]>
            </summary>
            <updated>2025-08-29T00:32:34+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3255</id>
            <title type="text"><![CDATA[Solid]]></title>
            <link rel="alternate" href="https://solidproject.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3255"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Solid is an evolution of the web by its creator Sir Tim Berners-Lee. Solid realizes Tim&amp;#039;s original vision for the Web as a medium for the secure, decentralized exchange of public and private data.

- [Solid @ GitHub](https://github.com/solid/).]]>
            </summary>
            <updated>2025-08-29T00:58:45+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3341</id>
            <title type="text"><![CDATA[Podcasting 2.0]]></title>
            <link rel="alternate" href="https://podcasting2.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3341"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Podcasting 2.0 is making podcasting better for audiences, podcasters, and developers.

Podcasting 2.0 is a set of new features and standards that make podcasting better for everyone.

Podcasting 2.0 extends the RSS standard - the core technology that makes podcasting possible - to add new features. None of these features break any existing podcast feeds or podcast players, but, where supported, they enable podcasters to do more things, and enhance the experience for the audience.]]>
            </summary>
            <updated>2025-08-29T01:12:59+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3394</id>
            <title type="text"><![CDATA[GeoJSON]]></title>
            <link rel="alternate" href="https://geojson.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3394"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[GeoJSON is a format for encoding a variety of geographic data structures.

GeoJSON supports the following geometry types: Point, LineString, Polygon, MultiPoint, MultiLineString, and MultiPolygon. Geometric objects with additional properties are Feature objects. Sets of features are contained by FeatureCollection objects.]]>
            </summary>
            <updated>2025-08-29T01:21:59+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3486</id>
            <title type="text"><![CDATA[The KDL Document Language]]></title>
            <link rel="alternate" href="https://kdl.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3486"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[KDL is a small, pleasing document language with xml-like semantics that looks like you&amp;#039;re invoking a bunch of CLI commands! It&amp;#039;s meant to be used both as a serialization format and a configuration language, much like JSON, YAML, or XML.

Related contents:

- [Abstraction, not syntax @ Ruud van Asseldonk](https://ruudvanasseldonk.com/2025/abstraction-not-syntax).]]>
            </summary>
            <updated>2025-10-14T12:14:51+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3493</id>
            <title type="text"><![CDATA[Nostr]]></title>
            <link rel="alternate" href="https://nostr.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3493"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[a simple protocol for decentralizing social media that has a chance of working.
a truly censorship-resistant alternative to Twitter that has a chance of working.

A better internet is possible: decentralize Twitter, eBay, IoT and other stuff.

Smart-client/dumb-server architecture that can create the free and open internet we were promised.

- [Nostr @ GitHub](https://github.com/nostr-protocol/nostr).
- [Nostr Apps](https://nostrapps.com/).
- [Nature&amp;#039;s many attempts to evolve a Nostr @ Squishy](https://newsletter.squishy.computer/p/natures-many-attempts-to-evolve-a).
- [Use Protocols, Not Services @ ~~p](https://notnotp.com/notes/use-protocols-not-services/).]]>
            </summary>
            <updated>2026-02-17T12:53:04+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3651</id>
            <title type="text"><![CDATA[XDG Base Directory Specification]]></title>
            <link rel="alternate" href="https://specifications.freedesktop.org/basedir-spec/latest/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3651"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Various specifications specify files and file formats. This specification defines where these files should be looked for by defining one or more base directories relative to which files should be located.]]>
            </summary>
            <updated>2025-08-29T02:05:33+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3763</id>
            <title type="text"><![CDATA[Patch Codes]]></title>
            <link rel="alternate" href="https://www.alliancegroup.co.uk/patch-codes.htm" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3763"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Patch codes are a set of 6 distinct barcode patterns (1, 2, 3, 4, 6 and T) that are typically used as document separators when scanning.]]>
            </summary>
            <updated>2025-08-29T02:23:31+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3802</id>
            <title type="text"><![CDATA[ForgeFed]]></title>
            <link rel="alternate" href="https://forgefed.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3802"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[ForgeFed is a federation protocol for software forges and code collaboration tools for the software development lifecycle and ecosystem. This includes repository hosting websites, issue trackers, code review applications, and more. ForgeFed provides a common substrate for people to create interoperable code collaboration websites and applications.

- [Episode 129: Forged Alliance @ Self Hosted](https://selfhosted.show/129).]]>
            </summary>
            <updated>2025-08-29T02:30:35+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3837</id>
            <title type="text"><![CDATA[Fair Source]]></title>
            <link rel="alternate" href="https://fair.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3837"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Software Sharing for Modern Businesses.

Engage the developer community with your company&amp;#039;s core software products. Fair Source Software (FSS):

* is publicly available to read;
* allows use, modification, and redistribution with minimal restrictions to protect the producer’s business model; and
* undergoes delayed Open Source publication (DOSP).

The intention is for the first point to be a bright line, and for the second to invite exploration. We expect Fair Source licenses to emerge and evolve and shake out into a few clear winners over time, as companies apply Fair Source within their own particular business context. 

- [fair.io @ GitHub](https://github.com/fairsource/fair.io).]]>
            </summary>
            <updated>2025-08-29T02:37:36+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3904</id>
            <title type="text"><![CDATA[tus - resumable file uploads]]></title>
            <link rel="alternate" href="https://tus.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3904"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[resumable file uploads.

tus is the open protocol standard for resumable and reliable file uploads across the web, facilitating efficient and seamless file transfer experiences.

- [tus @ GitHub](https://github.com/tus).]]>
            </summary>
            <updated>2025-08-29T02:47:40+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/3965</id>
            <title type="text"><![CDATA[JSON:API]]></title>
            <link rel="alternate" href="https://jsonapi.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/3965"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A specification for building APIs in JSON.

Documentation for the application/vnd.api+json media type, a specification for APIs that use JSON.

If you’ve ever argued with your team about the way your JSON responses should be formatted, JSON:API can help you stop the bikeshedding and focus on what matters: your application.
By following shared conventions, you can increase productivity, take advantage of generalized tooling and best practices. Clients built around JSON:API are able to take advantage of its features around efficiently caching responses, sometimes eliminating network requests entirely.

- [JSON:API @ GitHub](https://github.com/json-api/json-api).]]>
            </summary>
            <updated>2025-08-29T02:57:51+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4062</id>
            <title type="text"><![CDATA[C2PA]]></title>
            <link rel="alternate" href="https://c2pa.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4062"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Coalition for Content Provenance and Authenticity.

An open technical standard providing publishers, creators, and consumers the ability to trace the origin of different types of media. 

- [C2PA @ GitHub](https://github.com/c2pa-org).

Related contents:

- [481 : Episode du 12 février 2025 @ Les Technos :fr:](https://lestechnos.be/les-technos-481-episode-du-12-fevrier/).]]>
            </summary>
            <updated>2025-08-29T03:14:03+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4201</id>
            <title type="text"><![CDATA[Architectural Decision Records]]></title>
            <link rel="alternate" href="https://adr.github.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4201"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An Architectural Decision (AD) is a justified design choice that addresses a functional or non-functional requirement that is architecturally significant.

- [Architecture decision record (ADR) @ GitHub](https://github.com/joelparkerhenderson/architecture-decision-record).
- [Pourquoi écrire des Documents de Choix d&amp;#039;Architecture ? (Architecture Decision Record)  @ Avalon Lab&amp;#039;s dev.to :fr:](https://dev.to/avalon-lab/pourquoi-ecrire-des-documents-de-choix-d-architecture-architecture-decision-record-101c).]]>
            </summary>
            <updated>2025-08-29T03:38:09+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4235</id>
            <title type="text"><![CDATA[TypeSpec]]></title>
            <link rel="alternate" href="https://typespec.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4235"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Describe APIs. Describe your data up front and generate schemas, API specifications, client / server code, docs, and more.

TypeSpec is a language for defining cloud service APIs and shapes. TypeSpec is a highly extensible language with primitives that can describe API shapes common among REST, OpenAPI, gRPC, and other protocols.

- [TypeSpec @ GitHub](https://github.com/Microsoft/typespec).
- [Introduction to TypeSpec @ Nordic APIs](https://nordicapis.com/introduction-to-typespec/).
- [ After 6 years of using GraphQL in production we aren&amp;#039;t reaching for it as much as we once did.  @ Mahdi Y.&amp;#039;s LinkedIn](https://www.linkedin.com/posts/myusuf3_after-6-years-of-using-graphql-in-production-activity-7205361996836302848-I100/).]]>
            </summary>
            <updated>2025-08-29T03:42:15+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4240</id>
            <title type="text"><![CDATA[The C4 model]]></title>
            <link rel="alternate" href="https://c4model.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4240"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The C4 model for visualising software architecture: Context, Containers, Components, and Code.

The C4 model was created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase. It&amp;#039;s a way to create maps of your code, at various levels of detail, in the same way you would use something like Google Maps to zoom in and out of an area you are interested in. 

- [What is the C4 model? @ IcePanel](https://icepanel.io/blog/2024-07-18-what-is-the-c4-model).
- [Comparison - C4 model vs UML @ IcePanel](https://icepanel.io/blog/2024-07-29-comparison-c4-model-vs-UML).
- [The C4 Model for Software Architecture @ InfoQ](https://www.infoq.com/articles/C4-architecture-model/).]]>
            </summary>
            <updated>2025-08-29T03:43:12+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4241</id>
            <title type="text"><![CDATA[JSON Schema]]></title>
            <link rel="alternate" href="https://json-schema.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4241"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[While JSON is probably the most popular format for exchanging data, JSON Schema is the vocabulary that enables JSON data consistency, validity, and interoperability at scale.]]>
            </summary>
            <updated>2025-08-29T03:43:12+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4251</id>
            <title type="text"><![CDATA[JSON5]]></title>
            <link rel="alternate" href="https://json5.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4251"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[JSON for Humans.

JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). It is not intended to be used for machine-to-machine communication. (Keep using JSON or other file formats for that. 🙂)

- [JSON5 @ GitHub](https://github.com/json5/json5),

Related contents:

- [Abstraction, not syntax @ Ruud van Asseldonk](https://ruudvanasseldonk.com/2025/abstraction-not-syntax).]]>
            </summary>
            <updated>2025-10-14T12:16:15+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4255</id>
            <title type="text"><![CDATA[libyear]]></title>
            <link rel="alternate" href="https://libyear.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4255"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A simple measure of software dependency freshness. It is a single number telling you how up-to-date your dependencies are.]]>
            </summary>
            <updated>2025-08-29T03:46:16+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4282</id>
            <title type="text"><![CDATA[Schema.org]]></title>
            <link rel="alternate" href="https://schema.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4282"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond.

Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences.]]>
            </summary>
            <updated>2025-08-29T03:50:19+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4354</id>
            <title type="text"><![CDATA[JSON Meta Application Protocol Specification (JMAP)]]></title>
            <link rel="alternate" href="https://jmap.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4354"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Become a leader in email innovation. JMAP is the developer-friendly, open API standard for modern mail clients and applications to manage email faster.

It’s official! JMAP has been published by the Internet Engineering Task Force (IETF).]]>
            </summary>
            <updated>2025-08-29T04:02:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4362</id>
            <title type="text"><![CDATA[Open Initiative for Process Specifications]]></title>
            <link rel="alternate" href="https://outreach.eclipse.foundation/open-source-cybersecurity-specifications" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4362"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Open Initiative for Process Specifications.

The open source community is collaborating to establish common specifications for secure software development based on open source best practices. 

- [New Open Initiative for Cybersecurity Standards @ Python Software Foundation&amp;#039;s Blogspot](https://pyfound.blogspot.com/2024/04/new-open-initiative-for-cybersecurity.html).]]>
            </summary>
            <updated>2025-08-29T04:03:24+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4427</id>
            <title type="text"><![CDATA[OpenFeature]]></title>
            <link rel="alternate" href="https://openfeature.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4427"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Standardizing Feature Flagging for Everyone.

OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool or in-house solution.

- [OpenFeature @ GitHub](https://github.com/open-feature).]]>
            </summary>
            <updated>2025-08-29T04:14:36+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4500</id>
            <title type="text"><![CDATA[Docker Compose Specification]]></title>
            <link rel="alternate" href="https://compose-spec.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4500"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A specification for developer-centric application definition used in Cloud Native Applications

The Compose Specification is a developer-focused standard for defining cloud and platform agnostic container-based applications.

- [compose-spec @ GitHub](https://github.com/compose-spec/compose-spec).]]>
            </summary>
            <updated>2025-12-02T10:35:39+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4518</id>
            <title type="text"><![CDATA[RFC 7807 - Problem Details for HTTP APIs]]></title>
            <link rel="alternate" href="https://datatracker.ietf.org/doc/html/rfc7807" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4518"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[This document defines a &amp;quot;problem detail&amp;quot; as a way to carry machine-readable details of errors in a HTTP response to avoid the need to define new error response formats for HTTP APIs.]]>
            </summary>
            <updated>2025-08-29T04:30:38+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4530</id>
            <title type="text"><![CDATA[OpenPubkey]]></title>
            <link rel="alternate" href="https://www.bastionzero.com/openpubkey" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4530"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[OpenPubkey is an open source project that binds public keys and workload identities using standard SSO and OpenID Connect.

Use OpenPubkey today to SSH to machines on your network without SSH keys.

- [OpenPubkey @ GitHub](https://github.com/openpubkey/openpubkey).
- [OpenPubkey: Augmenting OpenID Connect with User held Signing Keys @ Cryptology ePrint Archive](https://eprint.iacr.org/2023/296).
- [How to Use OpenPubkey to Solve Key Management via SSO @ Docker Blog](https://www.docker.com/blog/how-to-use-openpubkey-to-solve-key-management-via-sso/).]]>
            </summary>
            <updated>2025-08-29T04:31:38+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4578</id>
            <title type="text"><![CDATA[security.txt]]></title>
            <link rel="alternate" href="https://securitytxt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4578"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A proposed standard which allows websites to define security policies.

 “When security risks in web services are discovered by independent security researchers who understand the severity of the risk, they often lack the channels to disclose them properly. As a result, security issues may be left unreported. security.txt defines a standard to help organizations define the process for security researchers to disclose security vulnerabilities securely.”]]>
            </summary>
            <updated>2025-08-29T04:39:42+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4629</id>
            <title type="text"><![CDATA[Willow]]></title>
            <link rel="alternate" href="https://willowprotocol.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4629"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A protocol for peer-to-peer data stores. The best parts? Fine-grained permissions, a keen approach to privacy, destructive edits, and a dainty bandwidth and memory footprint.]]>
            </summary>
            <updated>2025-08-29T04:48:45+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4717</id>
            <title type="text"><![CDATA[Minimum Viable Secure Product]]></title>
            <link rel="alternate" href="https://mvsp.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4717"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A minimum security baseline for enterprise-ready products and services.

Minimum Viable Secure Product (MVSP) is a list of essential application security controls that should be implemented in enterprise-ready products and services. The controls are designed to be simple to implement and provide a good foundation for building secure and resilient systems and services. MVSP is based on the experience of contributors in enterprise application security and has been built with contributions from a range of companies.

- [Two years later: a baseline that drives up security for the industry @ Google Security Blog](https://security.googleblog.com/2023/11/two-years-later-baseline-that-drives-up.html).]]>
            </summary>
            <updated>2025-08-29T05:02:59+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4840</id>
            <title type="text"><![CDATA[editingprotocol&amp;#039;s Blog]]></title>
            <link rel="alternate" href="https://editingprotocol.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4840"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Green Standard Editing Protocol for Internet Publishing. 

a set of rules and guidelines that can be used by humans and machines to determine whether a story is worth publishing, how to specifically improve the story’s content, and how to distribute the story with more reach and relevance.

- [HackerNoon Releases “The Editing Protocol” - Technical Documentation for Digital Publishing at Scale @ HackerNoon](https://hackernoon.com/hackernoon-releases-the-editing-protocol-technical-documentation-for-digital-publishing-at-scale).]]>
            </summary>
            <updated>2025-08-29T05:23:09+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4932</id>
            <title type="text"><![CDATA[Open Federation Initiative]]></title>
            <link rel="alternate" href="https://open-federation.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4932"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Open Federation is a community-driven open source initiative to create and maintain a specification for federated GraphQL APIs. Be part of the future; let&amp;#039;s craft together.]]>
            </summary>
            <updated>2025-08-29T05:39:14+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4970</id>
            <title type="text"><![CDATA[The Penetration Testing Execution Standard (PTES)]]></title>
            <link rel="alternate" href="http://www.pentest-standard.org/index.php/Main_Page" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4970"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The penetration testing execution standard consists of seven (7) main sections.

These cover everything related to a penetration test - from the initial communication and reasoning behind a pentest, through the intelligence gathering and threat modeling phases where testers are working behind the scenes in order to get a better understanding of the tested organization, through vulnerability research, exploitation and post exploitation, where the technical security expertise of the testers come to play and combine with the business understanding of the engagement, and finally to the reporting, which captures the entire process, in a manner that makes sense to the customer and provides the most value to it.]]>
            </summary>
            <updated>2025-08-29T05:45:15+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5048</id>
            <title type="text"><![CDATA[OpenMetrics]]></title>
            <link rel="alternate" href="https://openmetrics.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5048"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Evolving the Prometheus exposition format into a standard.

OpenMetrics a specification built upon and carefully extending Prometheus exposition format in almost 100% backwards-compatible ways.

[OpenMetrics @ GitHub](https://github.com/OpenObservability/OpenMetrics).]]>
            </summary>
            <updated>2025-08-29T05:59:22+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5056</id>
            <title type="text"><![CDATA[sFlow]]></title>
            <link rel="alternate" href="https://sflow.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5056"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Making the Network Visible.

sFlow® is an industry standard technology for monitoring high speed switched networks. It gives complete visibility into the use of networks enabling performance optimization, accounting/billing for usage, and defense against security threats.]]>
            </summary>
            <updated>2025-08-29T05:59:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5075</id>
            <title type="text"><![CDATA[Hydra W3C Community Group]]></title>
            <link rel="alternate" href="http://www.hydra-cg.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5075"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Hydra simplifies the development of interoperable, hypermedia-driven Web APIs]]>
            </summary>
            <updated>2025-08-29T06:03:31+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5076</id>
            <title type="text"><![CDATA[JSON-LD]]></title>
            <link rel="alternate" href="https://json-ld.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5076"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[JSON for Linking Data.
Data is messy and disconnected. JSON-LD organizes and connects it, creating a better Web.]]>
            </summary>
            <updated>2025-08-29T06:03:32+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5100</id>
            <title type="text"><![CDATA[HTML Purifier]]></title>
            <link rel="alternate" href="http://htmlpurifier.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5100"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Filter your HTML the standards-compliant way!

HTML Purifier is an HTML filtering solution that uses a unique combination of robust whitelists and aggressive parsing to ensure that not only are XSS attacks thwarted, but the resulting HTML is standards compliant.

HTML Purifier is oriented towards richly formatted documents from untrusted sources that require CSS and a full tag-set. This library can be configured to accept a more restrictive set of tags, but it won&amp;#039;t be as efficient as more bare-bones parsers. It will, however, do the job right, which may be more important.

- [HTML Purifier @ GitHub](https://github.com/ezyang/htmlpurifier).
- [Security Tip: Is `strip_tags()` Secure? @ Securing Laravel](https://securinglaravel.com/p/security-tip-is-strip_tags-secure).]]>
            </summary>
            <updated>2025-08-29T06:07:27+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5225</id>
            <title type="text"><![CDATA[Open Source Program Office Definition (OSPOD)]]></title>
            <link rel="alternate" href="https://github.com/todogroup/ospodefinition.org" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5225"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open source program office (OSPO) serves as the center of competency for an organization&amp;#039;s open source operations and structure. It is responsible for defining and implementing strategies and policies to guide these efforts.]]>
            </summary>
            <updated>2025-08-29T06:27:40+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5322</id>
            <title type="text"><![CDATA[Semantic Line Breaks]]></title>
            <link rel="alternate" href="https://sembr.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5322"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[When writing text with a compatible markup language, add a line break after each substantial unit of thought.

Semantic Line Breaks describe a set of conventions for using insensitive vertical whitespace to structure prose along semantic boundaries.]]>
            </summary>
            <updated>2025-08-29T06:43:49+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5362</id>
            <title type="text"><![CDATA[Manifesto for Agile Software Development]]></title>
            <link rel="alternate" href="https://agilemanifesto.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5362"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[We are uncovering better ways of developing
software by doing it and helping others do it.]]>
            </summary>
            <updated>2025-08-29T06:51:48+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5364</id>
            <title type="text"><![CDATA[Humans TXT: We Are People, Not Machines.]]></title>
            <link rel="alternate" href="https://humanstxt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5364"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[What is humans.txt?

It&amp;#039;s an initiative for knowing the people behind a website. It&amp;#039;s a TXT file that contains information about the different people who have contributed to building the website.]]>
            </summary>
            <updated>2025-08-29T06:51:49+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5498</id>
            <title type="text"><![CDATA[SLSA]]></title>
            <link rel="alternate" href="https://slsa.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5498"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Supply-chain Levels for Software Artifacts, or SLSA (&amp;quot;salsa&amp;quot;).

SLSA is a specification for describing and incrementally improving supply chain security, established by industry consensus. It is organized into a series of levels that describe increasing security guarantees.

It’s a security framework, a checklist of standards and controls to prevent tampering, improve integrity, and secure packages and infrastructure. It’s how you get from &amp;quot;safe enough&amp;quot; to being as resilient as possible, at any link in the chain.

- [SLSA @ GitHub](https://github.com/slsa-framework/slsa).

Related contents:

- [Securing the software supply chain with the SLSA framework @ Trail of Bits Blog](https://blog.trailofbits.com/2024/10/01/securing-the-software-supply-chain-with-the-slsa-framework/).
- [Episode \#497: sécurisation de la chaîne d’approvisionnement logicielle (software supply chain) @ NoLimitSecu :fr:](https://www.nolimitsecu.fr/).
- [Kube-Policies BinauthZ: Closing the Supply Chain Gap in Kubernetes @ Block Engineering Blog](https://engineering.block.xyz/blog/kube-policies-binauthz-closing-the-supply-chain-gap-in-kubernetes).]]>
            </summary>
            <updated>2026-02-09T06:25:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5515</id>
            <title type="text"><![CDATA[Development containers]]></title>
            <link rel="alternate" href="https://containers.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5515"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open specification for enriching containers with development specific content and settings. 

A Development Container (or Dev Container for short) allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing. Dev containers can be run locally or remotely, in a private or public cloud.

- [Development Containers @ GitHub](https://github.com/devcontainers/spec).

Related contents:

- [Utilisation des DevContainer @ DevSecOps :fr:](https://blog.stephane-robert.info/docs/developper/autres-outils/ide/visual-studio-code/devcontainers/#pourquoi-utiliser-devcontainers-avec-vscode).
- [Run Your Project in a Dev Container, in Zed @ Zed blog](https://zed.dev/blog/dev-containers).]]>
            </summary>
            <updated>2026-01-19T06:47:33+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5547</id>
            <title type="text"><![CDATA[The Tao Of Backup]]></title>
            <link rel="alternate" href="http://www.taobackup.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5547"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A novice wanted to learn the Tao of Backup. The master said: To become enlightened, you must master the seven heads of Backup. He who knows the heads will keep all his data forever.]]>
            </summary>
            <updated>2025-08-29T07:21:06+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5550</id>
            <title type="text"><![CDATA[Reproducible Builds]]></title>
            <link rel="alternate" href="https://reproducible-builds.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5550"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Reproducible builds are a set of software development practices that create an independently-verifiable path from source to binary code.]]>
            </summary>
            <updated>2025-08-29T07:22:04+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5589</id>
            <title type="text"><![CDATA[Thread]]></title>
            <link rel="alternate" href="https://www.threadgroup.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5589"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Thread is a low-power and low-latency wireless mesh networking protocol built using open and proven standards. Thread solves the complexities of the IoT, addressing challenges such as interoperability, range, security, energy, and reliability. Thread networks have no single point of failure and include the ability to self-heal.]]>
            </summary>
            <updated>2025-08-29T07:28:14+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5601</id>
            <title type="text"><![CDATA[JSON Resume]]></title>
            <link rel="alternate" href="https://jsonresume.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5601"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The open source initiative to create a JSON-based standard for resumes. For developers, by developers.]]>
            </summary>
            <updated>2025-08-29T07:30:09+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5605</id>
            <title type="text"><![CDATA[Software Package Data Exchange (SPDX)]]></title>
            <link rel="alternate" href="https://spdx.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5605"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[International Open Standard (ISO/IEC 5962:2021).

SPDX is an open standard for communicating software bill of material information, including provenance, license, security, and other related information. SPDX reduces redundant work by providing common formats for organizations and communities to share important data, thereby streamlining and improving compliance, security, and dependability. The SPDX specification is recognized as the international open standard for security, license compliance, and other software supply chain artifacts as ISO/IEC 5962:2021.]]>
            </summary>
            <updated>2025-08-29T07:32:10+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5619</id>
            <title type="text"><![CDATA[Content-Security-Policy Header]]></title>
            <link rel="alternate" href="https://content-security-policy.com/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5619"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Content Security Policy Reference.

The new Content-Security-Policy HTTP response header helps you reduce XSS risks on modern browsers by declaring which dynamic resources are allowed to load.]]>
            </summary>
            <updated>2025-08-29T07:33:10+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5704</id>
            <title type="text"><![CDATA[Scrum Guides]]></title>
            <link rel="alternate" href="https://scrumguides.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5704"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Scrum is a framework for developing and sustaining complex products. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.]]>
            </summary>
            <updated>2025-08-29T07:48:21+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5719</id>
            <title type="text"><![CDATA[GDPR.txt]]></title>
            <link rel="alternate" href="https://gdpr-txt.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5719"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The GDPR.txt file is a proposed standard which informs hosting providers about the personal data collected by softwares. It aims to simplify the compliance to the General Data Protection Regulation (GDPR) of hosting providers. Note that a GDPR.txt file is not enough to make your project GDPR compliant (but it will help).]]>
            </summary>
            <updated>2025-08-29T07:50:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5765</id>
            <title type="text"><![CDATA[OpenWallet Foundation]]></title>
            <link rel="alternate" href="https://openwallet.foundation/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5765"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The OWF is a consortium of companies and non-profit organisations collaborating to drive global adoption of open, secure and interoperable digital wallet solutions as well as providing access to expertise and advice through our Government Advisory Council.]]>
            </summary>
            <updated>2025-08-29T07:57:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5766</id>
            <title type="text"><![CDATA[Open RAN]]></title>
            <link rel="alternate" href="https://open-ran.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5766"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Open RAN is intelligent Radio Access Network(RAN) integrated with general purpose platforms with open interface between software definced funtions.
Open RAN ecosystem enables enormous flexibility and interoperability with a complete openess to multi-vendor deployments.
Open RAN architecture is designed for building virtualized RAN with AI powered control, which is the key to tame the 5G/6G complexity.]]>
            </summary>
            <updated>2025-08-29T07:58:22+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5768</id>
            <title type="text"><![CDATA[Web Monetization]]></title>
            <link rel="alternate" href="https://webmonetization.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5768"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A JavaScript browser API that allows the creation of a payment stream from the user agent to the website.

[Web Monetization @ GitHub](https://github.com/WICG/webmonetization).]]>
            </summary>
            <updated>2025-08-29T07:58:23+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5902</id>
            <title type="text"><![CDATA[Nostr.how]]></title>
            <link rel="alternate" href="https://nostr.how/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5902"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A complete guide to Nostr.

The simplest open protocol that is able to create a censorship-resistant global &amp;quot;social&amp;quot; network once and for all. A social network for the decentralized era. A simple, open protocol that enables a truly censorship-resistant &amp;amp; global social network.

[Nostr @ GitHub](https://github.com/nostr-protocol/nostr).]]>
            </summary>
            <updated>2025-08-29T08:20:39+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5906</id>
            <title type="text"><![CDATA[BPMN Specification - Business Process Model and Notation]]></title>
            <link rel="alternate" href="https://www.bpmn.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5906"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A standard Business Process Model and Notation (BPMN) will provide businesses with the capability of understanding their internal business procedures in a graphical notation and will give organizations the ability to communicate these procedures in a standard manner. Furthermore, the graphical notation will facilitate the understanding of the performance collaborations and business transactions between the organizations. This will ensure that businesses will understand themselves and participants in their business and will enable organizations to adjust to new internal and B2B business circumstances quickly.]]>
            </summary>
            <updated>2025-08-29T08:21:34+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5911</id>
            <title type="text"><![CDATA[OpenIDL]]></title>
            <link rel="alternate" href="https://openidl.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5911"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[an open blockchain network for insurers.

openIDL (open Insurance Data Link) is an open blockchain network that streamlines regulatory reporting and provides new insights for insurers, while enhancing timeliness, accuracy, and value for regulators. openIDL is the first open blockchain platform that enables the efficient, secure, and permissioned-based collection and sharing of statistical data.

[OpenIDL @ GitHub](https://github.com/openidl-org).]]>
            </summary>
            <updated>2025-08-29T08:22:34+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5953</id>
            <title type="text"><![CDATA[H5P]]></title>
            <link rel="alternate" href="https://h5p.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5953"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Create, share and reuse interactive HTML5 content in your browser]]>
            </summary>
            <updated>2025-08-29T08:29:37+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5993</id>
            <title type="text"><![CDATA[OpenVEX Specification]]></title>
            <link rel="alternate" href="https://github.com/openvex/spec" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5993"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[OpenVEX is an implementation of the Vulnerability Exploitability Exchange (VEX for short) that is designed to be minimal, compliant, interoperable, and embeddable. The specification is available in the OPENVEX-SPEC.md file of this repository.]]>
            </summary>
            <updated>2025-08-29T08:36:45+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/6019</id>
            <title type="text"><![CDATA[Conventional Commits]]></title>
            <link rel="alternate" href="https://www.conventionalcommits.org/en/v1.0.0/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/6019"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A specification for adding human and machine readable meaning to commit messages.

- [Conventional Commits @ GitHub](https://github.com/conventional-commits/conventionalcommits.org).

Related contents:

- [Conventional Commit @ DevSecOps :fr:](https://blog.stephane-robert.info/docs/developper/conventional-commits/).]]>
            </summary>
            <updated>2025-08-29T08:40:47+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/6264</id>
            <title type="text"><![CDATA[gRPC]]></title>
            <link rel="alternate" href="https://grpc.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/6264"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A high performance, open source universal RPC framework.
gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services.

Related contents:

- [grpConf 2025 @ CNCF&amp;#039;s YouTube](https://www.youtube.com/playlist?list=PLj6h78yzYM2On4kCcnWjlO2lpHq-etZ1d).]]>
            </summary>
            <updated>2025-09-15T13:14:33+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/6473</id>
            <title type="text"><![CDATA[Guide to Web Authentication]]></title>
            <link rel="alternate" href="https://webauthn.guide/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/6473"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A better alternative for securing our sensitive information online.

The Web Authentication API (also known as WebAuthn) is a specification written by the W3C and FIDO, with the participation of Google, Mozilla, Microsoft, Yubico, and others. The API allows servers to register and authenticate users using public key cryptography instead of a password.]]>
            </summary>
            <updated>2025-08-29T09:57:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/6598</id>
            <title type="text"><![CDATA[Data Food Consortium]]></title>
            <link rel="alternate" href="https://www.datafoodconsortium.org/en/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/6598"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A common and open digital language to develop short supply chains]]>
            </summary>
            <updated>2025-08-29T10:17:39+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/7004</id>
            <title type="text"><![CDATA[Semantic Versioning]]></title>
            <link rel="alternate" href="https://semver.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/7004"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Given a version number MAJOR.MINOR.PATCH, increment the:

    MAJOR version when you make incompatible API changes,
    MINOR version when you add functionality in a backwards compatible manner, and
    PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

- [Using Semantic Versioning to Simplify Release Management @ AWS DevOps &amp;amp; Developer Productivity Blog](https://aws.amazon.com/blogs/devops/using-semantic-versioning-to-simplify-release-management/).
- [Against SemVer @ Nate Meyvis](https://www.natemeyvis.com/against-semver/).]]>
            </summary>
            <updated>2025-12-24T12:47:04+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/9150</id>
            <title type="text"><![CDATA[OASIS Darwin Information Typing Architecture (DITA) TC]]></title>
            <link rel="alternate" href="http://dita.xml.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/9150"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering readable information as discrete, typed topics.]]>
            </summary>
            <updated>2025-08-29T17:22:41+00:00</updated>
        </entry>
    </feed>
