First of all thank you for your work on the BIBFRAME Profiles. I think the notion of profiles will be increasingly important in the library community, and perhaps particularly for an exchange format like BIBFRAME that is not tied to a specific cataloguing code. I see some overlap with the work being done on RDF application profiles so I copy the DCMI Architecture List.

Having studied the document on BIBFRAME Profiles [1] I have some questions and hope that someone can shed some light here.

§2.2 Resource Template
How do the resourceURI and the resourceLabel relate to each other? My first understanding was that the resourceLabel is the label of the resource available at the resourceURI (and thus available by dereferencing the resourceURI). In the example (Fig 2.2a), however, there is the resourceLabel Book” and the resourceURI (which is not a book). Can you please expand a bit on this in the document?

§2.4 Value Constraint
Here, too, there is confusion regarding the relation between *URI and *label. The preferred way to express values or relations should always be URIs or – if not available – codes (e. g. ISO 639 language codes).

The value constraint “editable” specifies as value “URI”. Shouldn’t that be “Boolean”?

§2.5 Value datatype
Is there a reason not to use the XML schema datatypes, where applicable, and to define RDF/OWL datatypes (subclass of rdfs:Datatype and OWL Restrictions) when you need new ones? In Figure 2.5, you could just specify xsd:date.

§4 Serialisation
Is there a reason to restrict the available serialisations? In general you could say that any existing (RDFXML, Turtle, N-Triples, JSON-LD, …) or future RDF serialization is acceptable in BIBFRAME? And yes, examples please in Turtle.

§6.1 Default BIBFRAME Profile
Here I don’t understand what you mean by saying “Human readable labels for the display are extracted from the RDF schema associated with the class identifiers”. Which “class identifiers” do you refer to? And: If you can extract the label by dereferencing a URI, why repeat it in the profile?

In the example you use the domain name “”. In order to make sure that you do not (by accident) use a domain name actually used by someone, it would be better to use the domains or or their subdomains, e. g.

§6.2 RDA as a BIBFRAME Profile
Shouldn’t the frbr:Item map to bf:HeldItem instead of to bf:Instance?


Thanks for any insights,


*** Lesen. Hören. Wissen. Deutsche Nationalbibliothek *** 
Dr. Lars G. Svensson
Deutsche Nationalbibliothek
Telefon: +49-69-1525-1752
mailto:[log in to unmask]