Print

Print


The example shows that Bibframe is not different from MARC.

Data wrapped in verbose statements, with fillers like "v." or "pt.", is not
suitable for entities being linked and queried on the web. So, there should
no properties in Bibframe that contain pre-formatted information, like the
"statements" in MARC.

I would rather prefer an enhanced knowledge representation like this:

<journal1> a fabio:Journal;
    prism:publicationName "International archives of photogrammetry and
remote sensing"@en,
        "Internationales Archiv der Photogrammetrie und Fernerkundung"@de ;
    prism:issn "0256-1840";
    prism:volume "30";
    prism:part "3" .

<journal2> a fabio:AcademicProceedings, fabio:Journal;
    prism:publicationName "SPIE proceedings series";
    prism:issn "0277-786X";
    prism:volume "2357" .

<instance> frbr:partOf <journal1>, <journal2> .

Then, it is up to the interpreting program to print a formatted "series
statements" for the librarian, by calling it "Series", by adding fillers
etc.

Just my 2 cents.

Best regards,

Jörg


On Tue, May 31, 2016 at 4:55 PM, Joseph Kiegel <[log in to unmask]> wrote:

> The treatment of series information in BIBFRAME 2.0 is a significant
> improvement over 1.0.  It provides for transcription of series and
> subseries in a straightforward way.
>
>
>
> However, one problem remains:  how to handle multiple series and to keep
> associated series statements and enumerations together.  For example, take
> these series, which appear on a book:
>
> International archives of photogrammetry and remote sensing, 0256-1840 ;
> v. 30, pt. 3 = Internationales Archiv der Photogrammetrie und Fernerkundung
> ; Bd. 30, Teil 3
>
> SPIE proceedings series, 0277-786X ; v. 2357
>
>
>
> In 2.0, this becomes:
>
> < Instance> bf:seriesStatement “International archives of photogrammetry
> and remote sensing, 0256-1840 = Internationales Archiv der Photogrammetrie
> und Fernerkundung” ;
>
>                bf:seriesStatement “SPIE proceedings series, 0277-786X” ;
>
>                bf:seriesEnumeration “v. 30, pt. 3 = Bd. 30, Teil 3”  ;
>
>                bf:seriesEnumeration “v. 2357” .
>
>
>
> Unfortunately, there is no way to associate each of the
> bf:seriesEnumeration properties with its corresponding bf:seriesStatement
> in a way that machines understand.
>
>
>
> A possible solution is to introduce, for example, a class Series and a
> property bf:series, which would be used with Work or Instance and expect
> Series.  The existing properties bf:seriesStatement, bf:seriesEnumeration,
> bf:subseriesStatement, and bf:subseriesEnumeration would be used with
> Series and expect Literal.
>
>
>
> The example would look like this:
>
> < Instance> bf:series [ a bf:Series ;
>
>                               bf:seriesStatement “International archives
> of photogrammetry and remote sensing, 0256-1840 = Internationales Archiv
> der Photogrammetrie und Fernerkundung”  ;
>
>                               bf:seriesEnumeration “v. 30, pt. 3 = Bd. 30,
> Teil 3” ] ;
>
>                bf:series [ a bf:Series ;
>
>                               bf:seriesStatement “SPIE proceedings series,
> 0277-786X” ;
>
>                               bf:seriesEnumeration “v. 2357” ] .
>
>
>
> Multiple subseries would be handled in the same way, with
> bf:subseriesStatement and bf:subseriesEnumeration used in place of
> bf:seriesStatement and bf:seriesEnumeration.
>
>
>