Specs: try to import elements from module.exports as well as module.exports.*

sky/specs/modules.md

 Sky Module System
 =================
 
 This document describes the Sky module system.
 
 Overview
 --------
 
 The Sky module system is based on the ``import`` element. In its
 most basic form, you import a module as follows:
@@ skipping 24 matching lines @@
 
 A module can export a value by assigning the ``exports`` property of
 its ``Module`` object. By default, the ``exports`` property of a
 ``Module`` is an empty Object. Properties can be added to the object,
 or, it can be set to an entirely different object; for example, it
 could be set to the module's ``Document`` itself, in case the point of
 the module is to expose some ``template`` elements.
 
 ### Exporting element definitions ###
 
-When importing a module into another, Sky looks at the properties on
-the imported module's ``exports`` value, and for each property that is
-an element constructor (generated by ``registerElement()``), it adds
-an element to the importee's element registry.
+When importing a module into another, Sky runs the following steps:
+ - let export be the imported module's ``exports`` value
+ - try to import export
+ - if that fails:
+    - try to import each property of export
+
+"Try to import" a value means to run the following steps:
+ - if the value is an element constructor (generated by
+   ``registerElement()``), call this importer module's
+   ``registerElement()`` with the value
 
 ### IDL ###
 
 ```javascript
 dictionary InternalElementOptions {
   String tagName;
   Boolean shadow = false;
   Object prototype = Element;
 }
 interface InternalElementConstructorWithoutShadow {
@@ skipping 91 matching lines @@
 Where ``name_1`` through ``name_n`` are the names bound to the
 various named imports in the script element's document,
 ``source_code`` is the text content of the script element,
 ``source_module`` is the ``Module`` object of the script element's
 module, and ``value_1`` through ``value_n`` are the values
 exported by the various named imports in the script element's
 document.
 
 When an import fails to load, the ``as`` name for the import gets
 bound to ``undefined``.