933
933
All three keywords share the same algorithm for resolving variables from
934
934
instance data, which makes use of the "templatePointers" and "templateRequired"
935
935
keywords. When resolving "href", both it and any "base" templates
936
- needed for resolution to an absolute URI, the algorithm is modfied to
936
+ needed for resolution to an absolute URI, the algorithm is modified to
937
937
optionally accept user input based on the "hrefSchema" keyword.
938
938
</t >
939
939
<t >
973
973
<preamble >
974
974
This is the high-level algorithm as pseudocode. "T" comes from either
975
975
"href" or "anchor" within the LDO, or from "base" in a containing schema.
976
- Pseudocode for each step follows. "anchorOrHref " indicates which of the
977
- two started the process (since "base" is always resolved in order to finish
978
- resolving one or the other of those keywords).
976
+ Pseudocode for each step follows. "initialTemplateKeyword " indicates
977
+ which of the two started the process (since "base" is always resolved
978
+ in order to finish resolving one or the other of those keywords).
979
979
</preamble >
980
980
<artwork >
981
981
<![CDATA[
982
982
templateData = populateDataFromInstance(T, ldo, instance)
983
983
984
- if anchorOrHref == "href" and ldo.hrefSchema exists:
984
+ if initialTemplateKeyword == "href" and ldo.hrefSchema exists:
985
985
inputData = acceptInput(ldo, instance, templateData)
986
986
for varname in inputData:
987
987
templateData[varname] = inputData[varname]
@@ -1006,7 +1006,7 @@ R = rfc6570ResolutionAlgorithm(T, templateData)
1006
1006
appears in that keyword's value
1007
1007
</t >
1008
1008
<t >
1009
- Otherwise, look for a property names matching the variable in
1009
+ Otherwise, look for a property name matching the variable in
1010
1010
the instance location to which the link is attached
1011
1011
</t >
1012
1012
<t >
@@ -1062,7 +1062,7 @@ for varname in T:
1062
1062
<preamble >
1063
1063
"InputForm" represents whatevers sort of input mechanism is appropriate.
1064
1064
This may be a literal web form, or may be a more programmatic construct
1065
- such as a callback funciton accepting specific fields and data types,
1065
+ such as a callback function accepting specific fields and data types,
1066
1066
with the given initial values, if any.
1067
1067
</preamble >
1068
1068
<artwork >
0 commit comments