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, [email protected] <[email protected]> wrote: From: [email protected] <[email protected]> Subject: cc-devel Digest, Vol 51, Issue 1 To: [email protected] Date: Wednesday, November 4, 2009, 6:20 PM Send cc-devel mailing list submissions to [email protected] 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 [email protected] You can reach the person managing the list at [email protected] 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 <[email protected]> Subject: Re: [cc-devel] Added license information support on Evince To: Juan Jos? Mar?n Mart?nez <[email protected]> Cc: [email protected] Message-ID: <[email protected]> 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 <[email protected]>: > 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 > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > ------------------------------ _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel End of cc-devel Digest, Vol 51, Issue 1 ***************************************
_______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
