







An implementation of a Client ID Metadata Document Service
OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

Technical analysis of client identification mechanisms
[Proposal] AT-URI for cross-service records
tl;dr non-AtprotoPersonalDataServer services might host records, let’s introduce following AT-URI syntax with optional service field to reference those non-PDS hosted data. at://tangled_knot@did:plc:user/... ^^^^^^^^^^^^ ^^^ | path can be any format | (NSID/rkey prefered, but not enforced) service name (default to "atproto_pds" when omited) In this proposal, I’m going to explain why we need cross-service reco...

How Grobid uses Crossref metadata to enrich bibliographic information - Crossref | Luca F.
Early this year Crossref and I talked about how Grobid users rely on their API, and the numbers are big: in Q1 2026 alone, GROBID clients sent more than 100 million requests to consolidate extracted bibliographic data. Crossref offers three tiers: public (anonymous, low throughput), polite (identified by email, higher throughput) and Metadata Plus (paid, for large-scale use). GROBID’s integration dated back to 2014, and it turned out it needed an update. Since 0.9.0, GROBID lets you join the polite pool or use your Metadata Plus key. Consolidation is more reliable, and it’s fairer to a shared, open service. Luis M. Montilla and I had a conversation about how Grobid uses the Crossref metadata to enrich references extracted from PDFs, that eventually become a blog post: 🔗 https://lnkd.in/egxWRAV6 And there’s a next step: for really large volumes, a local service may be more suitable than the API. On 22 October at 15:15 UTC, I’ll present biblio-glutton in the Community Highlights session of the Crossref Annual Meeting. Biblio-glutton is a local metadata search service for scholary publications using the Crossref public dump and data from other services: Pubmed, HAL, OpenAlex, etc... I built with Patrice Lopez in 2016. It provides provide lookup, structured, and unstructured metadata search. The owners of the Crossref Metadata Plus subscription can keep it in sync with regular background jobs so the data is kept up-to-date. 🔗 Annual Meeting (online, free; register for Session 2): https://lnkd.in/ew699KCw 🔗 biblio-glutton: https://lnkd.in/eR6KvmJM
CID (Content IDentifier)
Self-describing content-addressed identifiers for distributed systems

tassis/atfield-core
Framework-agnostic AT Protocol utilities for identity resolution and public record reads.

From Personal Data Server to Personal Metadata Server - Liccium
Liccium builds the fundamental infrastructure that enables creators and rightsholders to publish machine-readable declarations about their digital works that…
n0-computer/iroh-docs
Multi-dimensional key-value documents with an efficient synchronization protocol.
Metadata Integration: A Systematic Review on Methods, Challenges and Applications Across Multiple Domains
Metadata contributes to ensuring semantic interoperability, data reuse, and efficient information retrieval across heterogeneous systems. However, existing studies present fragmented approaches and lack a consolidated view of the strategies adopted in different domains. This fragmentation creates a gap in understanding the current state of the art and identifying cross-domain trends and challenges. This systematic review aims to address this gap by analyzing metadata integration practices across multiple domains, including Health and Medicine, Smart Cities and IoT, Data Science, Geosciences, Cultural Heritage, Library and Information Science. This review follows the Kitchenham structure, encompassing the planning, execution, and reporting phases. A total of 81 peer-reviewed articles published between 2014 and 2025 were selected from five major databases, based on the defined inclusion and exclusion criteria and a structured quality assessment process. The results reveal a predominance of the use of ontology, followed by metadata-driven language, standards, processes, and common metadata schema with an emerging trend towards automation through the adoption of AI-based approaches. The identified challenges include semantic heterogeneity, lack of standardization, limited automation, and usability issues in the current tools and platforms. We provide a comprehensive synthesis of existing approaches, highlighting domain-specific and cross-domain trends, and identifying research opportunities to advance metadata integration through automation, semantic enrichment, and standardized practices.
Just spent a bunch of time working on the Client ID Metadata Documents internet draft to make it possible to support multiple token endpoint authentication methods — github.com/oauth-wg/draft-ietf-oauth-cli…
Document token endpoint auth methods supported by ThisIsMissEm · Pull Request #99 · oauth-wg/draft-ietf-oauth-client-id-metadata-document
github.comWhat if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
From Personal Data Server to Personal Metadata Server
liccium.leaflet.pubI've been working on an "at protocol notion". One of the things that has been holding it up has been coming to terms with the oddities of putting this data on a PDS. A document is a collection of edits, whose edits we collect will change that document pretty substantially. This is a feature