Peppol Pre-Award - March 2023 Release

The Search Notice Request is a query transaction that requests notices using either a set of criteria for notices usually based on the eTendering Service Providers or Economic Operators ambitions and capabilities.

Namespace

query urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0

Attributes

Use	Name	Description
O	@startIndex	Start index The Search Notice Request and Response support the ability to iterate over a large result set matching a query by allowing multiple QueryRequest requests to be submitted in succession such that each query requests a different subset of results within the result set. This feature enables the server to handle queries that match a very large result set, in a scalable manner. This attribute is used to indicate which result must be returned as the first result when iterating over a large result set. The default value is 0, which returns the result set starting with index 0 (first result). Default value: `0`
O	@maxResults	Maximum number of results This attribute specifies a limit on the maximum number of results the sender wishes the query to return. A receiver of the request MUST return a result set whose size is less than or equal to the maxResults parameter depending upon whether enough results are available starting at startIndex. If the default value -1 is used, the receiver SHOULD return all the results. Default value: `-1`
M	@id	Search notice request identifier Specifies the unique identifier for an Identifiable Search Notice Request. In case of different start index for same QueryRequest is used it is possible to use the same Search Notice Request Identifier.

Child elements

Card	Name	Description
1..1	rim:Slot@name=SpecificationIdentification	Specification identification An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms.
1..1	rim:Slot@name=BusinessProcessTypeIdentifier	Business process type identifier Identifies the business process context in which the transaction appears. It enables the receiver to process the document in an appropriate way.
1..1	rim:Slot@name=IssueDateTime	Issue date time The issue date and time when the Serch Notice request is issued. The issue date time must have granularity of seconds, and include time zone information.
1..1	rim:Slot@name=SenderElectronicAddress	Contracting body electronic address The electronic address of the contracting body.
1..1	rim:Slot@name=ReceiverElectronicAddress	Economic operator electronic address The electronic address of the economic operator.
1..1	query:ResponseOption	Response option An element to control the type and structure of results within the corresponding QueryResponse. For the Search Notice Request it is required that the notices are included as repository Items to the QueryResponse. This is indicated through the returnType "LeafClassWithRepositoryItem".
1..1	query:Query	Query The definition of the query and its parameters. This is indicated through the queryDefinition="SearchNotice".

Rules

Identifier/Error message	Flag
PEPPOL-T011-R001 QueryRequest Identifier value MUST be expressed in a UUID syntax (RFC 4122).	fatal
PEPPOL-T011-R002 There MUST be exactly 1 SpecificationIdentification.	fatal
PEPPOL-T011-R003 There MUST be exactly 1 BusinessProcessTypeIdentifier.	fatal
PEPPOL-T011-R004 There MUST be exactly 1 IssueDateTime.	fatal
PEPPOL-T011-R005 There MUST be exactly 1 SenderElectronicAddress.	fatal
PEPPOL-T011-R006 There MUST be exactly 1 ReceiverElectronicAddress.	fatal
PEPPOL-T011-R077 Value MUST have a text.	fatal
PEPPOL-T011-R078 A Value for each SlotValue MUST be given.	fatal
PEPPOL-T011-R079 rim:Element be of type rim:StringValueType.	fatal
PEPPOL-T011-R080 At least one element MUST be given in a CollectionValueType.	fatal

query:QueryRequest