November 2006 - tdwg-tag - lists.tdwg.org

RE: [tdwg-tapir] Problem with Tapir and Outputmodel.
by "Döring, Markus" 17 Nov '06

17 Nov '06

Ramon, It looks the way renato said. The wrapper complaints about missing subelements in: /Species/Record/RecordInformation /Species/Record /Species So its something within RecordInformation that causes the trouble. So this could be: SpeciesRecordID Language SpeciesRecordAuthors/Text DateLastModified TargetAudience/Text It doesn't only matter if the elements are mapped. If the query returns a NULL for one of the concepts, the element is removed. If that element was mandatory, its parent element is removed and so on. Is that the problem you are facing? Markus > -----Original Message----- > From: tdwg-tapir-bounces(a)lists.tdwg.org > [mailto:tdwg-tapir-bounces@lists.tdwg.org] On Behalf Of > Renato De Giovanni > Sent: Donnerstag, 16. November 2006 19:17 > To: tdwg-tapir(a)lists.tdwg.org > Subject: Re: [tdwg-tapir] Problem with Tapir and Outputmodel. > > > Ramón, > > This seems to be something specific to PyWrapper, not the protocol. > Looking at the pywrapperPCORE3.xml respose I can see that the query > was probably asking for three specific records by id. But you can > also find a diagnostic element saying "The element > /Species/Record..Sequence:99865776 was dropped 3 times because of > missing required subelements or attributes". > > As far as I know PyWrapper is clever enough not to include in the > response records that do not have all necessary data. So my guess is > that all three records don't have data for one or more mandatory > subelements/attributes defined in the output model. > > Hope this helps, > -- > Renato > > On 14 Nov 2006 at 9:18, Ramón Pérez Pérez wrote: > > > Hi all, > > > > This is Ramón Pérez of GBIF Spain. We are using tapir provider in a > > project with Inbio (Costa Rica). We want to integrate > information about > > species and specimens. > > > > I have configured a tapir provider but it doesn't do what I > expect it > > to do. > > > > I attach a compress file with the config file, two outputModel > > (pcore2.xml and pcore3.xml) and the pywrapper results > > (pywrapperpcore2.xml and pywrapperpcore3.xml). 1. > > Outputmodelpcore2.xml: the pywrapper does the query and returns the > > results. 2. Outputmodelpcore3.xml: the pywrapper does the query and > > informs me that it has 3 results. But it can't return me the schema > > defined by the outputmodel. > > > > I have revised the output model but I can't see the error. I think > > that it is an error of the pywrapper :-( > > > > I would be very grateful if you may help me. It is very > important for > > me. > > > > Best regards, > > > > Ramón. > > _______________________________________________ > tdwg-tapir mailing list > tdwg-tapir(a)lists.tdwg.org > http://lists.tdwg.org/mailman/listinfo/tdwg-> tapir >

3 2

[tdwg-tapir] Tapir SVN reaches TDWG
by "Döring, Markus" 17 Nov '06

17 Nov '06

Hello all, in our attempt to migrate all TAPIR resources to TDWG, we have frozen the current tapir subversion repository in berlin and moved it to tdwg, preserving all its history. Big thanks to Ricardo! As you might know, the subversion system in tdwg is used for the rs.tdwg.org domain. The latest HEAD version of the SVN is always shown under http://rs.tdwg.org/tapir, which is our namespace too. The tdwg SVN is accessible through https https://rs.tdwg.org/tapir, but you will need a TDWG account to do so. In case you want write access to the svn, please announce so on this list. We are currently creating new logins for all existing users of the berlin tapir svn and inform them individually. The old tapir svn in berlin is frozen and will be removed completely after some time once the new repository is well established. It can still be accessed at http://ww2.biocase.org/svn/tapir/ We also hope to move the tapir wiki pretty soon too. The new wiki can then be reached at http://wiki.tdwg.org/TAPIR Thanks, Markus

1 0

[tdwg-tapir] Problem with Tapir and Outputmodel.
by Ramón Pérez Pérez 16 Nov '06

16 Nov '06

Hi all, This is Ramón Pérez of GBIF Spain. We are using tapir provider in a project with Inbio (Costa Rica). We want to integrate information about species and specimens. I have configured a tapir provider but it doesn't do what I expect it to do. I attach a compress file with the config file, two outputModel (pcore2.xml and pcore3.xml) and the pywrapper results (pywrapperpcore2.xml and pywrapperpcore3.xml). 1. Outputmodelpcore2.xml: the pywrapper does the query and returns the results. 2. Outputmodelpcore3.xml: the pywrapper does the query and informs me that it has 3 results. But it can't return me the schema defined by the outputmodel. I have revised the output model but I can't see the error. I think that it is an error of the pywrapper :-( I would be very grateful if you may help me. It is very important for me. Best regards, Ramón.

2 1

[Tdwg-guid] LSID and RDF
by Kevin Richards 13 Nov '06

13 Nov '06

Hi all FYI A copy of the tutorial/presentation I gave at TDWG has bee put on the GUID web site at http://www.tdwg.org/subgroups/guid/documents-reports/ - the link to the tutorial and a short description of it http://www.tdwg.org/dav/subgroups/guid/LSIDAndRDF.htm - the actual tutorial I'll also take this opportunity to reiterate the fact that the Microsoft .NET version of the LSID framework is completed and available on Source Forge at http://sourceforge.net/projects/lsid-dotnet/ The Index Fungorum LSID resovler is currently using this .NET LSID framework. Kevin ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. Landcare Research http://www.landcareresearch.co.nz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1 0

