[tdwg-tapir] Tapir > Capabilities > Schemas > Concepts

"Döring, Markus" m.doering at BGBM.org
Thu Nov 3 16:20:36 CET 2005

you are right in your core thoughts.
If we do not allow dynamic views we dont need to expose the mapped conceptual schema "concepts". But thats only the case if we treat the static views as the source of our concepts. So yuo would have to use only those static view concepts (may I call them "local" concepts as defined in the local/inline view) in your request for filters. You couldnt request a darwincore record and specify a filter from abcd for example.

One more thing about the concepts: their id or "path" attribute looks like an xpath, but it is not! It is treated as a unique string and nothing more. So there is no implied parent/child relationship between any concepts - they are just a list of independent ids.

If a concept is searchable (default=true), then you can use it in a filter. If its not searchable, you can still use it in the response structure! Theres another attribute called mandatory which a provider can set to indicate that this concept is required to be rpesent in a response structure. Useful to force people to include some IPR for example.


-----Ursprüngliche Nachricht-----
Von: tdwg-tapir-bounces at lists.tdwg.org [mailto:tdwg-tapir-bounces at lists.tdwg.org] Im Auftrag von Roger Hyam
Gesendet: Donnerstag, 3. November 2005 14:17
An: tdwg-tapir at lists.tdwg.org
Betreff: [tdwg-tapir] Tapir > Capabilities > Schemas > Concepts

I am a little confused as to what is included in the capabilities response under capabilities/schemas/schema.

The annotation says:

"Each known and mapped concept of a schema listed with a boolean flag indicating if its searchable (default = true)."

I have a genus field in my database and I map it to the following concept:

<concept path="/DataSet/TaxonNames/TaxonName/CanonicalName/Genus" searchable="true" />

Should I also include the parent concepts:

<concept path="/DataSet/TaxonNames/TaxonName/CanonicalName" searchable="false" /> <concept path="/DataSet/TaxonNames/TaxonName" searchable="false" /> <concept path="/DataSet/TaxonNames" searchable="false" /> <concept path="/DataSet" searchable="false" />

or are they implied? I presume if they are included then they aren't searchable as they can't be used to build filters.

Does this: 

<concept path="/DataSet/TaxonNames/TaxonName/CanonicalName/Genus" searchable="true" />


*	This concept has been mapped to data and can be used in arbitrary response structures and filters in combination with concepts from any of the other conceptual schemas listed in here.

If so is the entire schemas section of capabilities response optional if arbitrary views are not supported? Both the schemas and concepts are given in views anyhow - so do we need to list them here?

Your thoughts most appreciated - I may just have the wrong end of the stick.



 Roger Hyam
 Technical Architect
 Taxonomic Databases Working Group
 roger at tdwg.org
 +44 1578 722782

More information about the tdwg-tag mailing list