{"action":"created","issue":{"url":"https://api.github.com/repos/maidsafe/rfcs/issues/115","repository_url":"https://api.github.com/repos/maidsafe/rfcs","labels_url":"https://api.github.com/repos/maidsafe/rfcs/issues/115/labels{/name}","comments_url":"https://api.github.com/repos/maidsafe/rfcs/issues/115/comments","events_url":"https://api.github.com/repos/maidsafe/rfcs/issues/115/events","html_url":"https://github.com/maidsafe/rfcs/issues/115","id":146940245,"number":115,"title":"Discuss Proposed - 0028-launcher-low-level-api","user":{"login":"rossmuir","id":6030823,"avatar_url":"https://avatars.githubusercontent.com/u/6030823?v=3","gravatar_id":"","url":"https://api.github.com/users/rossmuir","html_url":"https://github.com/rossmuir","followers_url":"https://api.github.com/users/rossmuir/followers","following_url":"https://api.github.com/users/rossmuir/following{/other_user}","gists_url":"https://api.github.com/users/rossmuir/gists{/gist_id}","starred_url":"https://api.github.com/users/rossmuir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rossmuir/subscriptions","organizations_url":"https://api.github.com/users/rossmuir/orgs","repos_url":"https://api.github.com/users/rossmuir/repos","events_url":"https://api.github.com/users/rossmuir/events{/privacy}","received_events_url":"https://api.github.com/users/rossmuir/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2016-04-08T14:15:03Z","updated_at":"2016-04-15T14:48:32Z","closed_at":null,"body":"RFC > https://github.com/maidsafe/rfcs/tree/master/proposed/0028-launcher-low-level-api\r\nForum > https://forum.safenetwork.io/t/rfc-exposing-low-level-apis-for-structured-data-and-immutable-data-handling/8546"},"comment":{"url":"https://api.github.com/repos/maidsafe/rfcs/issues/comments/210489940","html_url":"https://github.com/maidsafe/rfcs/issues/115#issuecomment-210489940","issue_url":"https://api.github.com/repos/maidsafe/rfcs/issues/115","id":210489940,"user":{"login":"krishnaIndia","id":7702996,"avatar_url":"https://avatars.githubusercontent.com/u/7702996?v=3","gravatar_id":"","url":"https://api.github.com/users/krishnaIndia","html_url":"https://github.com/krishnaIndia","followers_url":"https://api.github.com/users/krishnaIndia/followers","following_url":"https://api.github.com/users/krishnaIndia/following{/other_user}","gists_url":"https://api.github.com/users/krishnaIndia/gists{/gist_id}","starred_url":"https://api.github.com/users/krishnaIndia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krishnaIndia/subscriptions","organizations_url":"https://api.github.com/users/krishnaIndia/orgs","repos_url":"https://api.github.com/users/krishnaIndia/repos","events_url":"https://api.github.com/users/krishnaIndia/events{/privacy}","received_events_url":"https://api.github.com/users/krishnaIndia/received_events","type":"User","site_admin":false},"created_at":"2016-04-15T14:48:32Z","updated_at":"2016-04-15T14:48:32Z","body":">This would be awesome. The ability to encrypt/decrypt byte arrays on behalf of the user would be a big plus. I still think that the public key should also be exposed since, besides the myriad of other reasons\r\n\r\nAdded the api for encryption and decryption. Also the public key of the user can be fetched to validate the owner\r\n\r\n>So just to confirm, the version is an opaque value that the devs can derive no meaning from? Meaning if I have two versions, there is nothing about the structure that I can use to determine which is later short of querying for the versions and seeing the index of each one? This is totally ok with me, I just want to understand.\r\n\r\nYes, version is an opaque value. Since the list is sorted the index can probably be some help I hope.\r\n\r\n> I was not aware there was a data map ID. I am still a bit rusty on the details, sorry. I definitely support a smaller representation of a data map, so that is good. I just don't understand how it is used or where this ID is stored.\r\n\r\nWhen the raw data is created a Datamap is obtained after the self-encryption process. This DataMap is saved as an immutable data in the network and the ID of the Immutable Data is returned. The DataMap can be encrypted or saved as is based on how the api is invoked (isEcrypted param).\r\n\r\nAlso added a api for fetching the metadata of the DataMap.\r\n\r\n> If I GET some SD with tag 11, how do I know whether I own it and can update it? Can this metadata be returned on GET?\r\n\r\nUpdated the RFC  to indicate that the owner can be sent in the header. I also thought of using a HEAD call but I felt it would be unnecessary and decided to send it in the same GET request for  StructuredData. Would like to know your thoughts on the same from a usage perspective. \r\n\r\nThanks @cretz "}}