gdc-common-utils-ts 1.0.4 → 1.0.7

package/{src/models/oidc4ida.electronicRecord.model.ts → dist/models/oidc4ida.electronicRecord.model.d.ts}

@@ -1,10 +1,4 @@
-// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
-// File: crypto-ts/models/oidc4ida.electronicRecord.model.ts
-
 import { AttachmentExternalDLT, CheckDetails, VerifierDLT } from './oidc4ida.common.model';
-
-// TODO: IssuerElectronicRecordOpenID with personal_number
-
 /** OpenID 'electronic_record' evidence sub-element base data
  *  to be extended with 'attachments' and 'record' elements for blockchain or OpenID Evidence of Electronic Record
  *  The electronic health record can be about a VC, SHC, DGC, FHIR Bundle or single resource (e.g.: a single medical record).
@@ -14,12 +8,11 @@ import { AttachmentExternalDLT, CheckDetails, VerifierDLT } from './oidc4ida.com
  *  - 'time': Time stamp in ISO 8601:2004 format representing the date when it was verified.
  */
 export interface EvidenceElectronicRecordBase {
-    check_details?: CheckDetails[];      // OPTIONAL. Checks done in relation to the evidence. https://bitbucket.org/openid/ekyc-ida/wiki/identifiers
-    time?:          string;                   // OPTIONAL. Time stamp in ISO 8601:2004 [ISO8601-2004] YYYY-MM-DDThh:mm[:ss]TZD format representing the date when it was verified
-    type?:          'electronic_record';      // REQUIRED but not stored on blockchain in case of FHIR resources (they always are 'electronic_records').
-    verifier?:      VerifierDLT;              // OPTIONAL. A JSON object denoting the legal entity that performed the identity verification on behalf of the OP.
+    check_details?: CheckDetails[];
+    time?: string;
+    type?: 'electronic_record';
+    verifier?: VerifierDLT;
 }
-
 /** OpenID 'electronic_record' evidence sub-element for blockchain.
  *  The electronic health record can be about a VC, SHC, DGC, FHIR Bundle or single resource (e.g.: a single medical record).
  *  - 'record': 'source' (issuer), 'personal_number' (subject's DID), 'created_at', 'date_of_expiry', 'type' ('idcard' or 'vc', 'shc', 'dgc', 'fhir', etc: see 'Electronic Records' at https://bitbucket.org/openid/ekyc-ida/wiki/identifiers)
@@ -32,13 +25,10 @@ export interface EvidenceElectronicRecordBase {
  *
  *  NOTE: 'document_details' is not for electronic records (use 'record' instead).
  */
