On Sun, Mar 29, 2009 at 11:06 AM, amit sethi <[email protected]> wrote: >>>use existing recommendations like ccREL/RDFa to specify and detect the >>>license information. If you're looking at an image on its own, XMP >>>already allows you to specify the license in an object so using that >>>existing standard is my preference. > Actually i now think this is a better idea at least for media. Sorry for > being ill informed .Also i hope i was not condescending . I was just excited > about the idea . >>there are use cases that an >>>HTTP header would address that existing approaches don't, we can talk >>>about it (although I'll warn you that I'm going to be super >>>skeptical). > well i think this could be a great help to bloggers.This way not only the > media content but the textual content they produce can also be licensed > under creative common .
Are you saying that the HTTP header would let bloggers license their text as well as their images, video, etc? RDFa lets us do this already. I admit it's very possible I'm missing something as I'm a little sleep deprived at the moment :). >>>An F-Spot licensing plugin generally (that presumably used >>>liblicense?) would be fantastic and a perfect SoC project. > That is great although i wish to take a day or two to research this project > before submitting a proposal .I am interested on how F-spot handles metadata > . Great. > Especially if do add such a plugin how F-spot is going to handle writing it > to flickr when it uploads such an image to flickr etc ... It can import xmp > tags on an image. I think the following are interesting features for an F-Spot plugin: * select a license for your photos, individually as well as a default * allow filtering the view by photos of a particular license (or property, ie, "allows remixing") * when uploading to Flickr, use the Flickr API to set the corresponding license (this may be a patch to the existing Flickr plugin) * if possible, do the same for Picasa (no idea if their API supports that) * embed XMP on export, possibly controlled by a flag (ie, "export with XMP") > If you could recommend some reading for research for the project proposal it > would be . I think the places to start are with F-Spot and Mono documentation. You could conceivably leave all the XMP stuff to liblicense, but we'll need to make Mono/C# bindings. I think this would be a great project and fill a big gap in the CC+FLOSS desktop tools story. Looking forward to your proposal. Nathan >>>Yeah, I'm not 100% certain about how oembed works... I think it >>>typically gets consumed and transformed into HTML for embedding. >>>Better (license aware) oembed consumers would be useful. Of course > yes , you are right again it does get consumed. I think XMP is again a > better solution . > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
