data: URLs -- yet another sick hack for stuffing RDF into (X)HTML documents

On Thu, 2006-05-18 at 20:27 -0400, Evan Prodromou wrote:
> Anyways, I thought it was worth posting as an
interesting hack.

I appreciate an interesting hack.  Thank you very much!

NB http://wiki.crea
tivecommons.org/RDFa is where we're going.

-- 
  
http://wiki.creativecommons.org/User:Mike_Linksvayer

_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata

Heya, you could at least go ahead and add this to the cc
wiki. It is
quite hacky, but good to document.

http://wiki.
creativecommons.org/metadata

Please don't make it front and center though, as it would
be good to not
confuse ppl.

Are there other ways that you and others have thought of to
accomplish
the same task? It would be great to document as many as
possible for
different use cases.

Jon

On Thu, 2006-05-18 at 20:27 -0400, Evan Prodromou wrote:
> OK, so, I had a vision of yet another crazy way of
embedding RDF into
> an (X)HTML document, besides the various nutty
suggestions posted at
> http://creativecommons.org/technology/metadata/extend#
html .
> 
> Namely, use a data: URL within a <link> element.
Data URLs allow you
> to put data directly into the content of an URL; see
> http://www.ietf.o
rg/rfc/rfc2397.txt . So you could stuff all the RDF
> into a single <link> element, like:
>         <link rel="meta"
type="application/rdf+xml"
>        
href="data:application/rdf+xml,%3Crdf%3ARDF%20xmlns%3D
%22http%
>        
3A%2F%2Fweb.resource.org%2Fcc%2F%22%0D%0A%20%20%20%20xmlns%
>        
3Adc%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Felements%2F1.1%2F%22%
0D
>        
%0A%20%20%20%20xmlns%3Ardf%3D%22http%3A%2F%2Fwww.w3.org%
>        
2F1999%2F02%2F22-rdf-syntax-ns%23%22%3E%0D%0A%3CWork%20rdf%
>        
3Aabout%3D%22http%3A%2F%2Fexample.org%2Fgnomophone.mp3%22%3E
%
>        
0D%0A%20%20%3Cdc%3Atitle%3ECompilers%20in%20the%20Key%20of%2
0C
>        
%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3Cdc%3Adescription%3EA%
>        
20lovely%20classical%20work%20on%20compiling%20code.%3C%2Fdc
%
>        
3Adescription%3E%0D%0A%20%20%3Cdc%3Acreator%3E%3CAgent%3E%0D
%
>        
0A%20%20%20%20%3Cdc%3Atitle%3EYo-Yo%20Dyne%3C%2Fdc%3Atitle%3
E%
>        
0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Acreator%3E%0D%0A%20%20%
>        
3Cdc%3Arights%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%
>        
3EGnomophone%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C
%
>        
2Fdc%3Arights%3E%0D%0A%20%20%3Cdc%3Adate%3E1842%3C%2Fdc%3Ada
te
>        
%3E%0D%0A%20%20%3Cdc%3Aformat%3Eaudio%2Fmpeg%3C%2Fdc%3Aforma
t%
>        
3E%0D%0A%20%20%3Cdc%3Atype%20rdf%3Aresource%3D%22http%3A%2F%
>        
2Fpurl.org%2Fdc%2Fdcmitype%2FSound%22%20%2F%3E%0D%0A%20%20%
>        
3Cdc%3Asource%20rdf%3Aresource%3D%22http%3A%2F%2Fexample.net
%
>        
2Fgnomovision.mov%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%
>        
3Aresource%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%
>        
2Fby-nc-nd%2F2.0%2F%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%
>        
3Aresource%3D%22http%3A%2F%2Fwww.eff.org%2FIP%2FOpen_license
s%
>        
2Feff_oal.html%22%20%2F%3E%0D%0A%0D%0A%3C%2FWork%3E%0D%0A%0D
%
>         0A%3CLicense%20rdf%3Aabout%3D%22http%3A%2F%
>        
2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%3E%0
D%
>        
0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%
>        
2Fweb.resource.org%2Fcc%2FReproduction%22%20%2F%3E%0D%0A%20%
>         20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%
>        
2Fweb.resource.org%2Fcc%2FDistribution%22%20%2F%3E%0D%0A%20%
>         20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%
>        
2Fweb.resource.org%2Fcc%2FNotice%22%20%2F%3E%0D%0A%20%20%
>        
3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.o
rg
>        
%2Fcc%2FAttribution%22%20%2F%3E%0D%0A%20%20%3Cprohibits%20rd
f%
>        
3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%
>        
2FCommercialUse%22%20%2F%3E%0D%0A%0D%0A%3C%2FLicense%3E%0D%0
A%
>         3C%2Frdf%3ARDF%3E" />
> 
> (That's the RDF example from creativecommons.org.)
> 
> It's not ideal, but it does have the nice properties
of a) including
> the data in the HTML document itself, b) hiding the RDF
from lame old
> browsers, c) being at least reasonably RFC-compatible,
d) not being
> the grodie comment method. B-)
> 
> Anyways, I thought it was worth posting as an
interesting hack.
> 
> ~Eva
> 
> 
>
____________________________________________________________
__________
> 
> Evan Prodromou <evanprodromou.name>
> http://evan.prodromou.nam
e/
> _______________________________________________
> cc-metadata mailing list
> metadatacreativecommons.org
> http://lists.ibiblio.org/mailman/listinfo/cc-metadata
-- 
Jon Phillips

