Lines Matching full:properties

35 properties:
36   # A dictionary of DT properties for this binding schema
100       properties are not necessary.
136   # Vendor-specific properties
138   # Vendor-specific properties have slightly different schema requirements than
139   # common properties. They must have at least a type definition and
142     description: Vendor-specific properties must have a description
147     description: Vendor-specific properties must have a description. Boolean
148       properties are one case where the json-schema 'type' keyword can be used
153     description: Vendor-specific properties should reference a type in the
161     description: Vendor-specific properties having a standard unit suffix
179     properties:
181         description: Child node properties have all the same schema
188 # Describe the relationship between different properties
193   # Expressing 2 properties in both orders means all of the set of properties
205 # constraints on other properties.
213       properties:
222       properties:
224   # Altering schema depending on presence of properties is usually done by
230       properties:
234 # Ideally, the schema should have this line otherwise any other properties
235 # present are allowed. There's a few common properties such as 'status' and