257 lines
4.2 KiB
Plaintext
257 lines
4.2 KiB
Plaintext
head 1.12;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.12
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.11;
|
|
|
|
1.11
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.10;
|
|
|
|
1.10
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.9;
|
|
|
|
1.9
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.8;
|
|
|
|
1.8
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.7;
|
|
|
|
1.7
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.6;
|
|
|
|
1.6
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@Initial revision
|
|
@
|
|
|
|
|
|
1.12
|
|
log
|
|
@Revision 12
|
|
@
|
|
text
|
|
@---+++ AbcdConcept0004
|
|
|
|
---+++++ Identifier
|
|
|
|
<verbatim>DataSets/DataSet/TechnicalContacts/TechnicalContact</verbatim>
|
|
|
|
|
|
|
|
---+++++ Group
|
|
|
|
Meta
|
|
|
|
---+++++ Subgroup
|
|
|
|
UDDI
|
|
|
|
---+++++ Full Name
|
|
|
|
Technical Contact
|
|
|
|
---+++++ Documentation
|
|
|
|
A technical contact normally representing the agent acting as the publisher of the dataset in the network.
|
|
|
|
---+++++ Content
|
|
|
|
This is a metadata item normally not used for end-user display and is an element for the GBIF UDDI registry.
|
|
|
|
Questions and feedback about the availability of a provider or resource should be directed to the technical contact. The technical contact normally represents the agent acting as the publisher of the dataset in the network.
|
|
|
|
---++++ Recommended or Prescribed Values
|
|
|
|
|
|
---+++++ Example Value
|
|
|
|
|
|
---+++++ Example Explanation
|
|
|
|
|
|
---+++++ Reviewer
|
|
Berendsohn 22 Apr 2005
|
|
|
|
---++++ Editorial Notes
|
|
@
|
|
|
|
|
|
1.11
|
|
log
|
|
@Revision 11
|
|
@
|
|
text
|
|
@d41 1
|
|
a41 1
|
|
|
|
@
|
|
|
|
|
|
1.10
|
|
log
|
|
@Revision 10
|
|
@
|
|
text
|
|
@a43 2
|
|
|
|
$$Yael$$ We have a little problem here. The Technical Contact itself is an Agent, but it functions as Metadata. I think we should group all items underneath as Agent, but the actual person etc. should be grouped according to their role.
|
|
@
|
|
|
|
|
|
1.9
|
|
log
|
|
@Revision 9
|
|
@
|
|
text
|
|
@d11 1
|
|
a11 1
|
|
Agent
|
|
d15 1
|
|
d45 1
|
|
a45 3
|
|
I have copied the information from TechnicalContacts to this element instead (the parts that make sense in this context).
|
|
|
|
Perfect. Btw, the search for the $$ Walter thing has worked very nicely, try to use it for Yael. You just have to delete the $$ when you read and answered the message.
|
|
@
|
|
|
|
|
|
1.8
|
|
log
|
|
@Revision 8
|
|
@
|
|
text
|
|
@d46 1
|
|
a46 1
|
|
$$Yael$$ Perfect. Btw, the search for the $$ Walter thing has worked very nicely, try to use it for $$Yael$$. You just have to delete the $$ when you read and answered the message.
|
|
@
|
|
|
|
|
|
1.7
|
|
log
|
|
@Revision 7
|
|
@
|
|
text
|
|
@d44 1
|
|
a44 1
|
|
Nothing in the schema for this element - I just added a group - Agent. Should I take the information from Micro Agent-Contact etc?
|
|
d46 1
|
|
a46 3
|
|
$$Yael$$ The group is correct. The information belonging to this item is now under the container element TechnicalContacts. My suggestion was to restrict the text to individual element (i.e. this one, TechnicalContact), and restrict the documentation for the container element to group (container). We may still change our mind later on, but for the time being I suggest to proceed like that, i. e. to move the information now in the TechnicalContacts element to this one.
|
|
|
|
$$Walter$$ I have copied the information from TechnicalContacts to this element instead (the parts that make sense in this context).
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@Revision 6
|
|
@
|
|
text
|
|
@d22 1
|
|
d26 3
|
|
d47 2
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@Revision 5
|
|
@
|
|
text
|
|
@d40 3
|
|
a42 1
|
|
$$Walter$$ Nothing in the schema for this element - I just added a group - Agent. Should I take the information from Micro Agent-Contact etc?
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@Revision 4
|
|
@
|
|
text
|
|
@d40 1
|
|
a40 1
|
|
$$Walter$$ Nothing in the schema for this element - I just added a group - Agent. Should I take the information from MicroAgent-Contact etc?
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@Revision 3
|
|
@
|
|
text
|
|
@d18 1
|
|
d40 1
|
|
a40 1
|
|
$$Walter$$ Nothing in the schema for this element. I just added a group - Agent.
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@Revision 2
|
|
@
|
|
text
|
|
@d38 2
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@a0 1
|
|
|
|
d11 1
|
|
a37 2
|
|
|
|
|
|
@
|