{"action":"created","issue":{"url":"https://api.github.com/repos/TEIC/TEI/issues/1414","labels_url":"https://api.github.com/repos/TEIC/TEI/issues/1414/labels{/name}","comments_url":"https://api.github.com/repos/TEIC/TEI/issues/1414/comments","events_url":"https://api.github.com/repos/TEIC/TEI/issues/1414/events","html_url":"https://github.com/TEIC/TEI/issues/1414","id":122354402,"number":1414,"title":"ogrophy elements should be in att.canonical","user":{"login":"sydb","id":124655,"avatar_url":"https://avatars.githubusercontent.com/u/124655?v=3","gravatar_id":"","url":"https://api.github.com/users/sydb","html_url":"https://github.com/sydb","followers_url":"https://api.github.com/users/sydb/followers","following_url":"https://api.github.com/users/sydb/following{/other_user}","gists_url":"https://api.github.com/users/sydb/gists{/gist_id}","starred_url":"https://api.github.com/users/sydb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sydb/subscriptions","organizations_url":"https://api.github.com/users/sydb/orgs","repos_url":"https://api.github.com/users/sydb/repos","events_url":"https://api.github.com/users/sydb/events{/privacy}","received_events_url":"https://api.github.com/users/sydb/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/TEIC/TEI/labels/category:FeatureRequest","name":"category:FeatureRequest","color":"c7def8"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-15T20:02:34Z","updated_at":"2015-12-16T10:01:18Z","closed_at":null,"body":"It is simple hubris for us to presume that any given project's TEI contextual information is the be-all and end-all of data about the places with information is stored therein. An entry in a placeography, personography, bibliography, or whatever should be able to refer (using `@ref` or `@key`) to some other data structure that has further information about the same entity.\r\n\r\nI may well want to refer to a gazeteer elsewhere in addition to storing local information about the places in my corpus. At the moment, the only intelligent way I can do that (presuming I have structured data, not a sequence of paragraphs — why can't I have both?) is to develop some local convention like using `@ref` of a `<placeName>` child of `<place>`, or to put something like a `<ptr>` in a `<note>`. (Why can I have a `<link>` in a `<place>`, but not a `<ptr>`?)\r\n\r\nImagine a project that wants to keep track of the people mentioned in a set of mid-20th century American texts. The project wants to do two things with each contributing author’s name: a) to disambiguate it, so the reader can know exactly who is being referred to, and b) to annotate it with his rank within the Salvation Army, or her status as a practitioner of rheumatology (e.g. in med school, in residency, in fellowship, member of the American college of Rheumatology, faculty of the American college of Rheumatology) or whatever.\r\n\r\nSo, the project wants a TEI personography where each entry `<person>` has both a)  a reference to the persons entry in the Library of Congress name authority file, and b) their rank or status or whatever. My point is we provide no consistent way to do (a), and we should. I think the best way to do this is by allowing `@ref` (and `@key` for the web-impaired) on `<person>` and `<place>` (and I suppose `<org>`, `<bibl>`, and `<biblStruct>`, too)."},"comment":{"url":"https://api.github.com/repos/TEIC/TEI/issues/comments/165053676","html_url":"https://github.com/TEIC/TEI/issues/1414#issuecomment-165053676","issue_url":"https://api.github.com/repos/TEIC/TEI/issues/1414","id":165053676,"user":{"login":"bansp","id":312137,"avatar_url":"https://avatars.githubusercontent.com/u/312137?v=3","gravatar_id":"","url":"https://api.github.com/users/bansp","html_url":"https://github.com/bansp","followers_url":"https://api.github.com/users/bansp/followers","following_url":"https://api.github.com/users/bansp/following{/other_user}","gists_url":"https://api.github.com/users/bansp/gists{/gist_id}","starred_url":"https://api.github.com/users/bansp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bansp/subscriptions","organizations_url":"https://api.github.com/users/bansp/orgs","repos_url":"https://api.github.com/users/bansp/repos","events_url":"https://api.github.com/users/bansp/events{/privacy}","received_events_url":"https://api.github.com/users/bansp/received_events","type":"User","site_admin":false},"created_at":"2015-12-16T10:01:18Z","updated_at":"2015-12-16T10:01:18Z","body":"But then, James, you'd need a schema/grammar for link sequences, especially if you have more than one private URI of the same scheme there. Tricky tricky."}}