-... Rules for ordering Keywords within this Resource:
-... 1. User friendlier Keywords first.
-... 2. Get, Put, Post, Delete, Verify.
-... 3. Within class of equally usable, use order in which a suite would call them.
-... 4. Higher-level Keywords first.
-... 5. Json before Xml.
-... Motivation: Users read from the start, so it is important
-... to offer them the better-to-use Keywords first.
-... https://wiki.opendaylight.org/view/Integration/Test/Test_Code_Guidelines#Keyword_ordering
-... In this case, templates are nicer that raw data,
-... *_As_* keywords are better than messing wth explicit header dicts,
-... Json is less prone to element ordering issues.
-... PUT does not fail on existing element, also it does not allow
-... shortened URIs (container instead keyed list element) as Post does.
+... Rules for ordering Keywords within this Resource:
+... 1. User friendlier Keywords first.
+... 2. Get, Put, Post, Delete, Verify.
+... 3. Within class of equally usable, use order in which a suite would call them.
+... 4. Higher-level Keywords first.
+... 5. Json before Xml.
+... Motivation: Users read from the start, so it is important
+... to offer them the better-to-use Keywords first.
+... https://wiki.opendaylight.org/view/Integration/Test/Test_Code_Guidelines#Keyword_ordering
+... In this case, templates are nicer that raw data,
+... *_As_* keywords are better than messing wth explicit header dicts,
+... Json is less prone to element ordering issues.
+... PUT does not fail on existing element, also it does not allow
+... shortened URIs (container instead keyed list element) as Post does.