Norsh
HomeNTPNCLAPI
HomeNTPNCLAPI
  1. NCL - Norsh Commons License
  • Norsh
    • Usage Guide
      • Cryptographic Identity
    • API
      • Crypto
        • Generates a public and private key pair
        • Generates an address from a public key.
  • NTP - Norsh Technical Paper
    • LICENSE-NCL-11
    • Published
      • NTP-1: Norsh Technical Paper Specification
      • NTP-2: Standards for Encoding, Time and Localization
      • NTP-3: Cryptography and Hash Specification
      • NTP-4: Interchangeable Data Standard
      • NTP-5: Temporal Time-Step Model
      • NTP-6: Modular Prime Fragmentation
      • NTP-7: The End of Mining - PoW
      • NTP-8: The Fallacy of Stake - PoS
      • NTP-9: The Myth of Absolute Non-Censorship
      • NTP-10: Structural Failures of Decentralization
  • NCL - Norsh Commons License
    • NCL-0: Norsh Commons License
    • NCL-1: Attribution Requirement
    • NCL-2: Restricted Commercialization
    • NCL-4: Commercialization with Agreement or Royalties
    • NCL-8: Educational Use Permission
    • NCL-16: Complementary Use and Integration Permission
    • NCL-32: Pre-Approval for Application Publication
    • NCL-64: Restricted or Authorized Derivatives
    • NCL-128: Contribution Terms
  1. NCL - Norsh Commons License

NCL-32: Pre-Approval for Application Publication

NCL-32: Pre-Approval for Application Publication#

Permission is granted to develop applications or integrations based on the material licensed under NCL-16, with the condition that any resulting applications must be pre-approved by the platform owner prior to publication or distribution.

1. Scope#

This rule applies to:
Applications, plugins, or integrations developed under the permissions granted by NCL-16.
Any software or functionality that interacts with or enhances the original material.
The publication or distribution of such applications requires explicit approval from the platform owner, similar to the approval processes of app stores like Google Play and Apple App Store.

2. No Additional Restrictions#

No additional restrictions may be imposed on the application development process beyond those defined in this rule, unless specified by other NCL rules included in the license composition.

3. Transparency in Derivatives#

Applications or integrations developed under this rule must:
Clearly document the use of the original material.
Include evidence of approval from the platform owner for any public release or distribution.

4. Disclaimer#

This rule does not guarantee that approval will be granted for all applications or integrations. The decision to approve remains at the sole discretion of the platform owner and must comply with the terms of NCL-0 and NCL-16.
Note: NCL-32 must always be combined with NCL-0 and NCL-16 and may coexist with other rules in the NCL framework to define broader or narrower permissions.
Modified at 2025-01-13 14:16:01
Previous
NCL-16: Complementary Use and Integration Permission
Next
NCL-64: Restricted or Authorized Derivatives
Built with