Difference between revisions of "OpenOfficeOrg Addin"

From Creative Commons
Jump to: navigation, search
(Requirements)
(Moving discussion to the Talk page where it belongs.)
Line 30: Line 30:
 
* Educational component (wizard) assists people in selecting appropriate license types for their desires
 
* Educational component (wizard) assists people in selecting appropriate license types for their desires
 
* Display license information when opening CC licensed documents
 
* Display license information when opening CC licensed documents
 
== Discussion ==
 
 
* Would a straight up core addition to OpenOffice.org be more desirable than a plug-in? [[User:Jon Phillips|Jon Phillips]] 18:08, 6 July 2006 (UTC)
 
** I do not think so. Uno Framework and Extensions project is designed for such uses [[User:Laurent Godard|Laurent Godard]]
 
** Of note there are two open issues on the OpenOffice issue tracker in relation to this, [http://www.openoffice.org/issues/show_bug.cgi?id=66656 Equivalent of Creative Commons Add-in for Microsoft Office] (Opened June 2006) and [http://www.openoffice.org/issues/show_bug.cgi?id=29404 Marking documents with Creative Commons license metadata] (Opened May 2004). there are not many votes for either and now indication of how it would be implemented --[[User:Miguelpdl|Miguelpdl]] 11:50, 17 July 2006 (UTC)
 
* Insert license declaration text
 
** What about languages ?
 
*** We could make available some languages packages that user could choose during setup --[[User:Ksiomelo|Ksiomelo]] 01:59, 27 March 2007 (UTC)
 
** Possibly in a hidden section ?
 
  
 
== See also ==
 
== See also ==

Revision as of 15:36, 26 October 2007


A Creative Commons Add-in for OpenOffice.org would allow license information to be embedded in OpenOffice.org Writer, Impress and Calc documents.

Status


Requirements

  • Use the Creative Commons web services to display a licensing dialog and generate licensing information
    • available for Python
    • available for Java
    • can be encapsulated as an uno service if needed
  • Store license URI, properties and/or RDF in the document file
    • OOo user defined metadata can be used (metadata renamed and string stored)
  • Insert license declaration text (see discussion below)

Desirable Features

  • Make license text available as Auto Text. Just like a page number or "Author" auto text, this could be inserted in the footer of a document. If the license for the document was updated, the text would be updated as well.
    • translation ?
  • Educational component (wizard) assists people in selecting appropriate license types for their desires
  • Display license information when opening CC licensed documents

See also

External links