Knowledge preview

Understand

Concepts and mechanisms of the generative Web.

RAGLLMTransformers
UNDERSTAND THE TOPIC

RAG, multimodal models, linked data and models running locally are distinct building blocks. Explaining them requires precise accounts of what works, under which conditions, and which limitations remain.

What you will discover

  • Separate generation, retrieval and verification.
  • Avoid confusing teaching metaphors with technical mechanisms.
  • Connect concepts to scientific sources.

No live news collection or AI model connection is enabled in this preview.

DEEPEN YOUR KNOWLEDGE · RESEARCH DOSSIERS

In-depth explanations, concrete cases and their evidence

Every dossier connects mechanisms, cases, limitations and original documents. Independent scientific review remains pending; original sources are provided for verification.

5studies to explore
01 Recherche

Rigorous evaluation of RAG systems

Identify errors at each stage of retrieval-augmented generation.

Index evidence, not just text

A RAG system selects candidate passages and supplies them to a model to draft an answer. Document identity, edition, date and rights should remain attached to indexed fragments; otherwise citations lose context.

Separate retrieval recall from faithfulness

A system can retrieve relevant passages yet write an unfaithful answer, or generate plausible prose from irrelevant evidence. Evaluate retrieval, reranking, faithfulness, citation accuracy and abstention when evidence is missing separately.

View the verification workflow
  1. Prepare reference questions
  2. Measure retrieval separately
  3. Evaluate answer faithfulness
  4. Record corpus and model versions
02 Données

Structured data, JSON-LD and discoverability

Understand relationships between semantics, metadata and AI systems.

Linked data on the Web

JSON-LD represents resources and relations in JSON with a context defining identifiers. Linked data is neither an agent instruction nor a promise that a model will reproduce the content.

Schema.org and search

Page descriptions can clarify resource type, author, date or relationships. Google requires structured data to match visible content; artificial or misleading markup does not necessarily improve search eligibility.

View the verification workflow
  1. Choose stable identifiers
  2. Define JSON-LD context
  3. Check visible content consistency
  4. Test the graph
03 Exécution

WebNN and neural acceleration

Understand a Web API designed for inference on user devices.

The role of WebNN

WebNN aims to expose neural computation that can use processors and dedicated accelerators. Its purpose is not to provide a complete chatbot but a way to construct and execute suitable computational graphs.

Compatibility and performance

Device and implementation affect supported operators, precision and execution time. Applications should inspect actual capabilities and benchmark representative models rather than rely on theoretical claims.

View the verification workflow
  1. Inspect available capabilities
  2. Choose a supported model
  3. Measure inference performance
  4. Record failure modes
04 Exécution

WebGPU for computation and Web models

Separate GPU computation from model-level AI logic.

A GPU computation API

WebGPU lets Web applications render graphics and perform certain computations on GPUs. As of 13 November 2026 the consulted W3C publication is a Candidate Recommendation Draft; availability is not identical across all devices.

From GPU to inference

AI runtimes may use WebGPU for particular operations. WebGPU alone contains neither a model nor a dataset; it provides computation primitives.

View the verification workflow
  1. Inspect GPU support
  2. Measure performance and memory
  3. Implement a fallback
  4. Document browser support
05 Durabilité

Right-sized AI and sustainability on the Web

Choose model architecture proportionate to tasks and devices.

Problem first, model second

Not every feature needs a large generative model. Conventional search, explicit rules and specialized models can solve many tasks with lower complexity and cost.

Comparable measures

Compare quality, response time, energy, bandwidth, model size and actual costs. Parameter count alone does not summarize footprint or performance across devices.

View the verification workflow
  1. Define the target task
  2. Compare simpler alternatives
  3. Measure across devices
  4. Publish trade-offs