Jana, the purpose of bflc is for us to park things that are either :
a) only thought to be useful to LC (think 9xx in MARC) or
b) potentially useful in BIBFRAME, but we want to test it out first.
Since it is much easier to add than to delete, I would say that any nodes in bflc will stay there, especially in that version of bflc. A final outcome for a property or class may be "promotion" to BIBFRAME itself, or deprecation if we determine it is unhelpful, but not deletion within a given ontology file. Even promotion to bibframe would not mean deletion, since in BIBFRAME it might be implemented in a slightly different way, and for stability concerns such as you have raised.
LC will be coming out with some versioning documentation for updates to both BIBFRAME and BFLC in the near future, taking ideas from the https://bibliotek-o.org/ bibliotek-o extension ontology.
Hope that helps!
Network Development & MARC Standards Office
LA308, Mail Stop 4402
Library of Congress
Washington DC 20540
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Hentschke, Jana
Sent: Thursday, April 26, 2018 5:58 AM
To: [log in to unmask]
Subject: [BIBFRAME] Persistence of LC's BIBFRAME extension vocabulary?
We were wondering about the status of the vocab http://id.loc.gov/ontologies/bflc/.
Did LC colleagues state anything about its projected maintenance and persistence? (A quick look at http://id.loc.gov-Pages and a naïve search on this list and the web didn't immediately answer the question - apologies if I missed something)
My reason for asking is that we are considering to reuse bflc:projectedProvisionDate in our application profile. We would do so only if the vocab status is not - let's say - experimental/unstable/testing...
Thanks in advance and best regards from Germany, Jana
*** Reading. Listening. Understanding. German National Library***
Deutsche Nationalbibliothek / German National Library Information Infrastructure Adickesallee 1
60322 Frankfurt am Main
Telefon: +49 69 1525-1773
mailto:[log in to unmask]