Copyright (c) 2024, NorshPermission is hereby granted to use this license as the foundational framework for composing modular licenses under the Norsh Commons License (NCL) system. This document defines the scope of the license, its modular structure, and the requirements for usage and reference.
The NCL-0 serves as the core specification for the Norsh Commons License framework, providing guidance on how to apply, compose, and reference modular licenses. It establishes the baseline principles for managing copyrighted materials and defines the binary modular system for combining rules into custom licenses.
By default, the NCL-0 grants the following permissions:
No Attribution Required
Users are not required to cite or credit the original author or rights holder when using, modifying, or distributing the material.
Commercial Use Allowed
The material may be freely used for commercial purposes without requiring additional permissions or agreements.
Derivative Works Allowed
Users may create, modify, and distribute derivative works without restrictions.
These permissions establish the foundational openness of the NCL-0. However, they may be restricted or modified by additional NCL rules included in the license composition.
The material under NCL-0 is provided "as is," without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement.
8. Explanation of the Graphical Representation of NCL Rules#
The diagram illustrates the hierarchical and modular structure of the Norsh Commons License (NCL) framework. Each node represents a specific rule in the NCL system, and the connections between nodes demonstrate their dependencies and relationships. Here's a detailed breakdown:
1.
NCL-0 (Foundational Rule)
Positioned at the center of the structure, NCL-0 is the foundational rule that applies to all licenses in the NCL framework. Every license composition must include NCL-0 as its core.
2.
Primary Rules (NCL-1, NCL-2, NCL-4, NCL-8)
These rules branch directly from NCL-0, indicating that they are modular extensions of the foundational rule.
NCL-1: Attribution Requirement.
NCL-2: Restricted Commercialization.
NCL-4: Educational Use Permission.
NCL-8: Complementary or context-specific permissions.
3.
Derived or Specialized Rules (NCL-16, NCL-32, NCL-64, NCL-128)
These rules extend from a combination of other primary rules, showcasing their dependency.
NCL-16: Builds upon NCL-8, focusing on complementary use and integration permissions.
NCL-32: Adds pre-approval requirements for applications (e.g., app store-like approval processes) and depends on NCL-16.
NCL-64: Restricted or Authorized Derivatives, tied to NCL-2.
NCL-128: Contribution Terms, integrating principles from both commercial and collaborative contributions.
4.
Flow and Modularity
The arrows represent how rules depend on one another for specific contexts. For example:
NCL-32 relies on NCL-16 to ensure compliance with integration permissions.
NCL-128 integrates broader collaboration requirements across the framework.
This graphical representation is an essential tool for understanding how specific licenses (e.g., NCL-7, NCL-11) are composed. By combining the appropriate rules, users can craft tailored licensing agreements that meet their unique requirements while adhering to the modular and hierarchical structure of the NCL system.This structured example demonstrates how to compose and reference an NCL-based license, ensuring clarity and compliance.
