Markus,
Thanks for pointing out those files. I didn't remember them.
I just had to make a few changes to get everything working properly. I
also updated the file that maps terms from the new DarwinCore to the older
versions, so that TapirLink providers can easily migrate.
I took the liberty to copy most files to rs.tdwg.org/tapir just to keep
tapir-related things together. More specifically I copied:
cns:
http://rs.tdwg.org/tapir/cns/dwc_terms_2009_09_23.xml
simple output model:
http://rs.tdwg.org/tapir/cs/dwc/terms/2009-09-23/model/dwc_simple.xml
simple darwin schemas:
http://rs.tdwg.org/tapir/rs/
Please let me know if you think the corresponding files still need to
remain in darwincore.googlecode.com because in this case I should better
add it as a new default trusted domain for TapirLink providers.
Best Regards,
--
Renato
--
> Paul,
> you only need to change some configuration in TapirLink to enable the new
> darwin core terms for configuration.
> In addition to the output model for tapir we also host the official CNS
> (concept name server) file that tells tapir software which concepts/terms
> are available for mapping. You can find it next to the output model here:
> http://darwincore.googlecode.com/svn/trunk/tapir/dwc_terms.cns
>
> In TapirLink the best option is to update the tapirlink/config/schemas.xml
> file like this, so the new terms become available for any new resource:
>
> <?xml version="1.0" encoding="utf-8" ?>
> <schemas>
> <!-- renamed to dwc 1.4 to avoid confusion -->
> <schema alias="DarwinCore 1.4">
> <namespace>http://rs.tdwg.org/dwc/dwcore/</namespace>
> <location>http://rs.tdwg.org/tapir/cns/dwc_1_4.xml</location>
> <handler>CnsSchemaHandler_v2</handler>
> </schema>
> <schema alias="DarwinCore 1.4 curatorial extension">
> <namespace>http://rs.tdwg.org/dwc/curatorial/</namespace>
> <location>http://rs.tdwg.org/tapir/cns/dwcur_1_4.xml</location>
> <handler>CnsSchemaHandler_v2</handler>
> </schema>
> <schema alias="DarwinCore 1.4 geospatial extension">
> <namespace>http://rs.tdwg.org/dwc/geospatial/</namespace>
> <location>http://rs.tdwg.org/tapir/cns/dwgeo_1_4.xml</location>
> <handler>CnsSchemaHandler_v2</handler>
> </schema>
> <schema alias="ABCD 2.06">
> <namespace>http://www.tdwg.org/schemas/abcd/2.06</namespace>
> <location>http://rs.tdwg.org/tapir/cns/abcd_2_06.xml</location>
> <handler>CnsSchemaHandler_v2</handler>
> </schema>
> <!-- added to support new darwin core terms -->
> <schema alias="DarwinCore">
> <namespace>http://rs.tdwg.org/dwc/terms/</namespace>
> <location>http://darwincore.googlecode.com/svn/trunk/tapir/dwc_terms.cns</location>
> <handler>CnsSchemaHandler_v2</handler>
> </schema>
> </schemas>
>
>
> With this the new terms become available in the tapir link configurator.
> Alternatively you can insert the link to the cns file manually for every
> resource you want to configure in step5 (Mapping) at the bottom under
> "Location of additional schema:" enter
> http://darwincore.googlecode.com/svn/trunk/tapir/dwc_terms.cns and select
> CNS XML file.
>
>
> I am checking in this schema.xml change into the trunk of TapirLink at
> sourceforge now.
>
> Markus
>
>
> On Aug 8, 2010, at 13:38, Paul Flemons wrote:
>
>> Tim,
>> I think we will use TapirLink for now in which case we need to have the
>> Simple Darwin Core schema implemented in TapirLink.
>> Any volunteers for doing that?
>>
>> We will be interested in the IPT version at RC5.
>>
>> Ta
>> Paul
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
The Australian Museum.
The views in this email are those of the user and do
not necessarily reflect the views of the Australian Museum. The information
contained in this email message and any accompanying files is or may be
confidential and is for the intended recipient only. If you are not the intended
recipient, any use, dissemination, reliance, forwarding, printing or copying of
this email or any attached files is unauthorised. If you are not the intended
recipient, please delete it and notify the sender. The Australian Museum does
not guarantee the accuracy of any information contained in this e-mail or
attached files. As Internet communications are not secure, the Australian Museum
does not accept legal responsibility for the contents of this message or
attached files.
Please consider the environment before printing this email.