[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-55) Should new Tender Status Inquiry be Tender Status Enquiry
[ https://issues.oasis-open.org/browse/UBL-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64382#comment-64382 ]
Ken Holman edited comment on UBL-55 at 11/18/16 6:31 PM:
---------------------------------------------------------
Forgive me, Kees, but I missed the gist of your comment until just now (and yet it was obvious).
You rightly point out that the other status documents are just "...Status" and not "...StatusResponse". I will change it to TenderStatusRequest and TenderStatus.
Pre-award have given me the diagrams to draw for the other new documents and these reveal other opportunities to change names to be more consistent with the existing list of document types:
Expression of Interest -> Expression of Interest Request
Expression of Interest Confirmation -> Expression of Interest Response
Unsubscribe from Procedure -> Unsubscribe from Procedure Request
Unsubscribe from Procedure Confirmation -> Unsubscribe from Procedure Response
The difference appears to be that there is no response if the request is rejected. The response documents appear only to be confirmations.
So do we leave these as confirmations, or do we change them to be request/response names?
Or, a third option, can we just change the request document to be "...Request" and leave the response to be "...Confirmation" because there is no other kind of response? The diagrams I've been asked to draw indicate the same flow as other request/response flows. At least by adding "Request" to the end it indicates to the reader that a response of some kind (even if only a confirmation) is expected.
I'm finding naming to be very difficult because of the implications in the names if users choose not to read the details.
was (Author: gkholman):
Forgive me, Kees, but I missed the gist of your comment until just now (and yet it was obvious).
You rightly point out that the other status documents are just "...Status" and not "...StatusResponse". I will change it to TenderStatusRequest and TenderStatus.
Pre-award have given me the diagrams to draw for the other new documents and these reveal other opportunities to change names to be more consistent with the existing list of document types:
Expression of Interest -> Expression of Interest Request
Expression of Interest Confirmation -> Expression of Interest Response
Unsubscribe from Procedure -> Unsubscribe from Procedure Request
Unsubscribe from Procedure Confirmation -> Unsubscribe from Procedure Response
The difference appears to be that there is no response if the request is rejected. The response documents appear only to be confirmations.
So do we leave these as confirmations, or do we change them to be request/response names?
> Should new Tender Status Inquiry be Tender Status Enquiry
> ---------------------------------------------------------
>
> Key: UBL-55
> URL: https://issues.oasis-open.org/browse/UBL-55
> Project: OASIS Universal Business Language (UBL) TC
> Issue Type: Bug
> Components: Documents and business objects
> Reporter: Ken Holman
> Assignee: Ken Holman
>
> I think for consistency we need to change the name of this new document type from "Tender Status Inquiry" to be "Tender Status Enquiry".
> Please let me know if there are any objections.
> An easily overlooked issue ... we are supposed to be using Oxford English.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]