added refs to UC in guidelines

docs/modules/ROOT/pages/how-to-create-new-data-models.adoc

@@ -3,7 +3,7 @@
 [[sec:create-a-new-xsd-schema]]
 === Create a new XSD schema
 
-This section provides detailed instructions for addressing use case UC1.1. +
+This section provides detailed instructions for addressing use case xref:use-cases.adoc#sec:uc11[UC1.1].
 
 To create a new XSD schema, the following steps need to be observed:
 
@@ -51,7 +51,7 @@ Overall, the choice between these patterns should be informed by the intended us
 [[sec:create-a-new-json-ld-context-definition]]
 === Create a new JSON-LD context definition
 
-This section provides detailed instructions for addressing use case UC1.2.
+This section provides detailed instructions for addressing use case xref:use-cases.adoc#sec:uc12[UC1.2].
 
 JSON-LD combines the simplicity, power, and web ubiquity of JSON with the concepts of Linked Data. Creating JSON-LD context definitions facilitates this synergy. This ensures that when data is shared or integrated across systems, it maintains its meaning and can be understood in the same way across different contexts. Here’s a guide on how to create new JSON-LD contexts for existing CVs, using the Core Person Vocabulary as an example.
 

docs/modules/ROOT/pages/how-to-map-existing-data-models.adoc

@@ -13,7 +13,7 @@ The subsequent sections will delve into the specific methodologies of mapping 
 [[sec:map-an-existing-ontology]]
 === Map an existing Ontology
 
-This section provides detailed instructions for addressing use case UC2.1.
+This section provides detailed instructions for addressing use case xref:use-cases.adoc#sec:uc21[UC2.1].
 
 In this section we adopt the definition from this xref:references.adoc#ref:54[paper] of the following concepts:
 
@@ -144,7 +144,7 @@ Moreover, this stage involves the creation of *maintenance protocols* to preserv
 [[sec:map-an-existing-xsd-schema]]
 === Map an existing XSD schema
 
-This section provides detailed instructions for addressing use case UC2.2.
+This section provides detailed instructions for addressing use case xref:use-cases.adoc#sec:uc22[UC2.2]
 
 In order to create an XSD mapping one needs to decide on the purpose and level of specificity of the XSD schema mapping. It can range from producing a lightweight alignment at the level of vocabulary down to a fully fledged executable set of rules for data transformation.
 

docs/modules/ROOT/pages/use-cases.adoc

@@ -77,6 +77,7 @@ We will use the following template to describe the relevant use cases that were
 |*Note:* As this is a more generic use case it will be broken down into concrete use cases that focus on specific data formats.
 |===
 
+[[sec:uc11]]
 |===
 |{set:cellbgcolor: #a8c6f7}
 *Use Case UC1.1: Create a new XSD schema*
@@ -93,6 +94,7 @@ We will use the following template to describe the relevant use cases that were
 |*Note:* A detailed methodology to be applied for this use case will be provided in the xref:how-to-create-new-data-models.adoc#sec:create-a-new-xsd-schema[Create a new XSD schema]
 |===
 
+[[sec:uc12]]
 |===
 |{set:cellbgcolor: #a8c6f7}
 *Use Case UC1.2: Create a new JSON-LD context definition*
@@ -125,6 +127,7 @@ We will use the following template to describe the relevant use cases that were
 |*Note:* Since this is a more generic use case it will be broken down into concrete use cases that focus on specific data models and/or data formats. Some of those use cases will be described in detail below, while others will be included in the xref:use-cases.adoc#sec:unaddressed-use-cases[next section], which is dedicated to the unaddressed use cases.
 |===
 
+[[sec:uc21]]
 |===
 |{set:cellbgcolor: #a8c6f7}
 *Use Case UC2.1: Map an existing Ontology to a Core Vocabulary*
@@ -143,6 +146,7 @@ We will use the following template to describe the relevant use cases that were
 |*Note:* A detailed methodology to be applied for this use case will be provided in the xref:how-to-map-existing-data-models.adoc#sec:map-an-existing-ontology[Map an existing Ontology] section.
 |===
 
+[[sec:uc22]]
 |===
 |{set:cellbgcolor: #a8c6f7}
 *Use Case UC2.2: Map an existing XSD Schema to a Core Vocabulary*