diff --git a/src/main/resources/org/springframework/data/gemfire/config/spring-gemfire-1.0.xsd b/src/main/resources/org/springframework/data/gemfire/config/spring-gemfire-1.0.xsd
index 4ccc5ec5..0fe0b7bc 100644
--- a/src/main/resources/org/springframework/data/gemfire/config/spring-gemfire-1.0.xsd
+++ b/src/main/resources/org/springframework/data/gemfire/config/spring-gemfire-1.0.xsd
@@ -222,6 +222,62 @@ redundancy. Each copy provides extra backup at the expense of extra storages.
 							</xsd:restriction>
 						</xsd:simpleType>
 					</xsd:attribute>
+					<xsd:attribute name="colocated-with" type="xsd:string" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The name of the partitioned region with which this newly created partitioned region is colocated.
+							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					<xsd:attribute name="local-max-memory" type="xsd:positiveInteger" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The maximum amount of memory, in megabytes, to be used by the region in this process. If not set, a default of 90%
+of available heap is used.
+							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					<xsd:attribute name="recovery-delay" type="xsd:long" default="-1" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The delay in milliseconds that existing members will wait before satisfying redundancy after another member crashes.
+-1 (the default) indicates that redundancy will not be recovered after a failure.
+							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					<xsd:attribute name="startup-recovery-delay" type="xsd:long" default="-1" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The delay in milliseconds that new members will wait before satisfying redundancy. -1 indicates that adding new members
+ will not trigger redundancy recovery. The default is to recover redundancy immediately when a new member is added.
+ 							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					<xsd:attribute name="total-max-memory" type="xsd:positiveInteger" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The maximum amount of memory, in megabytes, to be used by the region in all process.
+
+Note: This setting must be the same in all processes using the region.
+							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					<xsd:attribute name="total-buckets" type="xsd:positiveInteger" use="optional">
+						<xsd:annotation>
+							<xsd:documentation><![CDATA[
+The total number of hash buckets to be used by the region in all processes. 
+
+A bucket is the smallest unit of data management in a partitioned region. Entries are stored in buckets and buckets may
+ move from one VM to another. Buckets may also have copies, depending on redundancy to provide high availability in the
+  face of VM failure.
+The number of buckets should be prime and as a rough guide at the least four times the number of partition VMs. However
+, there is significant overhead to managing a bucket, particularly for higher values of redundancy.
+ 
+Note: This setting must be the same in all processes using the region.
+							]]></xsd:documentation>
+						</xsd:annotation>
+					</xsd:attribute>
+					
 				</xsd:extension>
 			</xsd:complexContent>
 		</xsd:complexType>