updated references

docs/modules/ROOT/pages/introduction.adoc

@@ -5,8 +5,8 @@
 Interoperability in the EU context refers to the capacity of systems or organisations, including public administrations,
 businesses, and citizens, to collaborate effectively and pursue common objectives across borders. This capability is crucial
 for providing efficient digital public services, facilitating economic transactions, and supporting the free movement of goods,
-services, people, and data. The European Interoperability Framework (EIF) [[ref:1]], [[ref:2]] and Interoperable Europe Act
-(IEA) [[ref:3]] emphasise that interoperability involves the seamless exchange of information and trusted data sharing across
+services, people, and data. The European Interoperability Framework (EIF)[xref:references.adoc#ref:eif[eif]], [[ref:2]][eif2] and Interoperable Europe Act
+(IEA) [[ref:3]][reg24-903] emphasise that interoperability involves the seamless exchange of information and trusted data sharing across
 sectors and administrative layers, which is essential for improving policy-making and public service delivery.
 
 The term itself combines ‘inter’ (Latin for between), ‘opera’ (Latin for work), and ‘ability’, suggesting the intrinsic nature
@@ -35,7 +35,7 @@ and decision-making at all governmental levels.
 
 [[sec:interoperability-through-semantic-specifications]]
 === Interoperability through semantic specifications
-The EIF [[ref:1]], [[ref:2]] identifies four crucial layers of interoperability necessary for effective data exchange across the
+The EIF [[ref:1]], [[ref:2]][eif2] identifies four crucial layers of interoperability necessary for effective data exchange across the
 EU: Legal, Organisational, Semantic, and Technical. The Semantic and Technical layers, in particular, play pivotal roles in ensuring
 that data is not only exchanged efficiently but also understood consistently by all parties involved.
 
@@ -51,7 +51,7 @@ that help manage how data is defined, represented, and communicated across diffe
 that are both machine-readable and human-understandable, thus supporting consistent interpretation and utilisation across
 diverse IT environments and stakeholders (e.g. developers, business experts, end users, administrators, etc.).
 
-The SEMIC Style Guide [[ref:4]] serves as an important resource in this context, providing essential guidelines on creating
+The SEMIC Style Guide [[ref:4]][sem-sg] serves as an important resource in this context, providing essential guidelines on creating
 and managing  such specifications. It covers naming conventions, syntax, and the organisation of artefacts within two critical
 types of semantic data specifications: Core Vocabularies and Application Profiles.
 
@@ -62,10 +62,10 @@ practices, ensuring seamless service delivery that meets the needs of citizens a
 
 [[sec:what-are-the-core-vocabularies]]
 === What are the Core Vocabularies?
-In the vision document “e-Government Core Vocabularies” [[ref:5]], Core Vocabularies are defined as simplified, reusable and
+In the vision document “e-Government Core Vocabularies” [[ref:5]][cv-hb], Core Vocabularies are defined as simplified, reusable and
 extensible data models that capture the fundamental characteristics of a data entity in a context-neutral and syntax-neutral
-fashion. SEMIC style guide provides a terminological clarification about the Core Vocabularies [[ref:6]] and elaborates that they
-are context-neutral semantic building blocks, like the Dublin Core Terms [[ref:7]] or the Organization Ontology [[ref:8]], that can
+fashion. SEMIC style guide provides a terminological clarification about the Core Vocabularies [[ref:6]][sem--sg-cvs] and elaborates that they
+are context-neutral semantic building blocks, like the Dublin Core Terms [[ref:7]][dcmi] or the Organization Ontology [[ref:8]][org], that can
 be extended into context-specific semantic data specifications. The use of the Core Vocabularies as a common building block
 for developing context-specific data models guarantees a minimum of semantic consistency. When the Core Vocabularies are extended
 to create domain specifications and information exchange models, additional meaning (semantics) is added to the specifications,

docs/modules/ROOT/pages/references.adoc

@@ -1,39 +1,39 @@
 == References
 
-. [[ref:1]] New European Interoperability Framework. Available at: https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf
-. [[ref:2]] European Interoperability Framework – Implementation Strategy. Available at: https://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_1&format=PDF
-. [[ref:3]] REGULATION (EU) 2024/903. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L_202400903
-. [[ref:4]] The SEMIC Style Guide for Semantic Engineers. Available at: https://semiceu.github.io/style-guide
-. [[ref:5]] e-Government Core Vocabularies handbook. Available at: https://joinup.ec.europa.eu/sites/default/files/inline-files/ISA%20Handbook%20for%20using%20Core%20Vocabularies.pdf
-. [[ref:6]] The SEMIC Style Guide for Semantic Engineers: What is a Core Vocabulary (CV) specification?. Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-cv-specification
-. [[ref:7]] DCMI Metadata Terms. Available at: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-1
-. [[ref:8]] The Organization Ontology. Available at: https://www.w3.org/TR/vocab-org/
-. [[ref:9]] SEMIC Support Center. Available at: https://joinup.ec.europa.eu/collection/semic-support-centre/specifications
-. [[ref:10]] Semantic Interoperability Community GitHub repository. Available at: https://github.com/SEMICeu
-. [[ref:11]] The SEMIC Style Guide for Semantic Engineers: What is an ontology? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-an-ontology
-. [[ref:12]] Motik, B., Patel-Schneider, P. F., Parsia, B., Bock, C., Fokoue, A., Haase, P., …​ & Smith, M. (2009). OWL 2 web ontology language: Structural specification and functional-style syntax. W3C recommendation, 27(65), 159. Available at: http://www.w3.org/TR/2012/REC-owl2-syntax-20121211/
-. [[ref:13]] The SEMIC Style Guide for Semantic Engineers: What is a data shape specification? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-data-shape-contraint
-. [[ref:14]] Knublauch, H., & Kontokostas, D. (2017). Shapes Constraint Language (SHACL), W3C Recommendation. World Wide Web Consortium. Available at: https://www.w3.org/TR/shacl/
-. [[ref:15]] The SEMIC Style Guide for Semantic Engineers: What is a data specification document? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-specification-document
-. [[ref:16]] ReSpec Documentation. Available at: https://respec.org/docs/
-. [[ref:17]] Sporny, M., Longley, D., Kellogg, G., Lanthaler, M., & Lindström, N. (2020). JSON-LD 1.1. W3C Recommendation, Jul.
-. [[ref:18]] The SEMIC Style Guide for Semantic Engineers: Technical artefacts and concerns. Available at: https://semiceu.github.io/style-guide/1.0.0/arhitectural-clarifications.html#sec:technical-concerns-and-artefacts
-. [[ref:19]] The SEMIC Style Guide for Semantic Engineers: What is a conceptual model? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-conceptual-model
-. [[ref:20]] Unified Modeling Language. Available at: https://www.omg.org/spec/UML
-. [[ref:21]] CC-BY 4.0 licence. Available at: https://creativecommons.org/licenses/by/4.0/
-. [[ref:22]] EC11a
-. [[ref:23]] D3.1 – PROCESS AND METHODOLOGY FOR CORE VOCABULARIES. Available at: https://joinup.ec.europa.eu/sites/default/files/document/2012-03/D3.1-Process%20and%20Methodology%20for%20Core%20Vocabularies_v1.01.pdf
-. [[ref:24]] The SEMIC Style Guide for Semantic Engineers: Clarifications on "reuse". Available at: https://semiceu.github.io/style-guide/1.0.0/clarification-on-reuse.html
-. [[ref:25]] Swagger OpenAPI Guide: Components Section. Available at: https://swagger.io/docs/specification/components/
-. [[ref:26]] The SEMIC Style Guide for Semantic Engineers: What is a semantic data specification? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-specification-document
-. [[ref:27]] Diataxis. Available at: https://diataxis.fr/
-. [[ref:28]] Barthelemy, F. et al. Core Person vocabulary. Available at: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00
-. [[ref:29]] Barthelemy, F. et al. Core Business Vocabulary. Available at: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.2.0/
-. [[ref:30]] According to the classification of A. Cockburn in “Writing Effective Use Cases” Cockburn99, pg 14-15
-. [[ref:31]] OOTS XML schema mappings. Available at: https://ec.europa.eu/digital-building-blocks/sites/pages/viewpage.action?pageId=706382149
-. [[ref:32]] Core Person Vocabulary - JSON-LD. Available at: https://github.com/SEMICeu/Core-Person-Vocabulary/blob/master/releases/2.1.1/context/core-person-ap.jsonld
-. [[ref:33]] Core Business Vocabulary - JSON-LD. Available at: https://github.com/SEMICeu/Core-Business-Vocabulary/blob/master/releases/2.2.0/context/core-business-ap.jsonld
-. [[ref:34]] Mapping Core Person to Schema.org. Available at: https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Person/Schema.org
-. [[ref:35]] Mapping Core Business to Schema.org. Available at: https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Business/Schema.org
+- *[[ref:eif]][eif]* New European Interoperability Framework. Available at: https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf
+- *[[ref:2]][eif2]* European Interoperability Framework – Implementation Strategy. Available at: https://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_1&format=PDF
+- *[[ref:3]][reg24-903]* REGULATION (EU) 2024/903. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L_202400903
+- *[[ref:4]][sem-sg]* The SEMIC Style Guide for Semantic Engineers. Available at: https://semiceu.github.io/style-guide
+- *[[ref:5]][cv-hb]* e-Government Core Vocabularies handbook. Available at: https://joinup.ec.europa.eu/sites/default/files/inline-files/ISA%20Handbook%20for%20using%20Core%20Vocabularies.pdf
+- *[[ref:6]][sem--sg-cvs]* The SEMIC Style Guide for Semantic Engineers: What is a Core Vocabulary (CV) specification?. Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-cv-specification
+- *[[ref:7]][dcmi]* DCMI Metadata Terms. Available at: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-1
+- *[[ref:8]][org]* The Organization Ontology. Available at: https://www.w3.org/TR/vocab-org/
+- *[[ref:9]][semic]* SEMIC Support Center. Available at: https://joinup.ec.europa.eu/collection/semic-support-centre/specifications
+- *[[ref:10]][semic-gh]* Semantic Interoperability Community GitHub repository. Available at: https://github.com/SEMICeu
+- *[[ref:11]][sem-sg-wio]* The SEMIC Style Guide for Semantic Engineers: What is an ontology? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-an-ontology
+- *[[ref:12]][owl2]* Motik, B., Patel-Schneider, P. F., Parsia, B., Bock, C., Fokoue, A., Haase, P., …​ & Smith, M. (2009). OWL 2 web ontology language: Structural specification and functional-style syntax. W3C recommendation, 27(65), 159. Available at: http://www.w3.org/TR/2012/REC-owl2-syntax-20121211/
+- *[[ref:13]][sem-sg-wds]* The SEMIC Style Guide for Semantic Engineers: What is a data shape specification? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-data-shape-contraint
+- *[[ref:14]][shacl]* Knublauch, H., & Kontokostas, D. (2017). Shapes Constraint Language (SHACL), W3C Recommendation. World Wide Web Consortium. Available at: https://www.w3.org/TR/shacl/
+- *[[ref:15]][sem-sg-wdsd]* The SEMIC Style Guide for Semantic Engineers: What is a data specification document? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-specification-document
+- *[[ref:16]][respec]* ReSpec Documentation. Available at: https://respec.org/docs/
+- *[[ref:17]][w3c]* Sporny, M., Longley, D., Kellogg, G., Lanthaler, M., & Lindström, N. (2020). JSON-LD 1.1. W3C Recommendation, Jul.
+- *[[ref:18]][json-ld]* The SEMIC Style Guide for Semantic Engineers: Technical artefacts and concerns. Available at: https://semiceu.github.io/style-guide/1.0.0/arhitectural-clarifications.html#sec:technical-concerns-and-artefacts
+- *[[ref:19]][sem-sg-wcm]* The SEMIC Style Guide for Semantic Engineers: What is a conceptual model? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-conceptual-model
+- *[[ref:20]][uml]* Unified Modeling Language. Available at: https://www.omg.org/spec/UML
+- *[[ref:21]][cc-by]* CC-BY 4.0 licence. Available at: https://creativecommons.org/licenses/by/4.0/
+- *[[ref:22]][ec11a]* EC11a
+- *[[ref:23]][cv-met]* D3.1 – PROCESS AND METHODOLOGY FOR CORE VOCABULARIES. Available at: https://joinup.ec.europa.eu/sites/default/files/document/2012-03/D3.1-Process%20and%20Methodology%20for%20Core%20Vocabularies_v1.01.pdf
+- *[[ref:24]][sem-sg-reuse]* The SEMIC Style Guide for Semantic Engineers: Clarifications on "reuse". Available at: https://semiceu.github.io/style-guide/1.0.0/clarification-on-reuse.html
+- *[[ref:25]][swagger]* Swagger OpenAPI Guide: Components Section. Available at: https://swagger.io/docs/specification/components/
+- *[[ref:26]][sem-sg-wsds]* The SEMIC Style Guide for Semantic Engineers: What is a semantic data specification? Available at: https://semiceu.github.io/style-guide/1.0.0/terminological-clarifications.html#sec:what-is-a-specification-document
+- *[[ref:27]][dtx]* Diataxis. Available at: https://diataxis.fr/
+- *[[ref:28]][cpv]* Barthelemy, F. et al. Core Person vocabulary. Available at: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00
+- *[[ref:29]][cbv]* Barthelemy, F. et al. Core Business Vocabulary. Available at: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.2.0/
+- *[[ref:30]][weuc]* According to the classification of A. Cockburn in “Writing Effective Use Cases” Cockburn99, pg 14-15
+- *[[ref:31]][oots]* OOTS XML schema mappings. Available at: https://ec.europa.eu/digital-building-blocks/sites/pages/viewpage.action?pageId=706382149
+- *[[ref:32]][cpv-json-ld]* Core Person Vocabulary - JSON-LD. Available at: https://github.com/SEMICeu/Core-Person-Vocabulary/blob/master/releases/2.1.1/context/core-person-ap.jsonld
+- *[[ref:33]][cbv-json-ld]* Core Business Vocabulary - JSON-LD. Available at: https://github.com/SEMICeu/Core-Business-Vocabulary/blob/master/releases/2.2.0/context/core-business-ap.jsonld
+- *[[ref:34]][map-cp2org]* Mapping Core Person to Schema.org. Available at: https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Person/Schema.org
+- *[[ref:35]][map-cb2org]* Mapping Core Business to Schema.org. Available at: https://github.com/SEMICeu/Semantic-Mappings/tree/main/Core%20Business/Schema.org
 
-. [[ref:344]] eProcurement Ontology. Available at:
+- *[[ref:344]][epo]* eProcurement Ontology. Available at:

docs/modules/ROOT/pages/semic-core-vocabularies.adoc

@@ -4,7 +4,7 @@ This section contains a brief overview of the Core Vocabularies, indicating how
 
 Since 2011 the European Commission facilitates international working groups to forge consensus and maintain the SEMIC Core Vocabularies.
 A short description of these vocabularies is included in the Table [below]. The latest release of the Core Vocabularies can be
-retrieved via the SEMIC Support Center[[ref:9]], or directly in the GitHub repository[[ref:10]].
+retrieved via the SEMIC Support Center[[ref:9]][semic], or directly in the GitHub repository[[ref:10]][semic-gh].
 
 |===
 |Vocabulary|Description
@@ -81,20 +81,20 @@ and processing information related to public events.
 === Representation formats
 The Core Vocabularies are semantic data specifications that are disseminated as the following artefacts:
 
-* lightweight ontology [[ref:11]] for vocabulary definition expressed in OWL[[ref:12]],
-* loose data shape specification [[ref:13]] expressed in SHACL[[ref:14]],
-* human-readable reference documentation [[ref:15]] in HTML (based on ReSpec[[ref:16]]),
-* JSON-LD [[ref:17]] context definitions[[ref:18]],
-* conceptual model specification [[ref:19]] expressed in UML[[ref20]].
+* lightweight ontology [[ref:11]][sem-sg-wio] for vocabulary definition expressed in OWL[[ref:12]][owl2],
+* loose data shape specification [[ref:13]][sem-sg-wds] expressed in SHACL[[ref:14]][shacl],
+* human-readable reference documentation [[ref:15]][sem-sg-wdsd] in HTML (based on ReSpec[[ref:16]][respec]),
+* JSON-LD [[ref:17]][w3c] context definitions[[ref:18]][json-ld],
+* conceptual model specification [[ref:19]][sem-sg-wcm] expressed in UML[[ref20]].
 
 [[sec:licensing-conditions]]
 === Licensing conditions
-The Core Vocabularies are published under the CC-BY 4.0 licence [[ref:21]].
+The Core Vocabularies are published under the CC-BY 4.0 licence [[ref:21]][cc-by].
 
 [[sec:core-vocabularies-lifecycle]]
 === Core Vocabularies lifecycle
-The Core Vocabularies have been developed following the ‘Process and methodology for developing Core Vocabularies’ [[ref:22]].
-The Core Vocabularies have an open change and release management process [[ref:23]], supported by SEMIC, that ensures continuous
+The Core Vocabularies have been developed following the ‘Process and methodology for developing Core Vocabularies’ [[ref:22]][ec11a].
+The Core Vocabularies have an open change and release management process [[ref:23]][cv-met], supported by SEMIC, that ensures continuous
 improvement and relevance to evolving user needs.
 
 This process begins with the identification of needs from stakeholders or issues raised in existing implementations. The Working Group
@@ -115,8 +115,8 @@ public services.
 [[sec:claiming-conformance]]
 === Claiming conformance
 Claiming conformance to Core Vocabularies is an integral part of validating (a) how well a new or a mapped data model or
-semantic data specification aligns with the principles and practices established in the SEMIC Style Guide [[ref:4]] and (b) to
-what degree the Core Vocabularies are reused (fully or partially) [[ref:24]]. The conformance assessment is voluntary, and shall
+semantic data specification aligns with the principles and practices established in the SEMIC Style Guide [[ref:4]][sem-sg] and (b) to
+what degree the Core Vocabularies are reused (fully or partially) [[ref:24]][sem-sg-reuse]. The conformance assessment is voluntary, and shall
 be published as a self-conformance statement. This statement must assert which requirements are met by the data model or
 semantic specification.