<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>G. De Mulder);</journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gertjan De Mulder</string-name>
          <email>gertjan.demulder@ugent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ruben Dedecker</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ben De Meester</string-name>
          <email>ben.demeester@ugent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pieter Colpaert</string-name>
          <email>pieter.colpaert@ugent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Verifiable Credentials, SPARQL</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ghent University - imec</institution>
          ,
          <addr-line>Technologiepark-Zwijnaarde 122, 9052 Ghent</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>IDLab, Department of Electronics and Information Systems</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>With initiatives such as the European Digital Identity Wallet, the exchange of verifiable data via digital credentials using digital wallets is reaching mainstream adoption. While digital wallets gain adoption and the ecosystem grows, the flexibility and interoperability of querying verifiable data remains limited: digital credentials can only be directly queried based on JSON keys, thus hampering support for internationalization and alternative semantics. With this work, we present a practical approach to leverage Semantic Web technologies to combine the expressiveness of RDF with the semantic nature of W3C's recommended Verifiable Credentials and existing wallet protocols like OID4VP. We leverage SPARQL queries to request specific claims within the OID4VP protocol, which are evaluated over the combined RDF representation of the wallet credentials, to return Verifiable Presentations that contain the requested claims using selective disclosure. We applied named graphs with blank node graph names to ensure a uniform and globally unique connection between credentials and their corresponding claims and proof graphs when storing credentials in a wallet's Knowledge Graph. To retrieve which claims need to be selectively disclosed from their original credentials, we applied an initial conversion from RDF triple predicates to JSONPath pointers, thus currently supporting only a subset of SPARQL expressivity. Through the addition of a SPARQL query in the OID4VP authorization flow, we enable semantically enriched query evaluation over the stored credentials, opening the way to semantic alignment of multilingual vocabularies and similar ontologies used in diferent online ecosystems. Future work is needed to improve SPARQL support to enable querying over complex claim requirements, in terms of the query to JSONPath pointers, as well as addressing metadata requirements for the requested claims.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Digital credentials – i.e., tamper-evident digital assertions issued by a trusted authority to represent
