-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moravian Lives schema docs - fix NERVE behaviour #233
Comments
Duplicate of #230 which is fixed, but not yet deployed |
not quite, I would say, @ajmacdonald , since The Moravian Lives schema has the same entity mappings as CWRC TEI lite )(and consequently should have NERVE assign the "proper" tags to identified named entities (i.e. persName, orgName, placeName, and NOT RS) |
Ah, I had the wrong mappings for the Moravian schema. So it should be the CWRC Basic Schema mappings then. |
right - it should be identical to TEI Lite. |
It got pushed using |
It's confusing because the cwrc version's url includes tei lite: https://cwrc.ca/schemas/cwrc_tei_lite.rng |
NOte that TEI Lite (the default, TEI consortium TEI Lite schema) uses RS only, but the CWRC TEI Lite schema is a CWRC TEI customization that does support nominal entity tags (persName, placeName, orgName) |
Right. My point is just that it can be easy to confuse the two. |
Document: https://dev-cwrc-writer.cwrc.ca/?githubPath=TestGitWriterSchemaCSSchange&githubRepo=ilovan%2FGit-Writer-tests
Two Errors:
NERVE identifies everything as person:

Once the NERVE-generated entities are all edited and accepted, they are all saved as RS tags.

Moravian Lives has the same entity mappings as the schemas listed here: #120
Moravian Lives itself was set up by @lucaju : cwrc/CWRC-GitWriter#65
May be related to how the handling is set up at: #194
The text was updated successfully, but these errors were encountered: