Skip to content
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

Lossless Round Tripping of Projects #79

Closed
jonathanrobie opened this issue Nov 14, 2019 · 6 comments
Closed

Lossless Round Tripping of Projects #79

jonathanrobie opened this issue Nov 14, 2019 · 6 comments
Labels
Close Request Someone wants to close this - close or clear label Policy How things work here, also how SB should work and evolve in a general sense Rabbit Hole Maybe this issue has gone deep enough, so we should stop digging

Comments

@jonathanrobie
Copy link
Collaborator

Scripture Burrito is intended to allow lossless roundtripping of projects between ecosystems. This depends to some extent on references to ecosystem servers that enable reconnection with different ecosystem-specific contexts.

Do we really believe this? I think a project includes information about the people, project status, etc. that we do not intend to support in Scripture Burrito.

@mvahowe
Copy link
Contributor

mvahowe commented Nov 14, 2019

The question here seems to be how to define a project. The wider that definition, the harder it is to roundtrip. So what's our working definition of a project? Also, ecosystem servers provide a route to conversations etc, providing we have an agreed API.

@jonathanrobie
Copy link
Collaborator Author

jonathanrobie commented Nov 14, 2019 via email

@mvahowe
Copy link
Contributor

mvahowe commented Nov 14, 2019

Your use case uses the word "project". What does that word mean? If it means "whatever anyone wants it to mean", I'm not sure we can say anything at all about the use case. It might mean "a recipe for crême brûlée".

@mvahowe
Copy link
Contributor

mvahowe commented Nov 14, 2019

I suspect that we need a word for "what can travel in a portable manner between system via a SB" and another word for "the complete human and technological system that surrounds an instance of Bible translation". The text of a translation obviously fits within the first definition. I would say that conversations about the translation don't. I think there's a discussion to be had about, eg,hyphenation dictionaries.

@mvahowe
Copy link
Contributor

mvahowe commented Nov 14, 2019

See #52 which I think frames the question in a way we could answer, ie how much of a PT project needs to be portable?

@mvahowe
Copy link
Contributor

mvahowe commented Feb 20, 2020

Personally, I think we can only answer this question empirically, ie we do what we can and find out how lossless the result is. We have other issues such as #52 which are trying to nail down the specifics. So can we close this?

@mvahowe mvahowe added Policy How things work here, also how SB should work and evolve in a general sense Rabbit Hole Maybe this issue has gone deep enough, so we should stop digging Close Request Someone wants to close this - close or clear label and removed Editorial labels Feb 20, 2020
@jag3773 jag3773 closed this as completed Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Close Request Someone wants to close this - close or clear label Policy How things work here, also how SB should work and evolve in a general sense Rabbit Hole Maybe this issue has gone deep enough, so we should stop digging
Projects
None yet
Development

No branches or pull requests

3 participants