<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Metadata and data structures	</title>
	<atom:link href="./index.html" rel="self" type="application/rss+xml" />
	<link>./../index.html</link>
	<description>Artist- and Librarian-At-Large</description>
	<lastBuildDate>
	Sat, 04 Jun 2016 18:04:58 +0000	</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.1.8</generator>
			<item>
				<title>
				By: Eric Lease Morgan				</title>
				<link>./../comment-page-1/index.html#comment-647</link>
		<dc:creator><![CDATA[Eric Lease Morgan]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 12:18:05 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=45#comment-647</guid>
					<description><![CDATA[Avi, thank you for the feedback.

If I understand your question correction, then I know for certain MARCXML is not designed to contain full-text mark-up. I&#039;m pretty sure MODS is the same way. Both are intended to contain bibliographic metadata. On the other hand, it would be entirely possible to included a link (think &quot;call number&quot;) in either a  MARCXML or MODS file pointing to the full-text of a journal article.

As for the mark-up of the journal article itself, I would advocate the use of TEI. Many might think this is overkill since TEI leans towards the very analytic and scholarly, but in reality, TEI is well-suited to general mark-up of text -- prose or poetry.

HTH. --ELM]]></description>
		<content:encoded><![CDATA[<p>Avi, thank you for the feedback.</p>
<p>If I understand your question correction, then I know for certain MARCXML is not designed to contain full-text mark-up. I&#8217;m pretty sure MODS is the same way. Both are intended to contain bibliographic metadata. On the other hand, it would be entirely possible to included a link (think &#8220;call number&#8221;) in either a  MARCXML or MODS file pointing to the full-text of a journal article.</p>
<p>As for the mark-up of the journal article itself, I would advocate the use of TEI. Many might think this is overkill since TEI leans towards the very analytic and scholarly, but in reality, TEI is well-suited to general mark-up of text &#8212; prose or poetry.</p>
<p>HTH. &#8211;ELM</p>
]]></content:encoded>
						</item>
						<item>
				<title>
				By: Avi Rappoport				</title>
				<link>./../comment-page-1/index.html#comment-642</link>
		<dc:creator><![CDATA[Avi Rappoport]]></dc:creator>
		<pubDate>Sat, 23 Aug 2008 01:42:24 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=45#comment-642</guid>
					<description><![CDATA[I&#039;m pretty much a fan of MODS at this point, it&#039;s much less fiddly than MARC for my purposes.  

However, I&#039;m wondering if there&#039;s any discussion of a &quot;full-text&quot; tag for journal articles, etc.  I don&#039;t mean articles that an author has posted, but something more general, like the PLoS or preprint servers.  In my case, there&#039;s no URI because the text doesn&#039;t exist as separate from its metadata, the MODS record *is* the online version.  Any guidance for me?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty much a fan of MODS at this point, it&#8217;s much less fiddly than MARC for my purposes.  </p>
<p>However, I&#8217;m wondering if there&#8217;s any discussion of a &#8220;full-text&#8221; tag for journal articles, etc.  I don&#8217;t mean articles that an author has posted, but something more general, like the PLoS or preprint servers.  In my case, there&#8217;s no URI because the text doesn&#8217;t exist as separate from its metadata, the MODS record *is* the online version.  Any guidance for me?</p>
]]></content:encoded>
						</item>
						<item>
				<title>
				By: Eric Lease Morgan				</title>
				<link>./../comment-page-1/index.html#comment-609</link>
		<dc:creator><![CDATA[Eric Lease Morgan]]></dc:creator>
		<pubDate>Wed, 06 Aug 2008 16:41:21 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=45#comment-609</guid>
					<description><![CDATA[Thank you for the feedback, and you make a number of great points.

Yes, the word &quot;properties&quot; would have been better than &quot;elements&quot; to describe Dublin Core items. Yes, exactly, RDF, just like METS, can be used to mix content from various vocabularies together into a single XML file. That is what I meant. Regarding SKOS, again, your distinction is more precise than my description.

The devil is in the details.]]></description>
		<content:encoded><![CDATA[<p>Thank you for the feedback, and you make a number of great points.</p>
<p>Yes, the word &#8220;properties&#8221; would have been better than &#8220;elements&#8221; to describe Dublin Core items. Yes, exactly, RDF, just like METS, can be used to mix content from various vocabularies together into a single XML file. That is what I meant. Regarding SKOS, again, your distinction is more precise than my description.</p>
<p>The devil is in the details.</p>
]]></content:encoded>
						</item>
						<item>
				<title>
				By: Bruce D'Arcus				</title>
				<link>./../comment-page-1/index.html#comment-608</link>
		<dc:creator><![CDATA[Bruce D'Arcus]]></dc:creator>
		<pubDate>Wed, 06 Aug 2008 15:44:40 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=45#comment-608</guid>
					<description><![CDATA[I don&#039;t mean to be pedantic, but you&#039;re conclusions are a little sloppy. You say:

1) &quot;Dublin Core does not define how data should be encoded. It is simply a list of elements.&quot;

So you&#039;re using a concept from XML (&quot;element&quot;) to describe a format that is independent of XML, and so in fact distorting its purpose in the process.

I&#039;d say the core DC terms (title, etc.) are data properties or attributes. But DC is of course much more than just those core terms thee days.

2) &quot;RDF is similar to METS&quot;

&quot;Similar&quot; how?? I see very little similarity, except at the most superficial level that both allow mixing of different metadata structures. RDF, however, is a data model; METS is not.

3) &quot;SKOS is an XML format for thesauri&quot;

SKOS is an RDF vocabulary that can (like any RDF) be serialized as XML. But it is NOT fundamentally an &quot;XML format.&quot;

I don&#039;t mean to pick on you, but if you&#039;re making sweeping suggestions like this, you need to be more careful about the details.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t mean to be pedantic, but you&#8217;re conclusions are a little sloppy. You say:</p>
<p>1) &#8220;Dublin Core does not define how data should be encoded. It is simply a list of elements.&#8221;</p>
<p>So you&#8217;re using a concept from XML (&#8220;element&#8221;) to describe a format that is independent of XML, and so in fact distorting its purpose in the process.</p>
<p>I&#8217;d say the core DC terms (title, etc.) are data properties or attributes. But DC is of course much more than just those core terms thee days.</p>
<p>2) &#8220;RDF is similar to METS&#8221;</p>
<p>&#8220;Similar&#8221; how?? I see very little similarity, except at the most superficial level that both allow mixing of different metadata structures. RDF, however, is a data model; METS is not.</p>
<p>3) &#8220;SKOS is an XML format for thesauri&#8221;</p>
<p>SKOS is an RDF vocabulary that can (like any RDF) be serialized as XML. But it is NOT fundamentally an &#8220;XML format.&#8221;</p>
<p>I don&#8217;t mean to pick on you, but if you&#8217;re making sweeping suggestions like this, you need to be more careful about the details.</p>
]]></content:encoded>
						</item>
			</channel>
</rss>
