{"action":"created","issue":{"url":"https://api.github.com/repos/adobe/xdm/issues/40","repository_url":"https://api.github.com/repos/adobe/xdm","labels_url":"https://api.github.com/repos/adobe/xdm/issues/40/labels{/name}","comments_url":"https://api.github.com/repos/adobe/xdm/issues/40/comments","events_url":"https://api.github.com/repos/adobe/xdm/issues/40/events","html_url":"https://github.com/adobe/xdm/issues/40","id":281476295,"number":40,"title":"Method of defining tags or keyword","user":{"login":"ieb","id":68709,"avatar_url":"https://avatars2.githubusercontent.com/u/68709?v=4","gravatar_id":"","url":"https://api.github.com/users/ieb","html_url":"https://github.com/ieb","followers_url":"https://api.github.com/users/ieb/followers","following_url":"https://api.github.com/users/ieb/following{/other_user}","gists_url":"https://api.github.com/users/ieb/gists{/gist_id}","starred_url":"https://api.github.com/users/ieb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ieb/subscriptions","organizations_url":"https://api.github.com/users/ieb/orgs","repos_url":"https://api.github.com/users/ieb/repos","events_url":"https://api.github.com/users/ieb/events{/privacy}","received_events_url":"https://api.github.com/users/ieb/received_events","type":"User","site_admin":false},"labels":[{"id":769113006,"url":"https://api.github.com/repos/adobe/xdm/labels/enhancement","name":"enhancement","color":"84b6eb","default":true},{"id":769113007,"url":"https://api.github.com/repos/adobe/xdm/labels/help%20wanted","name":"help wanted","color":"33aa3f","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2017-12-12T17:42:36Z","updated_at":"2017-12-13T22:35:25Z","closed_at":null,"author_association":"NONE","body":"## What are the schemas that are affected by the issue\r\n\r\nhttps://ns.adobe.com/xdm/assets/asset\r\nbut might be its own schema or impact other schema.\r\n\r\n## What are examples of products that are impacted by the issue\r\n\r\nAEM and other products that store content that needs to be tagged.\r\n\r\n\r\nWhile the assets schema has xmp:keywords and xmp:machineKeywords which might be used to tag an asset with a keyword, there is no XDM way of describing a keyword or organising a keyword into an ontology of tags, even if that ontology is flat.\r\n\r\nMany products that store content organise that content using tags and organise those tags into an ontology. Some examples:\r\n\r\nExample 1.\r\nIn a DAM, Photographs may be tagged with \"cars\" which would be organised as a narrower term for \"vehicles\" and cards would contain narrower terms of \"performance\", \"family\".\r\n\r\nExample 2.\r\nIn a Drugs dictionary, Documents containing medical advice for prescription drugs may be tagged with the family of drug and the families of drugs that cause adverse interactions, hence a patient taking Asprin, classified as a salicylate and a nonsteroidal anti-inflammatory drug would alerted that it has a serious interaction with Ketorolac, by virtue of Aspirin being a NSAIDs. Each tag would be defined in a managed ontology. \r\n\r\nExample 3.\r\nIn an audience targeting platform, the segments into which browsers are placed would be related to one another.\r\n\r\n\r\nThe structure of defined tags or keywords needs to support both hierarchical (DAG) and non DAG type graphs, although most uses are probably for hierarchical relationships rather than multi faceted relationships between the keyword or tag definitions.\r\n\r\nThe ask is for\r\na) A schema to define the tags and keywords\r\nb) a mechanism to define the relationships between those definitions.\r\n"},"comment":{"url":"https://api.github.com/repos/adobe/xdm/issues/comments/351547331","html_url":"https://github.com/adobe/xdm/issues/40#issuecomment-351547331","issue_url":"https://api.github.com/repos/adobe/xdm/issues/40","id":351547331,"user":{"login":"trieloff","id":39613,"avatar_url":"https://avatars3.githubusercontent.com/u/39613?v=4","gravatar_id":"","url":"https://api.github.com/users/trieloff","html_url":"https://github.com/trieloff","followers_url":"https://api.github.com/users/trieloff/followers","following_url":"https://api.github.com/users/trieloff/following{/other_user}","gists_url":"https://api.github.com/users/trieloff/gists{/gist_id}","starred_url":"https://api.github.com/users/trieloff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trieloff/subscriptions","organizations_url":"https://api.github.com/users/trieloff/orgs","repos_url":"https://api.github.com/users/trieloff/repos","events_url":"https://api.github.com/users/trieloff/events{/privacy}","received_events_url":"https://api.github.com/users/trieloff/received_events","type":"User","site_admin":false},"created_at":"2017-12-13T22:35:25Z","updated_at":"2017-12-13T22:35:25Z","author_association":"COLLABORATOR","body":"> Keywords don't live in `xmp:keywords`. They live in the Dublin Core Subject `dc:subject` AND in the Lightroom Hierarchical Subject `lr:hierarchicalSubject` nodes. Bridge and Lightroom understand that these two nodes define the lowest level keyword AND the hierarchy in which the keyword resides. AEM does not understand this multi-node metadata behavior.\r\n\r\nI forgot about `dc:subject` and we do not have `lr: hierarchicalSubject` defined. @lrosenthol should we?"}}
{"actor":{"display_login":"trieloff"}}