# Combination Guide

Sometimes a solution applies under more than one category, for example, they may apply as Open Software and Open Data or Open Content and Open Data. 

{% hint style="info" %} <mark style="color:red;">**‼️**</mark> This guide only mentions the main indicators where differences can be found for solutions applying under multiple categories. For detailed guides under each category please navigate through the panel on the left.&#x20;
{% endhint %}

#### <mark style="color:yellow;">Keep in mind:</mark>&#x20;

{% tabs %}
{% tab title="✅  Indicator 2" %}

### Use of Approved Open Licences

{% endtab %}

{% tab title="Explanation" %}
When applying under more than one category, you must have a license for both the categories.&#x20;
{% endtab %}

{% tab title="Example" %}
The content under \<Project name> is licensed through CC0-1.0 and the software component is licensed through MIT. Evidence of the content license can be found here \<insert link> and the software license can be found here \<link 2>&#x20;
{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="🔑 Indicator 4" %}

### <mark style="color:yellow;">Platform Independence</mark>

{% endtab %}

{% tab title="Explanation" %}
Both components (for example, open data as well as open software) must demonstrate complete platform independence or be able to provide independent open source alternatives for both.&#x20;
{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="📜 Indicator 5" %}

### Documentation

{% endtab %}

{% tab title="Explanation" %}
The documentation for both categories submitted is different and both sets of expectations (both from a technical and non-technical point of view) should be met.&#x20;
{% endtab %}

{% tab title="Example" %}
The documentation regarding the software part of the solution can be found here \<link> and the documentation regarding how to access + navigate through the content collections can be found \<here>&#x20;
{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://digital-public-goods.gitbook.io/knowledge-centre/combination-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.