3.1.5 mapsĪn object describing which parameter(s) specific Consumers SHOULD use for some purpose. add, edit, or remove those parameters at once). Authors are NOT REQUIRED to reference each parameter in at least one Set object.Ī Consumer MAY encourage users to interact with parameters in a Set together (e.g. Authors MAY include a parameter in multiple Set objects. List of groups of parameters that can be used together.Īuthors MUST ensure that the sets object contains only Set objects. 3.1.3 paramOrderĪuthors MUST ensure the paramOrder array contains all parameter names exactly once.Ĭonsumers SHOULD display the parameters in this order. 3.1 Root 3.1.1 descriptionĭescribes each of the template's parameters to a User.Īuthors MUST ensure that the params object maps parameter names to Param objects. Requirements for non-Required ("optional") properties only apply if the property is present. Other properties MAY be omitted.Īuthors MUST ensure objects do not have multiple properties with the same key. Authors MUST ensure that properties and structures marked as "Required" are present. Properties not specified here MUST not be present. 3 StructuresĪuthors MUST ensure TemplateData blobs have exactly one top-most structure of key–value pairs (hereafter referred to as "objects" having "properties") that follow the specification for the "Root" structure, as specified in section 3.1 below.Īll objects share the following requirements:Īuthors MUST ensure they only have properties described in this specification. 2.5 UserĪ person using a TemplateData consumer program. 2.4 ConsumerĪ program interpreting TemplateData blobs (supplied by a TemplateData author). 2.3 AuthorĪ program that creates and modifies TemplateData blobs, and distributes them to TemplateData consumer programs. 2.2 ParameterĪ key–value pair associated with the transclusion of a template in order to alter the behaviour of a template (and by extend, the content it will return as part of the transclusion). Refer to for documentation about what templates are capable of and how to create or use them. 2 Terminology 2.1 TemplateĪ page on a MediaWiki website that can be transcluded into other pages. The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. This document specifies the structure that TemplateData blobs must follow. Forrester, Marielle Volz, Moriel Schottlender, C.Scott Ananian, eranroz, Adam Wight TemplateData Specification Living Standard
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |