Template:Generic Pattern Adjacent Service Row: Difference between revisions

From OIAr
Jump to navigation Jump to search
(added relation for adjacent services)
(motivation rewording)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
<includeonly>
<includeonly>
|{{FriendlyPageLink|{{{service|}}}}}
|{{FriendlyPageLink|{{{service|}}}}}
|[[{{{choice|Must}}} have adjacent service::{{{service|}}}]]{{#switch: {{{choice|Must}}}||Must=mandatory|May=optional|undefihned}}
|{{#switch: {{{choice|Must}}}
|MAY
|May
|may=optional[[May have adjacent service::{{{service|}}}|]]
|#default=recommended[[Must have adjacent service::{{{service|}}}|]]}}
|{{#show: {{{service|}}} | ?Brief description}}
|{{{reason|not specified}}}
|{{{reason|not specified}}}
|-</includeonly><noinclude>
|-</includeonly><noinclude>

Latest revision as of 07:52, 15 August 2013

Template documentation

This template creates a single row in a table listing all Adjacent Services for a Generic Pattern. It takes the following, mandatory, named parameters:

  • service: must be the name of a page representing the adjacent Generic Service;
  • choice: the architect can specify if the adjacency of the Pattern Type is mandatory or optional, by using either the word "Must" or "May". If left empty, "Must" is assumed!
  • reason: here the architect will usually insert an explanatory text, describing the rationale for adjacency.

To use this template, cut and paste the following text:

{{Generic Pattern Adjacent Service Row
|service=
|choice=
|reason=
}}