Sources and Licenses
Maqor distinguishes public-domain source content, third-party licensed datasets, generated study data, and the proprietary application code and presentation layer.
Source categories
| Category | Use in Maqor | License responsibility |
|---|---|---|
| Biblical source texts | Original-language display for Hebrew, Greek, and Syriac corpora where configured. | Each corpus must be tracked according to its own public-domain status or license terms. |
| Morphology data | Compact and expanded morphology information in word boxes and popups. | Dataset-specific licenses and attribution must be preserved. |
| Lexical identifiers | Strong's or analogous references shown in the interface. | Source and license depend on the lexicon dataset. |
| Generated data | Normalized morphology, IPA output, display formatting, and alignment support. | Generated by Maqor unless otherwise noted. |
| Application code and design | Frontend, backend, UI, API, and data presentation. | Proprietary to Maqor/Helko unless explicitly released otherwise. |
Reuse principle
Public-domain materials remain public domain. Maqor does not claim ownership of public-domain biblical texts. However, the application code, interface design, generated presentation, normalized data decisions, future community tools, and proprietary compilation choices are protected as Maqor/Helko work unless a separate license says otherwise.
Why source transparency matters
Interlinear tools combine several kinds of material that users can easily confuse. A biblical text may be public domain, a morphology dataset may have its own license, a lexicon may require attribution, and a generated pronunciation line may be produced by Maqor. Those categories cannot be treated as one undifferentiated dataset. This page exists so users and reviewers can see that the project is tracking those distinctions.
When Maqor displays a word, the visible block may contain both upstream material and generated support data. For example, the surface word comes from a source corpus, the morphology may come from an upstream morphology file, the compact display code may be normalized by Maqor, and the IPA may be generated by project rules. Reuse permissions depend on which part of the block is being reused.
Attribution and future improvements
The source list will need to become more detailed as the product matures. Each corpus should eventually have a dedicated source record with origin, license, version, conversion script, date imported, and known limitations. This is especially important if the future forum model allows contributors to cite or discuss source data directly. A correction to a word display should be traceable back to the upstream source and to any Maqor transformation applied to it.
The current approach is conservative: public-domain portions can remain shareable, third-party materials keep their original terms, and Maqor's own code and generated presentation remain proprietary unless explicitly released otherwise. That distinction is also reflected in the Terms page.
Examples of what can and cannot be reused
If a biblical source text is public domain, users may be able to reuse that source text under public-domain rules. That does not mean the entire Maqor word card can be copied as a proprietary dataset. A word card may include source text, generated IPA, normalized morphology display, interface choices, and alignment decisions. Those added layers may be Maqor work or may depend on third-party licenses.
If a user wants to cite a single verse or discuss a morphology value, that is different from scraping the whole service. The Terms are intended to permit normal reading, study, citation, and discussion while preventing bulk extraction or republication of the assembled product. This balance is important because Maqor wants public-domain material to remain usable while still protecting the work required to build and maintain the app.
Source corrections
Source corrections should be handled carefully. Some errors may be import bugs. Others may be upstream data issues. Others may be display or normalization errors created by Maqor. A good report should identify which layer seems wrong. This is why the future source records and correction workflow are part of the product roadmap rather than an afterthought.
How Maqor should cite sources
Every public corpus should eventually have a visible citation trail. A useful citation trail includes the corpus name, source project, license or public-domain note, version or release date when available, conversion script, and the date the material was imported into Maqor. This prevents a common problem in Bible software: users can see a label, but they cannot tell which exact dataset produced the word they are reading.
That detail matters when a user reports a problem. If a Hebrew form, Greek accent, Syriac lemma, or morphology tag appears wrong, the first question is not simply "what should the app display?" The first question is "which layer produced this value?" A wrong value may come from the upstream source, from the import script, from normalization, from a display rule, or from a generated pronunciation rule.
Public-domain content and Maqor presentation
Maqor's licensing approach is intended to be practical. Public-domain biblical text should remain shareable as public-domain content. At the same time, a full Maqor page or word-card dataset includes organization, interface design, generated fields, and editorial decisions. Those additions are not automatically public domain merely because one field inside the card is public domain.
This distinction protects the app without locking away public material. Users should be able to quote, study, and discuss public-domain source text. They should not assume that bulk copying Maqor's assembled database, generated IPA, normalized morphology, and UI-specific alignment is the same thing as copying the underlying public-domain verse text.
For license or source concerns, contact helko.contact@gmail.com.