NCL-0: Norsh Commons License

Norsh Commons License - Base (NCL or NCL-0)

Permission 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.

1. Purpose

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.

2. Scope of Application

This license applies to any copyrighted material, including but not limited to:

Source code

Texts

Images and videos

3D models

Technical documentation

Any other form of intellectual creation

3. Default Permissions

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.

4. Modular Structure

The NCL framework uses a binary modular system to define the composition of licenses:

NCL-0: The foundational rule that applies to all NCL-based licenses and is always included in every NCL composition.

Other rules (e.g., NCL-1, NCL-2, NCL-4, NCL-8, ...) can be combined to address specific needs.

Example 1: NCL-7 includes NCL-1, NCL-2, and NCL-4.

Example 2: NCL-11 includes NCL-1, NCL-2, and NCL-8.

5. Usage Guidelines

To apply the NCL framework, follow these steps:

License Document Naming
The license document must be named as:
LICENSE-NCL-XYZ, where XYZ is the sum of the binary values of the rules applied.

Example: LICENSE-NCL-7, LICENSE-NCL-11.

Include Author Information
The license document must include:

The name of the author or entity issuing the license

Contact information (optional but recommended)

A list of the NCL rules included in the license (e.g., NCL-0, NCL-1, etc.)

Additional notes relevant to the specific application of the license

Reference to Rules
The included rules must be clearly listed, with links or references to their full text for transparency and ease of access.

6. General Principles

The NCL-0 provides a standard framework for managing rights and permissions while ensuring consistency across modular licenses.

All combined rules must fully comply with their original terms when integrated into a composed license.

7. Disclaimer of Warranty

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.

Example LICENSE-NCL-7

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:

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.

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.

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.

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.

Use of the Diagram in Practice

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.

NCL-0: Norsh Commons License

Norsh Commons License - Base (NCL or NCL-0)#

1. Purpose#

2. Scope of Application#

3. Default Permissions#

4. Modular Structure#

5. Usage Guidelines#

6. General Principles#

7. Disclaimer of Warranty#

Example LICENSE-NCL-7#

8. Explanation of the Graphical Representation of NCL Rules#

Use of the Diagram in Practice#