Changes between Version 5 and Version 6 of RuSqr

Timestamp:

Nov 1, 2010, 1:01:10 PM (14 years ago)

Author:

zach

Comment:

--

RuSqr

@@ -36 +36 @@
 For a simple query, a validation process takes place on the server side to verify that the following set of rules is satisfied.
 
-The four first fields i.e. ID, ResourceID, Operation, ObservationArea do not have any specific requirements.
+The four first fields i.e. ID, !ResourceID, Operation, !ObservationArea do not have any specific requirements.
 
-When one of the fields EoI, Attribute, EntityType, Value, QoA, QoI, Cost, an IOPEType has to be specified. As a matter of fact this part of the lookup will try to identify tuples of parameters e.g. (EoI, EntityType) when an EoI and an EntityType are specified that belongs to the same type of IOPE, for instance Input. The IOPEType parameter can take a value in the set {Input, Output, PreCondition, PostCondition, any}. The GUI returns a set of bindings matching the request.
+When one of the fields !EoI, Attribute, !EntityType, Value, QoA, QoI, Cost, an IOPEType has to be specified. As a matter of fact this part of the lookup will try to identify tuples of parameters e.g. (!EoI, !EntityType) when an EoI and an !EntityType are specified that belongs to the same type of IOPE, for instance Input. The IOPEType parameter can take a value in the set {Input, Output, !PreCondition, !PostCondition, any}. The GUI returns a set of bindings matching the request.
 
 For a complex query, the Template has to match the schema specified at [https://ncit-cluster.grid.pub.ro/trac/Sensei-Cookbook/attachment/wiki/ED/binding.xsd], the server returns an error otherwise.