Optional Attributes in Data Files: Difference between revisions
From HLKitWiki
Jump to navigationJump to search
New page: {{context|Kit Reference|Conventions Used in Reference Section}} Information that is defined through XML attributes and/or PCDATA blocks is always required by default. The exception is an ... |
No edit summary |
||
Line 1: | Line 1: | ||
{{context|Kit Reference | {{context|Kit Reference}} | ||
Information that is defined through XML attributes and/or PCDATA blocks is always required by default. The exception is an entry that is specifically designated as optional. If an entry is optional, it will be clearly designated as such within its description, with the text "(Optional)" appearing before the type is given. An optional attribute will always specify the default value that is used if the attribute is left blank. Optional PCDATA blocks are always treated as empty by default. | Information that is defined through XML attributes and/or PCDATA blocks is always required by default. The exception is an entry that is specifically designated as optional. If an entry is optional, it will be clearly designated as such within its description, with the text "(Optional)" appearing before the type is given. An optional attribute will always specify the default value that is used if the attribute is left blank. Optional PCDATA blocks are always treated as empty by default. |
Latest revision as of 05:10, 4 December 2008
Context: HL Kit … Kit Reference
Information that is defined through XML attributes and/or PCDATA blocks is always required by default. The exception is an entry that is specifically designated as optional. If an entry is optional, it will be clearly designated as such within its description, with the text "(Optional)" appearing before the type is given. An optional attribute will always specify the default value that is used if the attribute is left blank. Optional PCDATA blocks are always treated as empty by default.