search

tdwg / ac

Audiovisual Core
http://www.tdwg.org/standards/638
Creative Commons Attribution 4.0 International
11 stars 6 forks source link

Should the dcterms:identifier be permitted to be the same as one of the ac:accessURIs #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The dcterms:identifier is a URI of the resource itself.  An accessURI 
identifies a service, which is not the same thing.

Many people will want to use one identifier for both.... 

What to do?

Original issue reported on code.google.com by morris.bob on 1 Oct 2012 at 2:52

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
For those using content negotiation, using the same URI for content and 
metadata is a possible solution. Those that don't need separate URIs.

Original comment by g.m.hage...@gmail.com on 10 Oct 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Personally, I think it is a bad practice to use the same URI for access service 
and metadata. They are NOT the same object.  Content negotiation is a specific 
http URI resolution mechanism and has nothing to do with whether two objects 
are the same or not. Furthermore, if the accessURI changes, user confusion is 
likely because it can lead to things that naive users think are two different 
"files". 

I am changing this to High priority, but think the entire community should 
discuss it.

Original comment by morris.bob on 12 Oct 2012 at 3:40

GoogleCodeExporter commented 9 years ago

Original comment by morris.bob on 25 Nov 2012 at 11:47

GoogleCodeExporter commented 9 years ago 
Since the spec is silent on whether it's a bad practice, I leave it to Best 
Practices documents and resolve this with WontFix

Original comment by morris.bob on 8 Jun 2013 at 6:51