The International Foundation for Information Technology (IF4IT)
  • Home
  • Best Practices & More
  • Articles
  • About Us
  • Contact Us
  • Catalog
  • Search
Software Technologies Inventory and Attributes
Contractual and legal attributes record the terms under which each software technology may be used. License Type is Crawl-tagged because it governs everything downstream: whether entitlement compliance applies, whether open source obligations attach, and whether a usage change re

Software Technologies Inventory and Attributes - Contractual and Legal attributes for the Software Technologies Inventory

Software Technologies Inventory and Attributes


Chapter 23. Contractual and Legal attributes for the Software Technologies Inventory

Authored and Published By: The International Foundation for Information Technology (IF4IT), LLC

Previous Chapter <<Table of Contents>> Next Chapter

Executive Summary: Chapter Overview

IF4IT

💡 The Bottom Line

Contractual and legal attributes record the terms under which each software technology may be used. License Type is Crawl-tagged because it governs everything downstream: whether entitlement compliance applies, whether open source obligations attach, and whether a usage change requires legal review before it is made.

📝 Core Concepts

ConceptDefinition & Strategic Role
License TypeThe specific licence governing use — the fact that determines which obligations attach and which do not.
Open Source ObligationsThe duties a permissive or copyleft licence creates, particularly where the technology is embedded in something the enterprise distributes.
Usage RestrictionLimits the licence places on how, where, or by whom the technology may be used, which constrain deployment independently of technical capability.

🤖 Quick Q&A

Question: Why is License Type here when Licensing Model is a classification attribute?

Answer: Licensing Model says which world the technology lives in — commercial, open source, or internal. License Type names the specific licence within that world, and the specific licence is what actually creates obligations. The first routes governance; the second determines it.

⬇ Read More Below ⬇


Previous Chapter <<Table of Contents>> Next Chapter

Contractual and legal attributes record the terms under which each software technology may be used, and the obligations those terms create.

Attribute NameMaturityDescription and Notes
License TypeCrawl

Description — The specific licence governing the enterprise's use of the technology.

Benefit(s) — Determines which obligations actually attach — entitlement compliance, source disclosure, attribution, or none — and governs whether a usage change needs legal review.

Source — Manual.

Examples — Perpetual, Subscription, Per-Core, Apache 2.0, GPL-3.0, MIT

Notes — Crawl-tagged because it governs everything downstream. Distinct from Licensing Model, which records only the broad category.

License Agreement ReferenceWalk

Description — Reference to the governing licence agreement or open source licence text.

Benefit(s) — Makes the actual terms retrievable when a question arises, rather than relying on recollection of what was agreed.

Source — Manual.

Notes — For commercial technologies, cross-reference the entitlement records held in the software licence and subscription inventories.

Open Source License ObligationsWalk

Description — The obligations the open source licence creates for the enterprise.

Benefit(s) — Surfaces duties — attribution, source disclosure, copyleft propagation — that are easy to incur unknowingly and expensive to remediate late.

Source — Manual.

Notes — Most consequential where the technology is embedded in something the enterprise distributes. Leave empty for commercial technologies.

Usage RestrictionsRun

Description — Limits the licence places on how, where, or by whom the technology may be used.

Benefit(s) — Prevents deployment or expansion that is technically possible and contractually prohibited.

Source — Manual.

Notes — Common restrictions include environment limits, user or core counts, and prohibitions on use by affiliates or in service delivery to third parties.

Contract ReferenceRun

Description — Reference to the governing commercial contract, where one exists.

Benefit(s) — Connects the technology to its commercial terms, renewal dates, and negotiated protections.

Source — Manual.

Notes — A typed reference to the contract record rather than a restatement of its content.

Indemnification StatusRun

Description — Whether the supplier indemnifies the enterprise against intellectual property claims arising from use of the technology.

Benefit(s) — Establishes where legal risk actually sits, which differs sharply between commercial and open source technologies.

Source — Manual.

Notes — Open source technologies are generally supplied without indemnification; recording that explicitly is more useful than leaving the field empty.

Previous Chapter <<Table of Contents>> Next Chapter

How to cite this page

When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.

Example (informal web citation):

The International Foundation for Information Technology (IF4IT), LLC. Contractual and Legal attributes for the Software Technologies Inventory | Software Technologies Inventory and Attributes. https://if4it.org/best-practices/software-technologies-inventory-and-attributes/contractual-and-legal-attributes-for-the-software-technologies-inventory/ (accessed 2026-07-28).

See About Us for content governance and site-wide citation guidance.

Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present

Legal Disclaimers
Share:
Contact Us → Subscribe →
© The International Foundation for Information Technology (IF4IT) 2008 - Present Legal Disclaimers