Timeline for What are "future works"?
Current License: CC BY-SA 4.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 9, 2018 at 18:34 | comment | added | DVK-on-Ahch-To | @Möoz - see my reply to Mcavity on separate comment today. He had an example where it was a pretty clear FWP, as the topic clearly wasn't covered in prior canon | |
May 7, 2018 at 15:36 | comment | added | DVK-on-Ahch-To | @Möoz - " if it tends to be somewhat evident that we will get an actual answer after a certain period of time?" - if you replace "somewhat evident" with "very likely", the question is FWP. That's almost verbatim definition from the answer I gave. If you don't have any evidence other than "somewhat evident", "we don't know" is a good answer and shouldn't be limited at all | |
May 5, 2018 at 13:04 | comment | added | phantom42 | How many “we don’t know” answers are we going to be ok with? How many “correct” answers are we ok with? We don’t limit those. We do sometimes comment if the new answer doesn’t provide any new insight or information, and that’d be fair to do with “we don’t know” answers as well, but there’s no reason to limit them, per se. | |
May 5, 2018 at 7:21 | comment | added | user31178 | Sometimes "we don't know" is a good answer. If a user can show that they were thorough in the material they looked through, or their expertise/familiarity with it, then that may be exactly the answer you need. It saves the asker the time of having to try and sift through all that material themselves, which they may be much less familiar with than our resident experts. | |
May 3, 2018 at 2:29 | comment | added | phantom42 | I'd agree that we probably have to accept some sort of degree of "likely", but I think we should stay closer to Null's idea. Mooz is correct in that just because it's in the trailer, doesn't mean we'll get an explanation, but a trailer literally showing Magneto pulling Mystique is a better indication of likelihood than "well, we met Snoke in ep 7, so we'll likely get his backstory in 8". | |
May 3, 2018 at 1:25 | comment | added | Möoz | And how many "we don't know" answers are we going to be ok with, if it tends to be somewhat evident that we will get an actual answer after a certain period of time? | |
May 3, 2018 at 1:24 | comment | added | Möoz | @Null I disagree, likely is actually a good indicator. Besides, what happens in trailers often does not happen in the movie, so we can never be sure. So all we have to go by is how likely it is to be answered. Especially since most answers will undoubtedly include "we don't know, yet it will likely be revealed in X" | |
May 2, 2018 at 15:44 | comment | added | Null Mod | -1 for "likely to contain an answer". The key word I disagree with there is "likely". I only support closing as FW if the future work will contain an answer. For example, "What happens to so-and-so in this trailer?" will clearly be more answerable once the movie that the trailer is for is released. Since no one know what a future work will contain, it's pure speculation that a future work will "likely" answer the question. It's better to err on the side of keeping such questions open, IMO. In such cases it's perfectly acceptable to answer "I searched here and there, but we don't know." | |
May 2, 2018 at 15:18 | history | edited | Skooba | CC BY-SA 4.0 |
added 168 characters in body
|
May 2, 2018 at 15:16 | comment | added | Skooba | @phantom42 Good point, but I would say that if at time the question was asked and answered it was not future works and should remain open. I will probably update my answer to cover this. As DVK said, we shouldn't close all our Star Wars questions just because a new sequel/prequel/spin off is announced. | |
May 2, 2018 at 15:11 | comment | added | phantom42 | Re: Avatar - now that Cameron announced 4 sequels, would you suggest we go back and close any "we don't knows" as FWP? | |
May 2, 2018 at 15:09 | history | edited | Skooba | CC BY-SA 4.0 |
added 4 characters in body
|
May 2, 2018 at 14:49 | history | answered | Skooba | CC BY-SA 4.0 |