Creative Commons promotes standard license expression


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Creative Commons promotes standard license expression
# 1  
Old 05-07-2008
Creative Commons promotes standard license expression

Wed, 07 May 2008 18:00:00 GMT
If Creative Commons (CC) has any say in the matter, the Web will soon have a standard machine-readable notation for licenses. Named the Creative Commons Rights Expression Language (ccREL), the notation has been under development for the last few years, partly with the cooperation of the World Wide Web Consortium (W3). It is described in a paper by four Creative Commons employees and published by Communia, a European site that explores the relationship between technology and the public domain. Creative Commons plans future presentations of ccREL, and is also actively explaining the need for it -- which is what CC's Chief Technology Officer, Nathan Yergler, was doing when Linux.com caught up with him at the recent Open Web Conference in Vancouver.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
2 Replies

2. UNIX for Dummies Questions & Answers

Redirect Standard output and standard error into spreadsheet

Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway? Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies

3. Shell Programming and Scripting

standard error to standard out question

Hi there how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no... (5 Replies)
Discussion started by: hcclnoodles
5 Replies

4. SuSE

Creative Zen MicroPhoto File Transfer

hello I need help finding a file transfer program for suse linux compatible with a creative zen microphoto. I have tried kzenexplorer but it doesn't work. Any suggestions would be much appreciated. Thanks. (1 Reply)
Discussion started by: byronfarnum
1 Replies

5. Gentoo

Creative Zen Sleek Photo...

Hi all, My thanks in advance for reading and any posts. Just wondering if anyone knows of anywhere where I can get a driver from for a creative zen sleek photo for redhad Fedora? I ordered it stupidly without making sure that it would work on Fedora, seems that it only works on WinXP. ... (2 Replies)
Discussion started by: B14speedfreak
2 Replies
Login or Register to Ask a Question
Config::Model::models::Debian::Dpkg::Copyright::FileLiceUser3Contributed Perl DocuConfig::Model::models::Debian::Dpkg::Copyright::FileLicense(3pm)

NAME
Config::Model::models::Debian::Dpkg::Copyright::FileLicense - Configuration class Debian::Dpkg::Copyright::FileLicense VERSION
version 2.021 DESCRIPTION
Configuration classes used by Config::Model Elements short_name abbreviated name for the license. If empty, it is given the default value 'other'. Only one license per file can use this default value; if there is more than one license present in the package without a standard short name, an arbitrary short name may be assigned for these licenses. These arbitrary names are only guaranteed to be unique within a single copyright file. The name given must match a License described in License element in root node . Optional. Type uniline. Here are some explanations on the possible values: 'Apache' Apache license. For versions, consult the Apache_Software_Foundation. 'Artistic' Artistic license. For versions, consult the Perl_Foundation 'BSD-2-clause' Berkeley software distribution license, 2-clause version 'BSD-3-clause' Berkeley software distribution license, 3-clause version 'BSD-4-clause' Berkeley software distribution license, 4-clause version 'CC-BY' Creative Commons Attribution license 'CC-BY-NC' Creative Commons Attribution Non-Commercial 'CC-BY-NC-ND' Creative Commons Attribution Non-Commercial No Derivatives 'CC-BY-NC-SA' Creative Commons Attribution Non-Commercial Share Alike 'CC-BY-ND' Creative Commons Attribution No Derivatives 'CC-BY-SA' Creative Commons Attribution Share Alike license 'CC0' Creative Commons Universal waiver 'CDDL' Common Development and Distribution License. For versions, consult Sun Microsystems. 'CPL' IBM Common Public License. For versions, consult the IBM_Common_Public License_(CPL)_Frequently_asked_questions. 'EFL' The Eiffel Forum License. For versions, consult the Open_Source_Initiative 'Expat' The Expat license 'FreeBSD' FreeBSD Project license 'GFDL' GNU Free Documentation License 'GFDL-NIV' GNU Free Documentation License, with no invariant sections 'GPL' GNU General Public License 'ISC' Internet_Software_Consortium's license, sometimes also known as the OpenBSD License 'LGPL' GNU Lesser General Public License, (GNU Library General Public License for versions lower than 2.1) 'LPPL' LaTeX Project Public License 'MPL' Mozilla Public License. For versions, consult Mozilla.org 'Perl' Perl license (equates to "GPL-1+ or Artistic-1") 'Python-CNRI' Python Software Foundation license. For versions, consult the Python_Software Foundation 'QPL' Q Public License 'W3C' W3C Software License. For more information, consult the W3C IntellectualRights FAQ and the 20021231 W3C_Software_notice_and_license 'ZLIB' zlib/libpng_license 'Zope' Zope Public License. For versions, consult Zope.org Note: short_name is migrated with '$replace{$alias}' and with $alias => ""- - License-Alias"" and '$replace{Perl}' => ""Artistic or GPL-1+"" exception License exception. Optional. Type uniline. Here are some explanations on the possible values: 'Font' The GPL "Font" exception refers to the text added to the license notice of each file as specified at How_does_the_GPL_apply_to_fonts?. The precise text corresponding to this exception is: As a special exception, if you create a document which uses this font, and embed this font or unaltered portions of this font into the document, this font does not by itself cause the resulting document to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the document might be covered by the GNU General Public License. If you modify this font, you may extend this exception to your version of the font, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. 'OpenSSL' The GPL "OpenSSL" exception gives permission to link GPL-licensed code with the OpenSSL library, which contains GPL-incompatible clauses. For more information, see "The_-OpenSSL_License_and_The_GPL" by Mark McLoughlin and the message "middleman_software_license_conflicts_with_OpenSSL" by Mark McLoughlin on the debian-legal mailing list. The text corresponding to this exception is: In addition, as a special exception, the copyright holders give permission to link the code of portions of this program with the OpenSSL library under certain conditions as described in each individual source file, and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than OpenSSL. If you modify file(s) with this exception, you may extend this exception to your version of the file (s), but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. If you delete this exception statement from all source files in the program, then also delete it here. full_license if left blank here, the file must include a stand-alone License section matching each license short name listed on the first line (see the Standalone License Section section). Otherwise, this field should either include the full text of the license(s) or include a pointer to the license file under /usr/share/common-licenses. This field should include all text needed in order to fulfill both Debian Policy requirement for including a copy of the software distribution license, and any license requirements to include warranty disclaimers or other notices with the binary package. Optional. Type string. SEE ALSO
o cme AUTHOR
Dominique Dumont COPYRIGHT
2010,2011 Dominique Dumont LICENSE
LGPL2 perl v5.14.2 2012-11-09 Config::Model::models::Debian::Dpkg::Copyright::FileLicense(3pm)