> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/emarketplace/3-terminology.md).

# 3 Terminology

<table><thead><tr><th width="348">Term</th><th>Description</th></tr></thead><tbody><tr><td><strong>B2G</strong></td><td>Businesses selling products/services to government.</td></tr><tr><td><strong>G2P</strong></td><td>Government providing products/services to persons.</td></tr><tr><td><strong>e-Marketplace</strong></td><td>An e-Marketplace enables trade of products and/or services via electronic media. This is supported by innovative information and communication technologies to match supply and demand.</td></tr><tr><td><p><strong>Government</strong></p><p><strong>e-marketplace</strong></p></td><td>An online, end-to-end e-marketplace for the procurement and sale of commonly used goods and services by/from Government ministries, departments, public sector undertakings (PSUs), and other affiliated bodies.</td></tr><tr><td><strong>Specification</strong></td><td>A technical document that describes how a system is to be developed to achieve a specific set of objectives or requirements.</td></tr><tr><td><strong>Ecosystem</strong></td><td>An ecosystem is a community of stakeholders that support platforms implementing the specification. Ecosystems can be made up of developers, resellers, customers, software, services, and more.</td></tr><tr><td><strong>Ecosystem Maturity</strong></td><td>The level of readiness of an ecosystem to design, build, and use implementations of the specification. This can range from basic access to internet infrastructure to more advanced features like digital identities, assets, payments, and trust infrastructure.</td></tr><tr><td><strong>Consumer</strong></td><td>A person, or an organization that wants to discover, buy or avail products, services, and/or opportunities.</td></tr><tr><td><strong>Provider</strong></td><td>A person, or an organization that wants to publish, sell, allocate, or provide products, services, and/or opportunities.</td></tr><tr><td><strong>Application Platform</strong></td><td>The platform where the consumer (typically the buyer) is onboarded.</td></tr><tr><td><strong>Provider Platform</strong></td><td>The platform where the provider (typically the seller) is onboarded.</td></tr><tr><td><strong>Intent</strong></td><td>A consumer’s desire to purchase, procure, or avail something being offered by a provider.</td></tr><tr><td><strong>Catalog</strong></td><td>A provider’s list of products, services, and opportunities that is made available to consumers.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://specs.govstack.global/emarketplace/3-terminology.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.