diff --git a/reference/XML_Definition.adoc b/reference/XML_Definition.adoc
index b70998c358..6cb0dff78d 100644
--- a/reference/XML_Definition.adoc
+++ b/reference/XML_Definition.adoc
@@ -24,6 +24,7 @@ For example, if a VDB defines a table "TableA" in schema "modelName" with column
 
         <permission>
             <resource-name>modelName.TableA</resource-name>
+            <resource-type>TABLE</resource-type>
             <allow-create>true</allow-create>
             <allow-read>true</allow-read>
             <allow-update>true</allow-update>
@@ -38,11 +39,13 @@ For example, if a VDB defines a table "TableA" in schema "modelName" with column
 
         <permission>
             <resource-name>modelName.TableA</resource-name>
+            <resource-type>TABLE</resource-type>
             <allow-read>true</allow-read>
         </permission>
 
         <permission>
             <resource-name>modelName.TableA.colum2</resource-name>
+            <resource-type>COLUMN</resource-type>
             <allow-read>false</allow-read>
         </permission>
 
@@ -63,6 +66,8 @@ The "mapped-role-name" defines the container JAAS roles that are assigned the da
 
 Using the grant-all option provides every permission on over object in the vdb.  When importing a vdb and its roles, grant-all applies only to resources from the imported vdb. 
 
+NOTE: The optional resource-type element currently accepts LANGUAGE, SCHEMA, DATABASE, PROCEDURE, FUNCTION, TABLE, COLUMN.  This property ensures that migration issues will be prevented when switching to DDL vdbs or dealing with multi-part table names.  
+
 *Additional Role Attributes*
 
 You may also choose to allow any authenticated user to have a data role by setting the any-authenticated attribute value to true on data-role element.
diff --git a/reference/vdb_properties.adoc b/reference/vdb_properties.adoc
index ef56092fd4..b830d8af7c 100644
--- a/reference/vdb_properties.adoc
+++ b/reference/vdb_properties.adoc
@@ -2,6 +2,10 @@
 
 == Properties DATABASE Level
 
+* _domain-ddl_
+
+* _schema-ddl_
+
 * _cache-metadata_
 
 Can be "true" or "false". defaults to "false" for -vdb.xml deployments otherwise "true". If "false", Teiid will obtain metadata once for every launch of the vdb. "true" will save a file containing the metadata into the PROFILE/data/teiid directory
@@ -29,7 +33,6 @@ NOTE: An admin needs to configure a matching "custom-security" login module in s
 
 For use by the ODBC transport and OData to set default connection/execution properties. See link:../client-dev/Driver_Connection.adoc[Driver Connection] for all properties. Note these are set on the connection after it has been established.
 
-
 [source,xml]
 ----
    <property name="connection.partialResultsMode" value="true" />