The Publish Notice is a transaction which sends notices and their attachments as new notices or updates to already known notices to the publication offices.

Namespace
lcm urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0
Attributes
Use Name Description
M @id

Publish notice identifier
Specifies the unique identifier for an Identifiable Publish Notice.

M @mode

Mode
Mode for the publishment of the notice, regarding if it is new or a change to an already existing notice. If a notice does not exist, the publishing office MUST create it as a new notice. If a notice already exists,the publishing office MUST not alter the existing object and instead it MUST create a new version of the existing object using the state of the submitted notice. So it is ensured that the old notice will not be overwritten but stays readable as an outdated version.

Fixed value: CreateOrVersion

Child elements
Card Name Description
1..1 rim:Slot@name=SpecificationIdentification

Specification identification
Specifies the unique identifier for an the Request to publish a notice.

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 Publish Notice 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 identifier
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 rim:Slot@name=PublicationRequested

Publication requested
This indicator shows if the attached notice needs to be published or if it only needs to be validated by the publication body. The check by the publication body can help the contracting party to determine the validity of the notice with regard to a possible publication.

1..1 rim:Slot@name=NoticePublicationDatePreferred

Issue date time
The "Notice Publication Date Preferred" is the date on which the buyer wishes the notice to be published. It can be used to help the buyer respect the requirements that exist between publications at national and European levels.

1..1 rim:RegistryObjectList

Registry object list
The Registry Object List contains the information to be published. It describes the notice instances that need to be published.

Rules
Identifier/Error message Flag
PEPPOL-T015-R001
LCM Identifier value MUST be expressed in a UUID syntax (RFC 4122).
fatal
PEPPOL-T015-R002
A Notice SubmitObjectsRequest MUST have an identifier.
fatal
PEPPOL-T015-R003
There MUST be exactly 1 BusinessProcessTypeIdentifier.
fatal
PEPPOL-T015-R004
There MUST be exactly 1 IssueDateTime.
fatal
PEPPOL-T015-R005
There MUST be exactly 1 SenderElectronicAddress.
fatal
PEPPOL-T015-R006
There MUST be exactly 1 ReceiverElectronicAddress.
fatal
PEPPOL-T015-R020
There MUST be exactly 1 PublicationRequested.
fatal
PEPPOL-T015-R037
Value MUST have a text.
fatal
PEPPOL-T015-R038
A Value for each SlotValue MUST be given.
fatal
PEPPOL-T015-R039
rim:Element be of type rim:StringValueType.
fatal
PEPPOL-T015-R040
At least one element MUST be given in a CollectionValueType.
fatal