Difference between revisions of "Default value attribute candidates for removal"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
This page is a list of defaultVals for consideration. | This page is a list of defaultVals for consideration. | ||
| + | ===aloud (said)=== | ||
| + | defaultVal: unknown | ||
| + | THIS HAS NO valList | ||
| + | |||
| + | ===anchored (note)=== | ||
| + | defaultVal: true | ||
| + | THIS HAS NO valList | ||
| + | |||
| + | ===autoPrefix (content)=== | ||
| + | defaultVal: true | ||
| − | + | **true : Each name referenced in e.g. a rng:ref element within a content model is automatically prefixed by the value of the prefix attribute on the current schemaSpec | |
| − | + | **false : No prefixes are added: any prefix required by the value of the prefix attribute on the current schemaSpec must therefore be supplied explicitly, as appropriate. | |
| − | |||
| − | |||
Revision as of 20:16, 3 June 2015
Ticket [1] asks for the removal of default values for attributes, since they are generally more confusing than helpful, and because most users are not aware of them, and are therefore magically asserting things that they do not know they are asserting.
This page is a list of defaultVals for consideration.
aloud (said)
defaultVal: unknown THIS HAS NO valList
anchored (note)
defaultVal: true THIS HAS NO valList
autoPrefix (content)
defaultVal: true
- true : Each name referenced in e.g. a rng:ref element within a content model is automatically prefixed by the value of the prefix attribute on the current schemaSpec
- false : No prefixes are added: any prefix required by the value of the prefix attribute on the current schemaSpec must therefore be supplied explicitly, as appropriate.
