Ticket #34 (closed task: fixed)

Opened 3 years ago

Last modified 1 year ago

Format for paper abstract in triples/pseudo triples

Reported by: amit Assigned to: amit
Priority: high Milestone:
Component: information-model Version:
Keywords: abstract triples format Cc: amit
Blocking: Blocked By:

Description

While discussing Topaz with John Wilbanks of Science Commons with regards to interesting applications we could build on top of the triples framework, he recommended we try and achieve a small, albeit significant social change in peer reviewed STM articles. He would like authors to write an abstract of the paper in triples or close to triples format stating the various premises and conclusions of the article. OUr thinking is that this is a very useful idea, but needs the precise format to be determined.

Dependency Graph

Change History

04/30/06 16:17:20 changed by amit

  • status changed from new to assigned.

I sent an email to John Wilbanks of Science Commons asking if they have created a profile for this. His response on April 26, 2006 indicates that he is very busy, but will respond later this week with some details.

05/22/06 11:11:07 changed by amit

We have a potential solution to this thanks to Jimmy Wales of Wikipedia. He recommended instead of focusing on authors and a pre-defined format, allow anyone to edit and create triples abstract of articles. This will allow testing of multiple ideas and hopefully lead to convergence in the long run.

I sent an email to John Wilbanks with regards to this and he concurred. So essentially the rough working of this will be:

  1. An attached annotation page can be exposed by applications as wiki pages
  2. This annotation page will contain RDF triples or close to triples format of the paper abstract
  3. Applications can expose this using whatever tools they feel is best, an RDF editor, plain wiki, etc.
  4. The service will check the submitted syntax (RDF or N3 or Turtle...) to make sure it conforms before storing this in the repository
  5. The service could also extract the vocabulary and export that so users can reuse pieces they feel necessary
  6. Service will track revisions and allow users to see the change history

05/30/06 12:44:14 changed by amit

  • milestone changed from snowcrash to Nirvana.

Exchanged emails with Chris with regards to this and he is in support. Questions on all sides is that can we deliver this for our fall launch? From a Topaz platform perspective, this might not be too difficult, but if the applications (say PLoS ONE) cannot take advantage of it, it might be more useful to concentrate on other features. Moving this to Nirvana as we should implement this in the future (given we have a decent design now).

06/19/06 04:34:05 changed by chris

I'm completely happy with this. I'm also interested in exploring what other uses for wiki enabled annotation pages could be produced. e.g. alternative language translations, general public summary, collaborative review.

07/13/06 17:28:55 changed by amit

  • status changed from assigned to closed.
  • resolution set to fixed.

Closing as this will be done and tracked through #66.

08/07/07 16:25:51 changed by

  • milestone deleted.

Milestone Bugs deleted