lcnetdev / marc2bibframe2

Convert MARC records to BIBFRAME2 RDF
http://www.loc.gov/bibframe/
Creative Commons Zero v1.0 Universal
86 stars 34 forks source link

language properties from 008/35-37 and 041 MARC codes #39

Open wafschneider opened 7 years ago

wafschneider commented 7 years ago

Currently, language properties from the 008/35-37 can have as their object a linked data resource from id.loc.gov, e.g.:

<bf:Work rdf:about="http://example.org/1#Work">
  <bf:language>
    <bf:Language rdf:about="http://id.loc.gov/vocabulary/languages/eng"/>
  </bf:language>
</bf:Work>

This seems a little more elaborate than necessary. Would it be better to just convert like this?

<bf:Work rdf:about="http://example.org/1#Work">
  <bf:language rdf:resource="http://id.loc.gov/vocabulary/languages/eng"/>
</bf:Work>

In addition, the 041 creates entities like this:

<bf:Work rdf:about="http://example.org/1#Work">
  <bf:language>
    <bf:Language>
      <bf:identifiedBy>
        <bf:Identifier>
          <rdf:value rdf:resource="http://id.loc.gov/vocabulary/languages/eng"/>
          <bf:source>
            <bf:Source rdf:about="http://id.loc.gov/vocabulary/languages"/>
          </bf:source>
        </bf:Identifier>
      </bf:identifiedBy>
    </bf:Language>
  </bf:language>
</bf:Work>

In the case where there is no bf:part property of the bf:Language entity, perhaps it would be better to simplify this down to the same pattern:

<bf:Work rdf:about="http://example.org/1#Work">
  <bf:language rdf:resource="http://id.loc.gov/vocabulary/languages/eng"/>
</bf:Work>
kirkhess commented 7 years ago

That makes more sense to me since that URI resolves to madsrdf and the bf:Source is the same as the madsrdf:isMemberOfMADSScheme

-Kirk

On Wed, Jun 7, 2017 at 3:16 PM, Wayne Schneider notifications@github.com wrote:

Currently, language properties for these elements can have as their object a linked data resource from id.loc.gov, e.g.:

This seems a little more elaborate than necessary. Would it be better to just convert like this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or mute the thread .