claims about a subject – are gaining adoption: in government by the European Parliament [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and
implemented in the European Digital Identity Wallet [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], in industry [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and in international organizations
through standardization, showcased by, e.g., the recently W3C recommended Verifiable Credentials
(VC) 2.0 specifications [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Due to its gaining adoption, the legal obligations for preserving the privacy
of the individual and ensuring data minimization [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] have to be taken into account. This is typically
achieved through cryptographic methods such as selective disclosure [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Selective disclosure for Verifiable Credentials is made available by deriving Verifiable Presentations
(VPs) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]: creating newly combined verifiable subsets of claims derived from credentials stored in a
personal wallet. For example, at the job ofice, instead of requesting individuals to provide a complete
set of documents containing more information than needed (potentially introducing bias), a selection of
relevant claims can be requested, such as (i) a valid driver’s license; (ii) a valid diploma degree; and
(iii) the job title of the applicant’s current job (if available). Minimizing the information shared reduces
the likelihood of discrimination against potential candidates.
      </p>
      <p>LGOBE</p>
      <p>CEUR</p>
      <p>ceur-ws.org</p>
      <p>As credentials become increasingly integrated in digital data flows, we expect an increasing need to
request and share flexible combinations of credentials.</p>
      <p>
        At the heart of this flexibility requirement, the semantics of the exchanged data need to be well
understood. Here, the Verifiable Credential Data Model [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] makes use of the JSON-LD format [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] to
represent the data stored in the credentials using the Resource Description Framework [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] in JSON
format. This gives the double advantage of (i) managing the syntactic representation of the credential
using (widely adopted) JSON tooling, whilst (ii) handling the semantic interpretation of the data using
RDF. However, while existing works aim to formalize selective disclosure and ZKP algorithms for RDF
triples and RDF terms [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ], the current protocols for Verifiable Credentials and the resulting Verifiable
Presentations tend to disregard this semantic information throughout their lifespan. Instead, they
rely on JSONPath pointers through protocols such as the Presentation Exchange [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] or the Digital
Credential Query Language [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] to specify the selection of claims from specific credentials that are
being requested for disclosure.
      </p>
      <p>The reliance on JSONPath pointers – which are one-to-one coupled with the Verifiable Credential’s
schema – imposes an implicit reliance on the issuer’s chosen context, which is typically influenced
by the issuer’s local context such as language and culture. This limits the reusability of the pointer
outside the issuer’s local context. Taking the example of a diploma credential: the European Learning
Model1 specifies its model using English keys (e.g., accreditation linking to http://data.europa.eu/snb/
model/elm/accreditation); where the Flemish derived application profile 2 specifies the same terms, but
using Flemish keys (e.g., Bewijs.accreditatie, also linking to http://data.europa.eu/snb/model/elm/
accreditation). We assume such discrepancies in JSON keys to occur more and more frequently, making
interoperability dificult even when the underlying managed data models are correctly reused. Secondly,
as JSONPath pointers use tree-based traversal, they do not support graph-based selections over multiple
credentials. Even simple cases could require graph-based selections. Taking the example of proving
ownership of a car: A person holding the credentials of both a valid license and insurance would require
claim retrieval over multiple interlinked credentials, which would benefit from graph-based selection.</p>
      <p>
        With this work, we present a novel method to leverage mature Semantic Web technologies to more
lfexibly but still efectively combine claims represented in Verifiable Credentials, leveraging a SPARQL
subset as a selective disclosure mechanism to automatically combine claims from multiple Verifiable
Credentials into a Verifiable Presentation. We apply our method to the maturing OpenID for Verifiable
Presentations protocol (OID4VP) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Method and Implementation</title>
      <p>
        In this section, we show how we can retrieve and combine arbitrary claims from multiple Verifiable
Credentials semantically – i.e., without needing to rely on the specific credential schemas used – by
extending the OID4VP authorization request [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] with SPARQL query functionality. A proof of concept
implementation of the SPARQL query evaluation over Verifiable Credentials can be found on Github 3.
Our method consists of five steps (Figure 1): (i) integrate all wallet’s credentials in a single graph
store without losing the credentials’ internal connections; (ii) request a selectively disclosed set of
claims using a SPARQL query instead of a list of JSONPath pointers; (iii) transform the SPARQL query
to match the credentials’ internal representation to retrieve which credentials contain which claims;
(iv) transform the semantic relations back to the credentials’ JSONPaths to construct the Verifiable
Presentation; and (v) return the compliant Verifiable Presentation to the original requester.
      </p>
      <sec id="sec-2-1">
        <title>Step 1: Integrate all wallet’s credentials in a single graph store To enable the evaluation of a</title>
        <p>SPARQL query over stored Verifiable Credentials, these credentials are stored in a graph store on the
1Retrieved via https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/
dataset/snb-model&amp;version=3.2 at 10/07/2025.
2Retrieved via https://data.vlaanderen.be/doc/applicatieprofiel/leerprestatiecredential/ at 04/07/2025.
3Github repository for the POC is located at: https://github.com/KNowledgeOnWebScale/queryable-vcs
 poc.ipynb's implements following processes</p>
        <p>INGEST
QUERY
COMPOSE</p>
        <p>Verifier
1</p>
        <p>INGEST
2</p>
        <p>QUERY
Create Conjunctive Graph</p>
        <p>
          cg
wallet instance. Verifiable Credentials can be interpreted in RDF. However, as indicated by Braun et
al. [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], the Verifiable Credential Data Model mandates linking the proof graph from a node within
the default graph. This is problematic when storing multiple credentials in their RDF representation:
all claims of all credentials, being part of the default graph, are subject to automated merging when
inserted into a knowledge graph. This makes it impossible to distinguish which claims originate from
which credential in their RDF representation.
        </p>
        <p>
          To ensure we keep the link between claims and their originating credential, the ingestion of these
credentials into the graph store requires the contents of their default graph to be embedded in a named
graph [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. A subsequent skolemization step ensures that all graph names used are converted to blank
nodes that are relabeled on ingestion in the graph store, preventing coreferencing between the content
graphs of diferent credentials.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Step 2: Request a selectively disclosed set of claims using a SPARQL query To query the</title>
        <p>
          wallet’s credentials, we envision the reuse of the OID4VP Authorization Request [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], where we
introduce a sparql_query parameter, similar to how the dcql_query parameter is used to pass DCQL
queries to the wallet [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
        </p>
        <p>We assume that the SPARQL query is formed based on the native RDF representation of the credentials
over which the query is evaluated (Listing 1). Querying the credential metadata currently means that
the requester must be made aware of how the wallet links the claims with the credential metadata (i.e.,
via the minted credential graphs). Given this was introduced in Step 1 (combining multiple credentials
in one Knowledge Graph), this is no longer aligned with the VC standard. Extending the VC standard
to support these types of metadata queries is out of the scope of this paper, and we focus on querying
the claims themselves.
1 PREFIX ex: &lt;http://example.org/&gt;
2 SELECT *
3 WHERE {
4 ?s ex:degreeTitle ?z ;
5 ex:driversLicense ?x ;
6 ex:jobPosition ?y
7 }</p>
        <p>Listing 1: Querying claims from diferent credentials</p>
      </sec>
      <sec id="sec-2-3">
        <title>Step 3: Transform the SPARQL query to match the credentials’ internal representation At</title>
        <p>the credential wallet, an incoming SPARQL query must be converted to take into account the internal
RDF representation of the stored credentials. To achieve this, the query statements are embedded in
the GRAPH keyword to direct the queried statements to the named graphs storing the credential claims
(Listing 2). This aligns the queries with the conversion performed in Step 1. Within the context of
this proof of concept, our considered query examples are chosen with simplicity in mind, allowing us
to discuss the system as a whole. Hence, future research is needed to support more complex query
mapping scenarios (e.g., in the case of VCs that have a more complex structure).</p>
        <p>
          Step 4: Construct the Verifiable Presentation Having found the relevant credentials for the
requested claims, we can rely on mature JSON-LD compaction algorithms [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] for the wallet to transform
the semantic relations used in the SPARQL query back to JSONPaths conforming to the credentials’
original JSON representation. These JSONPath pointers are needed to construct the Verifiable Presentation
using existing Verifiable Credential libraries (e.g., https://github.com/digitalbazaar/vc).
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>Step 5: Return the compliant Verifiable Presentation to the original requester At the request</title>
        <p>ing side, the Verifiable Presentation returned from the authorization request can now be validated based
on its signature and the identity of its issuer. The original query, as shown in Listing 1, can now be
evaluated over the Verifiable Presentation’s native RDF representation to receive the verified results for
the query.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Conclusions</title>
      <p>With this initial work, we demonstrate a practical solution for the selective disclosure of claims via
Verifiable Presentations based on SPARQL queries applied to the OID4VP protocol, by taking into account
the underlying RDF semantics of Verifiable Credentials. The result of the query is a presentation of
claims from the original credentials, which is then, at the requesting side, re-processed with the same
mappings to provide a query response. As such, we ensure that claims are verified correctly.</p>
      <p>The addition of a sparql_query as an alternative to the dcql_query parameter is a mild intrusion
in the OID4VP authorization request flow. We provide a straightforward adoption path for integrating
SPARQL queries without impacting the overall flow or functionality. Our method allows for more flexible
querying of claims, but does not influence authorization decisions, as the authorization mechanisms
are based on the claims that are being returned, not on the internal query evaluation process. The
evaluation of the returned presentations for their metadata and query results occurs outside the existing
protocol stack.</p>
      <p>Integrating the semantics of credentials into the request flow enables the use of existing Web standards
such as OWL for schema alignment, facilitating alignment of credentials over multiple languages and
ecosystems. Where initial wallet implementations can rely on ecosystem enforcement of standardized
schemas (e.g. ISO standards), further adoption is likely to cause divergence between data models.
Standardized mappings can be provided at an ecosystem level, and ad hoc mappings can be passed by a
requesting party to allow wider matching of requested claims to stored credentials.</p>
      <p>Although the provided implementation validates its feasibility, the avenues for future work are
manifold.</p>
      <p>A JSONPath-to-SPARQL transformation could be devised to serve as a proxy for existing OID4VP
clients (i.e., reinterpreting the dcql_query parameter as a SPARQL query), resulting in a completely
OID4VP-compatible solution.</p>
      <p>Introducing SPARQL support strains the current Verifiable Credentials Data Model, as the native
RDF representation requires additional transformations to allow for unambiguous query evaluation
matching claims with the credential they originate from, supporting only a subset of the current RDF
and SPARQL capabilities. Further investigation is needed to assess the possibility for the Verifiable
Credential model to support native querying over both claims and metadata in its RDF representation.</p>
      <p>
        We currently need to rely on JSON-based Verifiable Credential libraries to create the Verifiable
Presentation (i.e., the reverse transformation into JSONPaths in Step 4). The work of Braun et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]
provides a basis for an RDF-native representation of signatures over RDF graphs with support for
selective disclosure of individual terms, opening avenues to extending OID4VP to an RDF-native
protocol to further increase its flexibility.
      </p>
      <p>In terms of functionality requirements, the proposed approach imposes an overhead on the wallet
instance: for managing Verifiable Credentials as a knowledge graph, and for matching a user query over
that knowledge graph to individual claim requirements over the stored credentials. Research is needed
towards the added benefit of semantic cross-credential querying and ontology alignment outweighs
this added cost.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgments</title>
      <p>The described research activities were supported by SolidLab Vlaanderen (Flemish Government, EWI
and RRF project VV023/10), and Interreg project SecuWeb (0100085).</p>
    </sec>
    <sec id="sec-5">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author(s) used GPT-4o to: Grammar and spelling check. After
using these tool(s)/service(s), the author(s) reviewed and edited the content as needed and take(s) full
responsibility for the publication’s content.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <article-title>[1] Consolidated text: Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market</article-title>
          and
          <source>repealing Directive</source>
          <year>1999</year>
          /93/EC,
          <source>Oficial Journal of the European Union</source>
          (
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>EU</given-names>
            <surname>Digital Identity Wallet - Architecture and Reference Framework</surname>
          </string-name>
          ,
          <source>Technical Report, European Commission</source>
          ,
          <year>2025</year>
          . URL: https://eu-digital
          <article-title>-identity-wallet.github.io/ eudi-doc-architecture-and-reference-</article-title>
          <source>framework/2</source>
          .4.0/, version 2.0.0.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>D.</given-names>
            <surname>Deimel</surname>
          </string-name>
          , et al.,
          <article-title>Organisations-identitäten</article-title>
          ,
          <source>Technical Report, Bitkom</source>
          ,
          <year>2025</year>
          . URL: https://www. bitkom.org/sites/main/files/2025-01/bitkom-whitepaper-organisationsidentitaeten.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Sporny</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. Thibodeau</given-names>
            <surname>Jr</surname>
          </string-name>
          , I. Herman, G. Cohen,
          <string-name>
            <given-names>M. B.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <source>Verifiable Credentials Data Model v2.0</source>
          ,
          <string-name>
            <given-names>W3C</given-names>
            <surname>Recommendation</surname>
          </string-name>
          , Verifiable Credentials Working Group,
          <year>2025</year>
          . URL: https://www.w3. org/TR/vc-data
          <source>-model-2</source>
          .0/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>I.</given-names>
            <surname>Lella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Theocharidou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Magonara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Malatras</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. Svetozarov</given-names>
            <surname>Naydenov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ciobanu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Georgios</surname>
          </string-name>
          ,
          <source>ENISA Threat Landscape</source>
          <year>2024</year>
          ,
          <source>Technical Report, The European Union Agency for Cybersecurity (ENISA)</source>
          ,
          <year>2024</year>
          . URL: https://www.enisa.europa.eu/publications/enisa-threat-landscape-
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Š. B. Ramić</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Cogo</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <string-name>
            <surname>Prazina</surname>
            , E. Cogo,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Turkanović</surname>
            ,
            <given-names>R. T.</given-names>
          </string-name>
          <string-name>
            <surname>Mulahasanović</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Mrdović</surname>
          </string-name>
          ,
          <article-title>Selective disclosure in digital credentials: A review</article-title>
          ,
          <source>ICT Express 10</source>
          (
          <year>2024</year>
          )
          <fpage>916</fpage>
          -
          <lpage>934</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.icte.
          <year>2024</year>
          .
          <volume>05</volume>
          .011.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M.</given-names>
            <surname>Sporny</surname>
          </string-name>
          , G. Kellogg,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Lanthaler, JSON-LD 1.1 - A JSON-based Serialization for Linked Data</article-title>
          , Recommendation,
          <source>World Wide Web Consortium (W3C)</source>
          ,
          <year>2020</year>
          . URL: http://www.w3.org/TR/ json-ld/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>R.</given-names>
            <surname>Cyganiak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Wood</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lanthaler</surname>
          </string-name>
          ,
          <source>RDF 1.1 Concepts</source>
          and
          <string-name>
            <given-names>Abstract</given-names>
            <surname>Syntax</surname>
          </string-name>
          , Recommendation,
          <source>World Wide Web Consortium (W3C)</source>
          ,
          <year>2014</year>
          . URL: https://www.w3.org/TR/rdf11-concepts/, accessed:
          <fpage>2023</fpage>
          -09-29.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>D.</given-names>
            <surname>Yamamoto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Suga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Sako</surname>
          </string-name>
          ,
          <article-title>Formalising linked-data based verifiable credentials for selective disclosure</article-title>
          ,
          <source>in: 2022 IEEE European Symposium on Security and Privacy Workshops (EuroS&amp;PW)</source>
          ,
          <year>2022</year>
          , pp.
          <fpage>52</fpage>
          -
          <lpage>65</lpage>
          . doi:
          <volume>10</volume>
          .1109/EuroSPW55150.
          <year>2022</year>
          .
          <volume>00013</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>C. H.-J. Braun</surname>
          </string-name>
          , T. Käfer,
          <article-title>RDF-Based Semantics for Selective Disclosure and Zero-Knowledge Proofs on Verifiable Credentials, in: The Semantic Web</article-title>
          , volume
          <volume>15718</volume>
          ,
          <year>2025</year>
          , pp.
          <fpage>383</fpage>
          -
          <lpage>402</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978- 3-
          <fpage>031</fpage>
          - 94575- 5_
          <fpage>21</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>D.</given-names>
            <surname>Buchner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Zundel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Riedel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. H.</given-names>
            <surname>Dufy</surname>
          </string-name>
          ,
          <source>Presentation Exchange 2.1</source>
          .1,
          <string-name>
            <given-names>DIF</given-names>
            <surname>Ratiifed</surname>
          </string-name>
          <string-name>
            <surname>Specification</surname>
          </string-name>
          , Decentralized Identity Foundation,
          <year>2024</year>
          . URL: https://identity.foundation/ presentation-exchange
          <source>/spec/v2.1</source>
          .1/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>O.</given-names>
            <surname>Terbu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lodderstedt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Yasuda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Fett</surname>
          </string-name>
          , J. Heenan,
          <source>OpenID for Verifiable Presentations 1.0</source>
          ,
          <string-name>
            <surname>Technical</surname>
            <given-names>Report</given-names>
          </string-name>
          , OpenID Digital Credentials Protocols,
          <year>2025</year>
          . URL: https://openid.net/specs/ openid-4
          <string-name>
            <surname>-</surname>
          </string-name>
          verifiable-presentations-
          <volume>1</volume>
          _0.html.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>R.</given-names>
            <surname>Dedecker</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. De Roo</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Esteves</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Colpaert</surname>
          </string-name>
          ,
          <article-title>Demonstrating a pragmatic solution to context associations in RDF using Blank Node Graphs</article-title>
          ,
          <source>in: The Semantic Web: ESWC 2025 Posters &amp; Demos</source>
          ,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>D.</given-names>
            <surname>Longley</surname>
          </string-name>
          , G. Kellogg, P.
          <article-title>-A. Champin, JSON-LD 1.1 Processing Algorithms</article-title>
          and API, W3C Recommendation, JSON-LD Working Group,
          <year>2020</year>
          . URL: https://www.w3.org/TR/json-ld11-api/, https://www.w3.org/TR/2020/REC-json-ld11
          <string-name>
            <surname>-</surname>
          </string-name>
          api-20200716/.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>