summaryrefslogtreecommitdiff
path: root/gfx/include/gfx/scene/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'gfx/include/gfx/scene/README.md')
-rw-r--r--gfx/include/gfx/scene/README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/gfx/include/gfx/scene/README.md b/gfx/include/gfx/scene/README.md
index 916596b..1910abe 100644
--- a/gfx/include/gfx/scene/README.md
+++ b/gfx/include/gfx/scene/README.md
@@ -21,7 +21,7 @@ former, the API could create the illusion that the hierarchy can be a DAG.
21The strict tree hierarchy should not be that restrictive in practice. Even the 21The strict tree hierarchy should not be that restrictive in practice. Even the
22glTF 2.0 spec [enforces this](https://github.com/KhronosGroup/glTF/blob/master/specification/2.0/README.md#nodes-and-hierarchy): 22glTF 2.0 spec [enforces this](https://github.com/KhronosGroup/glTF/blob/master/specification/2.0/README.md#nodes-and-hierarchy):
23 23
24*For Version 2.0 conformance, the glTF node hierarchy is not a directed acyclic 24> *For Version 2.0 conformance, the glTF node hierarchy is not a directed
25graph (DAG) or scene graph, but a disjoint union of strict trees. That is, no 25> acyclic graph (DAG) or scene graph, but a disjoint union of strict trees. That
26node may be a direct descendant of more than one node. This restriction is meant 26> is, no node may be a direct descendant of more than one node. This restriction
27to simplify implementation and facilitate conformance.* 27> is meant to simplify implementation and facilitate conformance.*