<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>specification</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/1986/feed"/>
    <updated>2026-04-19T01:28:50+00:00</updated>
    <id>https://links.biapy.com/guest/tags/1986/feed</id>
            <entry>
            <id>https://links.biapy.com/links/11846</id>
            <title type="text"><![CDATA[WebMCP]]></title>
            <link rel="alternate" href="https://webmachinelearning.github.io/webmcp/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11846"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[The WebMCP API enables web applications to provide JavaScript-based tools to AI agents.

- [WebMCP @ GitHub](https://github.com/webmachinelearning/webmcp/).

Related contents:

- [Chrome’s WebMCP makes AI agents stop pretending @ Reading.sh&amp;#039;s Medium](https://medium.com/reading-sh/chromes-webmcp-makes-ai-agents-stop-pretending-e8c7da1ba650).
- [\#127 - News Février 2026, du WebMCP, des agents spammeurs et du Markdown @ Double Slash :fr:](https://double-slash.dev/podcasts/news-fev26/).]]>
            </summary>
            <updated>2026-02-20T07:11:25+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11482</id>
            <title type="text"><![CDATA[Open Responses]]></title>
            <link rel="alternate" href="https://www.openresponses.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11482"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Open Responses is an open-source specification and ecosystem for building multi-provider, interoperable LLM interfaces based on the OpenAI Responses API. It defines a shared schema, and tooling layer that enable a unified experience for calling language models, streaming results, and composing agentic workflows—independent of provider.

- [Open Responses @ GitHub](https://github.com/openresponses/openresponses).]]>
            </summary>
            <updated>2026-01-16T12:56:54+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/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/10556</id>
            <title type="text"><![CDATA[Score]]></title>
            <link rel="alternate" href="https://score.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10556"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[One easy way to configure all your workloads. Everywhere.

 The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration inconsistencies between environments. 

- [The Score Specification @ GitHub](https://github.com/score-spec/spec).]]>
            </summary>
            <updated>2025-10-06T11:56:03+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10385</id>
            <title type="text"><![CDATA[Tessl]]></title>
            <link rel="alternate" href="https://tessl.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10385"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[AI Native Development Platform.

Supercharge your agents with spec-driven development.
Get the speed of agentic coding with the reliability of production software.

Related contents:

- [Ep 63: Running Linux on an IPad @ Linux Matters](https://linuxmatters.sh/63/).
- [The uncomfortable truth about vibe coding @ RedHat Developer](https://developers.redhat.com/articles/2026/02/17/uncomfortable-truth-about-vibe-coding).]]>
            </summary>
            <updated>2026-02-24T07:19:15+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/10072</id>
            <title type="text"><![CDATA[🌱 Spec Kit]]></title>
            <link rel="alternate" href="https://speckit.org/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/10072"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[💫 Toolkit to help you get started with Spec-Driven Development.

Build high-quality software faster.

An effort to allow organizations to focus on product scenarios rather than writing undifferentiated code with the help of Spec-Driven Development. 

Spec-Driven Development flips the script on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the &amp;quot;real work&amp;quot; of coding began. Spec-Driven Development changes this: specifications become executable, directly generating working implementations rather than just guiding them.

- [Spec Kit @ GitHub](https://github.com/github/spec-kit).
- [Spec Kit&amp;#039;s GitHub Pages](https://github.github.com/spec-kit/).

Related contents:

- [What&amp;#039;s The Deal With GitHub Spec Kit @ Den Delimarsky](https://den.dev/blog/github-spec-kit/).
- [The ONLY guide you&amp;#039;ll need for GitHub Spec Kit @ Den Delimarsky&amp;#039;s YouTube](https://www.youtube.com/watch?v=a9eR1xsfvHg).
- [How to write a good spec for AI agents @ Addy Osmani](https://addyosmani.com/blog/good-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:11+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/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>
    </feed>
