-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework Versification as part of a burrito #212
Comments
Does this mean shipping a |
Most projects have customized their versification in some way so it makes sense that they should be included with the project. |
Ideally, the current project's versification could be provided as a delta against a known "standard" versification. I think @jonathanrobie and versification group was going to define how this happens (maybe they have already?). For non-Scripture types, I think we just need to reference the versification scheme being used. For example, a set of translation notes shouldn't be able to customize a versification scheme, but it may be keyed to a BCV scheme and the tool just needs to know which one that is. |
But that versification scheme would probably be a customized version belonging to a project, would it not? If we just reference it "by name", then that means we need to have a name (or some designation) for every customized versification that exists. |
To emulate the status quo, I think we have two reasonable options.
1. Each project's versification is a delta from "org", and is contained as
a versification file in a burrito, or
2. We support other standard versifications like "eng" by name and require
them to be available in a public place (e.g. the Copenhagen Alliance site).
A project's versification can also be defined as a delta from one of these
schemes.
In practice, many projects use the versification of an existing gateway
language translation, which suggests we might also want to be able to
specify diffs from:
3. A specific revision of a specific resource
I would suggest that we support all three.
…On Fri, Dec 11, 2020 at 11:55 AM Tim Steenwyk ***@***.***> wrote:
For example, a set of translation notes shouldn't be able to customize a
versification scheme, but it may be keyed to a BCV scheme and the tool just
needs to know which one that is.
But that versification scheme would probably be a customized version
belonging to a project, would it not? If we just reference it "by name",
then that means we need to have a name (or some designation) for every
customized versification that exists.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#212 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANPTPLZFLMQ3B5H3ZHWP7DSUJFHNANCNFSM4QGG2IBA>
.
|
@jtauber to prep and then talk to @jonathanrobie about possible work needed in versification group. |
See #243 for discussion for @jonathanrobie to take to versification group. |
As discussed last week and in #243, all deltas will be expressed against org and no other versification system. They may have originally been expressed as delta to some other versification system but, for the purposes of generating a burrito, the delta against org is calculated and that is all that can be in a burrito. |
Yes, I agree.
…On Thu, Feb 11, 2021 at 8:25 AM James Tauber ***@***.***> wrote:
As discussed last week and in #243
<#243>,
all deltas will be expressed against *org* and no other versification
system. They may have *originally* been expressed as delta to some other
versification system but, for the purposes of generating a burrito, the
delta against *org* is calculated and that is all that can be in a
burrito.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#212 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANPTPPL362GOD7XXVAZSI3S6PLFVANCNFSM4QGG2IBA>
.
|
I think this is now going to be done as a new role for an ingredient which is a delta from the |
as now covered by #248, this can be closed. |
Currently, versification is a standalone flavor but it should be built into at least the following flavortypes:
The text was updated successfully, but these errors were encountered: