# Syntax
A set of rules that defines the combinations of symbols that are considered to be correctly structured statements or expressions in a language or data format. Syntax therefore refers to the form of the data or code, and is contrasted with [semantics](https://github.com/IEA-Task-43/glossary/blob/main/terms/collections.md) – the meaning.
## Examples
We can express semantically identical data (in this case metadata for a webpage header) using different syntaxes.
{% tabs %}
{% tab title="HTML" %}
In HTML (HyperText Markup Language) with opengraph attributes:
```html
```
{% endtab %}
{% tab title="JSON" %}
In JSON (JavaScript Object Notation):
```json
{
"type": "article",
"description": "Science to build on",
}
```
{% endtab %}
{% endtabs %}
## Useful syntaxes for metadata
We think the following syntaxes will be useful for definition of [metadata](https://github.com/IEA-Task-43/glossary/blob/main/terms/live-edit-and-locked-edits.md) (but this is by no means an exhaustive list:
* [OWL (Web Ontology Language)](https://www.w3.org/TR/owl-semantics/syntax.html)
* [JSON (Javascript Object Notation)](https://www.json.org/json-en.html)
* [OpenGraph](https://ogp.me)
---
# 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://iea-task-43.gitbook.io/iea-task-43-glossary/terms/syntax.md?ask=
```
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.