Comments (6)
It should be a location standardized for tdwg (what is the species id page, who
is it run by?), easily accessible by tdwg members, and preferable the same
location as our overarching normative information (i.e., the ac wiki). One
should be shifted to the other location. And someone needs to keep up-to-date
on the species id page. Making changes in two different locations is bad.
Original comment by [email protected]
on 18 Jan 2012 at 7:33
from ac.
The current DwC, and fairly common modern practice, separates the link
value---or more properly, the URI for the term, from the URI resolution and
dereference, which contains the actual information defining the term. For
example, http://rs.tdwg.org/dwc/terms/catalogNumber is the URI for the DwC
catalogNumber term, but if you put that URL into a browser, you will find that
it takes you to
http://darwincore.googlecode.com/svn/trunk/terms/index.htm#catalogNumber which
is where the DwC group maintains the authoritative version. This is NOT what
happens for DwC terms borrowed from other vocabularies, which appropriately are
resolved and dereferenced in whatever way the original vocabulary provides. For
example , dc:type resolves to http://purl.org/dc/terms/type, which happens to
provide an entire RDF document, giving all the dc terms (though that's an
artifact of a poor choice on dc's part).
The corresponding thing for AC would be to assign URI's in rs.tdwg.org for
those terms in the ac namespace but resolve them to the species-id wiki at the
appropriate place. That is indeed what my present arrangement is with the
rs.tdwg.org maintainers. Borrowed vocabulary is resolved, as for DwC, by the
originating mechanism, however inconvenient it may be.
There is no downside to this. Maintenance of the AC vocabulary remains entirely
on species-id. The version on code.google.com is for no purpose other than
public commenting, especially with the issue manager, which is way better than
giving all of TDWG edit permission on species-id.
With about a few days work between Gregor and me, it is probably feasible to
provide a media-wiki robot that would automatically update the "informative"
version on google code whenever the authoritative species-id is updated.
Original comment by morris.bob
on 18 Jan 2012 at 8:16
from ac.
This is done in the proposed AC at http://terms.gbif.org/w/index.php?oldid=8875
Original comment by morris.bob
on 25 Nov 2012 at 8:43
- Changed state: Fixed
from ac.
Original comment by morris.bob
on 4 Jun 2013 at 11:29
- Changed state: Done
from ac.
Original comment by morris.bob
on 8 Jun 2013 at 7:59
- Added labels: Milestone-Release1.0
from ac.
Original comment by morris.bob
on 22 Oct 2013 at 2:27
- Added labels: Type-Task
- Removed labels: Type-Enhancement
from ac.
Related Issues (20)
- "leaf" orientation for bryophytes HOT 3
- subjectOrientation definitions are somewhat circular HOT 2
- Consider fungal parts as additions to Views CV HOT 12
- Include fly examples from Zenodo HOT 1
- 3D terms Proposal: new dc:type term and new ac terms HOT 1
- Outdated Link in Notes for Iptc4xmpExt:CVterm HOT 2
- Views controlled vocabularies proposal HOT 41
- Proposal to create a controlled vocabulary for content description HOT 6
- Investigate GUANO audio metadata standard HOT 3
- New term proposal: ac:Digital3DResource HOT 5
- Do the renaming to "Audio-visual Core" in github, website etc HOT 8
- Update ac.tdwg.org to make use of new TDWG branding HOT 2
- Example for identification keys/tools HOT 8
- rs.tdwg.org/ac redirection issue for `variant/2020-10-13` HOT 2
- Table cell boundaries not visible under new website theme HOT 4
- Error in definition of the subjectPart concept scheme HOT 3
- Implementation of subjectPart and subjectOrientation in Myriatrix HOT 6
- w3c FragmentSelector to AC terms? HOT 1
- Term change: correct reference to `ac:accessURI` in `ac:serviceExpectation` HOT 4
- Typo in dc:format HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ac.