search

cc-archive / exif

Proposal for a formal way of expressing public license information in Exif
Creative Commons Zero v1.0 Universal
2 stars 5 forks source link

how to kick off discussion and feedback #1

Closed janetpkr closed 8 years ago

janetpkr commented 8 years ago

So I think this is good to start. Are there specific questions you'd want to ask and lead the discussion with @mattl @robmyers ? I'll be posing them on the WMF multimedia mailing list, in addition to reaching out 1:1 to platforms on the EXIF doc list.

I think important is to leave open how this goes (esp with WMF) and let platforms get their skin in the game by raising issues and needs.

mattl commented 8 years ago

It would probably be useful to have some sample code that can be used to set the tags.

We already have https://github.com/CreativeCommons-Seneca/cc-xmp-tag/tree/master/cc-xmp-tag which would need a little work to bring them to up spec.

janetpkr commented 8 years ago

Ok. I have this on my list:

write/clean this up with examples to share:

1) tool for individual users - web app: chooser, export in exif. allow cc to retain a copy do server side for prototype; consider client-side for later versions 2) proposed co-opted field for platforms to adopt

put on labs - share with WMF developers and WMC community, other platforms

mattl commented 8 years ago

I think the first step of a tool would be a command line proof of concept -- pass in a JPEG and some details about creator, title, license and it would update the JPEG.

Spec includes space in the Author and Title fields for a platform URL. I imagine those would be useful to a Flickr type platform.

janetpkr commented 8 years ago

Right, agree on the platform URL. Yeah, I think showing how it looks if a user were to use X platform to add fields would be good. When do you think we could get that up?

The flip side of this is the platform reading and retaining from external sources. A few platforms say they do leave in EXIF info. So if the EXIF fields are not filled in the standard way, should they strip and repopulate the fields according to the standard? But maybe this is one of the questions up for discussion.

mattl commented 8 years ago

I'd be interested to know what you'd expect if I take a photo from my own website (example.com/mattl/cat.jpg) -- put it on flickr (flickr.com/anne.other/1234567) -- download it from flickr and put it on Wikimedia Commons.... would the URL change from platform to platform, or would it stay as example.com forever?

janetpkr commented 8 years ago

I imagine the URL would change from platform to platform, esp if that is one of the incentives for platforms to adopt the standard. Of course platforms like WMC might be more interested in provenance and therefore let the original URL stand. But generally speaking, most platforms strip out the EXIF and add back their own or only pieces of it.

rheaplex commented 8 years ago

Changing the fields may be a question for legal (I don't know).

I can write a command line tool quickly?

janetpkr commented 8 years ago

I'm pretty sure it's up to the platform TOS @sarahpearson

In any case, these are questions and issues that will come up for discussion once we publish a draft and ask for comments.

@robmyers that would be great, so we can get this out the door

janetpkr commented 8 years ago

Checking in on status of this. Possible to publish this week so I can start reaching back out to platforms to meet them F2F when I'm in SF the week before ITW? I would need to start schedule the meetings ASAP.

mattl commented 8 years ago

Are you just waiting on a command line tool?

janetpkr commented 8 years ago

That and I'm not sure if you were still planning to do a post on labs? Or is this Github post it.

mattl commented 8 years ago

We should probably just post it to the various lists

janetpkr commented 8 years ago

Ok, what about the command line tool, though? Should I go ahead and kick off a discussion without it?

mattl commented 8 years ago

I suspect @robmyers will have that finished today.

janetpkr commented 8 years ago

Great. I'll wait to reach out until we have that then.

rheaplex commented 8 years ago

I'm sorry, I'm at the dentist this afternoon. I'll get that done tomorrow.

janetpkr commented 8 years ago

Hey @robmyers, how's the command line tool going?

rheaplex commented 8 years ago

The tool is now being debugged - development was more involved than expected.

rheaplex commented 8 years ago

Ah I wrote that before I saw your comment. Yes It's almost ready to go it's just been a pain to get working properly.

mattl commented 8 years ago

Jane tool is good to go: https://github.com/creativecommons/exif/commit/a4b84da7e323086a6afb14992e3a474b9709d293

janetpkr commented 8 years ago

Cool! But ah, is it testable by a lay person like me?

mattl commented 8 years ago

I'm going to make a GIF showing how it works for you. We're debugging it a little more first.

mattl commented 8 years ago

out-5

mattl commented 8 years ago

Rob, see a bit of a weird bug above on that minor error JPEG, but it handles the other one (from Wikipedia) no problem

rheaplex commented 8 years ago

The [warning] that has to be suppressed? That's expected behaviour.

The software doesn't ignore it automatically as we don't want to make an unexpected change to the user's file (it's a problem during writing). Using --ignoreminorerrors ( -m is easier...) is the same as in exiftool. As it's not for production we can change it to be the default if we think that's better?

janetpkr commented 8 years ago

Ready to share?

mattl commented 8 years ago

I'd say so, yep.

rheaplex commented 8 years ago

Yes let's send this out into the world. :-)

janetpkr commented 8 years ago

Cool. So where is the link to the tool exactly? Is it just a bunch of code for now? Or is there something for a lay user to try?

mattl commented 8 years ago

Command line tool in the repo, so point people to the repo for both the description and the tool.

I don't know if the lay user is manipulating the Exif tags on their own JPEGs.

janetpkr commented 8 years ago

Ok. I'm thinking more product people (non-developers), but this should be fine to start.

mattl commented 8 years ago

I'm not sure what the tool would look like for them. A web page where you upload an image?

janetpkr commented 8 years ago

Yeah.

On Tue, Feb 9, 2016 at 3:26 PM, Matt Lee notifications@github.com wrote:

I'm not sure what the tool would look like for them. A web page where you upload an image?

— Reply to this email directly or view it on GitHub https://github.com/creativecommons/exif/issues/1#issuecomment-182131848.

Jane Park Director of Platforms and Partnerships Creative Commons | Los Angeles @janedaily

https://stateof.creativecommons.org/ Get updates: http://bit.ly/commonsnews

mattl commented 8 years ago

Yeah, that's not typically how these things are done. You build for developers, and developers at $PLATFORM can build something for their own people. Our code is a proof of concept for the developers.

janetpkr commented 8 years ago

Ok, sounds good.

On Tue, Feb 9, 2016 at 3:30 PM, Matt Lee notifications@github.com wrote:

Yeah, that's not typically how these things are done. You build for developers, and developers at $PLATFORM can build something for their own people. Our code is a proof of concept for the developers.

— Reply to this email directly or view it on GitHub https://github.com/creativecommons/exif/issues/1#issuecomment-182132926.

Jane Park Director of Platforms and Partnerships Creative Commons | Los Angeles @janedaily

https://stateof.creativecommons.org/ Get updates: http://bit.ly/commonsnews