npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@byu-oit/ts-claims-engine

v2.2.1

Published

Claims engine implementation in TypeScript

Downloads

580

Readme

Installation

npm i @byu-oit/ts-claims-engine

Introduction

The Claim Adjudicator Module (CAM, aka the Claims Engine) provides a facet of the domain contract through which other domains may verify information without having to obtain a copy of that information. For example, in order to determine whether a person is older than 21, many systems store that person's birth date. The CAM enables domains to store the binary answer to the questions, "Is this person older than 21?", instead of the more problematic date of birth.

Terminology

  • Claim - A subject identifier and one or more tuples defining the relationship of the value of a concept associated with the subject and a reference value
  • Concept - A domain-specific value or state about which a claim may be validated. A concept can be anything from a single internal data element to the result of a complex internal process. That is, concepts can be more abstract than the properties associated with a domain's resources and subresources.
  • Mode - A verb that modifies the behavior of the claim engine. Modes include ALL (the default), which requires all claims in the claim array to be true to verify the claim, and ONE, which requires only one of the claims in the claim array to be true to verify the claim.
  • Qualifier - An optional object containing domain-specific properties that is passed to the concept resolution code to further qualify the claim.
  • Relationship - The claimed relationship between the value of the concept for the specified subject and the reference value. Relationships include "match," "gt_or_eq-to," and "lt_or_eq-to."
  • Subject - A domain-specific resource identifier.

Description

More formally, the CAM determines whether a claimed relationship between the value of the instance of a concept and a reference value can be verified.

One or more claims may be made in the context of a subject. A claim expression is comprised of a subject identifier, a mode, and an array of claim tuples:

{
  "subject": "123456789",
  "mode": "ALL",
  "claims": [
  ]
}

The claim, "this person is older than 21," is expressed as a typed tuple:

{
  "concept": "age",
  "relationship": "gt_or_eq",
  "value": "21"
}

The CAM operates on domain-specific concepts. A concept may be anything from a the value of a specific column in a row identified by the subject ID to a value dynamically determined by a function.

In the older-than-21 example, the domain might subtract the birth date of the subject from the current date to derive an age to compare with the reference value.

Qualifier

The claim tuple in the example above omitted the optional qualifier property. A qualifier is an object with domain-specific properties. It is passed, along with the subject ID to the concept resolution code to further qualify the claim.

{
  "concept": "age",
  "relationship": "gt_or_eq",
  "value": "21",
  "qualifier": { ageMonthOffset: 5 }
}

In this example, the ageMonthOffset qualifier asks if the person will be older than 21 in 5 months.

API

Some of the parameters and return types are complex objects. Instead of defining them in the method definitions, they have been defined in the types file. Some of the more important types are defined in the Appendix under API Reference.

ClaimsAdjudicator

Creates a new instance of the ClaimsAdjudicator

ClaimsAdjudicator(concepts: Concepts)

IMPORTANT One of the concepts must be the subjectExists concept. The subjectExists property can be in any case. However, if the key is not in camelCase, a copy will be added to the concepts with the key in camelCase. For example:

const concepts = {
    subject_exists: new Concept({
        description: 'The subject exists',
        longDescription: 'Determines whether a subject is a known entity within the domain.',
        type: 'boolean',
        relationships: ['eq', 'not_eq'],
        qualifiers: ['age'],
        getValue: async (id, qualifiers) => {
            if (qualifiers && qualifiers.age) {
                return subjects[id] !== undefined && subjects[id].age === qualifiers.age
            } else {
                return subjects[id] !== undefined
            }
        }
    })
}

;(async () => {
    const engine = new ClaimsAdjudicator(concepts)
    const conceptInfo = await engine.getConcepts()
    console.log(JSON.stringify(conceptInfo, null, 2))
    
      //[
      //   {
      //     "id": "subject_exists",
      //     "description": "The subject exists",
      //     "longDescription": "Determines whether a subject is a known entity within the domain.",
      //     "type": "boolean",
      //     "relationships": [
      //       "eq",
      //       "not_eq"
      //     ],
      //     "qualifiers": [
      //       "age"
      //     ]
      //   },
      //   {
      //     "id": "subjectExists",
      //     "description": "The subject exists",
      //     "longDescription": "Determines whether a subject is a known entity within the domain.",
      //     "type": "boolean",
      //     "relationships": [
      //       "eq",
      //       "not_eq"
      //     ],
      //     "qualifiers": [
      //       "age"
      //     ]
      //   }
      // ]
})()

Public Methods

verifyClaims: Verifies the claims body against the the concept configuration.

verifyClaims(claims: any): Promise<ClaimsResponse>

The claims parameter will accept any type in the function though it will throw a BadRequest Error if the structure of the claims cannot be interpreted. The correct structure is defined in the Appendix under API Reference.

verifyClaim: Verifies a single claim against the concept configuration.

verifyClaim(claim: any): Promise<boolean | InternalError | BadRequest>

The claim parameter will accept any type in the function though it will throw a BadRequest Error if the str

conceptExists: Verifies that a concept has been defined.

conceptExists(key: string): boolean

getConcepts: Retrieves only the concepts definition information. It does not retrieve the getValue function.

getConcepts(): ConceptInfo[]

getConcept: Retrieves a particular concept including the getValue function.

getConcept(key: string): Concept<any>

Appendix

API Reference


/*********************************************************
 *                      CLAIMS API
 *********************************************************/
interface Claims {
    [key: string]: Claim
}

interface Claim {
    subject: string;
    mode: Mode;
    claims: Claims;
}

export type ClaimItem = {
    concept: string
    relationship: Relationship.GT | Relationship.GTE | Relationship.LT | Relationship.LTE | Relationship.EQ | Relationship.NE
    value: string
    qualifier?: Qualifiers
} | {
    concept: string
    relationship: Relationship.UN | Relationship.DE
    qualifier?: Qualifiers
}

interface Qualifiers<> {
    [key: string]: any;
}

export enum Relationship {
    GT = 'gt',
    GTE = 'gt_or_eq',
    LT = 'lt',
    LTE = 'lt_or_eq',
    EQ = 'eq',
    NE = 'not_eq',
    UN = 'undefined',
    DE = 'defined'
}

export enum Mode {
    ONE = 'one',
    ANY = 'any',
    ALL = 'all'
}

/*********************************************************
 *                      CONCEPT API
 *********************************************************/
export interface ConceptInfo {
    name: string
    description: string
    longDescription?: string
    relationships: Relationship[]
    qualifiers: string[]
}

export interface ConceptOptions<T> {
    name: string
    description: string
    longDescription?: string
    relationships: [Relationship, ...Relationship[]]
    qualifiers?: string[]
    getValue: GetValueFunction<T>
    compare: CompareFn<T> | Comparator<T>
    cast: CastFn<T>
}

export type GetValueFunction<T> = (subjectId: string, qualifiers?: Qualifiers) => Promise<T | undefined>

export type CompareFn<T> = (left: T, right: T) => number

export type CastFn<T> = (value: string) => T

Related Packages