DEVELOPMENT VERSION: This is an experimental DALICC environment. Features, data and APIs may change or be reset without notice. A stable version of this service, with a potentially different feature set, will be made available soon at dalicc.net.

2026

Dependency Graph Viewer

Licenses do not conflict because two words differ; they conflict because the actions behind those words relate to each other. The DALICC reasoner reads that relationship from a dependency graph: 46 statements over the ODRL, Creative Commons and DALICC action vocabularies. That is what turns "this license permits odrl:sell" and "that license prohibits odrl:commercialize" into a reported conflict.

How reasoning works walks through what the reasoner does with these statements, step by step. To keep a graph of your own, with the statements you decide, use the Dependency Graph Editor.

The source of truth of this graph is the difference file licensedata/dependencygraph/differences/dg_us.ttl in the DALICC repository, which holds what it adds to, removes from and replaces in the core graph; the graph shown here is built from it and the core graph.

Graphs you can reason with

Core graph

Jurisdiction graphs (the core graph plus local default rules)

The core graph is curated by the project, and it is what everybody reasons with. Each jurisdiction graph is complete: it is the core graph with the default rules proposed for one market, and says what it removes or replaces when it does. While you are signed in, your own graphs and the ones shared with you appear here too, drafts included. Any of them can be chosen in the License Composer and the License Compatibility Checker straight away; compare two of them or manage your graphs.

Download as Turtle The same data as JSON Compare with the core graph The DALICC vocabulary Report an issue

United States default rules

Named graph https://dalicc.net/dependencygraph/dg_us.

This graph is the core graph (version 2) plus 2 default rules. It is complete: the reasoner reads this graph alone and follows no link to another one.

What this graph adds 2

The default rules this graph adds to the core graph: what applies to an action a license is silent about, where, and on the strength of which source, with a plain explanation of each. The status says whether the library has adopted the rule or only proposes it for review. Nothing stated here is legal advice.

Status
dalicc:reverseEngineerForInteroperability Reverse engineer for interoperability Granted by default United States 17 U.S.C. 1201(f), and Sega v. Accolade 977 F.2d 1510 (9th Cir. 1992) and Sony Computer Entertainment v. Connectix 203 F.3d 596 (9th Cir. 2000), under which intermediate copying to reach the unprotected elements needed for interoperability is fair use. Bowers v. Baystate Technologies 320 F.3d 1317 (Fed. Cir. 2003) enforced a contract term against reverse engineering, so the rule is not marked unwaivable Proposed
A licence that says nothing about reverse engineering for interoperability is read as allowing it. United States law exempts reverse engineering for interoperability from the anti-circumvention rules, and the Ninth Circuit has held the intermediate copying it needs to be fair use (Sega v Accolade; Sony v Connectix); other courts have enforced a contract term against reverse engineering (Bowers v Baystate), so no finding is reported when a licence forbids it. Combining a licence that is silent about it with one that prohibits it shows a conflict marked as coming from this rule.
dalicc:sellCopy Sell copy Granted by default United States 17 U.S.C. 109(a): the owner of a lawfully made copy may sell or otherwise dispose of that copy without the authority of the copyright owner. Vernor v. Autodesk 621 F.3d 1102 (9th Cir. 2010): a person who receives a copy under a licence that reserves title and restricts transfer is a licensee, not an owner. Capitol Records v. ReDigi 910 F.3d 649 (2d Cir. 2018): the doctrine does not cover the resale of a digital file that requires a new copy to be made Proposed
A licence that says nothing about reselling a copy is read as allowing the owner of a lawfully made copy to sell that copy on. The first-sale doctrine of section 109(a) of the Copyright Act protects the owner of a copy, not a licensee: where a licence reserves title and restricts transfer, courts may find no sale took place (Vernor v Autodesk), and it does not cover resale of a digital file that requires a new copy to be made (Capitol Records v ReDigi). Combining a licence that is silent about it with one that prohibits it shows a conflict marked as coming from this rule.

46 axioms, the same as the core graph
  • odrl:includedIn
  • odrl:implies
  • owl:sameAs
  • dalicc:contradicts

odrl:includedIn 24

