Difference between revisions of "Talk:Module Development Collaboration"

From CrossWire Bible Society
Jump to: navigation, search
(Go Bible tools: :::See also Projects:Go Bible/Go Bible Creator. ~~~~)
(Metadata: new section)
Line 12: Line 12:
  
 
This note is to remind everyone that the [http://pathway.sil.org/ SIL Pathway] project overlaps some of the proposed collaboration tasks. [[User:David Haslam|David Haslam]] 04:04, 25 June 2012 (MDT)
 
This note is to remind everyone that the [http://pathway.sil.org/ SIL Pathway] project overlaps some of the proposed collaboration tasks. [[User:David Haslam|David Haslam]] 04:04, 25 June 2012 (MDT)
 +
 +
== Metadata ==
 +
 +
Trawling through correspondence with the owners/suppliers of the original files can be tedious, and may even be confusing. We should determine the important and critical properties for conf files as early as possible, and record permissions, license agreements, copyright status, etc in a separate meta folder. [[User:David Haslam|David Haslam]] 05:22, 25 June 2012 (MDT)

Revision as of 11:22, 25 June 2012

Go Bible tools

Wrt "ThML for import to Go Bible?", I generally use a TextPipe filter for this purpose. Yet please remember that Go Bible Creator can process USFM files directly as one of the input formats, so ThML is not always required. David Haslam 03:34, 25 June 2012 (MDT)

As regards nomenclature, to avoid confusion, I try to avoid the word "module" for Go Bible applications. It's preferable to reserve the word for SWORD modules. David Haslam 03:36, 25 June 2012 (MDT)
If we can make the primary focus the collaboration on making the SWORD module, there are existing methods (involving the use of diatheke & TextPipe) to make a ThML file for use with Go Bible Creator. David Haslam 04:01, 25 June 2012 (MDT)
See also Projects:Go Bible/Go Bible Creator. David Haslam 04:07, 25 June 2012 (MDT)

SIL Pathway

This note is to remind everyone that the SIL Pathway project overlaps some of the proposed collaboration tasks. David Haslam 04:04, 25 June 2012 (MDT)

Metadata

Trawling through correspondence with the owners/suppliers of the original files can be tedious, and may even be confusing. We should determine the important and critical properties for conf files as early as possible, and record permissions, license agreements, copyright status, etc in a separate meta folder. David Haslam 05:22, 25 June 2012 (MDT)