251 lines
5.4 KiB
Plaintext
251 lines
5.4 KiB
Plaintext
|
head 1.11;
|
||
|
access;
|
||
|
symbols;
|
||
|
locks; strict;
|
||
|
comment @# @;
|
||
|
|
||
|
|
||
|
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.11
|
||
|
log
|
||
|
@Revision 11
|
||
|
@
|
||
|
text
|
||
|
@---+ Methods Supported by the Protocol
|
||
|
|
||
|
Currently the following request methods are identified to be useful for the new protocol.
|
||
|
They are mainly based on the DifferencesInRequestTypes of the CurrentProtocols.
|
||
|
Are they sufficient or do we need more convenient methods for specific problems?
|
||
|
|
||
|
|
||
|
---+++++ Major Request Types
|
||
|
|
||
|
* ProtocolFeaturesRequestMethodsPingRequest: Check if a provider or resource is online.
|
||
|
* ProtocolFeaturesRequestMethodsCapabilitiesRequest: Ask the provider for his "know concepts". That is metadata about the concepts that are mapped and are existing in his database.
|
||
|
* ProtocolFeaturesRequestMethodsMetadataRequest: Request a providers metadata only.
|
||
|
* ProtocolFeaturesRequestMethodsSearchRequest: Search a datasource to receive structured data.
|
||
|
* ProtocolFeaturesRequestMethodsInventoryRequest: Ask for a list of distinct terms within 1 concept. A scan request in BioCASE terminology.
|
||
|
* ProtocolFeaturesRequestMethodsCountRequest: Request the record number of a scan or a search. Is this a request on its own?
|
||
|
|
||
|
---+++++ Potential New Request Types
|
||
|
|
||
|
* a method for replication or complete data dumping?
|
||
|
|
||
|
* a method for write access to databases for feedbacks and annotations? What kind of requests do we need for this?Updates, Inserts, Deletes?
|
||
|
@
|
||
|
|
||
|
|
||
|
1.10
|
||
|
log
|
||
|
@Revision 10
|
||
|
@
|
||
|
text
|
||
|
@d10 3
|
||
|
a13 1
|
||
|
|
||
|
a14 1
|
||
|
|
||
|
a16 6
|
||
|
* ProtocolFeaturesRequestMethodsMetadataRequest: Request a providers metadata only.
|
||
|
|
||
|
* ProtocolFeaturesRequestMethodsCapabilitiesRequest: Ask the provider for his "know concepts". That is metadata about the concepts that are mapped and are existing in his database.
|
||
|
|
||
|
* ProtocolFeaturesRequestMethodsPingRequest: Check if a provider or resource is online.
|
||
|
|
||
|
@
|
||
|
|
||
|
|
||
|
1.9
|
||
|
log
|
||
|
@Revision 9
|
||
|
@
|
||
|
text
|
||
|
@d12 1
|
||
|
a12 1
|
||
|
* ProtocolFeaturesRequestMethodsScanRequest: Ask for a list of distinct terms within 1 concept. An inventory request in DiGIR terminology.
|
||
|
@
|
||
|
|
||
|
|
||
|
1.8
|
||
|
log
|
||
|
@Revision 8
|
||
|
@
|
||
|
text
|
||
|
@d20 1
|
||
|
@
|
||
|
|
||
|
|
||
|
1.7
|
||
|
log
|
||
|
@Revision 7
|
||
|
@
|
||
|
text
|
||
|
@d3 2
|
||
|
a4 1
|
||
|
Currently the following request methods are identified within the DiGIR and BioCASe protocols.
|
||
|
d8 1
|
||
|
a8 3
|
||
|
---+++++ Major Existing Request Types
|
||
|
|
||
|
Follow the links to see subtypes
|
||
|
d14 1
|
||
|
a14 1
|
||
|
* ProtocolFeaturesRequestMethodsCountRequest: Request the record number of a scan or a search
|
||
|
a19 1
|
||
|
---+++++ Possible New Request Types
|
||
|
d21 3
|
||
|
a23 1
|
||
|
* Do we need some method for replication or complete data dumping?
|
||
|
d25 1
|
||
|
a25 3
|
||
|
* Do we need write access to databases for feedbacks and annotations?
|
||
|
What kind of requests do we need for this?
|
||
|
Updates, Inserts, Deletes?
|
||
|
@
|
||
|
|
||
|
|
||
|
1.6
|
||
|
log
|
||
|
@Revision 6
|
||
|
@
|
||
|
text
|
||
|
@d7 1
|
||
|
a7 1
|
||
|
*Major Existing Request Types*
|
||
|
d15 1
|
||
|
a15 1
|
||
|
* ProtocolFeaturesRequestMethodsCountRequest: Request the number of something (records matched=search or distinct values=scan).
|
||
|
d21 1
|
||
|
d23 5
|
||
|
@
|
||
|
|
||
|
|
||
|
1.5
|
||
|
log
|
||
|
@Revision 5
|
||
|
@
|
||
|
text
|
||
|
@d7 1
|
||
|
a7 1
|
||
|
*Major Request Types*
|
||
|
d10 12
|
||
|
a21 5
|
||
|
ProtocolFeaturesRequestMethodsSearchRequest: Search a datasource to receive structured data.
|
||
|
ProtocolFeaturesRequestMethodsScanRequest: Ask for a list of distinct terms within 1 concept. An inventory request in DiGIR terminology.
|
||
|
ProtocolFeaturesRequestMethodsCountRequest: Request the number of something (records matched=search or distinct values=scan).
|
||
|
ProtocolFeaturesRequestMethodsMetadataRequest: Request a providers metadata only.
|
||
|
ProtocolFeaturesRequestMethodsCapabilitiesRequest: Ask the provider for his "know concepts". That is metadata about the concepts that are mapped and are existing in his database.
|
||
|
@
|
||
|
|
||
|
|
||
|
1.4
|
||
|
log
|
||
|
@Revision 4
|
||
|
@
|
||
|
text
|
||
|
@d10 5
|
||
|
a14 1
|
||
|
ProtocolFeaturesRequestMethodsSearchRequest: Search a datasource to receive structured data.
ProtocolFeaturesRequestMethodsScanRequest: Ask for a list of distinct terms within 1 concept. An inventory request in DiGIR terminology.
ProtocolFeaturesRequestMethodsCountRequest: Request the number of something (records matched=search or distinct values=scan).
ProtocolFeaturesRequestMethodsMetadataRequest: Request a providers metadata only.
ProtocolFeaturesRequestMethodsCapabilitiesRequest: Ask the provider for his "know concepts". That is metadata about the concepts that are mapped and are existing in his database.
|
||
|
@
|
||
|
|
||
|
|
||
|
1.3
|
||
|
log
|
||
|
@Revision 3
|
||
|
@
|
||
|
text
|
||
|
@d7 1
|
||
|
a7 1
|
||
|
*Major Types of Requests*
|
||
|
d10 1
|
||
|
a10 2
|
||
|
|
||
|
SearchRequest Search a datasource to receive structured data.
|
||
|
@
|
||
|
|
||
|
|
||
|
1.2
|
||
|
log
|
||
|
@Revision 2
|
||
|
@
|
||
|
text
|
||
|
@a9 1
|
||
|
<br>
|
||
|
d11 1
|
||
|
a11 1
|
||
|
<br> SearchRequest Search a datasource to receive structured data.
|
||
|
@
|
||
|
|
||
|
|
||
|
1.1
|
||
|
log
|
||
|
@Initial revision
|
||
|
@
|
||
|
text
|
||
|
@d6 1
|
||
|
a6 2
|
||
|
<br>
|
||
|
<br>
|
||
|
d8 1
|
||
|
@
|