Action subsumption, and therefore hierarchical: exercising the subject action is one way of exercising the object action, so a rule that holds for the broader action also holds for the narrower one.
cc:Attribution Attribution odrl:includedIn odrl:use Use
cc:DerivativeWorks Derivative works odrl:includedIn odrl:distribute Distribute
cc:Notice Notice odrl:includedIn odrl:use Use
cc:ShareAlike Share alike odrl:includedIn odrl:use Use
cc:SourceCode Source code odrl:includedIn odrl:use Use
dalicc:chargeLicenseFee Charge license fee odrl:includedIn odrl:transfer Transfer
dalicc:modificationNotice Modification notice odrl:includedIn odrl:AttachPolicy Attach policy
dalicc:ModifiedWorks Modified works odrl:includedIn odrl:distribute Distribute
dalicc:sellCopy Sell copy odrl:includedIn odrl:sell Sell
odrl:copy Copy odrl:includedIn odrl:use Use
odrl:derive Derive odrl:includedIn odrl:use Use
odrl:display Display odrl:includedIn odrl:present Present
odrl:display Display odrl:includedIn odrl:use Use
odrl:distribute Distribute odrl:includedIn odrl:use Use
odrl:ensureExclusivity Ensure exclusivity odrl:includedIn odrl:use Use
odrl:execute Execute odrl:includedIn odrl:use Use
odrl:extract Extract odrl:includedIn odrl:reproduce Reproduce
odrl:extract Extract odrl:includedIn odrl:use Use
odrl:modify Modify odrl:includedIn odrl:use Use
odrl:present Present odrl:includedIn odrl:use Use
odrl:print Print odrl:includedIn odrl:present Present
odrl:print Print odrl:includedIn odrl:use Use
odrl:sell Sell odrl:includedIn odrl:commercialize Commercialize
odrl:sell Sell odrl:includedIn odrl:transfer Transfer

odrl:implies 7

Entailment: permitting the subject action necessarily permits the object action too, so a prohibition of the implied action conflicts with a permission of the implying one.
cc:Attribution Attribution odrl:implies cc:Notice Notice
cc:ShareAlike Share alike odrl:implies cc:SourceCode Source code
dalicc:chargeLicenseFee Charge license fee odrl:implies odrl:commercialize Commercialize
dalicc:chargeLicenseFee Charge license fee odrl:implies odrl:sell Sell
odrl:derive Derive odrl:implies cc:DerivativeWorks Derivative works
odrl:extract Extract odrl:implies cc:SourceCode Source code
odrl:modify Modify odrl:implies cc:SourceCode Source code

owl:sameAs 14

Synonymy: the two actions denote the same act in different vocabularies, so every statement about one is a statement about the other, both ways.
cc:Attribution Attribution owl:sameAs odrl:attribute Attribute
cc:CommercialUse Commercial use owl:sameAs odrl:commercialize Commercialize
cc:Notice Notice owl:sameAs odrl:AttachPolicy Attach policy
cc:ShareAlike Share alike owl:sameAs odrl:shareAlike Share alike (ODRL)
cc:SourceCode Source code owl:sameAs odrl:attachSource Attach source
dalicc:sublicense Sublicense owl:sameAs odrl:grantUse Grant use
odrl:AttachPolicy Attach policy owl:sameAs cc:Notice Notice
odrl:attachSource Attach source owl:sameAs cc:SourceCode Source code
odrl:attribute Attribute owl:sameAs cc:Attribution Attribution
odrl:commercialize Commercialize owl:sameAs cc:CommercialUse Commercial use
odrl:copy Copy owl:sameAs odrl:reproduce Reproduce
odrl:grantUse Grant use owl:sameAs dalicc:sublicense Sublicense
odrl:reproduce Reproduce owl:sameAs odrl:copy Copy
odrl:shareAlike Share alike (ODRL) owl:sameAs cc:ShareAlike Share alike

dalicc:contradicts 1

Mutual exclusion: the two actions cannot both be exercised under one policy, so a permission of one conflicts with a permission of the other.
odrl:ensureExclusivity Ensure exclusivity dalicc:contradicts odrl:commercialize Commercialize

Default rules from the core graph 1

An axiom above relates two actions. A default rule says what applies to an action a license is silent about, in which territory it holds, and which statute or principle it rests on. A rule marked Adopted takes part in every check that runs under this graph; one marked Proposed is written down for review and reaches only a reader who chose this graph. Nothing stated here is legal advice: what a license means is decided by its text, and what the law of a country requires is decided by that country's courts.

