embedding metadata in MIDI?

Lucas Gonze lgonze at panix.com
Thu Jul 3 13:33:43 EDT 2003


Hi Keven,

A bot would look for the string "verify at" and, if it's present, use
everything after it as the URL.

- Lucas

On Thu, 3 Jul 2003, Kevin Shrieve wrote:

> And is that considered to be "machine-readable"?  Is it anticipated
> that a search engine harvesting files with a particular license would
> use the first URL in the "copyright event" as the search criterion?
>
> Thanks,
>
> Kevin Shrieve
>
> http://www.mp3.com/DreamArtScience
>
>
> >>I guess the copyright field is unformatted text -- would you use it
> >>in such a way that it could be machine-readable, say by a search
> >>engine?
> >
> >The copyright field is unformatted text, but we'll recommend a
> >specific format from which license and license claim urls can be
> >extracted. Excerpted from
> ><http://creativecommons.org:8000/learn/technology/mp3>:
> >
> >   TCOP (Copyright Text) should include a human-readable license and
> >   license claim information. The contents of this frame are displayed
> >   by many programs in a "file info" window. Example value: 1995 Example
> >   Band. Licensed to the public under
> >   http://creativecommons.org/licenses/by/1.0/ verify at
> >   http://example.com/cclicenses.html
> >
> >   If "verify at " exists in TCOP, everything after it must be the
> >   license claim URL, and if there is a license claim URL then it must
> >   be preceded by "verify at ".
> >
> >For MIDI the instructions would be the same, just replace "TCOP"
> >with "copyright event".
> >
> >--
> >   Mike Linksvayer
>
> _______________________________________________
> cc-metadata mailing list
> metadata at creativecommons.org
> http://lists.ibiblio.org/mailman/listinfo/cc-metadata
>



More information about the cc-metadata mailing list