[Tdwg-guid] EGU 2007 Call for abstracts: "Building A Global Geosciences Cyberinfrastructure
by Robert Huber 08 Nov '06

08 Nov '06

(Appologies for cross-posting) Dear Colleague, Please consider submitting an abstract to: SSP11/GI11 "Building A Global Geosciences Cyberinfrastructure" <http://www.cosis.net/members/meetings/sessions/information.php?p_id=244&s_i d=4465> Co-organized by Geosciences Instrumentation and Data Systems (GI) and Stratigraphy, Sedimentology and Palaeontology (SSP) Convenors: Jens Klump (GFZ Potsdam), Robert Huber (Univ. Bremen/MARUM), Walt Snyder (Boise State Univ.) Description: Data on stratigraphy, sedimentology and paleontology are heterogeneous and diverse. The same is true for geophysics, tectonics, paleoceanography, and other fields that all need to be integrated for a better understanding of the processes shaping our planet Earth. In many countries around the globe, a rapidly increasing number of Geoscience projects are developing and maintaining digital data and information systems together with tools for data analysis and visualization. The emerging Geoscience cyberinfrastructure must be an international effort in order to successfully promote advances in geoscience research and enable new approaches to addressing scientific problems that in turn lead to new discoveries and an improved understanding of the Earth. In order to maximize the impact of these globally distributed Geoinformatics resources, it is essential that these efforts be collaborative and integrated. This sessions focuses on collaboration and integration between cyberinfrastructure projects in Geoscience and has two objectives: (1) to discuss how the political, cultural, organizational, and technical challenges towards a truly global cyberinfrastructure for the Geosciences have been addressed, and (2) to highlight examples of international collaborations that successfully coordinate and integrate their efforts. Important Deadlines: 08 December 2006 - Deadline for Support Applications 15 January 2007 - Deadline for Receipt of Abstracts 15 - 20 April 2007 - European Geosciences Union - General Assembly 2007 Yours sincerely, Dr. Robert Huber WDC-MARE / PANGAEA - www.pangaea.de, www.wdc-mare.org Stratigraphy.net - www.stratigraphy.net _____________________________________________ MARUM - Institute for Marine Environmental Sciences (location) University Bremen Leobener Strasse POP 330 440 28359 Bremen Phone ++49 421 218-65593, Fax ++49 421 218-65505 e-mail rhuber(a)wdc-mare.org, robert.huber(a)stratigraphy.net

1 0

[tdwg-tapir] Fwd: [wfs-dev] name change
by Javier de la Torre 02 Nov '06

02 Nov '06

Jeje, Funny. In OGC they are also considering splitting WFS into several levels of complexity and to not force the use of GML, I wonder when they are going to start talking about WFS Lite. Cheers. Begin forwarded message: > From: "Panagiotis (Peter) A. Vretanos" <pvretano(a)cubewerx.com> > Date: 2 de noviembre de 2006 20:44:25 GMT+01:00 > To: Raj Singh <rsingh(a)opengeospatial.org> > Cc: wfsbasic.users(a)opengeospatial.org, wfs-dev(a)opengeospatial.org > Subject: Re: [wfs-dev] name change > > Well, > > Not quite a FULL WFS without transactions. > > The WFS includes the capabilities and filter capabilities to allow > servers to declare what the are capable of. > > This means that servers can declare that they support very little. > For > example, the following filter capabilities: > > <ogc:Filter_Capabilities xmlns:ogc="http://www.opengis.net/ogc"> > <ogc:Spatial_Capabilities> > <ogc:GeometryOperands xmlns:gml="http://www.opengis.net/gml"> > <ogc:GeometryOperand>gml:Point</ogc:GeometryOperand> > </ogc:GeometryOperands> > <ogc:SpatialOperators> > <ogc:SpatialOperator name="BBOX" /> > </ogc:SpatialOperators> > </ogc:Spatial_Capabilities/> > <ogc:Id_Capabilities> > <ogc:EID /> > </ogc:Id_Capabilities> > </ogc:Filter_Capabilities> > > indicates that this server only supports BBOX on gml:Point types. > > So the most complex request you could form (on as single feature type) > would be something like: > > http://www.server.com/wfs/wfs.cgi? > service=WFS&version=1.1.0&request=GetCapabilities&typeName=myns:Points > OfInterest&BBOX=10,10,20,20 > > I would prefer that this work (WFS Simple I mean) be rolled back into > the WFS specification as a level 0 conformance class rather than > having > two independent specifications that do similar things ... even if this > means making GML a preferred but not mandatory output format for the > GetFeature operation. > > The WFS already allows other formats, other than GML, to be > supported so > something like KML is well within the scope of the current spec.. > > Ciao. > > Raj Singh wrote: >> In the WFS specification the idea of a 'Basic WFS' is mentioned that >> pertains to a full WFS that is read-only--no transactional support. >> This is quite different from the intent of this effort, so the >> working name has been changed to 'WFS Simple'. >> --- >> Raj >> >> >> _______________________________________________ >> wfs-dev mailing list >> wfs-dev(a)opengeospatial.org >> https://mail.opengeospatial.org/mailman/listinfo/wfs-dev >> > > -- > Panagiotis (Peter) A. Vretanos CubeWerx Inc. > Big Kahuna (Senior Database Developer) http://www.cubewerx.com > Tel. 416-701-1985 Fax. 416-701-9870 pvretano(a)cubewerx.com > > "If you want to make an apple pie from scratch, you must first > create the universe." -- Carl Sagan > _______________________________________________ > wfs-dev mailing list > wfs-dev(a)opengeospatial.org > https://mail.opengeospatial.org/mailman/listinfo/wfs-dev

1 0