From af626918c7424576cbe6311d7e1e0303afe2a5da Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 6 Jun 2008 23:13:08 +0000 Subject: [PATCH] there is no MAY NOT git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1927 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0141.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0141.xml b/xep-0141.xml index f963ef42..84946e98 100644 --- a/xep-0141.xml +++ b/xep-0141.xml @@ -283,7 +283,7 @@

In order to prevent the processing from becoming too complex, there are some restrictions in how fields are distributed within the layout.

-

First, all displayable, modifiable fields (e.g. all except fields of type "FIXED" or "HIDDEN") SHOULD be referenced by a page or section. Any that are not referenced MAY NOT be rendered, although implementations MAY provide some support for this. To include a "FIXED" field in the layout, it MUST possess a "var" attribute.

+

First, all displayable, modifiable fields (e.g. all except fields of type "FIXED" or "HIDDEN") SHOULD be referenced by a page or section. Any that are not referenced MAY remain unrendered, although implementations MAY provide some support for this. To include a "FIXED" field in the layout, it MUST possess a "var" attribute.

Second, the same field SHOULD NOT be referenced by more than one page or section. Additionally, a field SHOULD NOT be referenced by the same page or section more than once.

Finally, the order of layout elements SHOULD be maintained. Pages SHOULD be rendered in the order they are defined within the x:data form, and sections and fields SHOULD be rendered in the order they are defined or referenced within a page or section.