[OASIS Issue Tracker] (UBL-46) TenderingQuestion and TenderingAnswer requirements

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63351#comment-63351 ] 

Ken Holman commented on UBL-46:
-------------------------------

I have made a few minor grammatical changes to some of the descriptions.

Now I am trying to picture an application working with these messages in order to build a threaded discussion presentation.  If a response to a request can, itself, be responded to, should it not have the same "LatestReplyDate" and "LatestReplyTime"?

And, in a response to a response, who is the requestor and who is the responder?

The two documents look almost identical ... is there a way to make one document and use it to both initiate a response with an inquiry as well as become something that can have a response?  After all, there are not two kinds of email message, just one.

Oh ... perhaps I see the answer.  Maybe not, though.  I note that GeneralEnquiry has ParentDocumentReference.  Is that the distinction?  If I respond to a GeneralEnquiry with another GeneralEnquiry, is that soliciting a response?  Would a discussion end with a GeneralResponse?

The way you have modeled it, I think I can do everything with GeneralEnquiry:  both ask the question and respond to the question.  And when I respond to the question, and I want a reply to my response, I can specify that.  I would then change the definition of "ResponderParty" to be "The party to whom the enquiry is directed".  Then we might simply this to "FromParty" and "ToParty" so as not to layer on any confusion about the role of requestor/responder when both are sending messages.

I can't see anything in the response that makes it special, and in a threaded discussion (that they asked for), a response has to be treated the same as an inquiry.  Can we toss out GeneralResponse and build everything they need with only GeneralInquiry?

> TenderingQuestion and TenderingAnswer requirements
> --------------------------------------------------
>
>                 Key: UBL-46
>                 URL: https://issues.oasis-open.org/browse/UBL-46
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: New Feature
>          Components: Documents and business objects
>         Environment: Request received from Cécile Guasch, EC.
>            Reporter: Oriol Bausa Peris
>            Assignee: Ken Holman
>            Priority: Minor
>
>  My requirements for the TenderingQuestion and TenderingAnswer would be the following and I would like to know whether it is worth mentioning.
>  
> ·         We received a requirement to follow a "conversation thread", I do not think that the existing messages cater for it at first sight.
> ·         We would also need to be able to provide the requirement timeline for an answer to a question in certain cases.
> ·         In the post award we also encountered the need to manage questions and answers and I found it a pity that the current message is limited to 'tendering'.
>  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)