[whatwg] Helping people seaching for content filtered by license
bdarcus at gmail.com
Wed Jun 10 06:45:28 PDT 2009
On Wed, Jun 10, 2009 at 9:19 AM, Tab Atkins Jr.<jackalmage at gmail.com> wrote:
> On Wed, Jun 10, 2009 at 3:46 AM, Eduard Pascual<herenvardo at gmail.com> wrote:
>> On Fri, May 8, 2009 at 9:57 PM, Ian Hickson <ian at hixie.ch> wrote:
>>> This has some implications:
>>> - Each unit of content (recipe in this case) must have its own
>>> independent page at a distinct URL. This is actually good practice
>>> anyway today for making content discoverable from search engines, and
>>> it is compatible with what people already do, so this seems fine.
>> This is, on a wide range of cases, entirely impossible: while it might
>> work, and maybe it's even good practice, for contents that can be
>> represented on the web as a HTML document, it is not achievable for
>> many other formats. Here are some obvious cases:
>> Pictures (and other media) used on a page: An author might want to
>> have protected content, but to allow re-use of some media under
>> certain licenses. A good example of this are online media libraries,
>> which have a good deal of media available for reuse but obviously
>> protect the resources that inherently belong to the site (such as the
>> site's own logo and design elements): Having a separate page to
>> describe each resource's licensing is not easily achievable, and may
>> be completelly out of reach for small sites that handle all their
>> content by hand (most prominently, desginer's portfolio sites that
>> offer many of their contents under some "attribution" license to
>> promote their work).
> Even on small sites, though, if they have a picture gallery they
> almost certainly have the ability to view each picture individually as
> well, usually by clicking on the picture itself. That's the page
> you'd put the license information on.
What about the case where you have a JS-based viewer, and so when the
user clicks a photo, they do not go to a separate page, but instead
get a pop-up viewer?
Surely that's common, and it's entirely feasible that different photos
on the page would have different licenses.
Or another case: a weblog that includes third-party photo content
(could be your own photos too). You want to label your blog text with
one license, and the linked photos with another.
More information about the whatwg