{"action":"closed","issue":{"url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework/issues/17","repository_url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework","labels_url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework/issues/17/comments","events_url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework/issues/17/events","html_url":"https://github.com/GateNLP/gateplugin-LearningFramework/issues/17","id":145263017,"number":17,"title":"Support list-valued features as attributes","user":{"login":"johann-petrak","id":619106,"avatar_url":"https://avatars.githubusercontent.com/u/619106?v=3","gravatar_id":"","url":"https://api.github.com/users/johann-petrak","html_url":"https://github.com/johann-petrak","followers_url":"https://api.github.com/users/johann-petrak/followers","following_url":"https://api.github.com/users/johann-petrak/following{/other_user}","gists_url":"https://api.github.com/users/johann-petrak/gists{/gist_id}","starred_url":"https://api.github.com/users/johann-petrak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/johann-petrak/subscriptions","organizations_url":"https://api.github.com/users/johann-petrak/orgs","repos_url":"https://api.github.com/users/johann-petrak/repos","events_url":"https://api.github.com/users/johann-petrak/events{/privacy}","received_events_url":"https://api.github.com/users/johann-petrak/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/GateNLP/gateplugin-LearningFramework/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-04-01T19:20:32Z","updated_at":"2016-07-22T11:06:04Z","closed_at":"2016-07-22T11:06:04Z","body":"We should have a way to deal with a feature that contains a list of nominal values (possibly empty). Since we use, by default, one-of-k, this would be easy to extend to n-of-k where n is the number of distinct list elements. Strictly speaking if we really support lists (not sets) then each element may occur more than once and we should set the corresponding attribute to the count. \r\n\r\nThe attribute definition for a list attribute should allow to choose between representations of lists in a feature value. Probably either expecte List<String> or maybe just Collection<String> or a String where we give a separation char/string (e.g. |) ."}}
{"actor":{"display_login":"johann-petrak"}}