Closed rwarren2 closed 7 years ago
After discussion with @antimony27 and @SusanBrown, we will split NationalHeritageContext and NationalityContext as it is unclear what Orlando's granularity and use of tags is in practice. Also see Issue #63.
this needs to be captured in the ontology, then (adding this to my to-dos)
Sorry to muddy the waters but I don’t recall this discussion and right now feel happy with the idea of just a single NationalityContext rather than breaking them out. Simpler might be better?
On Jul 23, 2017, at 11:33 AM, lemaka notifications@github.com<mailto:notifications@github.com> wrote:
this needs to be captured in the ontology, then (adding this to my to-dos)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/cwrc/ontology/issues/64#issuecomment-317261383, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAhUoFXBYaEfplKtRe4aVqqrAq5klGJEks5sQ2fNgaJpZM4Nxuyk.
What happens when both Orlando tags exist, should the data be concatenated into the same instance?
If they share the same context string, then both triples should be linked to that context, if that is what you mean. There is only the NatioanalityIssue tag in the tagset so NationalHeritageContext would occur inside it if at all.
On Jul 25, 2017, at 12:11 AM, rwarren2 notifications@github.com wrote:
What happens when both Orlando tags exist, should the data be concatenated into the same instance?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cwrc/ontology/issues/64#issuecomment-317623622, or mute the thread https://github.com/notifications/unsubscribe-auth/AA1s9d8OLngJKRi7WmjqT6gKcheX3LC4ks5sRWrbgaJpZM4Nxuyk.
NationalityContext to be used in a all cases.
Can we have both NationalHeritage and Nationality covered by NationalityContext? I think that would be best.