Fix for issue #82 (#121)

* Fix for issue #82

Allow distributed definitions of DSDL namespaces.

* Update specification/dsdl/architecture.tex

Co-authored-by: Pavel Kirienko <[email protected]>

* adding change to the updates section

Co-authored-by: Pavel Kirienko <[email protected]>

Author: thirtytwobits

.gitignore

@@ -1,4 +1,4 @@
 *.tmp
 *.cache
 .mypy_cache
-
+.DS_Store

specification/dsdl/architecture.tex

@@ -143,10 +143,14 @@ \subsection{File hierarchy}
     \caption{Data type definition file name structure\label{fig:dsdl_definition_file_name_structure}}
 \end{figure}
 
-DSDL namespaces are represented as directories, where one directory defines exactly one namespace, possibly nested.
+DSDL namespaces are represented as directories, where one directory defines exactly one namespace\footnote{%
+    While a single directory can define only one namespace, the inverse is not prohibited; namespaces can be
+    defined as the union of the contents of multiple directories that share the same name and folder hierarchy (up to
+    the root namespace folder). The rules for how distributed definitions such as these are resolved are specific to any 
+    tools that manage them. This specification applies only to the resulting union assuming it is equivalent to a single
+    file tree.
+}, possibly nested.
 The name of the directory defines the name of its data type name component.
-A directory defining a namespace will always define said namespace in its entirety,
-meaning that the contents of a namespace cannot be spread across different directories sharing the same name.
 One directory cannot define more than one level of
 nesting\footnote{%
     For example, ``\texttt{foo.bar}'' is not a valid directory name.

specification/introduction/introduction.tex

@@ -216,6 +216,9 @@ \subsection{v1.0 -- work in progress}
 
     \item The default extent function has been removed (section \ref{sec:dsdl_composite_extent_and_sealing}).
     The extent now has to be specified explicitly always unless the data type is sealed.
+
+    \item The constraint on DSDL namespaces being defined in a single folder was removed. Namespaces can be hosted
+    across multiple repositories and code can be generated from a union of said folders.
 \end{itemize}
 
 \subsection{v1.0-beta -- Sep 2020}