LOC m2bf docs - Githubissues

dazza-codes commented 7 years ago

Keep a record of the LOC conversion specs in this repository for easy reference and for tracking them. Unless LOC are going to use some form of version control, this may be the only way to track their specs (and changes to their specs).

ndushay commented 7 years ago

Interesting idea, but I'm not comfortable keeping the LoC spec files in the code in this way. Here are some of my reasons:

they are not our documents ... we would have to clear permissions with them to share them in this way
in the past, for BF1, the changes to LoC specs did not make it back into their original spec documents ... they just went in their converter code. Their spec file became so stale they weren't sharing it.

I put spec-ish stuff in here originally because

it was only in mine and the senders' emails, otherwise
as I was starting out, I needed some sort of road map somewhere, and it happened to end up in here. I think it has been experienced a little bit as "noise" since then.

I'm going to close this and also tag @jgreben so he sees it.

dazza-codes commented 7 years ago

I'm not comfortable with unilateral decisions to close a PR without discussion.

jgreben commented 7 years ago

LOC does not want us publishing these specs, and they are out of date to boot. We are just using them as a springboard to get up a few tests and start a framework for further tests development by metadata staff.

ld4l-labs / marc2rdf-validator

LOC m2bf docs #23