From nathan at creativecommons.org Tue Nov 3 14:35:23 2009 From: nathan at creativecommons.org (Nathan Yergler) Date: Tue, 3 Nov 2009 11:35:23 -0800 Subject: [cc-devel] Added license information support on Evince In-Reply-To: <3635.10.160.5.69.1256686303.squirrel@correo.juntadeandalucia.es> References: <3635.10.160.5.69.1256686303.squirrel@correo.juntadeandalucia.es> Message-ID: HI Juanjo, That's great! I admit the situation with XMP isn't all that clear, but I don't think there's an inconsistency with what we're recommending. Let me take the fields/pieces one at a time. First, the XMP generated by the license chooser ([2] in your original message) defines three different things -- 1) xapRIghts:Marked is set to "True", indicating that there's rights information. 2) dc:rights contains a human readable statement about the license. 3) cc:license points to the actual license resource. So software displaying this information might show the contents of dc:rights and provide a license to cc:license if available. If you look at the description of xmpRights:WebStatement on http://wiki.creativecommons.org/XMP it indicates that it contains the "URL containing metadata about the XMP-embedded file". The XMP schema documentation describes it as "The location of a web page describing the owner and/or rights statement for this resource." So this isn't the license itself, but a page where more metadata or information is available (ie, maybe the copyright page for the work on my web site). Reviewing the schema documentation, I think you may be correct that our template needs to be updated in the following ways: 1) We need to use xmpRights as the RDF prefix for the XMP Rights schema (I believe this has changed in the XMP spec over the years). 2) We need to replace or supplement dc:rights with xmpRights:UsageTerms, as the schema documentation indicates this is human readable text for how the resource may be used. I've opened a ticket for that -- http://code.creativecommons.org/issues/issue505 Let me know if things still aren't clear or if I've missed something. Nathan 2009/10/27 Juan Jos? Mar?n Mart?nez : > Hi CC-developers, > > I added some basic license support for PDF documents on Evince [1], a document > viewer for multiple document formats from the GNOME desktop. > > The metadata I check for this is: > > 1) xmpRights:Marked > 2) dc:rights > 3) cc:license > 4) xmpRights:WebStatement > > However, I'm not quite sure if I've done the right thing because I've found > confusing information on the CC Wiki pages. > > On one hand, we are told to mark PDF files with dc:rights [2], but on another > hand, we are told to use xmpRights:UsageTerms for this [3]. > > What should I do ? .... And well, I think that the template or the XMP > instructions must be changed accordingly. > > TIA, > > ? -- Juanjo Mar?n > > [1] > http://git.gnome.org/cgit/evince/commit/?id=516c4e3273b664ee2b10d6348d3484726f4461fd > > [2] > http://creativecommons.org/license/xmp?q_1=2&q_1=1&field_commercial=yes&field_derivatives=yes&field_jurisdiction=us&field_format=&field_worktitle=&field_attribute_to_name=&field_attribute_to_url=&field_sourceurl=&field_morepermissionsurl=&lang=en_US&language=en_US&n_questions=3 > This link is on http://wiki.creativecommons.org/Marking/Creators , on the > instructions for PDF files. > > [3] http://wiki.creativecommons.org/XMP > > _______________________________________________ > cc-devel mailing list > cc-devel at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/cc-devel > From jajashabo at yahoo.com Thu Nov 5 18:04:23 2009 From: jajashabo at yahoo.com (Jaja Shabo) Date: Thu, 5 Nov 2009 15:04:23 -0800 (PST) Subject: [cc-devel] cc-devel Digest, Vol 51, Issue 1 Message-ID: <263612.54782.qm@web111808.mail.gq1.yahoo.com> HELLO jajashabo-arlenea, they don't understand that they have to paid in order to keep ther copyrights or licenses and need someone at your office to explain that to the general public of users to keep them informed of what is required to keep their business up and running.please keep me informed of the results i need to know something by tomorrow!! --- On Wed, 11/4/09, cc-devel-request at lists.ibiblio.org wrote: From: cc-devel-request at lists.ibiblio.org Subject: cc-devel Digest, Vol 51, Issue 1 To: cc-devel at lists.ibiblio.org Date: Wednesday, November 4, 2009, 6:20 PM Send cc-devel mailing list submissions to ??? cc-devel at lists.ibiblio.org To subscribe or unsubscribe via the World Wide Web, visit ??? http://lists.ibiblio.org/mailman/listinfo/cc-devel or, via email, send a message with subject or body 'help' to ??? cc-devel-request at lists.ibiblio.org You can reach the person managing the list at ??? cc-devel-owner at lists.ibiblio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of cc-devel digest..." Today's Topics: ???1. Re: Added license information support on Evince (Nathan Yergler) ---------------------------------------------------------------------- Message: 1 Date: Tue, 3 Nov 2009 11:35:23 -0800 From: Nathan Yergler Subject: Re: [cc-devel] Added license information support on Evince To: Juan Jos? Mar?n Mart?nez ??? Cc: cc-devel at lists.ibiblio.org Message-ID: ??? Content-Type: text/plain; charset=ISO-8859-1 HI Juanjo, That's great!? I admit the situation with XMP isn't all that clear, but I don't think there's an inconsistency with what we're recommending.? Let me take the fields/pieces one at a time. First, the XMP generated by the license chooser ([2] in your original message) defines three different things -- 1) xapRIghts:Marked is set to "True", indicating that there's rights information. 2) dc:rights contains a human readable statement about the license. 3) cc:license points to the actual license resource. So software displaying this information might show the contents of dc:rights and provide a license to cc:license if available. If you look at the description of xmpRights:WebStatement on http://wiki.creativecommons.org/XMP it indicates that it contains the "URL containing metadata about the XMP-embedded file".? The XMP schema documentation describes it as? ? ? ? ? ? ? ? ? ? "The location of a web page describing the owner and/or rights statement for this resource." So this isn't the license itself, but a page where more metadata or information is available (ie, maybe the copyright page for the work on my web site). Reviewing the schema documentation, I think you may be correct that our template needs to be updated in the following ways: 1) We need to use xmpRights as the RDF prefix for the XMP Rights schema (I believe this has changed in the XMP spec over the years). 2) We need to replace or supplement dc:rights with xmpRights:UsageTerms, as the schema documentation indicates this is human readable text for how the resource may be used. I've opened a ticket for that -- http://code.creativecommons.org/issues/issue505 Let me know if things still aren't clear or if I've missed something. Nathan 2009/10/27 Juan Jos? Mar?n Mart?nez : > Hi CC-developers, > > I added some basic license support for PDF documents on Evince [1], a document > viewer for multiple document formats from the GNOME desktop. > > The metadata I check for this is: > > 1) xmpRights:Marked > 2) dc:rights > 3) cc:license > 4) xmpRights:WebStatement > > However, I'm not quite sure if I've done the right thing because I've found > confusing information on the CC Wiki pages. > > On one hand, we are told to mark PDF files with dc:rights [2], but on another > hand, we are told to use xmpRights:UsageTerms for this [3]. > > What should I do ? .... And well, I think that the template or the XMP > instructions must be changed accordingly. > > TIA, > > ? -- Juanjo Mar?n > > [1] > http://git.gnome.org/cgit/evince/commit/?id=516c4e3273b664ee2b10d6348d3484726f4461fd > > [2] > http://creativecommons.org/license/xmp?q_1=2&q_1=1&field_commercial=yes&field_derivatives=yes&field_jurisdiction=us&field_format=&field_worktitle=&field_attribute_to_name=&field_attribute_to_url=&field_sourceurl=&field_morepermissionsurl=&lang=en_US&language=en_US&n_questions=3 > This link is on http://wiki.creativecommons.org/Marking/Creators , on the > instructions for PDF files. > > [3] http://wiki.creativecommons.org/XMP > > _______________________________________________ > cc-devel mailing list > cc-devel at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/cc-devel > ------------------------------ _______________________________________________ cc-devel mailing list cc-devel at lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/cc-devel End of cc-devel Digest, Vol 51, Issue 1 *************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/cc-devel/attachments/20091105/06811fcf/attachment.htm From wbossons at MIT.EDU Wed Nov 18 13:00:44 2009 From: wbossons at MIT.EDU (Wendy Bossons) Date: Wed, 18 Nov 2009 13:00:44 -0500 Subject: [cc-devel] CCO license class Message-ID: <03B697B8-A845-4501-ACE6-869C3B623939@mit.edu> Hello, I am still a newbie to CC, and am working on implementing the web service with DSpace (at MIT). Currently, DSpace is using the old integration approach. In that approach, there is an option for CCO, which I do not see as a possible response in the 1.5 CC api. What is the suggestion for the CCO option which was previously supported? regards, ..\Wendy Wendy Bossons Web Developer Contact Information: wbossons at mit.edu 617-253-0770 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1846 bytes Desc: not available Url : http://lists.ibiblio.org/pipermail/cc-devel/attachments/20091118/26a70364/attachment.bin From nathan at creativecommons.org Wed Nov 18 15:00:28 2009 From: nathan at creativecommons.org (Nathan Yergler) Date: Wed, 18 Nov 2009 12:00:28 -0800 Subject: [cc-devel] CCO license class In-Reply-To: <03B697B8-A845-4501-ACE6-869C3B623939@mit.edu> References: <03B697B8-A845-4501-ACE6-869C3B623939@mit.edu> Message-ID: HI Wendy, CC0's absence in the API is just an oversight/resource issue; we haven't had bandwidth to get it added to that system and no one had asked for it :/ . I've opened a ticket to track progress (http://code.creativecommons.org/issues/issue518) on adding it. Nathan On Wed, Nov 18, 2009 at 10:00 AM, Wendy Bossons wrote: > Hello, > > I am still a newbie to CC, and am working on implementing the web service > with DSpace (at MIT). Currently, DSpace is using the old integration > approach. In that approach, there is an option for CCO, which I do not see > as a possible response in the 1.5 CC api. What is the suggestion for the CCO > option which was previously supported? > > regards, > ..\Wendy > > Wendy Bossons > Web Developer > > Contact Information: > wbossons at mit.edu > 617-253-0770 > > > > > > > > _______________________________________________ > cc-devel mailing list > cc-devel at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/cc-devel > > From vecih at bol.com.br Fri Nov 20 07:46:58 2009 From: vecih at bol.com.br (Vanderci Eich) Date: Fri, 20 Nov 2009 10:46:58 -0200 Subject: [cc-devel] cc-devel Digest, Vol 51, Issue 4 In-Reply-To: References: Message-ID: <4b068fc29e6b6_5700be373e814@winter22.tmail> An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/cc-devel/attachments/20091120/6bb7cccd/attachment.htm