<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<base href="http://rbms.info/cv-comments/feed/"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;
font-style:italic;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2004815034;
mso-list-template-ids:-180331258;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This was a nice FAQ about the future of the RBMS controlled vocab project, thanks to all for sharing it. A question, will we still be able to add $z and $y to
our terms, once they go 2.0? I’m particularly concerned about the provenance-related terms. I’m still struggling with the nuances of LOD, so it’s entirely possible that I’m not understanding something here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Enquiring minds want to know,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">andrea<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">-- <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">(Ms.) Andrea Cawelti
<br>
Ward Music Cataloger <br>
Houghton Library <br>
Harvard University <br>
Cambridge, MA 02138 <br>
<br>
Phone: (617) 998-5259<br>
FAX: (617) 495-1376 <br>
E-mail: <a href="mailto:cawelti@fas.harvard.edu">cawelti@fas.harvard.edu</a> <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Feed:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> RBMS Controlled Vocabularies Community Discussion<br>
<b>Posted on:</b> Thursday, July 26, 2018 1:58 PM<br>
<b>Author:</b> amyfbrown<br>
<b>Subject:</b> Frequently Asked Questions – Library of Congress Linked Open Data Hosting Solution<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<h5><span style="font-family:"Calibri",sans-serif;font-weight:normal">The RBMS Controlled Vocabularies Editorial Group (CVEG) seeks feedback on a partnership with the Library of Congress Linked Data Service (LDS) to host the RBMS Controlled Vocabularies (RBMS
CV). The CVEG has been investigating options for several years for making the RBMS CV available as Linked Open Data (LOD). Because of the technological infrastructure requirements, we are unable to host the vocabularies as LOD ourselves and have sought out
partnerships to pursue this important initiative. Below are some frequently asked questions about this project.
</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></h5>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">What is Linked Open Data (LOD)?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Releasing an authority file as Linked Open Data has a few basic requirements. Each thing, which in our case are individual terms, must:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri",sans-serif">Have a stable, unique, dereferenceable* URI<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri",sans-serif">Use a URI that provides useful information when queried by either humans or machines.
<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri",sans-serif">Use open data standards, such as <a href="https://en.wikipedia.org/wiki/Resource_Description_Framework">
RDF</a> or <a href="https://en.wikipedia.org/wiki/SPARQL">SPARQL</a><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri",sans-serif">Refer to other things when published<o:p></o:p></span></li></ul>
<p><span style="font-family:"Calibri",sans-serif">Linked Open Data makes traditional authority control much easier by relying on stable identifiers that point to a thing, rather than a string. For instance, in linked open data, the URI actually refers to a
conceptual understanding of “vellum bindings,” as opposed to simply listing the characters that compose the term “vellum bindings.” Using these URIs, developers can change preferred terms immediately, without having to manually change the character strings
displayed for users.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Relying on encoded relationships, LOD allows for searching, collocation and discovery across vocabularies, systems and encoding standards. In systems that take full advantage of LOD, information or examples
of certain concepts are easily findable and understandable by machines, which translates to easy findability of a resource via major search engines by people.<o:p></o:p></span></p>
<h5><span style="font-family:"Calibri",sans-serif">*</span><span style="font-family:"Calibri",sans-serif;font-weight:normal">Note: Dereferenceable URIs return human-readable information when queried through an http service. In other words, a dereferenceable
URI is one that you can point your browser to, and read the resulting web page.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></h5>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">Why should we release the RBMS CV as Linked Open Data?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Perhaps the most pressing reason is that releasing the RBMS CV as linked open data allows the vocabulary to be used more widely than by the cataloging community and outside of the MARC cataloging environment.
While this will be essential for BIBFRAME, it also enables easier use of the RBMS CV for other digital scholarship projects that exist outside MARC.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">As mentioned above, this project will also facilitate a higher level of authority control than was previously feasible with the RBMS CV. The RBMS CV will be available for download in a number of easily manipulatable
formats (RDF/XML, N-triples, and JSON) that can be utilized by most major authority control vendors.
<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Currently, Library of Congress vocabularies (including LCSH, LCGFT, and LCDGT), as well as AAT, are available as LOD. Releasing the RBMS CV data as LOD will allow for related concepts in different vocabularies
to be linked, thus improving overall discovery of library resources.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">How will I navigate the RBMS CV on the Library of Congress site?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Navigation of the vocabulary will be similar to other vocabularies available on the id.loc.gov site. To experiment, simply try searching a term
<a href="https://id.loc.gov/">here</a>. You can limit your search to a specific vocabulary by selecting it in the list below the search box. After implementation, you will be able to download the entire vocabulary from the “available datasets” section.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">Who will maintain the content of the RBMS CV?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">The Controlled Vocabularies Editorial Group, a committee of the Association of College and Research Libraries, a division of the American Libraries Association, will continue to maintain editorial control of
the RBMS CV. We will provide regular data dumps, probably quarterly, to the LC LDS, who will in turn host them on id.loc.gov.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">Will the terms change?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">No, the terms will not change. Concurrently, CVEG is working on a project to integrate and reorganize the RBMS CV. This project will result in new hierarchies and eliminate the need for parenthetical qualifiers
except in a few instances. The group will be providing updates on our blog as this project proceeds.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">Why not continue to host the RBMS CV as we do now?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">The current site is available in a simple html format. While this method provides a nice browsing interface, it makes even traditional library authority control difficult. Dynamic use outside of the MARC environment
is nearly impossible.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">As we strive to retain relevance and longevity over time, it is important for the RBMS CV to continue to adapt to changes in technologies and evolving standards, particularly given the Library of Congress’ continued
commitment to BIBFRAME.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">What other options have you considered?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">A lot! We looked into other partnerships, as well as hosting the vocabulary as LOD ourselves on rbms.info. Unfortunately, our website isn’t up to the challenge of providing both machines and humans the “useful
information” required to be LOD. Technically speaking, this means that the combination of our website software and server won’t be able to return machine-readable data formats (such as RDF or JSON) when queried.
<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">We also investigated other partnerships, and determined that the Library of Congress offers the best mix of usability, reliability and longevity available.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">What will happen to the current rbms.info/vocabularies site?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Because publication of LOD requires a single, stable URI to identify each thing, or, in our case, term, we will be retiring the current rbms.info site. This way, there will only be one referenceable http address
available for each term.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">As we proceed with integration, we are investigating the best methods of archiving the un-integrated thesaurus for authority control and record-keeping purposes. <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><i><span style="font-family:"Calibri",sans-serif">How long-term is this solution?</span></i><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">Although it is impossible to predict with absolute certainty the technological environment in the future, one requirement of LOD is that the URIs be stable over time. For this reason, hosting by LC LDS should
be considered a near-permanent solution. It would be very detrimental to switch publication solutions once the URIs are minted.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><em><span style="font-family:"Calibri",sans-serif">What is the proposed implementation date for this project?</span></em><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif">We do not have a specific date yet. However, implementation will necessarily take place after the integration and reorganization project is complete.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<h4><span style="font-family:"Calibri",sans-serif;font-weight:normal">Have other questions? Concerns? Feedback? Please let us know! We will be happy to receive comments here, or via e-mail at
<a href="mailto:vocabularies@rbms.info">vocabularies@rbms.info</a>.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></h4>
</td>
</tr>
</tbody>
</table>
<p><span style="font-family:"Calibri",sans-serif"><br>
<a href="http://rbms.info/cv-comments/2018/07/26/frequently-asked-questions-library-of-congress-linked-open-data-hosting-solution/">View article...</a><o:p></o:p></span></p>
</div>
</body>
</html>