Closed stoicflame closed 13 years ago
I'm not opposed to changing this. We should just make sure whatever term we use is general enough to encompass all types of records/documents.
On Sep 13, 2011, at 9:39 AM, Ryan Heatonreply@reply.github.com wrote:
I propose we rename 'document' to 'record' to conform to common convention, industry standard, and to more accurately reflect its generic use.
You can merge this Pull Request by running:
git pull https://github.com/FamilySearch/historical-data.org rename-document-to-record
Or you can view, comment on it, or merge it online at:
https://github.com/historical-data/schema/pull/21
-- Commit Summary --
- rename 'document' to 'record' to conform to common convention, industry standard, and to more accurately reflect its generic use.
-- File Changes --
M HistoricalEvent.html (4) M HistoricalFamily.html (4) M HistoricalPerson.html (4) R HistoricalRecord.html (30)
-- Patch Links --
https://github.com/historical-data/schema/pull/21.patch https://github.com/historical-data/schema/pull/21.diff
Reply to this email directly or view it on GitHub: https://github.com/historical-data/schema/pull/21
Hi. Just waking up this thread. Can I apply this?
Go for it.
On Sep 20, 2011, at 9:51 AM, Ryan Heatonreply@reply.github.com wrote:
Hi. Just waking up this thread. Can I apply this?
Reply to this email directly or view it on GitHub: https://github.com/historical-data/schema/pull/21#issuecomment-2147179
I propose we rename 'document' to 'record' to conform to common convention, industry standard, and to more accurately reflect its generic use.