Jon Phillips | 6 Mar 04:02 2006

http://wiki.creativecommons.org/Salon

First Creative Commons Salon . WED MAR 8, 6-9 PM
http://wiki.creativecommons.org/Salon

You are invited to the first CC Salon, taking place in San Francisco 
on Wednesday, March 8 from 6pm-9pm at Shine. CC Salon is a casual 
get-together focused on conversation and community-building. It's open
to anyone interested in art, technology, education, and copyright. We 
look forward to seeing you there!

CC Salon - San Francisco
Wednesday, March 8, 2006, 6 PM - 9 PM
Shine (http://shinesf.com/)
1337 Mission Street (between 9th and 10th), San Francisco

Featuring presentations by:

Josh Kinberg; FireAnt (http://fireant.tv/)
Eddie Codel; Geek Entertainment TV (http://geekentertainment.tv/)
Wagner James Au; Second Life (http://secondlife.com/)

And music by:

Minus Kelvin; ccMixter (http://ccmixter.org/)

Creative Commons Blog entry: 
http://creativecommons.org/weblog/entry/5804

There is a wiki setup where you can find the latest information about CC
Salon. This will also serve as a place where the community can 
contribute ideas, make suggestions, and submit proposals for future 
(Continue reading)

Brian Erdelyi | 7 Mar 21:15 2006
Picon

Extending CC Meta-Data

How could I go about extending CC meta-data to include some of these common characteristics?
 
I'm just acknowledging the existance of these characteristics that impact control over the user's experience, privacy and system security.  I'm not justifying whether the terms are legal, enforcable or appropriate.
 
Restrictions:
-no third-party software
-no reverse engineering
-no transfers
-no hosting
-no benchmarks or analysis
-age limitations
 
Contents:
-displays advertising
-intercepts or redirects web traffic
-collects system information
-collects usage information
-collects personal information
-contains DRM
-contains usage restricting technologies
-incompatibility can degrade performance
 

Brian 
_______________________________________________
cc-metadata mailing list
metadata@...
http://lists.ibiblio.org/mailman/listinfo/cc-metadata
Mike Linksvayer | 8 Mar 00:51 2006

Re: Extending CC Meta-Data

On Tue, 2006-03-07 at 12:15 -0800, Brian Erdelyi wrote:
> How could I go about extending CC meta-data to include some of these
> common characteristics?

You wouldn't be extending CC metadata, you'd be defining a new
vocabulary.  If you used RDF (which I recommend) it would coexist with
CC metadata -- you're just making additional assertions about a
resource, e.g., a web page.

You probably want to look for other people working on "policy aware web"
vocabularies (e.g., PICS) and attempt to collaborate with them and if
nobody is interested start your own mailing list to develop your
vocabulary.

--

-- 
  Mike Linksvayer
  http://creativecommons.org/about/people#21
Brian Erdelyi | 8 Mar 00:58 2006
Picon

Re: Extending CC Meta-Data

I get how it would be about defining a new vocabulary.  Regrettably, I'm still reading up about RDF so I dont
fully appreciate how it can be used.

Would anyone care to provide an example of representing a few of those characteristics using RDF that could
be used?

Any sources or documentation I could review for some guidance on how to develop this new vocabulary?

Thanks again,
Brian
Björn Lindström | 8 Mar 05:16 2006
Picon
Picon
Picon

Re: Extending CC Meta-Data

Brian Erdelyi <brian_erdelyi <at> yahoo.com>:

> Any sources or documentation I could review for some guidance on how
> to develop this new vocabulary?

http://www.w3.org/2001/sw/ has links to authoritative information on
RDF and related things.

--

-- 
Björn Lindström <bkhl <at> stp.lingfil.uu.se>
Student of computational linguistics, Uppsala University, Sweden

_______________________________________________
cc-metadata mailing list
metadata <at> creativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata
Renato Iannella | 8 Mar 05:55 2006
Picon

Re: Extending CC Meta-Data

Hi Brian - what you need is an *extensible* rights expression language.

The Open Digital Rights Language (ODRL) is one such example.
It's model is based on a comprehensive view of IPR and Contract requirements.
It's based on XML Schema and can be extended (easily) with your own Profile or reuse
of the core profile semantics.

And, even better, there already exists a Profile that captures the semantics of
the Creative Commons licenses terms. It is an approved recommendation and is
is available from:


Your additional restrictions, eg "no reverse engineering" can be part of your own community profile
and mixed with the ODRL/CC Profile.

I hope this is useful...

Cheers...  

Dr Renato Iannella

Program Leader

National ICT Australia (NICTA) -  Queensland Research Laboratory

Level 19, 300 Adelaide St, Brisbane, QLD, 4000 AUSTRALIA

P: +61 7 3000 0484 F: +61 7 3000 0480 M: +61 4 1313 2206

<renato-3w/jM7ZMsnj0CCvOHzKKcA@public.gmane.org> <http://nicta.com.au<aim:renatoi2003> <skype:riannella>



_______________________________________________
cc-metadata mailing list
metadata@...
http://lists.ibiblio.org/mailman/listinfo/cc-metadata
Björn Lindström | 8 Mar 06:11 2006
Picon
Picon
Picon

Re: Extending CC Meta-Data

Renato Iannella <renato <at> iannella.it>:

> The Open Digital Rights Language (ODRL) is one such example.  It's
> model is based on a comprehensive view of IPR and Contract
> requirements.  It's based on XML Schema and can be extended (easily)
> with your own Profile or reuse of the core profile semantics.

Please don't use this as an alternative to, but if anything as a
complement to, the regular CC metadata, though. It's tedious enough
supporting the regular format.

--

-- 
Björn Lindström <bkhl <at> stp.lingfil.uu.se>
Student of computational linguistics, Uppsala University, Sweden

_______________________________________________
cc-metadata mailing list
metadata <at> creativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata
Brian Erdelyi | 8 Mar 13:57 2006
Picon

Re: Extending CC Meta-Data

Thanks for the W3 reference, I'll continue to familiarise myself with the format.

>From this example...

<License rdf:about="http://creativecommons.org/licenses/by-nc-nd/2.0/">
  <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" />
  <prohibits rdf:resource="http://web.resource.org/cc/CommercialUse" />
</License>

I would reference the software's license (likely proprietary) in the first line and follow it by the characteristics.

PERMIT, REQUIRES and PROHIBIT are the three types of characteristics that CC includes, and each can have
specified values.

If I were to extend a vocabulary I would create additional characteristic types and specify possible
values for each?  I'll give this some thought to determine what works best.  My initial thought is that I only
need a characteristic that will describe OPERATION, BEHAVIOR or FUNCTIONALITY of the software.

Would adding additional values to the existing CC characteristics cause any problems or concern?

Brian
Mike Linksvayer | 8 Mar 20:50 2006

Re: Extending CC Meta-Data

On Wed, 2006-03-08 at 04:57 -0800, Brian Erdelyi wrote:
> Thanks for the W3 reference, I'll continue to familiarise myself with the format.
>  
> >From this example...
>  
> <License rdf:about="http://creativecommons.org/licenses/by-nc-nd/2.0/">
>   <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" />
>   <prohibits rdf:resource="http://web.resource.org/cc/CommercialUse" />
> </License>
> 
> I would reference the software's license (likely proprietary) in the first line and follow it by the characteristics.
>  
> PERMIT, REQUIRES and PROHIBIT are the three types of characteristics that CC includes, and each can have
specified values.
>  
> If I were to extend a vocabulary I would create additional characteristic types and specify possible
values for each?  I'll give this some thought to determine what works best.  My initial thought is that I only
need a characteristic that will describe OPERATION, BEHAVIOR or FUNCTIONALITY of the software.
>  
> Would adding additional values to the existing CC characteristics cause any problems or concern?

There would be no problem.  Keep in mind that in the above statement
License, permits, requires and prohibits are in the
http://web.resource.org/cc/ namespace, which would be defined in an
xmlns attribute the above is wrapped in.

You'd presumably have something like

<eula:EULA rdf:about="http://example.com/eula.html">
    <cc:prohibits
rdf:resource="http://web.resource.org/cc/CommercialUse" />
    <eula:requires rdf:resource="http://eula-rdf.org/Soul" />
</eual:EULA>

where the cc and eula namespaces would be specified in xmlns attributes.

--

-- 
  Mike Linksvayer
  http://creativecommons.org/about/people#21
Renato Iannella | 9 Mar 01:08 2006
Picon

Re: Extending CC Meta-Data


On 8 Mar 2006, at 15:11, Björn Lindström wrote:

> Please don't use this as an alternative to, but if anything as a
> complement to, the regular CC metadata, though. It's tedious enough
> supporting the regular format.

Bjorn - you have to make a choice - either the extensible ODRL/CC  
Profile
or not. You can't "mix" them together. The decision is based on the  
needs of
your community. If they are not meet by the fixed CC license types,  
and you
need additional features, then you then need to look at alternatives.

Also, be very clear that as soon as you "extend" a CC license (using  
whatever
technology you choose) - you no longer are using CC licenses.

Cheers

Renato

Gmane