remodel odps:acquisition/sample and odps:acquisition/subscribe

[GoogleCodeExporter]

It is not clear how odps:acquisition/sample relates to the other aquisition 
link types. Does it imply odps:acquisition (so a sample must be retrievable 
without payment) or can you combine it with odps:acquisition/borrow and 
odps:acquisition/buy? The same applies for odps:acquisition/subscribe.

Either the sample (or subscribe) information must be encoded by some other 
means or we need to define combinations like:

odps:acquisition/sample/buy
odps:acquisition/sample/borrow
odps:acquisition/sample/view (see ISSUE #38)

Original issue reported on code.google.com by siehea...@googlemail.com on 27 May 2010 at 7:59

[GoogleCodeExporter]

In the current spec, sample means an extract that is freely available for 
download.

I don't think that we want to go down that road and define multiple acquisition 
techniques for samples.
In this case, you should rather use a separate entry for the sample, use the 
already 
defined rel values (buy, borrow, subscribe) and use a link with the right rel 
value 
to explicit the relationship between the full publication and its elements.

Revues.org for example already provide a link to a feed with all the articles 
listed 
in a journal.

Original comment by hadrien....@gmail.com on 27 May 2010 at 8:30

[GoogleCodeExporter]

I'd like to reject this issue, can anyone else provide their feedback first ?

Original comment by hadrien....@gmail.com on 15 Jul 2010 at 4:29

[GoogleCodeExporter]

Original comment by abdela...@gmail.com on 4 Aug 2010 at 3:23

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

We don't feel that this has been justified by real-world implementations at 
this time. We'll be watching for implementations of this in the future.

Original comment by abdela...@gmail.com on 4 Aug 2010 at 3:39

• Changed state: WontFix