DBL Metadata 2.2.1

[mvahowe]

@klassenjm @smorrison @ericpyle As discussed last week, I've been thinking about a conservative, "as non-breaking as possible" metadata update. My suggestion is to allow three new, optional fields within the format section. (I don't think it's worth introducing conventions as this point.) Those fields would be

<usxVersion>3.0</usxVersion>
<timingDir>TIMING</timingDir> <!-- Denotes the presence of timing files in our XML format -->
<contentByStory>true</recordingsByStory> <!-- Denotes audio that is not for whole chapters -->

These are designed so that the status quo applies in the absence of these fields. ie USX is 2.x, there are no timing files and audio is structured the current, per-chapter way.

I'll make the schema handle 2.1, 2.2 or 2.2.1.

Any comments before I dive into the schema?

[ericpyle]

It's okay with me

…

On Fri, Jun 28, 2019, 11:12 AM Mark Howe ***@***.***> wrote: @klassenjm <https://github.com/klassenjm> @smorrison <https://github.com/smorrison> @ericpyle <https://github.com/ericpyle> As discussed last week, I've been thinking about a conservative, "as non-breaking as possible" metadata update. My suggestion is to allow three new, optional fields within the format section. (I don't think it's worth introducing conventions as this point.) Those fields would be <usxVersion>3.0</usxVersion> <timingDir>TIMING</timingDir> <!-- Denotes the presence of timing files in our XML format --> <contentByStory>true</recordingsByStory> <!-- Denotes audio that is not for whole chapters --> These are designed so that the status quo applies in the absence of these fields. ie USX is 2.x, there are no timing files and audio is structured the current, per-chapter way. I'll make the schema handle 2.1, 2.2 or 2.2.1. Any comments before I dive into the schema? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39?email_source=notifications&email_token=AAISZPNQXKKR4U37OF53RXDP4YZ6VA5CNFSM4H4GXATKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4LHCRQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAISZPPF4YFAY7XVI34WQULP4YZ6VANCNFSM4H4GXATA> .

[mvahowe]

On reflection, I think

<contentByChapter>false</contentByChapter>

is more explicit than

<contentByStory>true</contentByStory>

I'm also going to add in some extensible role values for sign language videos:

sign \S(.*\S)?
concept \S.*\S)?
place \S.*\S)?
map \S(.\S)?

This is ugly and almost certainly not what we want in SB, but it at least means we can put the extra content on Elbert's DVDs into DBL, at which point we can see what is there and have a conversation about how to better represent it in the future.

[mvahowe]

@klassenjm There's now a PR #40 that relates to this. (The spec moved on a bit, so see the description of that PR for details.)