<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Another ISO Standard: Bibliographic Data Element Directory</title>
	<atom:link href="http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/feed/" rel="self" type="application/rss+xml" />
	<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/</link>
	<description>Library and Information Technology Association</description>
	<pubDate>Fri, 21 Nov 2008 13:42:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Janifer Gatenby</title>
		<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-111913</link>
		<dc:creator>Janifer Gatenby</dc:creator>
		<pubDate>Wed, 11 Jun 2008 13:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-111913</guid>
		<description>OCLC Office of Research has mounted the database of mappings that was used in the consolidation process of ISO 8459.  The database is available for free search and browse at http://iso8459.oclc.org/.  Janifer</description>
		<content:encoded><![CDATA[<p>OCLC Office of Research has mounted the database of mappings that was used in the consolidation process of ISO 8459.  The database is available for free search and browse at <a href="http://iso8459.oclc.org/" rel="nofollow">http://iso8459.oclc.org/</a>.  Janifer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane Hillmann</title>
		<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-50525</link>
		<dc:creator>Diane Hillmann</dc:creator>
		<pubDate>Sun, 06 Jan 2008 18:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-50525</guid>
		<description>Janifer:

Making the data dictionary into a web service is an excellent idea.  I hope you'll keep us apprised of this work as it progresses.  As you may know, there's some work afoot to do something similar with RDA, which should fit very nicely into the environment you're thinking about.

Diane</description>
		<content:encoded><![CDATA[<p>Janifer:</p>
<p>Making the data dictionary into a web service is an excellent idea.  I hope you&#8217;ll keep us apprised of this work as it progresses.  As you may know, there&#8217;s some work afoot to do something similar with RDA, which should fit very nicely into the environment you&#8217;re thinking about.</p>
<p>Diane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janifer Gatenby</title>
		<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46989</link>
		<dc:creator>Janifer Gatenby</dc:creator>
		<pubDate>Mon, 17 Dec 2007 13:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46989</guid>
		<description>Diane,

We are currently in discussions with a potential maintenance agency about converting the mappings database and making it available as a web service.  The main point of the standard is as a base for protocol and schema standards rather than as a standard that any one system can implement and claim complaince.  The next step should be to identify more protocols and schemas that could be mapped and any other dictionaries of data elements.  I believe that DLF has one; it would be great if they could make it available.

Janifer</description>
		<content:encoded><![CDATA[<p>Diane,</p>
<p>We are currently in discussions with a potential maintenance agency about converting the mappings database and making it available as a web service.  The main point of the standard is as a base for protocol and schema standards rather than as a standard that any one system can implement and claim complaince.  The next step should be to identify more protocols and schemas that could be mapped and any other dictionaries of data elements.  I believe that DLF has one; it would be great if they could make it available.</p>
<p>Janifer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane Hillmann</title>
		<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46767</link>
		<dc:creator>Diane Hillmann</dc:creator>
		<pubDate>Thu, 13 Dec 2007 19:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46767</guid>
		<description>Janifer:

Thanks so much for this helpful context to the newly consolidated standard.  I find the goals in your final bullet points very compelling.  Do you think that the effort to accomplish those goals might be communicated fairly widely?  There's a lot of potential benefit reflected there, which sadly is difficult to realize in a closed standards environment.

Diane</description>
		<content:encoded><![CDATA[<p>Janifer:</p>
<p>Thanks so much for this helpful context to the newly consolidated standard.  I find the goals in your final bullet points very compelling.  Do you think that the effort to accomplish those goals might be communicated fairly widely?  There&#8217;s a lot of potential benefit reflected there, which sadly is difficult to realize in a closed standards environment.</p>
<p>Diane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janifer Gatenby</title>
		<link>http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46497</link>
		<dc:creator>Janifer Gatenby</dc:creator>
		<pubDate>Tue, 11 Dec 2007 13:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/2007/12/07/another-iso-standard-bibliographic-data-element-directory/#comment-46497</guid>
		<description>As part of the consolidation process, the data elements from the 5 parts were mapped to 8 protocols and ISO 2146, the registry standard.  This resulted in 545 elements and 674 mappings.  The alphabetical listing includes many synonyms.  The protocols mapped are EDItEUR, ISO ILL, NCIP, OpenURL Request Transfer Message, OAIPMH, Z39.50, SRU, ISO 2146 (Registries).  

The ISO Holdings Schema ISO 20775 which is also out to vote used ISO 8459 definitions, as did the Z39.50 Union Catalogue Profile (UCP) and part 4 was one of the input documents for NCIP.  There is also some interest in investigating the common elements among NCIP and ISO ILL from that part of the community.

The standard includes provision for a maintenance agency that will 
•	revise or correct data element definitions as the need arises
•	maintain a database of mappings of data elements to relevant protocol interchange and data schema standards
•	add new elements and definitions as the need arises
•	add new enumerated values or examples for data elements as the need arises
•	publish a web site with mappings and updated elements, values and definitions</description>
		<content:encoded><![CDATA[<p>As part of the consolidation process, the data elements from the 5 parts were mapped to 8 protocols and ISO 2146, the registry standard.  This resulted in 545 elements and 674 mappings.  The alphabetical listing includes many synonyms.  The protocols mapped are EDItEUR, ISO ILL, NCIP, OpenURL Request Transfer Message, OAIPMH, Z39.50, SRU, ISO 2146 (Registries).  </p>
<p>The ISO Holdings Schema ISO 20775 which is also out to vote used ISO 8459 definitions, as did the Z39.50 Union Catalogue Profile (UCP) and part 4 was one of the input documents for NCIP.  There is also some interest in investigating the common elements among NCIP and ISO ILL from that part of the community.</p>
<p>The standard includes provision for a maintenance agency that will<br />
•	revise or correct data element definitions as the need arises<br />
•	maintain a database of mappings of data elements to relevant protocol interchange and data schema standards<br />
•	add new elements and definitions as the need arises<br />
•	add new enumerated values or examples for data elements as the need arises<br />
•	publish a web site with mappings and updated elements, values and definitions</p>
]]></content:encoded>
	</item>
</channel>
</rss>
