[tdwg-tapir] Minor changes
m.doering at bgbm.org
Tue May 22 18:12:09 CEST 2007
I fully agree to keep the variables simple. And if we specify one way
of retrieving the contact details thats fine for me. I just wanted to
point out this issue. I also dont mind to not have contact variables
at all. In this case a provider simply needs to map to those few ABCD
concepts in addition to pure darwin core.
On 22.05.2007, at 01:12, Renato De Giovanni wrote:
> Hi Markus,
> I agree we can add "subject" and "bibliographicalCitation" to the
> list of
> predefined variables. dct:modified is already present in
> We never considered multiplicity of environment variables or
> between them. In principle they should be just single independent
> My suggestion is to keep using this simple approach, unless we
> really need
> more complex functionality.
> Anyway, adding more values to the official list of variables is the
> of change that we should always be able to do without bringing
> impact to
> the existing implementations. Perhaps we could be more strict by
> adding a
> prefix to all TAPIR predefined variables and then defining the
> corresponding type as the union between the list of prefixed values
> any string that does not start with the prefix. This way at least we
> completely avoid name clashes with custom variables.
> I'm using simple rules to get the content of technicalContactName and
> technicalContactEmail. I just get the first system administrator of
> first technical host entity. In the case of contentContactName and
> contentContactEmail I get the first data administrator of the first
> supplier entity. The specification should also be explicit about this.
> Let me know if you have other ideas.
> Best Regards,
>> as you might have guessed all your proposed changes are fine with me.
>> Regarding the metadata variables I would make all existing metadata
>> values available as TAPIR variables. Maybe we can leave out the
>> indexing preferences. This would mean to add dc:subject,
>> dct:bibliographicCitation and dct:modified
>> I am not sure yet how you will retrieve metadata values for
>> RelatedEntities though. There might be multiple and do you have a
>> simple rule in mind what to do in that case? That's the case for all
>> contact data.
> tdwg-tapir mailing list
> tdwg-tapir at lists.tdwg.org
More information about the tdwg-tag