abdelazer / openpub

Automatically exported from code.google.com/p/openpub
0 stars 0 forks source link

Draft section describing techniques to discover OPDS Catalogs #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Please draft a section of informative text for the specification that describes 
techniques that may be used to make OPDS Catalogs more discoverable. 

Original issue reported on code.google.com by abdela...@gmail.com on 10 Mar 2010 at 3:29

GoogleCodeExporter commented 9 years ago

Original comment by ed.summers on 10 Mar 2010 at 5:56

GoogleCodeExporter commented 9 years ago
Hadrien: Please contribute a rough draft of this section before the 8am Pacific 
call tomorrow, 5 May 2010.

Original comment by abdela...@gmail.com on 4 May 2010 at 6:13

GoogleCodeExporter commented 9 years ago
http://code.google.com/p/openpub/wiki/CatalogSpecDraft#Discovering_OPDS_Catalogs

Original comment by hadrien....@gmail.com on 12 May 2010 at 1:12

GoogleCodeExporter commented 9 years ago
I added a bit of text about auto-discovery for you guys to throw darts at, 
sorry for 
running with this without asking first:

  http://code.google.com/p/openpub/wiki/CatalogSpecDraft#Discovering_OPDS_Catalogs

Original comment by ed.summers on 12 May 2010 at 1:43

GoogleCodeExporter commented 9 years ago
Oh, shoot Hadrien did I stomp on your work?

Original comment by ed.summers on 12 May 2010 at 1:44

GoogleCodeExporter commented 9 years ago
Yeah, we should probably merge our efforts.

Original comment by hadrien....@gmail.com on 12 May 2010 at 1:51

GoogleCodeExporter commented 9 years ago
Hadrien, I'll leave the spec alone now. Please feel free to remove/change what 
I wrote 
as you see fit.

Original comment by ed.summers on 12 May 2010 at 2:00

GoogleCodeExporter commented 9 years ago
= Discovering OPDS Catalogs =

Autodiscovery links can point to both OPDS feeds and entries.

Links MUST use a type attribute "application/atom+xml;profile=opds-catalog".

For an OPDS entry, the link MUST use the "type" media parameter set to "entry": 
"application/atom+xml;type=entry;profile=opds-catalog"

== In HTML ==

The most common mechanism for encouraging the auto-discovery of OPDS Catalogs 
is to 
link from HTML document to the OPDS Catalog Root Resource, using the 
auto-discovery 
pattern popularized by the syndicated feed community `[AUTODISCOVERY]`.

Multiple links to OPDS catalogs MAY be expressed in a single HTML document.

{{{
<link rel="related" type="application/atom+xml;profile=opds-catalog" 
href="/opds-
catalogs/root" title="Example OPDS Catalog" /> 

<link rel="alternate" 
type="application/atom+xml;type=entry;profile=opds-catalog" 
href="/entry/1" title="Example OPDS Entry" /> 
}}}

== In HTTP Headers ==

Autodiscovery links MAY also be expressed using HTTP headers as defined in 
`[DRAFT-
Web-Linking]`.

Original comment by hadrien....@gmail.com on 19 May 2010 at 2:00

GoogleCodeExporter commented 9 years ago

Original comment by abdela...@gmail.com on 25 May 2010 at 5:44