CC OpenSearch - Revision history

Mike Linksvayer: /* See Also */

2010-09-06T18:31:20Z

‎See Also

2010-09-06T18:30:56Z

2007-01-31T02:21:51Z

‎CC options as special keywords

2007-01-31T02:20:39Z

‎OpenSearch Description Document

2007-01-31T02:18:53Z

‎Open Questions

2007-01-31T02:13:43Z

‎Extension with custom parameters

2007-01-31T02:06:07Z

‎Todo

2007-01-31T02:03:45Z

‎Extension with custom parameters

2007-01-31T02:02:37Z

‎Extension with custom parameters

2007-01-31T01:51:55Z

‎OpenSearch Description Document

@@ Line 97: / Line 97: @@
 * http://www.opensearch.org
 * http://en.wikipedia.org/wiki/OpenSearch
-* [[CcSearch]] -- CC's simple "frame" interface available at http://search.creativecommons.org, unrelated in terms of technology to OpenSearch
+* [[CC Search]] -- CC's simple "frame" interface available at http://search.creativecommons.org, unrelated in terms of technology to OpenSearch
 * [[Syndication]] -- license annotations in syndication formats
 [[Category:Search]]
 [[Category:Developer]]

← Older revision		Revision as of 02:21, 31 January 2007
Line 18:		Line 18:

	Absolutely no extension of the description document is required to faciliate this use.		Absolutely no extension of the description document is required to faciliate this use.
		+
		+	Going this route, it would be useful if search services supported a consistent syntax for license restrictions, as many do for link, site, etc.

	===Multiple description documents===		===Multiple description documents===

@@ Line 11: / Line 11: @@
 <code>Attribution</code> and <code>SyndicationRights</code> elements are ''not'' relevant -- they describe search results, not the content referred to by search results.
-How should a CC-enabled search engine describe itself?  Two options:
+How should a CC-enabled search engine describe itself?  Three options:
 ===Multiple description documents===

@@ Line 77: / Line 77: @@
 ===Open Questions===
-* Determine best practice for using OpenSearch Description Document to indicate availability of CC filtered search.
+* Determine best practice for using OpenSearch Description Document to faciliate CC filtered search.
 ** Multiple description documents?
 ** Extension with custom parameters -- how in practice to OpenSearch consumers deal with custom parameters?
 ===Implementation===

@@ Line 65: / Line 65: @@
 </pre>
-This solution may not be practical.  '''How do OpenSearch consumers handle custom parameters?'''
+This solution may not be practical.  '''How do [http://www.opensearch.org/Community/OpenSearch_enabled_search_clients OpenSearch consumers] handle custom parameters?'''
 ==OpenSearch Response Elements==

← Older revision	Revision as of 18:30, 6 September 2010
(No difference)

@@ Line 74: / Line 74: @@
 ==Todo==
 * Determine best practice for using OpenSearch Description Document to indicate availability of CC filtered search.
 * Encourage search services that support OpenSearch and remember license info for searchable materials to include license annotations in OpenSearch result feeds, per [[Syndication|existing extensions]].

@@ Line 64: / Line 64: @@
 </nowiki>
 </pre>
 ==OpenSearch Response Elements==

← Older revision		Revision as of 02:02, 31 January 2007
Line 34:		Line 34:

	An extension approach would be more elegant than a multiple description approach, but may not work well for existing services that may have URL formats difficult to map to parameters for each license attribute one may want to filter on.		An extension approach would be more elegant than a multiple description approach, but may not work well for existing services that may have URL formats difficult to map to parameters for each license attribute one may want to filter on.
		+
		+	An imaginary CC extension might include the following custom parameters:
		+
		+	<pre>
		+	<nowiki>
		+	{cc:permitsDistribution}
		+	{cc:prohibitsCommercialUse}
		+	{cc:permitsDerivativeWorks}
		+	</nowiki>
		+	</pre>
		+
		+	Others may be useful as well, e.g.,
		+
		+	<pre>
		+	<nowiki>
		+	{cc:requiresShareAlike}
		+	{cc:PublicDomain}
		+	{cc:license}
		+	</nowiki>
		+	</pre>
		+
		+	All of the above would presumably expect a boolean value (1/0, true/false), except the last, which might expect a license URL or pattern.
		+
		+	Example use in a <code>Url</code> element:
		+
		+	<pre>
		+	<nowiki>
		+	<Url type="application/atom+xml" template="http://example.com/?q={searchTerms}&cc-distribution={cc:permitsDistribution?}&cc-nocommercial={cc:prohibitsCommercialUse?}&cc-derivs={cc:permitsDerivativeWorks?}"/>
		+	</nowiki>
		+	</pre>

	==OpenSearch Response Elements==		==OpenSearch Response Elements==

@@ Line 13: / Line 13: @@
 How should a CC-enabled search engine describe itself?  Two options:
-* Multiple descriptions, one corresponding to each filter services wishes to expose, e.g., one of four for each of the examples [[CcSearch_integration|here]], specifically four OpenSearch Description Documents, each with a Url element (or elements, corresponding to HTML/RSS/Atom outputs) hardcoding desired filter, like
+===Multiple description documents===
 <pre>
 <nowiki>
@@ Line 25: / Line 27: @@
 </nowiki>
 </pre>
-[http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_URL_template_syntax URL templates]
+An extension approach would be more elegant than a multiple description approach, but may not work well for existing services that may have URL formats difficult to map to parameters for each license attribute one may want to filter on.
 ==OpenSearch Response Elements==