search

abdelazer / openpub

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

Draft summary of relationship between Dublin Core metadata, Atom metadata, and OPDS Catalog metadata #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Define relationship between Dublin Core metadata, Atom metadata, and OPDS
Catalog required metadata

Raj wrote:

"""
From an aggregator's viewpoint, it would be nice if OPDS standardized
the way metadata was included in catalog feeds.

Should dublin core be used for this? If so, what is the proper way of
adding dublin core to OPDS?

Should it be part of the content element, so that OPDS can validate as
an Atom feed?
"""

Please note that any discussion should happen on the mailing list rather
than the comments of the issue tracker.

Original issue reported on code.google.com by abdela...@gmail.com on 16 Jul 2009 at 7:11

GoogleCodeExporter commented 9 years ago 
Please develop a section of specification text that clarifies which schema is 
used to 
express metadata defined by both Dublin Core and Atom (title, author/creator, 
etc).

Original comment by abdela...@gmail.com on 10 Mar 2010 at 3:40

GoogleCodeExporter commented 9 years ago 
Raj: 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:14

GoogleCodeExporter commented 9 years ago 
The standardized way for including metadata in OPDS feeds is now described in 
the "Partial and Complete 
Catalog Entries" section of the draft.

Link to relevant section: 
http://code.google.com/p/openpub/wiki/CatalogSpecDraft#Element_Definitions

Original comment by rku...@archive.org on 10 May 2010 at 5:10

GoogleCodeExporter commented 9 years ago 
I still think we need more text clarifying when to use things from DC versus 
Atom when there are conflicts (title, 
for example).

Original comment by abdela...@gmail.com on 12 May 2010 at 5:54

GoogleCodeExporter commented 9 years ago 
Hadrien: I'm feeling pretty ill this weekend, so would you please work with 
Gavin to clarify this issue and draft 
some rough text to describe which vocabulary should be used to markup which 
elements. I realized how 
important this was after working through some very reasonable questions Gavin 
had while trying to update the 
O'Reilly Catalogs.

This is due 18 May 2010. Please let me know if that's not possible given your 
schedule.

Sample:
"""
For the date when the OPDS Catalog Entry was changed, use atom:updated, not 
dc:issued. Instead, use 
dc:issued for the publication date of the Publication itself (not atom:updated).

For the Publication's title, use atom:title (not dc:title).
"""

Original comment by abdela...@gmail.com on 16 May 2010 at 9:14

GoogleCodeExporter commented 9 years ago

Original comment by abdela...@gmail.com on 18 May 2010 at 6:04

GoogleCodeExporter commented 9 years ago 
Sorry, I was in Lille for a conference where I talked about OPDS yesterday...

How can I reach Gavin to start working on this section ?

Original comment by hadrien....@gmail.com on 18 May 2010 at 10:09

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/openpub/wiki/CatalogSpecDraft#Relationship_between_Atom
_and_
Dublin-Core_metadata

OPDS entries MUST be identified by atom:id. dc:identifier SHOULD be used to 
identify 
the publication itself, not the OPDS entry.

OPDS entries MUST provide a date where the entry was last updated using 
atom:updated. 
dc:issued SHOULD be used for the first publication date of the publication, not 
for 
any date related to the OPDS entry itself.

For the publication's title, Catalog providers MUST use atom:title. Catalog 
providers 
MUST NOT display this information in dc:title. 

A partial publication description SHOULD be displayed atom:summary, while a 
full 
description SHOULD be displayed in atom:content. Catalog providers MUST NOT 
display 
this information in dc:description.

For the publication's authors, Catalog providers SHOULD use atom:author. 
Catalog 
providers MUST NOT display this information in dc:creator.

For the publication's categories, Catalog providers SHOULD use atom:category. 
Catalog 
providers MUST NOT display this information in dc:subject.

For the publication's rights, Catalog providers SHOULD use atom:rights. Catalog 
providers MUST NOT display this information in dc:rights.

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

GoogleCodeExporter commented 9 years ago 
This all seems very sensible to me.

Original comment by liza31337@gmail.com on 19 May 2010 at 1:52

GoogleCodeExporter commented 9 years ago 
I don't feel that we have enough knowledge of prism: to actually be able to 
assert which elements SHOULD or 
SHOULD NOT be included.

Example: prism:issue doesn't even exist the in version of the spec I'm looking 
at.

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

GoogleCodeExporter commented 9 years ago

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