Lines Matching full:properties
35 properties:
36 # A dictionary of DT properties for this binding schema
101 properties are not necessary.
138 # Vendor specific properties
140 # Vendor specific properties have slightly different schema requirements than
141 # common properties. They must have at least a type definition and
144 description: Vendor specific properties must have a description
149 description: Vendor specific properties must have a description. Boolean
150 properties are one case where the json-schema 'type' keyword can be used
155 description: Vendor specific properties should reference a type in the
163 description: Vendor specific properties having a standard unit suffix
171 properties:
173 description: Child node properties have all the same schema
180 # Describe the relationship between different properties
185 # Expressing 2 properties in both orders means all of the set of properties
197 # constraints on other properties.
205 properties:
212 # Altering schema depending on presence of properties is usually done by
218 properties:
222 # Ideally, the schema should have this line otherwise any other properties
223 # present are allowed. There's a few common properties such as 'status' and