I took a quick look into the MS solution: They simply place some text and links into the document, that's all.
This, of course, can be done as a component, and people w/o that component will also see the license. Such a component shouldn't be to hard to implement - any volunteers? ;) Malte. Nathan R. Yergler wrote, On 07/07/06 13:21: >> My feeling is that it should be in the standard office installation, not >> an extension. > > Well that would obviously be preferred, we were just trying to go for > the shortest time to implement/deploy (path of least resistance, if you > will). Is there a formalized mechanism for suggesting features such as > this? I'm not familiar enough with the development model to know if its > possible to develop something as an extension and be able to > significantly reuse the code in the standard installation. > >> Reason: If I attach a license to my document, I want that everybody is >> aware of that when opening the doc, not just people who have the extension. >> >> License must be contained in the document container, and OOo might show >> a little symbol in the status bar, like for a signed document. > > Right; I guess if it weren't integrated into the standard installation, > it would be desirable for the license metadata to survive document > manipulation by people who do not have the extension installed. > >> But I didn't look deeper into the details right now... >> >> Malte. >> >> Nathan R. Yergler wrote, On 07/06/06 18:39: >>> Hello, >>> >>> You may have recently seen that Microsoft developed and released an >>> Addin for Microsoft Office that allows Creative Commons license >>> information to be embedded in Word, Excel and PowerPoint documents >>> (http://wiki.creativecommons.org/Microsoft_Office_Addin). We're very >>> interested in supporting open source and open formats by providing >>> similar functionality for OpenOffice.org. >>> >>> I've placed a stub page in the wiki at >>> http://wiki.creativecommons.org/OpenOfficeOrg_Addin which lists some >>> requirements and ideas for the project. We're interested in hearing >>> feedback about the project -- is it possible to do as an extension (if >>> that's the right terminology)? Any suggestions on starting points? >>> Anyone interested in helping out? :) >>> >>> Any feedback, suggestions or ideas other developers have would be very >>> welcome. >>> >>> Thanks for your help, >>> >>> Nathan >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
