For eligible GDSN Business Requirements Group members, the following 3 eBallots have been put out for vote:

08-221 eBallot -  Add a Trade Item Group ID parameter.

Note: this change request is to add this attribute to the Price

Synchronization message, and will be a free-form text field. The text of this ballot is as follows:

The eBallot for CR 08-221 will begin on November 11th 2008 if motioned to eBallot by the GDSN BRG; its purpose is to allow a condition to be specified that includes the ability to set the applicable Trade Item Group ID parameter. This would be a repeatable parameter applying to nil, 1 or many Trade Item Group IDs. It would be analogous to specifying a Target Market Sub-division for a Price, which again can be nil, 1 or many. This eBallot contains the Business Requirement for CR 08-221 (see tab 08-221) and a Link to the CR 08-221 in the CR system. Please cast your eBallot by 4 PM ET on November 25th 2008 (Close of eBallot).

08-233 eBallot - Add sub-region/country sub-division to countryOfOrigin attribute The eBallot for CR 08-233 will begin on November 18th 2008 if motioned to eBallot by the GDSN BRG; its purpose is to Add the capability to communicate a sub-region/country sub-division to the countryOfOrigin attribute for the trade item. This could be done by enabling a tradeItemCountryOfOriginSubDivisionCode which is to be populated with the corresponding ISO3166-2 similar to the current targetMarketSubdivisionCode implementation. Providing the subdivision for country of origin would be optional.  This eBallot contains the Business Requirement for CR 08-233 (see tab 08-233) and a Link to the CR 08-233 in the CR system. Please cast your eBallot by 4 PM ET on December 5th 2008 (Close of eBallot - Expanded due to USA Holidays).

To vote on this ballot, go here: 

http://community.gs1.org/apps/org/workgroup/gsmp_g_gdsn_brg/ballot.php?id=313

eBallot for CR 08-227 begins Nov-18-2008 and ends Dec-5-2008 due to USA Holiday. Proposal: Add the attached attribute code list value to the GDSN core item data model, or appropriate GDSN item data extension.  The CPV was introduced in 1996 as a means of raising the level of transparency and efficiency in the field of public acquisition. The use of the standard names of the CPV facilitates the marking of the procurement contracts they are interested in. In addition, CPV facilitates the swift and exact translation of contract information for publication in the official EU Bulletin as well as the preparation of procurement statistics. The CPV code consists of eight characters as well as a control character.  (Regulatory portion of this CR & attachment removed because there is no code list that exists today and adding one at this time with a limited number of values would cause an impediment to the use of this extension). This eBallot contains a Link to CR 08-227 in the CR s  ystem, the Business Requirement (See tab CR 08-227) and a Spreadsheet for the attribute attached to the CR. Please cast your eBallot  by Dec-5-2008 (Close of eBallot)  Simple LOI 1 CLARIFICATION NOTE: Submitter removed  the creation of a code list around regulatory agency in the Regulatory Extension for now because there is no code list that exists today and adding one at this time with a limited number of values would cause an impediment to the use of this extension.

To vote on this ballot, go here: 

http://community.gs1.org/apps/org/workgroup/gsmp_g_gdsn_brg/ballot.php?id=319