@@ -1401,7 +1401,7 @@ GET /foo/
14011401 All three keywords share the same algorithm for resolving variables from
14021402 instance data, which makes use of the "templatePointers" and "templateRequired"
14031403 keywords. When resolving "href", both it and any "base" templates
1404- needed for resolution to an absolute URI, the algorithm is modfied to
1404+ needed for resolution to an absolute URI, the algorithm is modified to
14051405 optionally accept user input based on the "hrefSchema" keyword.
14061406 </t >
14071407 <t >
@@ -1441,15 +1441,15 @@ GET /foo/
14411441 <preamble >
14421442 This is the high-level algorithm as pseudocode. "T" comes from either
14431443 "href" or "anchor" within the LDO, or from "base" in a containing schema.
1444- Pseudocode for each step follows. "anchorOrHref " indicates which of the
1445- two started the process (since "base" is always resolved in order to finish
1446- resolving one or the other of those keywords).
1444+ Pseudocode for each step follows. "initialTemplateKeyword " indicates
1445+ which of the two started the process (since "base" is always resolved
1446+ in order to finish resolving one or the other of those keywords).
14471447 </preamble >
14481448 <artwork >
14491449<![CDATA[
14501450templateData = populateDataFromInstance(T, ldo, instance)
14511451
1452- if anchorOrHref == "href" and ldo.hrefSchema exists:
1452+ if initialTemplateKeyword == "href" and ldo.hrefSchema exists:
14531453 inputData = acceptInput(ldo, instance, templateData)
14541454 for varname in inputData:
14551455 templateData[varname] = inputData[varname]
@@ -1474,7 +1474,7 @@ R = rfc6570ResolutionAlgorithm(T, templateData)
14741474 appears in that keyword's value
14751475 </t >
14761476 <t >
1477- Otherwise, look for a property names matching the variable in
1477+ Otherwise, look for a property name matching the variable in
14781478 the instance location to which the link is attached
14791479 </t >
14801480 <t >
@@ -1530,7 +1530,7 @@ for varname in T:
15301530 <preamble >
15311531 "InputForm" represents whatevers sort of input mechanism is appropriate.
15321532 This may be a literal web form, or may be a more programmatic construct
1533- such as a callback funciton accepting specific fields and data types,
1533+ such as a callback function accepting specific fields and data types,
15341534 with the given initial values, if any.
15351535 </preamble >
15361536 <artwork >
0 commit comments