San Francisco, CA
USA PH 510.499.0894
jonrejon.org
http://www.rejon.org

MSN, AIM, Yahoo Chat: kidproto
Jabber Chat: rejongristle.org
IRC: rejonirc.freenode.net

Inkscape (http://inkscape.org)
Open Clip Art Library (www.openclipart.org)
Creative Commons (www.creativecommons.org)
San Francisco Art Institute (www.sfai.edu)

_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata

Jon Phillips wrote:
> Heya, you could at least go ahead and add this to the
cc wiki. It is
> quite hacky, but good to document.
> 
> http://wiki.
creativecommons.org/metadata

I think the page in particular you want is
http:
//wiki.creativecommons.org/Extend_Metadata, as it
discusses options
for embedding RDF information in HTML.

> 
> Please don't make it front and center though, as it
would be good to not
> confuse ppl.

While documenting things is always a good idea, it should
also be noted
on the page that this is *not* a supported method for
embedding -- I
don't see tools like MozCC adding support for it any time
soon.


> 
> Are there other ways that you and others have thought
of to accomplish
> the same task? It would be great to document as many as
possible for
> different use cases.
> 
> Jon
> 
> On Thu, 2006-05-18 at 20:27 -0400, Evan Prodromou
wrote:
>> OK, so, I had a vision of yet another crazy way of
embedding RDF into
>> an (X)HTML document, besides the various nutty
suggestions posted at
>> http://creativecommons.org/technology/metadata/extend#
html .
>>
>> Namely, use a data: URL within a <link>
element. Data URLs allow you
>> to put data directly into the content of an URL;
see
>> http://www.ietf.o
rg/rfc/rfc2397.txt . So you could stuff all the RDF
>> into a single <link> element, like:
>>         <link rel="meta"
type="application/rdf+xml"
>>        
href="data:application/rdf+xml,%3Crdf%3ARDF%20xmlns%3D
%22http%
>>        
3A%2F%2Fweb.resource.org%2Fcc%2F%22%0D%0A%20%20%20%20xmlns%
>>        
3Adc%3D%22http%3A%2F%2Fpurl.org%2Fdc%2Felements%2F1.1%2F%22%
0D
>>        
%0A%20%20%20%20xmlns%3Ardf%3D%22http%3A%2F%2Fwww.w3.org%
>>        
2F1999%2F02%2F22-rdf-syntax-ns%23%22%3E%0D%0A%3CWork%20rdf%
>>        
3Aabout%3D%22http%3A%2F%2Fexample.org%2Fgnomophone.mp3%22%3E
%
>>        
0D%0A%20%20%3Cdc%3Atitle%3ECompilers%20in%20the%20Key%20of%2
0C
>>        
%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3Cdc%3Adescription%3EA%
>>        
20lovely%20classical%20work%20on%20compiling%20code.%3C%2Fdc
%
>>        
3Adescription%3E%0D%0A%20%20%3Cdc%3Acreator%3E%3CAgent%3E%0D
%
>>        
0A%20%20%20%20%3Cdc%3Atitle%3EYo-Yo%20Dyne%3C%2Fdc%3Atitle%3
E%
>>        
0D%0A%20%20%3C%2FAgent%3E%3C%2Fdc%3Acreator%3E%0D%0A%20%20%
>>        
3Cdc%3Arights%3E%3CAgent%3E%0D%0A%20%20%20%20%3Cdc%3Atitle%
>>        
3EGnomophone%3C%2Fdc%3Atitle%3E%0D%0A%20%20%3C%2FAgent%3E%3C
%
>>        
2Fdc%3Arights%3E%0D%0A%20%20%3Cdc%3Adate%3E1842%3C%2Fdc%3Ada
te
>>        
%3E%0D%0A%20%20%3Cdc%3Aformat%3Eaudio%2Fmpeg%3C%2Fdc%3Aforma
t%
>>        
3E%0D%0A%20%20%3Cdc%3Atype%20rdf%3Aresource%3D%22http%3A%2F%
>>        
2Fpurl.org%2Fdc%2Fdcmitype%2FSound%22%20%2F%3E%0D%0A%20%20%
>>        
3Cdc%3Asource%20rdf%3Aresource%3D%22http%3A%2F%2Fexample.net
%
>>        
2Fgnomovision.mov%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%
>>        
3Aresource%3D%22http%3A%2F%2Fcreativecommons.org%2Flicenses%
>>        
2Fby-nc-nd%2F2.0%2F%22%20%2F%3E%0D%0A%20%20%3Clicense%20rdf%
>>        
3Aresource%3D%22http%3A%2F%2Fwww.eff.org%2FIP%2FOpen_license
s%
>>        
2Feff_oal.html%22%20%2F%3E%0D%0A%0D%0A%3C%2FWork%3E%0D%0A%0D
%
>>         0A%3CLicense%20rdf%3Aabout%3D%22http%3A%2F%
>>        
2Fcreativecommons.org%2Flicenses%2Fby-nc-nd%2F2.0%2F%22%3E%0
D%
>>        
0A%20%20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%
>>        
2Fweb.resource.org%2Fcc%2FReproduction%22%20%2F%3E%0D%0A%20%
>>        
20%3Cpermits%20rdf%3Aresource%3D%22http%3A%2F%
>>        
2Fweb.resource.org%2Fcc%2FDistribution%22%20%2F%3E%0D%0A%20%
>>        
20%3Crequires%20rdf%3Aresource%3D%22http%3A%2F%
>>        
2Fweb.resource.org%2Fcc%2FNotice%22%20%2F%3E%0D%0A%20%20%
>>        
3Crequires%20rdf%3Aresource%3D%22http%3A%2F%2Fweb.resource.o
rg
>>        
%2Fcc%2FAttribution%22%20%2F%3E%0D%0A%20%20%3Cprohibits%20rd
f%
>>        
3Aresource%3D%22http%3A%2F%2Fweb.resource.org%2Fcc%
>>        
2FCommercialUse%22%20%2F%3E%0D%0A%0D%0A%3C%2FLicense%3E%0D%0
A%
>>         3C%2Frdf%3ARDF%3E" />
>>
>> (That's the RDF example from creativecommons.org.)
>>
>> It's not ideal, but it does have the nice
properties of a) including
>> the data in the HTML document itself, b) hiding the
RDF from lame old
>> browsers, c) being at least reasonably
RFC-compatible, d) not being
>> the grodie comment method. B-)
>>
>> Anyways, I thought it was worth posting as an
interesting hack.
>>
>> ~Eva
>>
>>
>>
____________________________________________________________
__________
>>
>> Evan Prodromou <evanprodromou.name>
>> http://evan.prodromou.nam
e/
>> _______________________________________________
>> cc-metadata mailing list
>> metadatacreativecommons.org
>> http://lists.ibiblio.org/mailman/listinfo/cc-metadata

