{"action":"created","issue":{"url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/12","repository_url":"https://api.github.com/repos/maieul/biblatex-bookinarticle","labels_url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/12/comments","events_url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/12/events","html_url":"https://github.com/maieul/biblatex-bookinarticle/issues/12","id":135099701,"number":12,"title":"field name / inheritance properties","user":{"login":"maieul","id":636640,"avatar_url":"https://avatars.githubusercontent.com/u/636640?v=3","gravatar_id":"","url":"https://api.github.com/users/maieul","html_url":"https://github.com/maieul","followers_url":"https://api.github.com/users/maieul/followers","following_url":"https://api.github.com/users/maieul/following{/other_user}","gists_url":"https://api.github.com/users/maieul/gists{/gist_id}","starred_url":"https://api.github.com/users/maieul/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maieul/subscriptions","organizations_url":"https://api.github.com/users/maieul/orgs","repos_url":"https://api.github.com/users/maieul/repos","events_url":"https://api.github.com/users/maieul/events{/privacy}","received_events_url":"https://api.github.com/users/maieul/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2016-02-20T16:57:19Z","updated_at":"2016-02-20T18:32:06Z","closed_at":null,"body":"Many remarks of @ClintEastwood on #10 made me thinking we should change the field name and the property, and think to a better datamodel.\r\n\r\nWhat are the contrainst for evolution:\r\n- not changing the meaning of the field of standard biblatex type.\r\n- changing as little as possible the field names of biblatex-bookinarticle.\r\n\r\nHere is the actually existing model.\r\n[biblatex-bookinarticle-crossref.pdf](https://github.com/maieul/biblatex-bookinarticle/files/139239/biblatex-bookinarticle-crossref.pdf)\r\n\r\nWe need to think to a better datamodel. Here is example with @mvcollection\r\n\r\nContrainst are : \r\n- Going from @mvcollection to @bookinincollection, by the the step of @collection and @incollection.\r\n- Have coherent name, as possible.\r\n- Be able to refers to the editor of:\r\n-* the @mvcollection\r\n-* the @collection\r\n-* the @bookinincollection\r\n\r\nSo we have to make distinction between two package:\r\n- one for the bottom level : the @book-in-something\r\n- one for adding translator/editor for the @mvcollection when being in @collection.\r\n\r\nSo what I would do is to write a new datamodel, and submit you. After that, take one week to be sure, and code only next week-end.\r\n\r\nSo @ClintEastwood, @moewew, @sonator, @doc73, what do you think of the general idea?\r\n"},"comment":{"url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/comments/186663068","html_url":"https://github.com/maieul/biblatex-bookinarticle/issues/12#issuecomment-186663068","issue_url":"https://api.github.com/repos/maieul/biblatex-bookinarticle/issues/12","id":186663068,"user":{"login":"moewew","id":6755835,"avatar_url":"https://avatars.githubusercontent.com/u/6755835?v=3","gravatar_id":"","url":"https://api.github.com/users/moewew","html_url":"https://github.com/moewew","followers_url":"https://api.github.com/users/moewew/followers","following_url":"https://api.github.com/users/moewew/following{/other_user}","gists_url":"https://api.github.com/users/moewew/gists{/gist_id}","starred_url":"https://api.github.com/users/moewew/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/moewew/subscriptions","organizations_url":"https://api.github.com/users/moewew/orgs","repos_url":"https://api.github.com/users/moewew/repos","events_url":"https://api.github.com/users/moewew/events{/privacy}","received_events_url":"https://api.github.com/users/moewew/received_events","type":"User","site_admin":false},"created_at":"2016-02-20T18:32:06Z","updated_at":"2016-02-20T18:32:06Z","body":"Ahh, again I didn't realise how smart your packages actually are ;-).\r\n\r\nThe new model looks very sensible to me. The four levels accumulate a pretty large number of fields that need intuitive names so people don't get lost. "}}