Skip to content

Main content

Metadata Relation Inverse Flag Tool

Compare an explicit inverse-relation map without asserting semantic inverse properties from names.

Loading tool…

Description

Find forward, return known, and compare its mapped inverse exactly with suppliedInverse.

Metadata obligations and relations apply to a declared record scope. Field presence, source coverage, cardinality, and value correctness are independent properties.

Find forward, return known, and compare its mapped inverse exactly with suppliedInverse.

When to use this tool

Use Metadata Relation Inverse Flag when you need a narrow metadata consistency or coverage check.

How to use the tool and how it works

  1. Enter forward, suppliedInverse, knownRelations, inverseRelations. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read known, inverseMatches. Inspect known, inverseMatches before interpreting the associated values.

Require aligned relation and inverse lists with unique knownRelations. Find forward, return known, and compare its mapped inverse exactly with suppliedInverse.1

Input fieldMeaning and unitsAccepted input
forwardForwardRequired. Text; maximum UTF-16 length 8192.
suppliedInverseSupplied InverseRequired. Text; maximum UTF-16 length 8192.
knownRelationsKnown RelationsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
inverseRelationsInverse RelationsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
knownKnownRequired. Boolean.
inverseMatchesInverse MatchesRequired. Boolean.
json
{
  "input": {
    "forward": "parent",
    "suppliedInverse": "child",
    "knownRelations": [
      "parent"
    ],
    "inverseRelations": [
      "child"
    ]
  },
  "output": {
    "known": true,
    "inverseMatches": true
  }
}

Limitations and assumptions

  • The relation vocabulary is caller defined; no graph edges or semantic inverse properties are verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Apply the complete metadata profile and inspect field values and provenance before accepting a record.

References

  1. Calculation and input contract: information-science/metadata-relation-inverse-flag — tool.io

Similar or alternative tools