_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata

Nathan R. Yergler wrote: 
> I think the page in particular you want is
> http:
//wiki.creativecommons.org/Extend_Metadata, as it
discusses options
> for embedding RDF information in HTML.

Done!

> > Please don't make it front and center though, as
it would be good to not
> > confuse ppl.
> >     
> 
> While documenting things is always a good idea, it
should also be noted
> on the page that this is *not* a supported method for
embedding -- I
> don't see tools like MozCC adding support for it any
time soon.

That's too bad. It seems like a special case of the
<link> method, and
it'd be really easy to implement. Considering that Mozilla
and Firefox
support data: URLs internally (see
http://www.mozilla.org/quality/networking/docs/abou
tdata.html), it might
already work! I'm going to do some testing and see.

~Evan


____________________________________________________________
____________
Evan Prodromou <evanprodromou.name>
http://evan.prodromou.nam
e/
_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata

On Wed, 2006-05-24 at 00:42 -0400, Evan Prodromou wrote:
> Nathan R. Yergler wrote: 
> > I think the page in particular you want is
> > http:
//wiki.creativecommons.org/Extend_Metadata, as it
discusses options
> > for embedding RDF information in HTML.
> 
> Done!

Cool, it would be great to keep contributing more methods
and cases to
the wiki...it is very cool of you! Great!

