General Discussion
- FRBR model - ePubs and ePrints have different interpretations of FRBR. -> Adoption of "Ping" must be independent of FRBR concepts.
- ePrints citations storage - citations block stored in one long literal field. Split by line break for lookup.
Idea/Issues on Ping
- metadata formats - Support for alternatives to Dublin Core in the metadata=[<xml>] ? Embedded RDF could contain list of formats supported/preferred.
- duplicate trackbacks - What if two copies of article A exist, stored in two repositories, both of which ping article B? Need duplicate removal.
- Anti-trackback - how can we send a 'delete' this trackback to correct an error. Send another ping, but to HTTP delete, or provide a trackback:deleteping in embedded RDF, or give action==delete as just-another-metadat in the POST.
- Whitlelist. Agree that IP may be problematic. DNS? What approaches to spam detection are available?
2 further items from later discussion in the Car:
- Embed more metadata about the cited resource in the trackback:ping embedded rdf. That way the calling repository can enhance/check metadata held about this citation.
- Generate a different trackback URI for every invocation? Can track who requested it and match against who pinged to improve spam handling.