-export interface EvidenceElectronicRecordDLT extends
-    EvidenceElectronicRecordBase    // 'type', 'validation_method', 'verification_method', 'verifier', 'time'
-{
-    attachments?:   AttachmentExternalDLT[];  // OPTIONAL. Array of JSON objects representing attachments like photocopies of documents or certificates.
-    record?:        ElectronicRecordDLT;      // JSON object representing the id document used to perform the id verification
+export interface EvidenceElectronicRecordDLT extends EvidenceElectronicRecordBase {
+    attachments?: AttachmentExternalDLT[];
+    record?: ElectronicRecordDLT;
 }
-
 /** OpenID 'electronic_record' evidence sub-element can be about an ID card, VC, SHC, DGC, etc.
  *  - 'type': can be 'idcard', 'vc', 'shc', 'dgc', 'fhir', etc (see 'Electronic Records' at https://bitbucket.org/openid/ekyc-ida/wiki/identifiers)
  *  - 'created_at': is the same as 'validFrom' property in a W3C credential.
@@ -48,13 +38,11 @@ export interface EvidenceElectronicRecordDLT extends
  *  NOTE: 'personal_number' (subject DID URI) is not excluded for now?
  */
 export interface ElectronicRecordBase {
-    type:               string;             // REQUIRED. string;denoting the type of electronic record. See https://bitbucket.org/openid/ekyc-ida/wiki/identifiers
-    created_at?:        string;             // OPTIONAL. The time the record was created as ISO 8601:2004 [ISO8601-2004] YYYY-MM-DDThh:mm[:ss]TZD format    date_of_expiry?:    string; // REQUIRED. If this attribute exists for the particular type of document. The date the document will expire as ISO 8601:2004 YYYY-MM-DD format.
-    date_of_expiry?:    string;             // OPTIONAL. The date the evidence will expire as ISO 8601:2004 [ISO8601-2004] YYYY-MM-DD format.
-    source?:            IssuerElectronicRecordBase; // OPTIONAL. Issuer as source of the record (can have jurisdiction and )
-    // personal_number?:   string;                     // OPTIONAL. Subject DID URI (it can be also the holder ID).
+    type: string;
+    created_at?: string;
+    date_of_expiry?: string;
+    source?: IssuerElectronicRecordBase;
 }
-
 /** OpenID 'electronic_record' evidence sub-element can be about a VC, SHC of DGC.
  *  - 'type': String denoting the type of electronic record. It can be a predefined value (idcard, etc) or 'vc', 'shc', 'dgc', 'fhir', etc (see 'Electronic Records' at https://bitbucket.org/openid/ekyc-ida/wiki/identifiers)
  *  - 'created_at' is the issued property.
@@ -62,25 +50,18 @@ export interface ElectronicRecordBase {
  *  NOTE:
  *  - 'personal_number' (subject DID) is excluded for now? (it is also the same as the 'holder.id' property in VC).
  */
-export interface ElectronicRecordDLT extends
-    ElectronicRecordBase    // 'type', 'personal_number', 'created_at', 'date_of_expiry'
-{
-    source?: IssuerElectronicRecordDLT; // OPTIONAL. Issuer as source of the record (API can set the name and jurisdiction for the OpenID source element)
+export interface ElectronicRecordDLT extends ElectronicRecordBase {
+    source?: IssuerElectronicRecordDLT;
 }
-
 /** Issuer's anonymized information (can be used for research purposes) */
 export interface IssuerElectronicRecordBase {
-    country_code?:  string; // ISO 3166/ICAO 3-letter codes [ICAO-Doc9303]. 2-letter ISO 3166/ICAO codes MAY be used in some circumstances for compatibility reasons.
-    jurisdiction?:  string; // ISO: String containing the region(s) / state(s) / province(s) / municipality(ies) that source has jurisdiction over
-    // postal_code?:string; // Zip code or postal code component.
+    country_code?: string;
+    jurisdiction?: string;
 }
-
 /** It replaces the issuer 'name' by 'id' and 'type' (for blockchain)
  *  and also includes 'country' and 'region' (but not 'postal_code', 'locality' or 'stree_address').
  */
-export interface IssuerElectronicRecordDLT extends
-    IssuerElectronicRecordBase
-{
-    id?:            string; // custom UHC property instead of 'name'
-    type?:          string; // custom UHC property
+export interface IssuerElectronicRecordDLT extends IssuerElectronicRecordBase {
+    id?: string;
+    type?: string;
 }

package/dist/models/oidc4ida.electronicRecord.model.js

@@ -0,0 +1,3 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/oidc4ida.electronicRecord.model.ts
+export {};

package/{src/models/oidc4ida.evidence.model.ts → dist/models/oidc4ida.evidence.model.d.ts}

@@ -1,9 +1,5 @@
-// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
-// File: crypto-ts/models/oidc4ida.evidence.model.ts
-
 import { EvidenceDocumentDLT } from "./oidc4ida.document.model";
 import { EvidenceElectronicRecordDLT } from "./oidc4ida.electronicRecord.model";
-
 /** W3C Evidence for VCs can be generated by the API from some OpenID evidence stored on blockchain.
  *  See EBSI v2: https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/Verifiable+Attestation
  *  - id: OPTIONAL. If present, it MUST contain a URL that points to where more information about this instance of evidence can be found (e.g.: urn:unid:uhc:vc:xyz or e.g.: "https://example.edu/evidence/f2aeec97-fc0d-42bf-8ca7-0548192dxyzab")
@@ -14,42 +10,35 @@ import { EvidenceElectronicRecordDLT } from "./oidc4ida.electronicRecord.model";
  *  - documentPresence:  REQUIRED. Defines how the document(s) which have been verified before Verifiable Credentials issuance have been provided, e.g.: 'Physical' or 'Digital'
  */
 export interface EvidenceW3C {
-    id?:                string;
-    type?:              string[];
-    verifier?:          string;
-    evidenceDocument?:  string;
-    subjectPresence?:   string;
-    documentPresence?:  string;
+    id?: string;
+    type?: string[];
+    verifier?: string;
+    evidenceDocument?: string;
+    subjectPresence?: string;
+    documentPresence?: string;
 }
-
 /** OpenID 'electronic_signature' evidence sub-element
  * 'serial_number' can be the DID of the public key for doing the verification process instead of the serial number of a certificate.
  */
-export interface EvidenceElectronicSignatureBase{
-    type:           'electronic_signature'; // REQUIRED: Fixed to 'electronic_signature'
-    signature_type: string;                 // REQUIRED. Type of signature used as evidence. The value range might be restricted by the respective trust framework.
-    issuer:         string;                 // REQUIRED. Certification authority that issued the signer's certificate.
-    serial_number:  string;                 // REQUIRED. DID#KID or Serial number of the certificate used to sign.
-    created_at:     string;                 // REQUIRED. The time the signature was created as ISO 8601:2004 YYYY-MM-DDThh:mm:ss±hh format
+export interface EvidenceElectronicSignatureBase {
+    type: 'electronic_signature';
+    signature_type: string;
+    issuer: string;
+    serial_number: string;
+    created_at: string;
 }
-
 /** The used language is not specified, but is usually bound to the jurisdiction of the underlying trust framework of the OP. */
 export interface AttachedSignatureDLT {
-  // desc?:          string; // OPTIONAL. Description of the document. This can be the filename or just an explanation of the content (e.g. "Back of id document")
-  content_type:   string; // e.g.: 'jws'
-  content:        string; // e.g. detached signature string (compact JWS) or bytes encoded in Base64
+    content_type: string;
+    content: string;
 }
-
 /** OpenID 'electronic_signature' evidence sub-element
  * 'serial_number' can be the DID of the public key for doing the verification process instead of the serial number of a certificate.
  * It also contains 'type', 'signature_type', 'issuer', 'serial_number', 'created_at' and external 'attachments' with 'digest.alg' and 'digest.value'.
  */
-export interface EvidenceElectronicSignatureDLT extends
-    EvidenceElectronicSignatureBase // 'type', 'signature_type', 'issuer', 'serial_number', 'created_at'
-{
-    attachments?:   AttachedSignatureDLT[];   // OPTIONAL. Array of JSON objects containing signatures, e.g. 'jws' or 'Ed25519' signature types.
+export interface EvidenceElectronicSignatureDLT extends EvidenceElectronicSignatureBase {
+    attachments?: AttachedSignatureDLT[];
 }
-
 /** Evidence is the certification of the authenticity of some (physical) document, (electronic) record, (electronic) signature, (utility) bill or vouch.
  * OpenID Connect for Identity Assurance 1.0: https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html
  * 5.1.1. Evidence Element - types of evidence:
@@ -59,11 +48,4 @@ export interface EvidenceElectronicSignatureDLT extends
  * - utility_bill: Verification based on a utility bill (this is to be deprecated in future releases and implementers are recommended to use the document type instead).
  * - electronic_signature: Verification based on an electronic signature.
  */
-export type EvidenceObjectDLT =
-    EvidenceElectronicRecordDLT         // e.g.: VC, SHC, DGC, FHIR record, etc.
-    | EvidenceDocumentDLT               // e.g.: evidence of a physical document
-    | EvidenceElectronicSignatureDLT    // evidence from a digital certificate signature (e.g. PDF document)
-    // | EvidenceVouchDLT
-    // | EvidenceBillDLT
-
-
+export type EvidenceObjectDLT = EvidenceElectronicRecordDLT | EvidenceDocumentDLT | EvidenceElectronicSignatureDLT;

package/dist/models/oidc4ida.evidence.model.js

@@ -0,0 +1,5 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/oidc4ida.evidence.model.ts
+export {};
+// | EvidenceVouchDLT
+// | EvidenceBillDLT

package/dist/models/openid-device.d.ts

@@ -0,0 +1,119 @@
+/**
+ * @fileoverview Defines data models for device registration based on OpenID Connect Dynamic Client Registration 1.0,
+ * with custom extensions for native device information.
+ * @see https://openid.net/specs/openid-connect-registration-1_0.html
+ */
+import { JwkSet } from "./jwk";
+/**
+ * Represents the information about the physical device being registered.
+ * This is a custom extension to the OpenID DCR standard.
+ */
+export interface OpenIdDeviceInfo {
+    /**
+     * The push notification token for the device.
+     * @example "ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]"
+     */
+    push_token: string;
+    /**
+     * The push notification provider.
+     * @example "expo"
+     */
+    push_provider: string;
+    /**
+     * A unique identifier for the device, such as the OS internal build ID.
+     * @example "19.6.0"
+     */
+    device_id: string;
+    /**
+     * A user-friendly name for the device.
+     * @example "John's iPhone"
+     */
+    device_name: string;
+}
+/**
+ * Represents the request payload for Dynamic Client Registration,
+ * based on OpenID Connect Registration 1.0.
+ * The `body` of the DIDComm message will contain this object.
+ * @see https://openid.net/specs/openid-connect-registration-1_0.html#RegistrationRequest
+ */
+export interface DcrRegistrationRequest {
+    /**
+     * Array of redirection URIs for use in redirect-based flows. For a native app,
+     * this could be a custom scheme URI.
+     * @example ["myapp://callback"]
+     */
+    redirect_uris: string[];
+    /**
+     * Kind of the application. The only supported value is 'native'.
+     */
+    application_type?: 'native';
+    /**
+     * Human-readable name of the client to be presented to the end-user.
+     * @example "My Awesome App"
+     */
+    client_name?: string;
+    /**
+     * URL of the home page of the client.
+     */
+    client_uri?: string;
+    /**
+     * Requested authentication method for the token endpoint.
+     * For apps using public keys, 'private_key_jwt' is common.
+     * 'none' can be used for public clients.
+     */
+    token_endpoint_auth_method?: 'none' | 'private_key_jwt';
+    /**
+     * A list of OAuth 2.0 grant types that the client will restrict itself to using.
+     */
+    grant_types?: ('authorization_code' | 'implicit' | 'refresh_token' | 'client_credentials')[];
+    /**
+     * URL for the client's JSON Web Key Set [JWK] document. If the client signs requests to the Server,
+     * it contains the signing key(s) the Server uses to validate signatures from the Client.
+     */
+    jwks_uri?: string;
+    /**
+     * JSON Web Key Set containing the client's public keys.
+     * REQUIRED if `jwks_uri` is not provided.
+     */
+    jwks?: JwkSet;
+    /**
+     * Custom data about the specific device instance being registered.
+     * This is prefixed to avoid collision with standard fields.
+     */
+    ext_device_info?: OpenIdDeviceInfo;
+}
+/**
+ * Represents the response payload for a successful Dynamic Client Registration,
+ * based on OpenID Connect Registration 1.0.
+ * This object will be nested inside the `resource` of the final BundleEntry.
+ * @see https://openid.net/specs/openid-connect-registration-1_0.html#RegistrationResponse
+ */
+export interface DcrRegistrationResponse {
+    /**
+     * Unique client identifier.
+     */
+    client_id: string;
+    /**
+     * Time at which the client_id was issued, represented as a Unix timestamp.
+     */
+    client_id_issued_at: number;
+    /**
+     * The client secret. For public clients or those using JWTs for client authentication,
+     * this may not be returned.
+     */
+    client_secret?: string;
+    /**
+     * Time at which the client_secret will expire, represented as a Unix timestamp.
+     * If 0, the secret does not expire.
+     */
+    client_secret_expires_at?: number;
+    /**
+     * A registration access token that can be used at the client configuration endpoint
+     * to perform subsequent operations upon the client registration.
+     */
+    registration_access_token?: string;
+    /**
+     * URL of the client's configuration endpoint.
+     */
+    registration_client_uri?: string;
+}

package/dist/models/openid-device.js

@@ -0,0 +1,3 @@
+// src/models/openid-device.ts
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+export {};

package/dist/models/operation-outcome.d.ts

@@ -0,0 +1,26 @@
+import { IssueLevel, IssueTypeCode } from './issue';
+/**
+ * A single detail associated with an operation, based on a simplified FHIR structure.
+ * Renamed from 'Issue' to be more neutral for potential success reporting.
+ */
+export interface OperationOutcomeDetails {
+    /**
+     * Indicates the severity of the detail.
+     */
+    severity: IssueLevel;
+    /**
+     * A code classifying the type of detail.
+     */
+    code: IssueTypeCode;
+    /**
+     * Additional diagnostic information, such as a stack trace or detailed error message.
+     */
+    diagnostics?: string;
+}
+/**
+ * A structured response detailing the result of an operation, based on a simplified FHIR structure.
+ */
+export interface OperationOutcome {
+    resourceType: 'OperationOutcome';
+    issue: OperationOutcomeDetails[];
+}

package/dist/models/operation-outcome.js

@@ -0,0 +1,3 @@
+// src/models/fhir/operation-outcome.ts
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+export {};

package/{src/models/params.ts → dist/models/params.d.ts}

@@ -1,6 +1,3 @@
-// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
-// File: crypto-ts/models/params.ts
-
 /**
  * Represents a interoperable claim for all specifications.
  */
@@ -15,7 +12,6 @@ export interface ClaimInteroperable {
      */
     value: any;
 }
-
 /**
  * Represents a single, named piece of data within an entity's configuration,
  * aligning with the structure of a Parameter in the FHIR Parameters resource.
@@ -28,32 +24,28 @@ export interface ClaimInteroperable {
  * @see {@link https://hl7.org/fhir/parameters.html}
  */
 export interface ParamAttribute extends ClaimInteroperable {
-  /**
-   * The name of the parameter, which often corresponds to a key in the
-   * 'indexed' attributes dictionary of the parent configuration.
-   *
-   * @example 'NNES' (for a Spanish DNI, unique=true)
-   * @example 'email' (unique=falsez)
-   */
-  name: string;
-
-  /**
-   * The original value of the parameter. Can be either a string or a number.
-   * This corresponds to a simplified `value[x]` (e.g., `valueString`) in a FHIR Parameter.
-   */
-  value: string | number | undefined;
-
-  /**
-   * A custom flag to indicate whether this attribute's value is expected to
-   * be unique across all entities of the same type. This is used for
-   * server-side validation logic and is not part of the FHIR standard.
-   * @default false
-   */
-  unique?: boolean;
+    /**
+     * The name of the parameter, which often corresponds to a key in the
+     * 'indexed' attributes dictionary of the parent configuration.
+     *
+     * @example 'NNES' (for a Spanish DNI, unique=true)
+     * @example 'email' (unique=falsez)
+     */
+    name: string;
+    /**
+     * The original value of the parameter. Can be either a string or a number.
+     * This corresponds to a simplified `value[x]` (e.g., `valueString`) in a FHIR Parameter.
+     */
+    value: string | number | undefined;
+    /**
+     * A custom flag to indicate whether this attribute's value is expected to
+     * be unique across all entities of the same type. This is used for
+     * server-side validation logic and is not part of the FHIR standard.
+     * @default false
+     */
+    unique?: boolean;
 }
-
 export type ParameterType = 'number' | 'date' | 'string' | 'token' | 'reference' | 'composite' | 'quantity' | 'uri' | 'period';
-
 /**
  * Represents a common interface for all types of parameters.
  */
@@ -103,7 +95,6 @@ export interface ParameterData extends ParamAttribute {
      */
     appliesTo?: string[];
 }
-
 export interface StringSearchParameter extends ParameterData {
     type: 'string';
     value: string;

package/dist/models/params.js

@@ -0,0 +1,3 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/params.ts
+export {};

package/dist/models/resource-document.d.ts

@@ -0,0 +1,14 @@
+/**
+ * A flexible record type for claims objects.
+ */
+export type ClaimsRecord = Record<string, any>;
+export interface RecordBase {
+    id: string;
+}
+/**
+ * Represents the configuration metadata for a vault.
+ * As defined in the original database abstract layer.
+ */
+export interface VaultConfig extends RecordBase {
+    custodian?: string;
+}

package/dist/models/resource-document.js

@@ -0,0 +1,3 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/resource-document.ts
+export {};

package/dist/models/response.d.ts

@@ -0,0 +1 @@
+export type { IDecodedDidcommPayload } from './confidential-message';

package/dist/models/response.js

@@ -0,0 +1,3 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/response.ts
+export {};

package/dist/models/urlPath.d.ts

@@ -0,0 +1,58 @@
+/**
+ * Defines the standardized business sectors supported by the gateway.
+ * Using an enum ensures type safety and prevents the use of arbitrary strings.
+ */
+export declare enum Sector {
+    TEST = "test",// For mock/demo endpoints and host registry in tests
+    SYSTEM = "system",// Reserved for the host's bootstrap operation (TODO: deprecate)
+    HEALTH_CARE = "health-care",
+    HEALTH_INSURANCE = "health-insurance",
+    EMERGENCY = "emergency",
+    RESEARCH = "research"
+}
+export declare enum Section {
+    /** Managing registration of organizations */
+    registry = "registry",
+    /** Managing data of the hosted organization */
+    entity = "entity",
+    /** Managing data of the hosted individual */
+    individual = "individual",
+    /** Managing data in the blockchain network */
+    network = "network"
+}
+/** Standards, specifications and formats for data supported in the url path */
+export declare enum Format {
+    Schema = "org.schema",
+    FhirApi = "org.hl7.fhir.api"
+}
+/** Types of resources supported in the url path */
+export declare enum Resource {
+    Person = "Person",
+    RelatedPerson = "RelatedPerson",
+    Employee = "Emloyee",
+    EmployeeRole = "EmloyeeRole",
+    Practitioner = "Practitioner",
+    PractitionerRole = "PractitionerRole",
+    Organization = "Organization",
+    Location = "Location",
+    Group = "Group"
+}
+export declare enum JobAction {
+    "_batch" = "_batch",
+    "_create" = "_create",
+    "_discovery" = "_discovery"
+}
+export declare enum knownDomainsReversedEnum {
+    'org.schema' = "org.schema",
+    'org.hl7.fhir.api' = "org.hl7.fhir.api",
+    'org.hl7.fhir.r4' = "org.hl7.fhir.r4",
+    'org.ilo.isco' = "org.ilo.isco",
+    'net.openid' = "net.openid"
+}
+/**
+ * A list of known, fully-qualified context prefixes in reverse DNS format.
+ * This is used by the claim normalization utility to identify claims that
+ * are already interoperable and should not be modified.
+ * All entries should be in lowercase.
+ */
+export declare const knownDomainsReversed: string[];

package/dist/models/urlPath.js

@@ -0,0 +1,76 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/urlPath.ts
+/**
+ * Defines the standardized business sectors supported by the gateway.
+ * Using an enum ensures type safety and prevents the use of arbitrary strings.
+ */
+export var Sector;
+(function (Sector) {
+    Sector["TEST"] = "test";
+    Sector["SYSTEM"] = "system";
+    Sector["HEALTH_CARE"] = "health-care";
+    Sector["HEALTH_INSURANCE"] = "health-insurance";
+    Sector["EMERGENCY"] = "emergency";
+    Sector["RESEARCH"] = "research";
+})(Sector || (Sector = {}));
+export var Section;
+(function (Section) {
+    /** Managing registration of organizations */
+    Section["registry"] = "registry";
+    /** Managing data of the hosted organization */
+    Section["entity"] = "entity";
+    /** Managing data of the hosted individual */
+    Section["individual"] = "individual";
+    /** Managing data in the blockchain network */
+    Section["network"] = "network";
+})(Section || (Section = {}));
+/** Standards, specifications and formats for data supported in the url path */
+export var Format;
+(function (Format) {
+    Format["Schema"] = "org.schema";
+    Format["FhirApi"] = "org.hl7.fhir.api";
+    //Pdf' = 'pdf',
+})(Format || (Format = {}));
+/** Types of resources supported in the url path */
+export var Resource;
+(function (Resource) {
+    Resource["Person"] = "Person";
+    Resource["RelatedPerson"] = "RelatedPerson";
+    Resource["Employee"] = "Emloyee";
+    Resource["EmployeeRole"] = "EmloyeeRole";
+    Resource["Practitioner"] = "Practitioner";
+    Resource["PractitionerRole"] = "PractitionerRole";
+    Resource["Organization"] = "Organization";
+    Resource["Location"] = "Location";
+    Resource["Group"] = "Group";
+})(Resource || (Resource = {}));
+export var JobAction;
+(function (JobAction) {
+    JobAction["_batch"] = "_batch";
+    JobAction["_create"] = "_create";
+    JobAction["_discovery"] = "_discovery";
+})(JobAction || (JobAction = {}));
+export var knownDomainsReversedEnum;
+(function (knownDomainsReversedEnum) {
+    knownDomainsReversedEnum["org.schema"] = "org.schema";
+    knownDomainsReversedEnum["org.hl7.fhir.api"] = "org.hl7.fhir.api";
+    knownDomainsReversedEnum["org.hl7.fhir.r4"] = "org.hl7.fhir.r4";
+    knownDomainsReversedEnum["org.ilo.isco"] = "org.ilo.isco";
+    knownDomainsReversedEnum["net.openid"] = "net.openid";
+    // Add other known standards here
+})(knownDomainsReversedEnum || (knownDomainsReversedEnum = {}));
+;
+/**
+ * A list of known, fully-qualified context prefixes in reverse DNS format.
+ * This is used by the claim normalization utility to identify claims that
+ * are already interoperable and should not be modified.
+ * All entries should be in lowercase.
+ */
+export const knownDomainsReversed = [
+    knownDomainsReversedEnum["org.schema"],
+    knownDomainsReversedEnum["org.hl7.fhir.api"],
+    knownDomainsReversedEnum["org.hl7.fhir.r4"],
+    knownDomainsReversedEnum["org.ilo.isco"],
+    knownDomainsReversedEnum["net.openid"]
+    // Add other known standards here
+];

package/dist/models/verifiable-credential.d.ts

@@ -0,0 +1,45 @@
+import { EvidenceObjectDLT } from "./oidc4ida.evidence.model";
+/**
+ * Defines the JSON-LD context URI for W3C Verifiable Credentials Data Model v2.0.
+ * This constant MUST be used for all V2 credential creations to ensure consistency.
+ * @see https://www.w3.org/TR/vc-data-model-2.0/#contexts
+ */
+export declare const VC_CONTEXT_V2 = "https://www.w3.org/ns/credentials/v2";
+/** ProofEBSIv2 foresees the possibility to use different types of proofs for Verifiable Credentials,
+ *  such as proofs derived from eIDAS keys (qualified) to DID keys (unqualified).
+ *  In EBSI 2.0, every V-ID will only contain a single proof, which must be derived from eIDAS keys.
+ *  Definition: https://www.w3.org/TR/vc-data-model/#proofs-signatures
+ *  See https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/Verifiable+Attestation
+ *  - 'created' is REQURED, it is the ISO 8601 original timestamp of the signature, it is not the same as credential.issued (tx timestamp) (in Aries go framework use *util.TimeWithTrailingZeroMsec instead of time.Time)
+ *  - 'jws' is REQUIRED, it defines the detached JWS signature string "<base64url(protectedheader)>..<base64url(signature)>"
+ *  - 'proofPurpose' is REQUIRED, e.g.: assertionMethod, authentication, keyAgreement, contractAgreement, capabilityInvocation, capabilityDelegation
+ *  - 'type' is REQUIRED, e.g.: "JsonWebSignature2020", "BbsBlsSignature2020", "BbsBlsSignatureProof2020".
+ *  - 'verificationMethod' is REQUIRED, it is the 'urndid#keyId' to verify the signature by using the issuer's public signature key.
+ */
+export interface ProofEBSIv2 {
+    created?: string;
+    jws?: string;
+    proofPurpose?: string;
+    type: string;
+    verificationMethod?: string;
+}
+/**
+ * Defines the structure for a W3C Verifiable Credential.
+ * The credentialSubject can be any object containing the claims.
+ * @see https://www.w3.org/TR/vc-data-model-2.0/#verifiable-credentials
+ */
+export interface VerifiableCredentialV2 {
+    '@context': string[];
+    id?: string;
+    type: string[];
+    /** Claims about the subject, such as the "identifier" or subject's URN */
+    credentialSubject: Record<string, any>;
+    /** Evidence for Identity Assurance: https://openid.net/specs/openid-ida-verified-claims-1_0-final.html#section-5.4.4 */
+    evidence?: EvidenceObjectDLT[];
+    /** The issuer is the creator (e.g., "did:web:gateway.example.com"), but could be distinct to the signer of a proof */
+    issuer: string;
+    /** Proof is optional during creation, but required for a signed VC */
+    proof?: ProofEBSIv2 | ProofEBSIv2[];
+    validFrom: string;
+    validUntil?: string;
+}

package/dist/models/verifiable-credential.js

@@ -0,0 +1,8 @@
+// Copyright 2025 Antifraud Services Inc. under the Apache License, Version 2.0.
+// File: crypto-ts/models/verifiable-credential.ts
+/**
+ * Defines the JSON-LD context URI for W3C Verifiable Credentials Data Model v2.0.
+ * This constant MUST be used for all V2 credential creations to ensure consistency.
+ * @see https://www.w3.org/TR/vc-data-model-2.0/#contexts
+ */
+export const VC_CONTEXT_V2 = 'https://www.w3.org/ns/credentials/v2';