> > > Please don't make it front and center
though, as it would be good to not
> > > confuse ppl.
> > >     
> > 
> > While documenting things is always a good idea, it
should also be noted
> > on the page that this is *not* a supported method
for embedding -- I
> > don't see tools like MozCC adding support for it
any time soon.
> 
> That's too bad. It seems like a special case of the
<link> method, and
> it'd be really easy to implement. Considering that
Mozilla and Firefox
> support data: URLs internally (see
> http://www.mozilla.org/quality/networking/docs/abou
tdata.html), it might
> already work! I'm going to do some testing and see.

> ~Evan

You are cool.

Jon

>
____________________________________________________________
____________
> Evan Prodromou <evanprodromou.name>
> http://evan.prodromou.nam
e/
> _______________________________________________
> cc-metadata mailing list
> metadatacreativecommons.org
> http://lists.ibiblio.org/mailman/listinfo/cc-metadata
-- 
Jon Phillips

San Francisco, CA
USA PH 510.499.0894
jonrejon.org
http://www.rejon.org

MSN, AIM, Yahoo Chat: kidproto
Jabber Chat: rejongristle.org
IRC: rejonirc.freenode.net

Inkscape (http://inkscape.org)
Open Clip Art Library (www.openclipart.org)
Creative Commons (www.creativecommons.org)
San Francisco Art Institute (www.sfai.edu)

_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata

On Thu, 2006-05-18 at 21:01 -0400, Evan Prodromou wrote:
> On Thu, 2006-18-05 at 17:32 -0700, Mike Linksvayer
wrote: 
> >  http://wiki.crea
tivecommons.org/RDFa is where we're going.
> That's pretty great, but it doesn't seem to be
backwards-compatible
> with older HTML processors. I mean, doesn't it depend
on XHTML 2? Or
> at least modular XHTML?

http
://rdfa.info/2006/05/28/rdfa-and-validation/

-- 
  
http://wiki.creativecommons.org/User:Mike_Linksvayer

_______________________________________________
cc-metadata mailing list
metadatacreativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata