[Ssc-dev] CFP J3M Workshop/Tutorial Draft

[Bryan Nunez]

Thanks Barbra!

I will add your suggestion to the submission and try to turn it in by the
end of the day.  If anyone else has something to add please let me know
asap!

Thanks,
Bryan

On Fri, Mar 1, 2013 at 8:29 AM, barbra <blmack at gmail.com> wrote:

> HI Bryan
>
> Actually, I think it sounds pretty good as is. I would attend :-)
>
> I know that the workshop is more focused on the metadata. But I guess if
> you wanted to add anything, you might want to also dedicate 5 mins to how a
> developer could use libraries developed for J3M. Not in depth, but just a
> short discussion about the android libraries available, what they mix with,
> and how these can be used in accompanying server, and point to the git
> repos, etc. If any developers attended, they might be interested.
>
> -barbra
>
> On Thu, Feb 28, 2013 at 12:42 PM, Bryan Nunez <bryan at witness.org> wrote:
>
>> Hi all,
>>
>> I took a stab at writing up a description of J3M-centered session for the
>> CFP.  I'm not sure if we should run it as a workshop or a tutorial.  I also
>> need a couple more points for the discussion outline.  It's due tomorrow so
>> if you have suggestions let me know.
>>
>> Thanks,
>> Bryan
>>
>> Among the general public, there's a vague understanding about the
>> metadata contained in media files and that this metadata can contain
>> information that can be used to identify the origin of an image or video.
>>  Deleting this metadata from the original file is a quick and dirty
>> approach to protecting one's privacy, but there are often times when this
>> metadata is useful.  As more and more mobile media finds it way into the
>> mainstream news, the need for verification mechanisms increase.   Embedded
>> metadata is one way to provide contextual information that can help
>> validate a piece of media, but it can sometimes contain sensitive
>> information that could put sources at risk.
>>
>> Within the human rights, legal, and journalism communities, there is a
>> need for a way to preserve and enhance the metadata within mobile media
>> files while at the same time protecting any information considered
>> sensitive.  The Guardian Project in collaboration with WITNESS, are working
>> on the creation of developer libraries that handle the capture of mobile
>> phone sensor data, cryptographic signing, and encryption.  This data can be
>> packaged into a standardized format which allows the data to be used across
>> different applications.  This data format, J3M (JSON Evidentiary Mobile
>> Media Metadata), encapsulates three top level objects:  Intent, Content,
>> and Data.  These objects describe the who, what, when, where, why, and how
>> of a media object.
>>
>> This (tutorial/workshop) will use J3M as well as existing metadata
>> standards as starting point to discuss potential implementations of
>> metadata standards with privacy or cryptographic features and the possible
>> limitations of such formats. We will look at how this data might be used
>> and review other systems with similar functionality.
>>
>>
>>
>> --
>> Bryan Nunez
>> Technology Manager
>> WITNESS
>> +1 (718) 783-2000 x-348
>> GPG ID: 54E3286C7C631254
>> GPG Fingerprint: 6115 6A41 0F5A 9AA0 67B6 79D8 54E3 286C 7C63 1254
>>
>> Check out our Human Rights Channel <http://www.youtube.com/humanrights> on
>> YouTube
>>
>> _______________________________________________
>> Ssc-dev mailing list
>>
>> Post: Ssc-dev at lists.mayfirst.org
>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev
>>
>> To Unsubscribe
>>         Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org
>>         Or visit:
>> https://lists.mayfirst.org/mailman/options/ssc-dev/blmack%40gmail.com
>>
>> You are subscribed as: blmack at gmail.com
>>
>>
>


-- 
Bryan Nunez
Technology Manager
WITNESS
+1 (718) 783-2000 x-348
GPG ID: 54E3286C7C631254
GPG Fingerprint: 6115 6A41 0F5A 9AA0 67B6 79D8 54E3 286C 7C63 1254

Check out our Human Rights Channel <http://www.youtube.com/humanrights> on
YouTube
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20130301/66346bc6/attachment.html>