Adjective for a “expected” or “aspirational” version of a document?Synonym for “final” or antonym for “draft”A word to describe “work that is ready to be done”Word for “release candidate” of draft documentBetter than expected as an adjective?Disambiguating 'dataset' in an overloaded contextNoun for “Things that can be improved/might change their state”Adjective for “something that took more resources than expected”Single Word for “Expected Disappointment”Word for “smaller version of”How to indicate that verification/correction is requested in the document
How can "mimic phobia" be cured or prevented?
Is XSS in canonical link possible?
Does a 'pending' US visa application constitute a denial?
Bob has never been a M before
Can the Supreme Court overturn an impeachment?
Can somebody explain Brexit in a few child-proof sentences?
Engineer refusing to file/disclose patents
Count the occurrence of each unique word in the file
How much character growth crosses the line into breaking the character
Can we have a perfect cadence in a minor key?
Journal losing indexing services
How do I nest cases?
Melting point of aspirin, contradicting sources
Can I use my Chinese passport to enter China after I acquired another citizenship?
Is '大勢の人' redundant?
Can someone explain how this makes sense electrically?
Open problems concerning all the finite groups
THT: What is a squared annular “ring”?
A social experiment. What is the worst that can happen?
How can I check how many times an iPhone or iPad has been charged?
Interest Rate Futures Question from Hull, 8e
Open a doc from terminal, but not by its name
Have I saved too much for retirement so far?
Is there a conventional notation or name for the slip angle?
Adjective for a “expected” or “aspirational” version of a document?
Synonym for “final” or antonym for “draft”A word to describe “work that is ready to be done”Word for “release candidate” of draft documentBetter than expected as an adjective?Disambiguating 'dataset' in an overloaded contextNoun for “Things that can be improved/might change their state”Adjective for “something that took more resources than expected”Single Word for “Expected Disappointment”Word for “smaller version of”How to indicate that verification/correction is requested in the document
We're creating a user manual for a software application. Like the manual, the application itself is a work in progress.
We have a version of the manual that describes the application as we expect it to be when completed. It could change over time, as the application is modified, but it's mostly stable.
If "draft" (or "draft version") is the term for the current, pre-publication version of user manual, and "final version" is what you'd call what is ultimately published, what's the adjective for the initial version?
"Expected version" isn't quite right, and "Aspirational" sounds pompous. "Target" might work, except that our tools use that term for something else and I don't want the confusion.
single-word-requests tech-writing
add a comment |
We're creating a user manual for a software application. Like the manual, the application itself is a work in progress.
We have a version of the manual that describes the application as we expect it to be when completed. It could change over time, as the application is modified, but it's mostly stable.
If "draft" (or "draft version") is the term for the current, pre-publication version of user manual, and "final version" is what you'd call what is ultimately published, what's the adjective for the initial version?
"Expected version" isn't quite right, and "Aspirational" sounds pompous. "Target" might work, except that our tools use that term for something else and I don't want the confusion.
single-word-requests tech-writing
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
1
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44
add a comment |
We're creating a user manual for a software application. Like the manual, the application itself is a work in progress.
We have a version of the manual that describes the application as we expect it to be when completed. It could change over time, as the application is modified, but it's mostly stable.
If "draft" (or "draft version") is the term for the current, pre-publication version of user manual, and "final version" is what you'd call what is ultimately published, what's the adjective for the initial version?
"Expected version" isn't quite right, and "Aspirational" sounds pompous. "Target" might work, except that our tools use that term for something else and I don't want the confusion.
single-word-requests tech-writing
We're creating a user manual for a software application. Like the manual, the application itself is a work in progress.
We have a version of the manual that describes the application as we expect it to be when completed. It could change over time, as the application is modified, but it's mostly stable.
If "draft" (or "draft version") is the term for the current, pre-publication version of user manual, and "final version" is what you'd call what is ultimately published, what's the adjective for the initial version?
"Expected version" isn't quite right, and "Aspirational" sounds pompous. "Target" might work, except that our tools use that term for something else and I don't want the confusion.
single-word-requests tech-writing
single-word-requests tech-writing
asked Feb 18 at 20:32
Shawn V. WilsonShawn V. Wilson
1143
1143
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
1
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44
add a comment |
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
1
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
1
1
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44
add a comment |
2 Answers
2
active
oldest
votes
Draft, working version, work in progress ('WIP') each convey the temporary nature of the document. I can't find any dictionary authority for 'working version' but it does show up in web searches with this meaning.
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
add a comment |
In software terms, it sounds like you're working on something that's out of beta and essentially complete—but still pending any last-minute changes prior to publication.
This is often described as a release candidate.
From PC Magazine's definition of release candidate:
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance of the official release. A release candidate is like a "sneak preview" of the final release with the added advantage that serious bugs may yet surface and be fixed before the general public uses it. Thus, there are alpha versions (internal), beta versions (external), release candidates (sometimes) and the final release of software. After that, there are countless updates that add features and fix bugs.
In editing terminology, a manuscript that has had its final round of technical input and copyediting is, as you've called it, a final draft:
[Merriam-Webster]
: a final version of something (such as a document) usually after a lot of editing and rewriting
// The final draft is due tomorrow.
However, what you're currently working on is something prior to that stage—and certainly prior to the even more complete stage of proof or galley proof (which, in the publishing world, is what a final drafte turns into when it's sent to a typesetter).
In general editing terms, a draft that comes before a final draft is simply a manuscript.
I know of no editing terminology that is the exact equivalent of release candidate, but that is the analogous term that you're looking for.
Note that you asked for the initial version in your question—but also said that you want something that's the expected or target version. Those two things seem incompatible to me. But if it's not actually release candidate that describes your current situation, then you could make use of either alpha or beta, depending on how you are interpreting things. Or even initial draft. But, again, you seem to be describing things at two different ends of the development cycle at the same time, so I'm not certain. A target version is also known as a prototype or proposal.
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "97"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f486117%2fadjective-for-a-expected-or-aspirational-version-of-a-document%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Draft, working version, work in progress ('WIP') each convey the temporary nature of the document. I can't find any dictionary authority for 'working version' but it does show up in web searches with this meaning.
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
add a comment |
Draft, working version, work in progress ('WIP') each convey the temporary nature of the document. I can't find any dictionary authority for 'working version' but it does show up in web searches with this meaning.
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
add a comment |
Draft, working version, work in progress ('WIP') each convey the temporary nature of the document. I can't find any dictionary authority for 'working version' but it does show up in web searches with this meaning.
Draft, working version, work in progress ('WIP') each convey the temporary nature of the document. I can't find any dictionary authority for 'working version' but it does show up in web searches with this meaning.
answered Feb 18 at 22:18
Jim MackJim Mack
7,06721832
7,06721832
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
add a comment |
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
Those are the words I'm using for the version we're actively writing, which will culminate in a final draft. This other one is sort of a target, and will only change if the developers make some modification in the application
– Shawn V. Wilson
Feb 19 at 6:27
add a comment |
In software terms, it sounds like you're working on something that's out of beta and essentially complete—but still pending any last-minute changes prior to publication.
This is often described as a release candidate.
From PC Magazine's definition of release candidate:
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance of the official release. A release candidate is like a "sneak preview" of the final release with the added advantage that serious bugs may yet surface and be fixed before the general public uses it. Thus, there are alpha versions (internal), beta versions (external), release candidates (sometimes) and the final release of software. After that, there are countless updates that add features and fix bugs.
In editing terminology, a manuscript that has had its final round of technical input and copyediting is, as you've called it, a final draft:
[Merriam-Webster]
: a final version of something (such as a document) usually after a lot of editing and rewriting
// The final draft is due tomorrow.
However, what you're currently working on is something prior to that stage—and certainly prior to the even more complete stage of proof or galley proof (which, in the publishing world, is what a final drafte turns into when it's sent to a typesetter).
In general editing terms, a draft that comes before a final draft is simply a manuscript.
I know of no editing terminology that is the exact equivalent of release candidate, but that is the analogous term that you're looking for.
Note that you asked for the initial version in your question—but also said that you want something that's the expected or target version. Those two things seem incompatible to me. But if it's not actually release candidate that describes your current situation, then you could make use of either alpha or beta, depending on how you are interpreting things. Or even initial draft. But, again, you seem to be describing things at two different ends of the development cycle at the same time, so I'm not certain. A target version is also known as a prototype or proposal.
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
add a comment |
In software terms, it sounds like you're working on something that's out of beta and essentially complete—but still pending any last-minute changes prior to publication.
This is often described as a release candidate.
From PC Magazine's definition of release candidate:
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance of the official release. A release candidate is like a "sneak preview" of the final release with the added advantage that serious bugs may yet surface and be fixed before the general public uses it. Thus, there are alpha versions (internal), beta versions (external), release candidates (sometimes) and the final release of software. After that, there are countless updates that add features and fix bugs.
In editing terminology, a manuscript that has had its final round of technical input and copyediting is, as you've called it, a final draft:
[Merriam-Webster]
: a final version of something (such as a document) usually after a lot of editing and rewriting
// The final draft is due tomorrow.
However, what you're currently working on is something prior to that stage—and certainly prior to the even more complete stage of proof or galley proof (which, in the publishing world, is what a final drafte turns into when it's sent to a typesetter).
In general editing terms, a draft that comes before a final draft is simply a manuscript.
I know of no editing terminology that is the exact equivalent of release candidate, but that is the analogous term that you're looking for.
Note that you asked for the initial version in your question—but also said that you want something that's the expected or target version. Those two things seem incompatible to me. But if it's not actually release candidate that describes your current situation, then you could make use of either alpha or beta, depending on how you are interpreting things. Or even initial draft. But, again, you seem to be describing things at two different ends of the development cycle at the same time, so I'm not certain. A target version is also known as a prototype or proposal.
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
add a comment |
In software terms, it sounds like you're working on something that's out of beta and essentially complete—but still pending any last-minute changes prior to publication.
This is often described as a release candidate.
From PC Magazine's definition of release candidate:
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance of the official release. A release candidate is like a "sneak preview" of the final release with the added advantage that serious bugs may yet surface and be fixed before the general public uses it. Thus, there are alpha versions (internal), beta versions (external), release candidates (sometimes) and the final release of software. After that, there are countless updates that add features and fix bugs.
In editing terminology, a manuscript that has had its final round of technical input and copyediting is, as you've called it, a final draft:
[Merriam-Webster]
: a final version of something (such as a document) usually after a lot of editing and rewriting
// The final draft is due tomorrow.
However, what you're currently working on is something prior to that stage—and certainly prior to the even more complete stage of proof or galley proof (which, in the publishing world, is what a final drafte turns into when it's sent to a typesetter).
In general editing terms, a draft that comes before a final draft is simply a manuscript.
I know of no editing terminology that is the exact equivalent of release candidate, but that is the analogous term that you're looking for.
Note that you asked for the initial version in your question—but also said that you want something that's the expected or target version. Those two things seem incompatible to me. But if it's not actually release candidate that describes your current situation, then you could make use of either alpha or beta, depending on how you are interpreting things. Or even initial draft. But, again, you seem to be describing things at two different ends of the development cycle at the same time, so I'm not certain. A target version is also known as a prototype or proposal.
In software terms, it sounds like you're working on something that's out of beta and essentially complete—but still pending any last-minute changes prior to publication.
This is often described as a release candidate.
From PC Magazine's definition of release candidate:
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance of the official release. A release candidate is like a "sneak preview" of the final release with the added advantage that serious bugs may yet surface and be fixed before the general public uses it. Thus, there are alpha versions (internal), beta versions (external), release candidates (sometimes) and the final release of software. After that, there are countless updates that add features and fix bugs.
In editing terminology, a manuscript that has had its final round of technical input and copyediting is, as you've called it, a final draft:
[Merriam-Webster]
: a final version of something (such as a document) usually after a lot of editing and rewriting
// The final draft is due tomorrow.
However, what you're currently working on is something prior to that stage—and certainly prior to the even more complete stage of proof or galley proof (which, in the publishing world, is what a final drafte turns into when it's sent to a typesetter).
In general editing terms, a draft that comes before a final draft is simply a manuscript.
I know of no editing terminology that is the exact equivalent of release candidate, but that is the analogous term that you're looking for.
Note that you asked for the initial version in your question—but also said that you want something that's the expected or target version. Those two things seem incompatible to me. But if it's not actually release candidate that describes your current situation, then you could make use of either alpha or beta, depending on how you are interpreting things. Or even initial draft. But, again, you seem to be describing things at two different ends of the development cycle at the same time, so I'm not certain. A target version is also known as a prototype or proposal.
edited Feb 19 at 7:18
answered Feb 19 at 7:10
Jason BassfordJason Bassford
19.1k32245
19.1k32245
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
add a comment |
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
They are incompatible; I probably shouldn't have said "initial" when speaking of the "target" version. (I called it that because it was written first). But I think "proposal" is probably closest.
– Shawn V. Wilson
Feb 19 at 23:39
add a comment |
Thanks for contributing an answer to English Language & Usage Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f486117%2fadjective-for-a-expected-or-aspirational-version-of-a-document%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You could call it the "premature" version.
– TRomano
Feb 18 at 20:54
1
I would call it preliminary version.
– michael.hor257k
Feb 18 at 22:52
Yes, preliminary is almost universal.
– Global Charm
Feb 19 at 1:35
Your software should have a version number X, and the manual is for version X. Whatever adjective you use will be context sensitive--it won't be preliminary or a draft once you release, but all your old documentation and emails will still read that way.
– jimm101
Feb 19 at 13:44