Brainstorming

• Cacheability of API and underlying data for use offline and to improve performance by having local access
• Stability of identifiers: Cool URIs don’t change!
• Linked Data
• Unification: merging variant texts together to create foundational intersection point for canonical linking. Old merged data is never removed or changed; new data is merged in with new identifiers.
• Interlinearization: linking corresponding semantic units between texts on graded scale; links consist of semantic clusters
• Atomic granularity: Every word and even every punctuation mark should be individually addressable.
• Stand-off markup
• Interlinking data even if it is not openly licensed via stand-off markup
• New texts are linked in via submitting a normalized XML schema that contains stand-off markup linking back to each data points origin.
• Ideally only the links would be stored back to the source documents, but realistically these sources don’t have APIs themselves; so the Open Scriptures API should itself serve as a proxy for the original data until each can (if ever) have its own API server. This would only work for open (CC-BY-SA) data. For this to work, the import document schema must be lossless so that every feature can be imported into the system.