Forum OpenACS Development: A licenses package?

Collapse
1: A licenses package?
Posted by David Arroyo Menéndez on 10/07/05 01:23 AM
I've done some hacks to the notes package and lars-blogger package to can choose a license when I publish an article in my blog.

I explain widely why I think that is important can choose a specific license when someone publish something here

I think that would be a nice feature to do a licenses package. I've some ideas about this development:

A name and a link to the official license site is sufficient to a datamodel license, but set locales in a similar mode to categories will be interesting due to licenses like Creative Commons does a big effort to internationalize licenses. Perhaps a local copy of the full license could be interesting or perhaps not.

I think that the site-wide administrator must be the people who manage licenses (add, edit and remove).

When the license package is finished would be good include the licenses option in lars-blogger, photo-album, content-repository, ... Step by step.

Someone is doing something similar?

Collapse
2: Re: A licenses package? (response to 1)
Posted by Carl Robert Blesius on 10/07/05 01:47 AM
Great idea David, but why put it in its own package? Why not just add this kind of info in a license category tree using the categories package and add support for the package in any application you want?
Collapse
3: Re: Res: A licenses package? (response to 1)
Posted by David Arroyo Menéndez on 10/07/05 12:07 PM

Thanks for your response Carl, it seems a good suggestion.

I think that I would need an external url to refer me to the license and internationalize external urls, too. I've seen that exits a cateories_links table but I think that it isn't the purpose. It's posible that another categories needs an external url could be a good idea extend the categories datamodel in this sense.

There are some attributes to a license that I don't think that will be a good idea use categories:

  • A rdf information with the license by example: 
     <!--Creative Commons License-->
<a rel="license" href="http://creativecommons.org/licenses/by/2.5/"><img alt="Creative Commons License" border="0" src="http://creativecommons.org/images/public/somerights20.png"/></a><br/>
		This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/2.5/">Creative Commons Attribution 2.5 License</a>.
		<!--/Creative Commons License--><!-- <rdf:RDF xmlns="http://web.resource.org/cc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
		<Work rdf:about="">
			<license rdf:resource="http://creativecommons.org/licenses/by/2.5/" />
	<dc:type rdf:resource="http://purl.org/dc/dcmitype/Text" />
		</Work>
		<License rdf:about="http://creativecommons.org/licenses/by/2.5/"><permits rdf:resource="http://web.resource.org/cc/Reproduction"/><permits rdf:resource="http://web.resource.org/cc/Distribution"/><requires rdf:resource="http://web.resource.org/cc/Notice"/><requires rdf:resource="http://web.resource.org/cc/Attribution"/><permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/></License></rdf:RDF> -->
  • The full license in a local copy (could be a good idea if the site of a license is broken frequently
  • A summary of the license like the creative commons summaries by example this it will be a good idea if the official site is broken, again.

Perhaps could be a good idea start using categories, although after or before we will need use fields that won't be adequated in categories. For it I thought create a new packages from the begining.

Nevertheless I think that I am not good with the openacs design, so I thanks more suggestions 😊