<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
In the case of both Darwin Core and Audubon Core, they exist in two
forms: a human-friendly version on the web and an official archived
version. For DwC, the human-friendly version is the web pages linked
to <a class="moz-txt-link-freetext" href="http://rs.tdwg.org/dwc/">http://rs.tdwg.org/dwc/</a> and for AC it's the pages linked to
<a class="moz-txt-link-freetext" href="http://terms.tdwg.org/wiki/Audubon_Core">http://terms.tdwg.org/wiki/Audubon_Core</a> . However, technically, the
standard is the set of documents that you get when you download the
archive from the standard's permanent URL,
<a class="moz-txt-link-freetext" href="http://www.tdwg.org/standards/450/">http://www.tdwg.org/standards/450/</a> for DwC, and
<a class="moz-txt-link-freetext" href="http://www.tdwg.org/standards/638/">http://www.tdwg.org/standards/638/</a> for AC . In the case of AC, the
archive contains the versions of those web pages as they existed at
ratification. In the case of DwC, it contains the web pages and RDF
documents as they existed after the last Decision that resulted in a
change to the standard
(<a class="moz-txt-link-freetext" href="http://rs.tdwg.org/dwc/terms/history/decisions/index.htm">http://rs.tdwg.org/dwc/terms/history/decisions/index.htm</a>
Decision-2013-10-09_13). <br>
<br>
This is a somewhat unwieldy system, since a citation of the "permanent
URL" for the standard leads to a version that is difficult to view and
which doesn't necessarily lead to the human-readable websites (although
in the cases of both AC and DwC, there are links to those websites if
one reads the fine print on the standard's cover page). But the point
of the archives is that they contain a version of the standard
documents in the form in which they existed the last time they were
officially approved. For some standards, the archives are the ONLY
version that is viewable at all. So it's important that those official
versions be stored in some immutable form that is not subject to
accidental tinkering or deletion as could happen with a regular website
(as we have seen happen with TAPIR). In the case of DwC, the standard
has changed over time. Those changes can be tracked on a large scale by
looking at the decision history, but on a detailed scale one would have
to look at the Darwin Core Google Code subversion repository (if one
knew to look there and what to look for among the myriad documents
stored there). <br>
<br>
In my view, the cover pages that resolve from the standards' cover
pages (e.g. <a class="moz-txt-link-freetext" href="http://www.tdwg.org/standards/638/">http://www.tdwg.org/standards/638/</a> ) should tell a user how
to locate a human-friendly web-viewable version, as well as how to
access an archive under version control (e.g. git or subversion) that
contains the official record. Not all of the standards have
human-friendly web versions. <br>
<br>
Steve<br>
<br>
Bob Morris wrote:
<blockquote
cite="mid:CADUi7O416v+aMZtPHw6GQZCfVjLMWLp80N_aqFpMMkNdqQ_3oA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<div dir="ltr">
<div>
<div>
<div>As to Audubon Core (AC), a little clarification is needed.<br>
<br>
</div>
The only thing so far adopted is the AC data model, more precisely "The
Audubon Core Multimedia Resources Metadata schema (“AC schema”, or
simply “AC”) is a set of metadata vocabularies for describing
biodiversity-related multimedia resources and collections. The
specification is independent of how these vocabularies may be
represented for machine use." [1] <br>
<br>
In particular, no artifacts akin to such things as the DwC normative
document [2] have been submitted for approval, nor have artifacts akin
to Simple Darwin Core [6] though some are under development (*, **).
In appearance, the AC documents [1, 3 and 4] together are a bit like
the most useful reference for DwC, namely [5]. But unlike [5], [3 and
4] are normative ([1] is not/). Those parts of AC are maintained in a
MediaWiki, and would be relatively pointles to put in a public source
code repository, perhaps except based on arguments of backup
sustainability. In such a case, they would be of use only to AC
maintainers, unless the repo happened to support MediaWiki.<br>
<br>
<br>
</div>
<div>Bob Morris<br>
</div>
<div>TDWG Image Interest Group co-convenor and AC <co-something or
other><br>
</div>
<div><br>
<br>
[1] <a moz-do-not-send="true"
href="http://terms.tdwg.org/wiki/Audubon_Core#Introduction">http://terms.tdwg.org/wiki/Audubon_Core#Introduction</a><br>
[2] <a moz-do-not-send="true"
href="http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf">http://rs.tdwg.org/dwc/rdf/dwctermshistory.rdf</a>
<br>
[3] <a moz-do-not-send="true"
href="http://terms.gbif.org/wiki/Audubon_Core_Structure">http://terms.gbif.org/wiki/Audubon_Core_Structure</a><br>
[4] <a moz-do-not-send="true"
href="http://terms.tdwg.org/wiki/Audubon_Core_Term_List">http://terms.tdwg.org/wiki/Audubon_Core_Term_List</a><br>
[5] <a moz-do-not-send="true" href="http://rs.tdwg.org/dwc/terms/">http://rs.tdwg.org/dwc/terms/</a><br>
[6] <a moz-do-not-send="true"
href="http://rs.tdwg.org/dwc/xsd/tdwg_dwc_simple.xsd">http://rs.tdwg.org/dwc/xsd/tdwg_dwc_simple.xsd</a><br>
<br>
</div>
(*) Readers beware: [2] is an RDF description of Darwin Core, not an
RDF description of biodiversity. <br>
</div>
(**) There will be a session devoted to AC at TDWG 2014 which will
hopefully be attended by those already using AC in one or another
specific, albeit unsubmitted form.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Sep 22, 2014 at 11:58 AM, James
Macklin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:james.macklin@gmail.com" target="_blank">james.macklin@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">I am also in favor of the GitHub repo but we really
need to hear from Stan about the status of the work he was having done
on the TDWG site. We will need to decide which is the "official" repo
but as others point out there is likely good reason to have
duplication! We also need to figure out who has time to do this if we
go forward. Looks like there have already been a couple of hands partly
raised ;-)
<div><br>
</div>
<div>Best, James</div>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Sep 22, 2014 at 10:29 AM, Bob
Morris <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:morris.bob@gmail.com" target="_blank">morris.bob@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<p dir="ltr">That was the answer in June too...</p>
<div>
<div>
<div class="gmail_quote">On Sep 22, 2014 9:23 AM, "Kampmeier,
Gail E" <<a moz-do-not-send="true" href="mailto:gkamp@illinois.edu"
target="_blank">gkamp@illinois.edu</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Stan
Blum is working with contractors on the new TDWG site. --Gail<br>
<br>
________________________________________<br>
From: <a moz-do-not-send="true"
href="mailto:tdwg-bounces@lists.tdwg.org" target="_blank">tdwg-bounces@lists.tdwg.org</a>
[<a moz-do-not-send="true" href="mailto:tdwg-bounces@lists.tdwg.org"
target="_blank">tdwg-bounces@lists.tdwg.org</a>] on behalf of Dave
Vieglais [<a moz-do-not-send="true" href="mailto:vieglais@ku.edu"
target="_blank">vieglais@ku.edu</a>]<br>
Sent: Monday, September 22, 2014 08:20<br>
To: Tim Robertson<br>
Cc: TDWG Content Mailing List; <a moz-do-not-send="true"
href="mailto:tdwg@lists.tdwg.org" target="_blank">tdwg@lists.tdwg.org</a>;
<a moz-do-not-send="true" href="mailto:tdwg-tag@lists.tdwg.org"
target="_blank">tdwg-tag@lists.tdwg.org</a>; Stoner, Dan<br>
Subject: Re: [tdwg] [tdwg-tag] another poke about Audubon Core status<br>
<br>
Would a GitHub organization satisfy the requirements of the TDWG site?<br>
<br>
- Dave V.<br>
<br>
On 22 Sep 2014, at 8:46, Tim Robertson wrote:<br>
<br>
> Hi Dan,<br>
><br>
> Thanks for your offer.<br>
><br>
> As far as I recall, the TDWG executive decided at the last meeting
to<br>
> move onto a whole new platform and put contractor money aside to
make<br>
> it happen.<br>
> I’m reluctant to point you at the tangled mess of the current
system<br>
> when I suspect it is to be replaced anyway. It really is a
convoluted<br>
> mess of Typo3 plugins, which try and keep a bunch of backend
systems<br>
> in sync and dues to bugs in there it does not work as expected. I<br>
> really don’t think it is something you want to get into, but I<br>
> sympathise that the TDWG site is broken and no-one is maintaining<br>
> it… a simpler vanilla CMS solution that even requires more manual<br>
> text editing etc. will be a far more manageable solution in my<br>
> opinion.<br>
><br>
> @TDWG Executive folks - is it still the intention to contract out
and<br>
> do a basic CMS site?<br>
> If not, I’ll try and pull up the code but I’d need your approval<br>
> to get him a DB dump as it holds user credentials / subscriptions
etc.<br>
> Please can you advise us? Anything we can do to help?<br>
><br>
> Thanks,<br>
> Tim<br>
><br>
><br>
> On 19 Sep 2014, at 23:05, Stoner, Dan <<a moz-do-not-send="true"
href="mailto:dstoner@acis.ufl.edu" target="_blank">dstoner@acis.ufl.edu</a>>
wrote:<br>
><br>
>> I see in the tdwg-tag mailing list archives that the status of
the<br>
>> Audubon Core Standard has been discussed recently:<br>
>><br>
>> <a moz-do-not-send="true"
href="http://lists.tdwg.org/pipermail/tdwg-tag/2014-June/002558.html"
target="_blank">http://lists.tdwg.org/pipermail/tdwg-tag/2014-June/002558.html</a><br>
>><br>
>><br>
>> So consider this another poke about getting the web site
updated with<br>
>> the official status of the Standard.<br>
>><br>
>> If there is anything I can do to facilitate the web site
update,<br>
>> please let me know (as in, I am volunteering to hack code or
whatever<br>
>> is needed).<br>
>><br>
>><br>
>> Thanks,<br>
>><br>
>> Dan Stoner<br>
>> iDigBio / ACIS Laboratory<br>
>> University of Florida<br>
>> _______________________________________________<br>
>> tdwg-tag mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:tdwg-tag@lists.tdwg.org" target="_blank">tdwg-tag@lists.tdwg.org</a><br>
>> <a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-tag" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-tag</a><br>
>><br>
><br>
> _______________________________________________<br>
> tdwg-tag mailing list<br>
> <a moz-do-not-send="true" href="mailto:tdwg-tag@lists.tdwg.org"
target="_blank">tdwg-tag@lists.tdwg.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-tag" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-tag</a><br>
_______________________________________________<br>
tdwg mailing list<br>
<a moz-do-not-send="true" href="mailto:tdwg@lists.tdwg.org"
target="_blank">tdwg@lists.tdwg.org</a><br>
<a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg</a><br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a moz-do-not-send="true"
href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-content"
target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
</blockquote>
</div>
</div>
</div>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a moz-do-not-send="true"
href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-content"
target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Robert A. Morris<br>
<br>
Emeritus Professor of Computer Science<br>
UMASS-Boston<br>
100 Morrissey Blvd<br>
Boston, MA 02125-3390<br>
<br>
<br>
Filtered Push Project<br>
Harvard University Herbaria<br>
Harvard University<br>
<br>
email: <a moz-do-not-send="true" href="mailto:morris.bob@gmail.com"
target="_blank">morris.bob@gmail.com</a><br>
web: <a moz-do-not-send="true" href="http://efg.cs.umb.edu/"
target="_blank">http://efg.cs.umb.edu/</a><br>
web: <a moz-do-not-send="true" href="http://wiki.filteredpush.org"
target="_blank">http://wiki.filteredpush.org</a><br>
<a moz-do-not-send="true" href="http://www.cs.umb.edu/%7Eram"
target="_blank">http://www.cs.umb.edu/~ram</a><br>
===<br>
The content of this communication is made entirely on my<br>
own behalf and in no way should be deemed to express<br>
official positions of The University of Massachusetts at Boston or
Harvard University.
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Steven J. Baskauf, Ph.D., Senior Lecturer
Vanderbilt University Dept. of Biological Sciences
postal mail address:
PMB 351634
Nashville, TN 37235-1634, U.S.A.
delivery address:
2125 Stevenson Center
1161 21st Ave., S.
Nashville, TN 37235
office: 2128 Stevenson Center
phone: (615) 343-4582, fax: (615) 322-4942
If you fax, please phone or email so that I will know to look for it.
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu">http://bioimages.vanderbilt.edu</a>
<a class="moz-txt-link-freetext" href="http://vanderbilt.edu/trees">http://vanderbilt.edu/trees</a>
</pre>
</body>
</html>