Take the 2-minute tour ×
English Language & Usage Stack Exchange is a question and answer site for linguists, etymologists, and serious English language enthusiasts. It's 100% free, no registration required.

I'm writing documentation for some code at work and I am trying to describe some parameters that must be specified by the user. Some of the parameters are specified with one word from a list of possible choices (e.g., "true" or "false"; "ags" or "wms"; "json", "xml", or "text"). Others are more "open-ended" and the user specifies anything they'd like (parameters like this include name, identifier, URL, etc).

I'd like to describe each of these two types of parameters. Are there words that describe one as open-ended and one as multiple choice? These descriptions I'm using don't seem to do it justice. They also seem to imply there is some kind of question involved when there isn't.

Does anyone have any ideas of what words I could use in my documentation to describe these two types of parameters?

share|improve this question
add comment

3 Answers

up vote 4 down vote accepted

For the "multiple-choice", you could use "enumerated"; however, it probably makes more sense to just list the options, using a full phrase: "either true or false", "one of: json, xml, text", etc.

For the "open-ended", you could use "free-form" or "arbitrary text"; but it's likely that there are some restrictions, in which case you can probably just describe those (e.g., "up to 128 characters", "cannot include whitespace") and leave it implied that there's not a fixed list of options.

share|improve this answer
2  
I've seen "free form input" a lot for this specific application. –  Alex Feinman Jul 16 '12 at 17:29
add comment

You could draw on the relatively familiar idioms of Web forms and describe the multiple-choice parameters as selections and the open-ended parameters as text inputs.

share|improve this answer
    
That's a good suggestion! Thanks. –  vulpix Jul 16 '12 at 17:18
add comment

When I've written code documentation I usually refer to them by their GUI widget names. Most code documentation is intended for other coders and I would assume they had a basic knowledge of the names.

Radio buttons/checkbox/drop-down for multiple choice, and text box for text.

share|improve this answer
    
Thing is, these are not GUI widgets, otherwise I would completely agree with you. These are servlet parameters. –  vulpix Jul 16 '12 at 17:51
    
Hm. How does the user input them then? –  Marcus_33 Jul 16 '12 at 18:05
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.