UBL Transportation SC

Hello PSC and TSC,

A question has arisen regarding two of the entries in the table of
UBL document types, DocumentStatus and DocumentStatusRequest.  The
current version of the table lists these, incorrectly, as related
to Tendering, but in fact they appear to have come from the BII
ePrior project.  We think that the purpose was to get the status
of a sent Invoice, but it seems that the documents can be used
with other processes as well.

Currently these table entries are as follows:

    
    

It appears that the descriptions are OK, but we need new entries
for Processes Involved, Submitter Role, and Receiver Role.
Please advise.

Jon

I imagine that the DocumentStatus is very useful to inform about the
status of business documents that cannot be updated on the road (e.g. the
invoice) due to integrity requirements.

For instance the approval workflow required for issuing, bookkeeping,
payment, storage are all providing a status.

The life-cycle of a document produces some additional status that can be
expressed here.

As the DocumentStatus and the DocumentStatusRequest are associated to any
Process I believe that could apply to any Actor as well.

So my suggestion is to indicate that any Actor involved in the life-cycle
of the document can be acting as the sender and/or receiver.

The document life-cycle processes are not limited to the original trade
process but could be related to archiving, bookkeping, so on...

Roberto

> Hello PSC and TSC,
>
> A question has arisen regarding two of the entries in the table of
> UBL document types, DocumentStatus and DocumentStatusRequest.  The
> current version of the table lists these, incorrectly, as related
> to Tendering, but in fact they appear to have come from the BII
> ePrior project.  We think that the purpose was to get the status
> of a sent Invoice, but it seems that the documents can be used
> with other processes as well.
>
> Currently these table entries are as follows:
>
>     
>     
>
> It appears that the descriptions are OK, but we need new entries
> for Processes Involved, Submitter Role, and Receiver Role.
> Please advise.
>
> Jon
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>


-- 
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor

  Roberto Cisternino

  mobile: +39 328 2148123 begin_of_the_skype_highlighting              +39
328 2148123      end_of_the_skype_highlighting
  skype:  roberto.cisternino.ubl-itlsc

[UBL Technical Committee]
    http://www.oasis-open.org/committees/ubl

[UBL Online Community]
    http://ubl.xml.org

[UBL International Conferences]
    http://www.ublconference.org

[UBL Italian Localization Subcommittee]
    http://www.oasis-open.org/committees/ubl-itlsc

[Iniziativa divulgativa UBL Italia]
    http://www.ubl-italia.org

I imagine that the DocumentStatus is very useful to inform about the
status of business documents that cannot be updated on the road (e.g. the
invoice) due to integrity requirements.

For instance the approval workflow required for issuing, bookkeeping,
payment, storage are all providing a status.

The life-cycle of a document produces some additional status that can be
expressed here.

As the DocumentStatus and the DocumentStatusRequest are associated to any
Process I believe that could apply to any Actor as well.

So my suggestion is to indicate that any Actor involved in the life-cycle
of the document can be acting as the sender and/or receiver.

The document life-cycle processes are not limited to the original trade
process but could be related to archiving, bookkeping, so on...

Roberto

> Hello PSC and TSC,
>
> A question has arisen regarding two of the entries in the table of
> UBL document types, DocumentStatus and DocumentStatusRequest.  The
> current version of the table lists these, incorrectly, as related
> to Tendering, but in fact they appear to have come from the BII
> ePrior project.  We think that the purpose was to get the status
> of a sent Invoice, but it seems that the documents can be used
> with other processes as well.
>
> Currently these table entries are as follows:
>
>     
>     
>
> It appears that the descriptions are OK, but we need new entries
> for Processes Involved, Submitter Role, and Receiver Role.
> Please advise.
>
> Jon
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>


-- 
* JAVEST by Roberto Cisternino
*
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor

  Roberto Cisternino

  mobile: +39 328 2148123 begin_of_the_skype_highlighting              +39
328 2148123      end_of_the_skype_highlighting
  skype:  roberto.cisternino.ubl-itlsc

[UBL Technical Committee]
    http://www.oasis-open.org/committees/ubl

[UBL Online Community]
    http://ubl.xml.org

[UBL International Conferences]
    http://www.ublconference.org

[UBL Italian Localization Subcommittee]
    http://www.oasis-open.org/committees/ubl-itlsc

[Iniziativa divulgativa UBL Italia]
    http://www.ubl-italia.org

Thanks, Roberto!

If no one objects, I'll just put "Any" in the process, submitter,
and receiver fields.

Jon

Roberto Cisternino wrote:
> I imagine that the DocumentStatus is very useful to inform about the
> status of business documents that cannot be updated on the road (e.g. the
> invoice) due to integrity requirements.
> 
> For instance the approval workflow required for issuing, bookkeeping,
> payment, storage are all providing a status.
> 
> The life-cycle of a document produces some additional status that can be
> expressed here.
> 
> As the DocumentStatus and the DocumentStatusRequest are associated to any
> Process I believe that could apply to any Actor as well.
> 
> So my suggestion is to indicate that any Actor involved in the life-cycle
> of the document can be acting as the sender and/or receiver.
> 
> The document life-cycle processes are not limited to the original trade
> process but could be related to archiving, bookkeping, so on...
> 
> Roberto
> 
>> Hello PSC and TSC,
>>
>> A question has arisen regarding two of the entries in the table of
>> UBL document types, DocumentStatus and DocumentStatusRequest.  The
>> current version of the table lists these, incorrectly, as related
>> to Tendering, but in fact they appear to have come from the BII
>> ePrior project.  We think that the purpose was to get the status
>> of a sent Invoice, but it seems that the documents can be used
>> with other processes as well.
>>
>> Currently these table entries are as follows:
>>
>>     
>>     
>>
>> It appears that the descriptions are OK, but we need new entries
>> for Processes Involved, Submitter Role, and Receiver Role.
>> Please advise.
>>
>> Jon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
> 
> 

Thanks, Roberto!

If no one objects, I'll just put "Any" in the process, submitter,
and receiver fields.

Jon

Roberto Cisternino wrote:
> I imagine that the DocumentStatus is very useful to inform about the
> status of business documents that cannot be updated on the road (e.g. the
> invoice) due to integrity requirements.
> 
> For instance the approval workflow required for issuing, bookkeeping,
> payment, storage are all providing a status.
> 
> The life-cycle of a document produces some additional status that can be
> expressed here.
> 
> As the DocumentStatus and the DocumentStatusRequest are associated to any
> Process I believe that could apply to any Actor as well.
> 
> So my suggestion is to indicate that any Actor involved in the life-cycle
> of the document can be acting as the sender and/or receiver.
> 
> The document life-cycle processes are not limited to the original trade
> process but could be related to archiving, bookkeping, so on...
> 
> Roberto
> 
>> Hello PSC and TSC,
>>
>> A question has arisen regarding two of the entries in the table of
>> UBL document types, DocumentStatus and DocumentStatusRequest.  The
>> current version of the table lists these, incorrectly, as related
>> to Tendering, but in fact they appear to have come from the BII
>> ePrior project.  We think that the purpose was to get the status
>> of a sent Invoice, but it seems that the documents can be used
>> with other processes as well.
>>
>> Currently these table entries are as follows:
>>
>>     
>>     
>>
>> It appears that the descriptions are OK, but we need new entries
>> for Processes Involved, Submitter Role, and Receiver Role.
>> Please advise.
>>
>> Jon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
> 
>