There should be normative URI for the type for the object of hasServiceAccesspoint

[GoogleCodeExporter]

In http://species-id.net/wiki/Audubon_Core_Term_List_RDF_Version there is a 
class for the objects of hasServiceAccessPoint, but in general the normative 
Term List is free of any notion of classes.  Nevertheless, there should be a 
standardized namespace and type name for constructing URI references for 
"objects" of hasServiceAccessPoint.

Pros:
1. It could uniformize documentation of implementations of AC
2. It could make mapping between implementation more transparent.

Cons:
1. It's a needless constraint.  Documentation of implementations would normally 
be targeted at people who are sophisticated about namespace. 
2. It's conceivable that some implementers may have underlying reasons for 
controlling both the name and namespace of the "class" of such objects.

Original issue reported on code.google.com by morris.bob on 28 Aug 2012 at 2:05

[GoogleCodeExporter]

I'm not in favor, especially for item 1 among the cons. 

Original comment by morris.bob on 28 Aug 2012 at 2:06

[GoogleCodeExporter]

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

• Added labels: Component-Terms

[GoogleCodeExporter]

There being no objection, I am resolving this as WontFix

Original comment by morris.bob on 8 Jun 2013 at 7:29

• Changed state: WontFix
• Added labels: Milestone-Release1.0