Status
dalicc:promote Promote Not granted by default Worldwide Trademark and name rights are separate from copyright: Regulation (EU) 2017/1001 article 9 lets the proprietor of an EU trade mark prevent all third parties not having his consent from using the sign in the course of trade, and Directive (EU) 2015/2436 article 10, 15 U.S.C. 1114 and 1125(a), section 12 BGB and section 43 ABGB protect marks and names in the same way. The library's evidence is Creative Commons 4.0 section 2(b)(2): Patent and trademark rights are not licensed under this Public License. A copyright licence that is silent grants no right to use the licensor's name or marks to suggest endorsement Adopted
A licence that says nothing about endorsement is read as not allowing it: the licence gives the licensee no right to use the licensor's name or marks in a way that states or implies that the licensor endorses the licensee or its product, while stating truthfully that a work is based on or uses the licensed work is a different act that this rule does not decide. A copyright licence grants rights in the work, and the right to use a name or a trademark is a separate right under trademark law and the protection of names, which a silent copyright licence does not pass on. Combining a licence that is silent about endorsement with one that permits it shows a conflict marked as coming from this rule.

The same list as JSON: /dependencygraph/rules?graph=dg_us.

History

The dependency graph has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.

  1. Version 2 current2026-09-24 Giray Havur

    The title no longer says proposal, and the graph is complete: it holds the 46 axioms and the adopted endorsement rule of the core graph beside its own rules, is generated from the core graph and its difference file, and every rule explains itself in plain words, checked against the statute it cites. Follows core graph version 2.

    View Turtle

    56 changes

    • changed dct:title "United States default rules"

      was dct:title "United States default rules (proposal)"

      dependency-graph-review A title that says proposal reads as if the graph itself were not published, and it is: every reader can choose it. What is proposed is each rule, and each rule says so with dalicc:ruleStatus dalicc:Proposed, which the pages show next to it. The rules are unchanged.

    • changed dct:description: This graph extends the DALICC deontic dependency graph with default rules for what a licence does not say, under the law of the United States: reverse engineering for interoperability and the first-sale doctrine. There is no general moral-rights rule and no mining rule, because the first reaches only works of visual art and the second is fair use decided case by case. Each rule names its legal basis. The rules are proposals until the association's legal reviewer adopts them. Nothing in this graph is legal advice.

      was dct:description: The core graph plus the default rules proposed for the United States: reverse engineering for interoperability and the first-sale doctrine. There is no general moral-rights rule and no mining rule, because the first reaches only works of visual art and the second is fair use decided case by case. Every rule is a proposal for the association's legal reviewer. Nothing in it is legal advice.

      dependency-graph-review The description says in plain sentences what the graph is: it extends the core graph with default rules for what a licence does not say, each rule names its legal basis, the rules are proposals until the association's legal reviewer adopts them, and nothing in the graph is legal advice.

    • added cc:Attribution odrl:implies cc:Notice

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:Attribution odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:Attribution owl:sameAs odrl:attribute

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:CommercialUse owl:sameAs odrl:commercialize

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:DerivativeWorks odrl:includedIn odrl:distribute

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:Notice odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:Notice owl:sameAs odrl:AttachPolicy

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:ShareAlike odrl:implies cc:SourceCode

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:ShareAlike odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:ShareAlike owl:sameAs odrl:shareAlike

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:SourceCode odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added cc:SourceCode owl:sameAs odrl:attachSource

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:chargeLicenseFee odrl:implies odrl:commercialize

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:chargeLicenseFee odrl:implies odrl:sell

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:chargeLicenseFee odrl:includedIn odrl:transfer

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:modificationNotice odrl:includedIn odrl:AttachPolicy

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:ModifiedWorks odrl:includedIn odrl:distribute

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:sellCopy odrl:includedIn odrl:sell

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added dalicc:sublicense owl:sameAs odrl:grantUse

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:AttachPolicy owl:sameAs cc:Notice

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:attachSource owl:sameAs cc:SourceCode

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:attribute owl:sameAs cc:Attribution

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:commercialize owl:sameAs cc:CommercialUse

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:copy odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:copy owl:sameAs odrl:reproduce

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:derive odrl:implies cc:DerivativeWorks

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:derive odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:display odrl:includedIn odrl:present

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:display odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:distribute odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:ensureExclusivity dalicc:contradicts odrl:commercialize

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:ensureExclusivity odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:execute odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:extract odrl:implies cc:SourceCode

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:extract odrl:includedIn odrl:reproduce

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:extract odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:grantUse owl:sameAs dalicc:sublicense

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:modify odrl:implies cc:SourceCode

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:modify odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:present odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:print odrl:includedIn odrl:present

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:print odrl:includedIn odrl:use

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:reproduce owl:sameAs odrl:copy

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:sell odrl:includedIn odrl:commercialize

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:sell odrl:includedIn odrl:transfer

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added odrl:shareAlike owl:sameAs cc:ShareAlike

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • added rule dalicc:promote dalicc:NotGrantedByDefault in dalicc:worldwide

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • changed rule dalicc:sellCopy dalicc:GrantedByDefault in dalicc:US

      was rule dalicc:sellCopy dalicc:GrantedByDefault in dalicc:US

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • changed rule dalicc:reverseEngineerForInteroperability dalicc:GrantedByDefault in dalicc:US

      was rule dalicc:reverseEngineerForInteroperability dalicc:GrantedByDefault in dalicc:US

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • changed dct:description The DALICC deontic dependency graph with default rules for what a licence does not say, under the law of the United States: reverse engineering for interoperability and the first-sale doctrine. There is no general moral-rights rule and no mining rule, because the first reaches only works of visual art and the second is fair use decided case by case. The graph is complete: it holds the axioms and the adopted rule of the core graph beside its own rules, and it is built from the core graph and a difference file. Each rule names its legal basis and says in plain words what it does. The rules are proposals until the association's legal reviewer adopts them. Nothing in this graph is legal advice.

      was dct:description This graph extends the DALICC deontic dependency graph with default rules for what a licence does not say, under the law of the United States: reverse engineering for interoperability and the first-sale doctrine. There is no general moral-rights rule and no mining rule, because the first reaches only works of visual art and the second is fair use decided case by case. Each rule names its legal basis. The rules are proposals until the association's legal reviewer adopts them. Nothing in this graph is legal advice.

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • changed dalicc:basedOnVersion 2

      was dalicc:basedOnVersion

      build_dependency_graphs Every published graph is now complete, a jurisdiction can remove a core axiom or replace a core rule, and every rule explains itself in plain words. licensedata/dependencygraph/differences/dg_us.ttl is now the source of truth and scripts/build_dependency_graphs.py writes this graph from it and the core graph; the rules keep their outcomes, territories and bases.

    • changed rule dalicc:promote dalicc:NotGrantedByDefault in dalicc:worldwide

      was rule dalicc:promote dalicc:NotGrantedByDefault in dalicc:worldwide

      build_dependency_graphs The explanations of the rules were reviewed against the statutes they cite; two were corrected: reverse engineering names the Ninth Circuit as the court that held the intermediate copying fair use (Sega v. Accolade; Sony v. Connectix) and Bowers v. Baystate as the reason no finding is reported; and first sale says that 17 U.S.C. 109(a) protects the owner of a copy, not a licensee (Vernor v. Autodesk), and does not cover the resale of a digital file (Capitol Records v. ReDigi). The adopted endorsement rule of the core graph cites its basis, says that only a use suggesting endorsement is refused, and names who adopted it. Follows core graph version 3.

    • changed rule dalicc:sellCopy dalicc:GrantedByDefault in dalicc:US

      was rule dalicc:sellCopy dalicc:GrantedByDefault in dalicc:US

      build_dependency_graphs The explanations of the rules were reviewed against the statutes they cite; two were corrected: reverse engineering names the Ninth Circuit as the court that held the intermediate copying fair use (Sega v. Accolade; Sony v. Connectix) and Bowers v. Baystate as the reason no finding is reported; and first sale says that 17 U.S.C. 109(a) protects the owner of a copy, not a licensee (Vernor v. Autodesk), and does not cover the resale of a digital file (Capitol Records v. ReDigi). The adopted endorsement rule of the core graph cites its basis, says that only a use suggesting endorsement is refused, and names who adopted it. Follows core graph version 3.

    • changed rule dalicc:reverseEngineerForInteroperability dalicc:GrantedByDefault in dalicc:US

      was rule dalicc:reverseEngineerForInteroperability dalicc:GrantedByDefault in dalicc:US

      build_dependency_graphs The explanations of the rules were reviewed against the statutes they cite; two were corrected: reverse engineering names the Ninth Circuit as the court that held the intermediate copying fair use (Sega v. Accolade; Sony v. Connectix) and Bowers v. Baystate as the reason no finding is reported; and first sale says that 17 U.S.C. 109(a) protects the owner of a copy, not a licensee (Vernor v. Autodesk), and does not cover the resale of a digital file (Capitol Records v. ReDigi). The adopted endorsement rule of the core graph cites its basis, says that only a use suggesting endorsement is refused, and names who adopted it. Follows core graph version 3.

  2. Version 1

    The version this model had before the content review of 2026-09-15.

    View Turtle

Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.