From 3cd0fbd02663912edfd5194f01b48a840f9d0a27 Mon Sep 17 00:00:00 2001 From: Adam Moore Date: Fri, 5 Aug 2016 09:22:15 -0700 Subject: [PATCH] resourcePath and resourcePathName are in the wrong order. It says "sets the value of resourcePathName and resourcePath parameters to "/bom/{itemId}" and "bom", respectively." Those should actually be reversed. --- versions/raml-10/raml-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/raml-10/raml-10.md b/versions/raml-10/raml-10.md index 30d22643..8cb7282b 100644 --- a/versions/raml-10/raml-10.md +++ b/versions/raml-10/raml-10.md @@ -2269,7 +2269,7 @@ A processing application MUST set the value of `<>` to the concate For example, applying a resource type or trait to a resource /users nested in a resource /{groupId} nested in a root-level resource /groups sets the value of the resourcePath parameter to ""/groups/{groupId}/users". Applying a resource type or trait to a resource /jobs/{jobId} sets the value of the resourcePathName parameter to "jobs". -When setting resourcePath and resourcePathName, processing applications MUST also omit any ext parameter and its parametrizing brackets ("{" and "}") found in the resource URI. For example, applying a resource type or trait to a root-level resource /bom/{itemId}{ext} sets the value of resourcePathName and resourcePath parameters to "/bom/{itemId}" and "bom", respectively. +When setting resourcePath and resourcePathName, processing applications MUST also omit any ext parameter and its parametrizing brackets ("{" and "}") found in the resource URI. For example, applying a resource type or trait to a root-level resource /bom/{itemId}{ext} sets the value of resourcePath and resourcePathName parameters to "/bom/{itemId}" and "bom", respectively. In trait declarations, **methodName** is a reserved parameter.