HIS Registry f Ministry Resurces Date: 2006-10-11 Status: Abstract: Editr: Changes since previus versin: Adpted Registry This registry is adpted by the HIS Stewards and ready fr use by members f the HIS cmmunity. Dcuments the Registry f Ministry Resurces (RMR) f the Harvest Infrmatin System (HIS) This registry defines standardized cdes fr classifying resurces used in ministry with respect t scpe f scripture, type f scripture material, nature f cntent, mde f expressin, and frmat f delivery. Jan Spanne (jan_spanne@sil.rg) Minr changes f wrding in the explanatry sectins f each f the registries. N changes t the cde sets were made. Table f cntents 1. Overview 2. tables 3. Other tables 4. Change management 5. Change histry 6. Distributin 1. Overview The functin f the Registry f Ministry Resurces (RMR) is t prvide standardized cdes fr classifying resurces used in ministry in varius ways. The registry cntains five cde tables: RMR_ScriptureScpe: fr Scripture-Related Scpe A cde in this cde set represents a bk f the Bible r a majr blck f bks (a testament) f which the resurce is an instance (r t which its subject is related). RMR_ScriptureType: fr Scripture-Related Type A cde in this cde set represents the genre r cmprehensiveness f a resurce that is (r is related t) sme r the entire Bible. RMR_Cntent: fr Nature f Cntent Page 1 f 10
A cde in this cde set represents the genre r tpic f a resurce ther than a Scripture-related resurce. RMR_Mde: fr Mde f Expressin A cde in this cde set represents the mde in which the cntent f the resurce is expressed, perceived, r interacted with. RMR_Frmat: fr Frmat f Distributin A cde in this cde set represents the means f delivery t the audience r user. In additin, there is a change histry table fr each cde set that has been changed since its initial release. There are n freign key relatinships amng these cde sets r between these cde sets and thse f ther registries. Thus, there is n need fr an entity-relatinship diagram fr this registry. A Nte addressing frequently asked questins regarding the use f the RMR has als been written and is included in the RMR distributin package. 2. tables The registry cntains five cde tables: RMR_ScriptureScpe, RMR_ScriptureType, RMR_Cntent, RMR_Mde, and RMR_Frmat. RMR_ScriptureScpe: fr Scripture-Related Scpe The dmain f the categries fr this cde set is the set f all bks f the Bible (encmpassing the Jude-Christian cannical and deutercannical Scripture). Each cde prvides a standardized three-letter string fr uniquely referring t a particular bk. In additin, there are cdes fr the entire Bible, fr the Old and New Testaments, and the Old Testament Apcrypha. Smaller grups f bks (such as the Trah r the Gspels) are nt addressed in this list; instead, the recmmendatin is t repeat this element fr resurces that encmpass multiple bks. See the cmplete cde set fr the reference table in HTML frmat. Using a cde frm this set asserts that a resurce pertains t the given bk r sectin f the Bible. It might be the cmplete text, a translatin f selected prtins, an abridgement, a cmmentary, r a study aid. Use a cde frm RMR_ScriptureType t indicate the genre r cmprehensiveness f the resurce. Fr database use, it is recmmended that each applicatin f a cde frm RMR_ScriptureScpe be paired directly with a cde frm RMR_ScriptureType. This will enable unambiguus identificatin f a resurce that includes, fr example, the cmplete New Testament, as well as a summary f the Old Testament. The decisin nt t include cmmn grupings f bks, such as the Majr Prphets, the Gspels, r the Pastral Epistles, was made in rder t avid ambiguity regarding hw t categrize a wrk that relates t multiple bks f the Bible, but less than a testament. A resurce that includes sme but nt all bks frm ne r mre grupings wuld ambiguusly indicate a scpe wider than intended if cdes fr grupings were applied. This ambiguity shuld be avided in the exchange f data between systems. It may be apprpriate fr a given applicatin used by an rganizatin t ffer grupings f bks in an interface fr its users, if that serves their needs mre effectively. Hwever, "behind the Page 2 f 10
scenes" in the data structures, a requirement shuld be that use f a grup designatin will map unambiguusly t specific bks f the Bible in rder t facilitate data sharing amng HIS registered user rganizatins. These cdes are based n the set already in widespread use within the Bible translatin cmmunity due t their incrpratin int the United Bible Scieties' Paratext Sftware. Anther standard fr identifying bks f the Bible (develped as part f the Open Scripture Infrmatin Standard) is the OSIS Nrmative Abbreviatins fr cannical and deutercannical bks; these are based n the abbreviatins specified in the Sciety f Biblical Literature's SBL Handbk f Style. This standard prvides abbreviatins that range in length frm tw t seven characters. The mapping frm Paratext cdes t OSIS abbreviatins is unambiguus and thus the cde table fr the RMR_ScriptureScpe cde set cntains a clumn that gives the mapping f the RMR cde nt the crrespnding OSIS abbreviatin. (Nte that this mapping exists nly fr RMR_ScriptureScpe cdes that represent a single bk.) The RMR_ScriptureScpe cde set cntains anther supplementary clumn named rder. It gives a three-digit string that can be srted t put the bks in cannical rder. In this sequence, cdes fr the entire Bible r an entire testament are in the 000s, the Old Testament bks are in the 100s, the New Testament bks are in the 200s, and the duetercannical bks are in the 300s. The cde table fr RMR_ScriptureScpe cntains the fllwing five clumns: Clumn Frmat Descriptin char(3) The three-letter cde fr the Bible bk r sectin. Name varchar(30) The name f the bk r sectin dented by the cde. Descriptin varchar(255) A descriptin f the bk r sectin dented by the cde. Order char(3) A digit string that can be srted t put the bks in cannical rder. OSIS varchar(7) The crrespnding OSIS abbreviatin. The SQL statement fr creating this table is as fllws: CREATE TABLE RMR_ScriptureScpe ( char(3) NOT NULL, Name varchar(30) NOT NULL, Descriptin varchar(255) NOT NULL, Order char(3) NOT NULL, OSIS varchar(7) NULL) Page 3 f 10
RMR_ScriptureType: fr Scripture-Related Type The dmain f the categries f this cde set is the genre f the resurce (such as translated text r cmmentary r cncrdance) r cmprehensiveness f the resurce (such as cmplete text r abridgement r selected prtins) as it relates specifically t Jude-Christian cannical r deutercannical Scripture. Each cde prvides a standardized tw-letter string fr uniquely referring t a particular type f Scripture-related resurce. One r mre cdes frm RMR_ScriptureScpe may be used in cnjunctin with a cde frm this set in rder t indicate the exact bks f the Bible t which the resurce is related. See the cmplete cde set reference table in HTML frmat. The cde table fr RMR_ScriptureType cntains the fllwing three clumns: Clumn Frmat Descriptin char(2) The tw-letter cde fr the type f the Scripture-related resurce. Name varchar(30) The name f the resurce type dented by the cde. Descriptin varchar(255) A descriptin f the resurce type dented by the cde. The SQL statement fr creating this table is as fllws: CREATE TABLE RMR_ScriptureType ( char(2) NOT NULL, Name varchar(30) NOT NULL, Descriptin varchar(255) NOT NULL) RMR_Cntent: fr Nature f Cntent The dmain f the categries fr this cde set is the genre r tpic f a resurce ther than a Scripture-related resurce. Devtinal, thelgical, and religius instructin resurces are described here, rather than in Scripture Type. The distinctin f Scripture Type versus Cntent is whether the material is drawn quite directly frm scripture (as text r adapted stry), r simply cntains cncepts that are drawn frm scripture but are part f ther material. In additin, ther cmmn resurce types related t wrk in general educatin, literacy, health and develpment are als included in this cde set. Each cde prvides a standardized tw-letter string fr uniquely referring t a particular type f nn-scripturerelated cntent. See the cmplete cde set as a reference table in HTML frmat. The cde table fr RMR_Cntent cntains the fllwing three clumns: Clumn Frmat Descriptin char(2) The tw-letter cde fr the cntent type f the resurce. Page 4 f 10
Name varchar(30) The name f the cntent type dented by the cde. Descriptin varchar(255) A descriptin f the cntent type dented by the cde. The SQL statement fr creating this table is as fllws: CREATE TABLE RMR_Cntent ( char(2) NOT NULL, Name varchar(30) NOT NULL, Descriptin varchar(255) NOT NULL) RMR_Mde: fr Mde f Expressin The dmain f the categries fr this cde set is the mde by which the cntent f the resurce is expressed, perceived, r interacted with. Distinctins f mde invlve sensry experience (as in auditry versus visual), time experience (as in full-mtin versus still image), methd f creatin (as in phtgraphic versus graphic), ptential r actual nature f resurce (as in recrding versus live perfrmance). Each cde prvides a standardized twletter string fr uniquely referring t a particular mde f expressin. See the cmplete cde set as a reference table in HTML frmat. The dmain f RMR_Mde is cmparable t the dmain fr the DCMI Type vcabulary f the Dublin Cre Metadata Initiative, but makes sme finer distinctins. The categries f RMR_Mde have been designed nt t verlap with multiple DCMI Type categries (that is, an RMR_Mde categry is either the same as a DCMI Type categry r is a subset f ne). Nte that tw DCMI Type categries d nt have cunterparts in RMR_Mde: Cllectin is nt a mde (rather multiple mdes may be identified if the resurce is a cllectin invlving multiple mdes), and Event is treated as "Live perfrmance" in RMR_Frmat. The cde table fr RMR_Mde has a clumn indicating the mapping t DCMI Type categries. The cde table fr RMR_Mde cntains the fllwing five clumns: Clumn Frmat Descriptin char(2) The tw-letter cde fr the mde f the resurce. Name varchar(30) The name f the mde dented by the cde. Descriptin varchar(400) A descriptin f the mde dented by the cde. DCMI_Type varchar(20) The crrespnding cde frm the DCMI Type vcabulary. Examples varchar(100) Examples f resurces characterized by this mde. vcabulary. Page 5 f 10
The SQL statement fr creating this table is as fllws: CREATE TABLE RMR_Mde ( char(2) NOT NULL, Name varchar(30) NOT NULL, Descriptin varchar(400) NOT NULL, DCMI_Type varchar(20) NULL, Examples varchar(100) NULL) RMR_Frmat: fr Frmat f Distributin The dmain f the categries fr this cde set is the frmat used as the means fr delivering the resurce t the audience r user, whether it is tangible (such as paper, cassette, r disc) r intangible (such as bradcast r internet r live perfrmance). Alternatively, it may be cnsidered the medium f strage f a resurce within a cllectin such as a library, r archives. Each cde prvides a standardized tw-letter string fr uniquely referring t a particular frmat fr distributin. The aim f this cde set is t prvide cdes fr cmmnly used distributin frmats (t cnsumers r perhaps t libraries). As new frmats are created and cme int wide use fr the kinds f ministry resurces that HIS users need t describe, new frmat cdes can be suggested and reviewed by the HIS cmmunity. The intent is nt t include all pssible frmats that may have been used either fr distributin in the past r fr strage in a specialized cllectin (such as riginal recrding media r specialized preservatin media). The recmmended data mdel wuld be t allw fr bth a cded value and text entry. The text field can be used t identify a frmat fr which n cde is prvided, r t refine a cde that grups uncmmn, but related frmat types, as with AT (Audi tape ther) r VT (Vide tape ther). See the cmplete cde set as a reference table in HTML frmat. The cde table fr RMR_Frmat cntains the fllwing three clumns: Clumn Frmat Descriptin char(2) The tw-letter cde fr the frmat f resurce. Name varchar(30) The name f the frmat dented by the cde. Descriptin varchar(255) A descriptin f the frmat dented by the cde. The SQL statement fr creating this table is as fllws: CREATE TABLE RMR_Frmat ( char(2) NOT NULL, Name varchar(30) NOT NULL, Descriptin varchar(255) NOT NULL) 3. Other tables The registry cntains n supplementary tables at this pint. Page 6 f 10
4. Change management This sectin defines the prcess that the registry steward will fllw t maintain the registry. Gverning philsphy The basic philsphy f the cde sets in this registry is nt t give exhaustively detailed lists, but t prvide ways f classifying instances int categries that are bth bradly useful and nn-verlapping. (The exceptin t this is RMR_ScriptureScpe, which des aim t be a cmplete list.) A change will be made when it can be shwn t crrect an errr, r t imprve the cverage and usefulness f a cde set (in keeping with the philsphy f nnverlapping brad classificatin). Hw t make a change request If yu believe any f the infrmatin in the Registry f Ministry Resurces is in errr, r if yu have an imprvement r additin t suggest, send yur prpsed change with ratinale by e- mail t HIS-admin@wycliffe.rg. Hw change requests are prcessed The RMR Steward will review the prpsal and acknwledge receipt with initial cmment r request fr clarificatin. RMR users (including the RMR Steward) are encuraged t discuss pssible changes and their impacts infrmally befre making a frmal change prpsal. If the change appears t be in line with the philsphy f the registry, the RMR Steward will frmally prpse the change. Prpsed changes will be batched fr review n an annual cycle by the HIS Cmmunity. The RMR Steward will cmpile all the prpsed changes f the previus 12 mnths and send the set f prpsed changes (which includes the cmplete cde table(s) and the crrespnding change table(s) dcumenting the prpsed changes) t the HIS Registrar. The HIS Registrar will ntify the Registered Users f the psting f prpsed changes and the review perid fr cmment. On evaluating the feedback frm the review perid, the RMR Steward need nt treat the set f prpsed cde changes as a single package it may be cncluded that sme shuld be adpted, while thers shuld be rejected r shuld be deferred fr further prcessing with the next set f prpsed changes. Given the nature f the cde sets in the RMR, it is anticipated that cde set changes will be few and infrequent, but it is als recgnized that a single cde change culd have a significant impact n ne r mre users, and s shuld be carefully cnsidered befre adptin by the HIS Cmmunity. Hw updates are made The registry will be updated when candidate updates are adpted by the HIS Registered Users. The mst recent versin will always be available fr dwnlad frm this page. What t d pending a change s beginning with the letter X are reserved fr lcal use. That is, n cdes in any f the RMR cde sets begin with X, and n new cdes beginning with X will be created. Thus, when users feel the need fr a cde that is nt yet part f a cde set, they may freely assign a meaning t a cde in the range f lcal use (XA - XZ r XAA - XZZ, depending n the standard length f the cde fr the registry in questin) and use it temprarily until the utcme f a request t add a cde is knwn. Page 7 f 10
5. Change histry The change histry tables f this registry are cnstructed as fllws: Change The cde that is affected by the change reprted in this recrd. A ne-letter cde indicating the type f change. These are the pssible values: C Created. The cde is newly created. E R U Extended. The meaning f the cde is extended by virtue f being merged with a cde that has been retired. Retired. The cde has been retired and shuld n lnger be used in a database. A cde might be retired be because its meaning has been merged int that f anther cde, which has been extended in meaning, r because the retired cde has been split int tw new cdes, each with narrwer meaning, r because there is n evidence that the retired cde as defined is actually needed. Updated. There has been n change t the cde r its meaning, but ther infrmatin in the cde table has been added r changed (e.g. the name has changed r supplementary infrmatin has been added). Date Descriptin The date the change was frmally prpsed, i.e., included in a batch f prpsed cde changes sent t the HIS Registrar. Brief descriptin f the change. In the case f changes f type R (retired), this will include instructins n what shuld be dne t existing uses f the cde in a database in rder t update them. Each change histry table fr all cde sets in this registry has an identical structure (thugh the width f the clumn varies, being either tw r three characters wide, depending n the cde set). The SQL statement fr creating a change histry table is as fllws: CREATE TABLE <cde>changehistry ( char(3) NOT NULL, Change char(1) NOT NULL, Date date NOT NULL, Descriptin varchar(255) ) By perfrming a SQL JOIN between a cded clumn in a user's database and the clumn f the change histry table, it is pssible t autmatically detect all database recrds that may need t be updated. The Descriptin clumn will then describe the needed change. Page 8 f 10
The cde table always hlds the mst current versin f the cmplete set f active cded values. Thus when a cde is retired, it is remved frm the cde table. The change histry table, hwever, always hlds the cmplete histry f all changes. That is, rws are never remved frm the change histry table; they are nly added as cdes are created r changed. The change histry table may thus be queried t learn the cmplete histry f a given cde, r t learn all the changes that have been made since a given date. At this time, the change histry tables dcument the creatin f the cdes in the initial Prpsed Registry, with a very few changes. They are named as fllws: RMR_ScriptureScpe Change Histry.tab RMR_ScriptureType Change Histry.tab RMR_Cntent Change Histry.tab RMR_Mde Change Histry.tab RMR_Frmat Change Histry.tab 6. Distributin A cmplete distributin f the Registry f Ministry Resurces includes: RMR.htm (this dcument) An RMR Nte dcument with fur supprting files: RMR_Nte_FAQ.htm RMRsampleRel.gif RMRsampleRelAlt.gif RMRallRel.gif RMR_ExcelExample.xls five HTML frmatted cde tables t be used fr human reference: RMR_ScriptureScpe.htm RMR_ScriptureType.htm RMR_Cntent.htm RMR_Mde.htm RMR_Frmat.htm five tab-delimited cde tables t be used fr lading int a database: RMR_ScriptureScpe.tab RMR_ScriptureType.tab RMR_Cntent.tab Page 9 f 10
RMR_Mde.tab RMR_Frmat.tab five tab-delimited cde tables giving cde change histries: RMR_ScriptureScpe Change Histry.tab RMR_ScriptureType Change Histry.tab RMR_Cntent Change Histry.tab RMR_Mde Change Histry.tab RMR_Frmat Change Histry.tab These are all available in a single zip file: RMR 2006-10-11.zip Page 10 f 10