Re: [ubl] Missing repair for PRD3?

[Jon Bosak <bosak@pinax.com>]

Thanks for putting the thought into these definitions.  The increased
usability is what we were hoping to accomplish.

The two approaches are equally correct.  I sort of like the separate
sentences, but I certainly couldn't justify that preference.

Jon

G. Ken Holman wrote:
> Thanks, Tim!
>
> Is the second sentence in each one a complete sentence?  Could these be 
> reduced to a single sentence by just using a comma (or does that make it 
> too many commas)?
>
>   Inventory Report:
>   A report on the quantities of each item that are, or will be,
>   in stock, sent by a Buyer (for example a retailer) to a Seller
>   (for example a producer).
>
>   Stock Availability Report:
>   A report on the quantities of each item that are, or will be,
>   in stock, sent by a Seller (for example a producer) to a Buyer
>   (for example a retailer).
>
> As two sentences we could use:
>
>   Inventory Report:
>   A report on the quantities of each item that are, or will be,
>   in stock.  This document is sent by a Buyer (for example a
>   retailer) to a Seller (for example a producer).
>
>   Stock Availability Report:
>   A report on the quantities of each item that are, or will be,
>   in stock.  This document is sent by a Seller (for example a
>   producer) to a Buyer (for example a retailer).
>
> An example of such a second sentence is in Statement:
>
>   http://docs.oasis-open.org/ubl/prd3-UBL-2.1/UBL-2.1.html#T-STATEMENT
>
> . . . . . . . . . Ken
>
> At 2013-04-16 08:22 +0800, Tim McGrath wrote:
> > These are different document types used in a different process so the 
> > definitions should be different. How about we change the definitions 
> > to something like:
> > Inventory Report:
> > A report on the quantities of each item that are, or will be, in 
> > stock. Sent buy a Buyer (for example a retailer) to a Seller (for 
> > example a producer).
> >
> > Stock Availability Report:
> > A report on the quantities of each item that are, or will be, in 
> > stock. Sent buy a Seller (for example a producer) to a Buyer (for 
> > example a retailer).
> >
> >
> > PS it also allows us to make the text consistent.
> >
> >
> > On 16/04/13 6:05 AM, G. Ken Holman wrote:
> > > I've just accidentally found that an identified issue that fell 
> > > through the cracks has not yet been addressed.
> > >
> > > A duplicate document ABIE definition was identified by a user and 
> > > commented on in http://ubl.xml.org as I indicated to the PSC:
> > >
> > > http://lists.oasis-open.org/archives/ubl-psc/201302/msg00000.html
> > >
> > > The duplicate definition remains in the PRD3 package and was not 
> > > addressed when it should have been.  Please note the definitions for 
> > > "Inventory Report" and "Stock Availability Report":
> > >
> > > http://docs.oasis-open.org/ubl/prd3-UBL-2.1/UBL-2.1.html#T-INVENTORY-REPORT 
> > >
> > >
> > >    A report on the quantities of each item that are, or will be, in 
> > > stock.
> > >
> > > http://docs.oasis-open.org/ubl/prd3-UBL-2.1/UBL-2.1.html#T-STOCK-AVAILABILITY-REPORT 
> > >
> > >
> > >    A report of the quantities of each item that are or will be in stock.
> > >
> > > The distinction between these two document types is found in the 
> > > roles of the submitter and receiver (this can be seen in the links 
> > > above).
> > > But would users go so far to check that?  If they are only looking at 
> > > the document model or the definition in the schema, there is no way 
> > > to distinguish the two documents.
> > >
> > > In order to prevent confusion from users who do not think to look at 
> > > the submitter and receiver roles in the UBL hub document, should we 
> > > distinguish the two definitions in the data model?  I would think 
> > > many users would come to the same quick conclusion the original 
> > > poster did that the definitions are duplicated in some kind of 
> > > error.  I, too, needed the guidance to understand the difference (I 
> > > think it was Kees who illuminated the difference for me).
> > >
> > > I'll add this to this week's agenda.  But does anyone have a comment 
> > > to make before the teleconferences?  Any suggestions for replacement 
> > > definitions.
> > >
> > > . . . . . . . . . Ken
>
>
> --
> Contact us for world-wide XML consulting and instructor-led training |
> Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm |
> Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/o/ |
> G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com |
> Google+ profile: https://plus.google.com/116832879756988317389/about |
> Legal business disclaimers:    http://www.CraneSoftwrights.com/legal |
>
>
> ---------------------------------------------------------------------
> 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