Closed cjcodeproj closed 8 months ago
Film Notes:
Film | Year | Location Setting | Time Setting |
---|---|---|---|
Blue Thunder | 1982 | Los Angeles, CA | present time |
To Live And Die in LA | 1985 | Los Angeles, CA | present time |
L.A. Confidential | 1997 | Los Angeles, CA | 1950s |
IT | 2017 | Derry, ME (fictional town) | 1989 |
American Flyers | 1985 | St. Louis, MI | present time |
White Sands | 1992 | Alamogordo, NM | present time |
The Specialist | 1994 | Miami, FL | present time |
Blade Runner | 1982 | Los Angeles, CA | 2019 (alternate future) |
Feature Add:
Timeline events that occur before or after major events.
Sample record:
<settings>
<setting>
<where>
<place><st abbrv='TX'>Texas</st></place>
</where>
</setting>
</settings>
Proposed change:
Make the first element under <settings>
an indicator of importance.
<settings>
<primary>
<where>
<place><ci>Las Vegas</ci><st abbrv='NV'>Nevada</st></place>
</where>
</primary>
</settings>
Child elements could be primary
, secondary
, trinary
, etc, etc. Or some other mechanism indicating importance.
Additional Note:
Settings element has been set up for the following films, which take place in San Francisco, CA.
San Diego setting value has been used for:
Los Angeles setting value has been used for:
Currently, the schema has a
<setting>
element, under the<genre>
element that has a very simplistic definition of trying to define a story. This ticket is a suggestion to deprecate the element, and create a better element under the<story>
element structure.The primary rational for moving the functionality under
story
is because the element may not work undercatalog
for non-fictional works.The
story/settings
element should be optional, and it should have a series of child elements that describe either a place or a time, or both.The elements should be structured to handle variances in how places and time are described, such as decades, eras, major events, undetermined times, non-specific geographic regions, and it should also support fictional places while also identifying that the location is fictional.
It should not be used to spoil story elements, or give away information that detracts from the story. It should be used in place of keywords that may describe an identical context. In that regard a
settings
element helps alleviate the workload currently handled bykeywords
.There should also be a spec document that goes along with the element describing how to use it.
There is an existing ticket, https://github.com/cjcodeproj/vtmedia-schema/issues/50 covering the existing element that should be closed, but it can be referenced when designing the new element.