[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl] Backward compatibility sanity check with 2010-05-12 18:48z document models
Hi Fulya and Suat, I think that no further changes are needed or at least we should select BBIEs that need to be changed ... however I suggest to wait for a feedback from Tim. Best regards Arianna il Mon, 07 Jun 2010 14:18:37 +0300 Fulya Tuncer <fulya@srdc.metu.edu.tr> ha scritto: > Dear Arianna and all, > > Regarding issue 2, we want to clarify one point before updating: > > There are a number of BBIEs named XXX Identifier. Identifier in >ABIEs and document models. Do we need to update all these identifiers >as XXX. Identifier and clear all other XXX Identifier. Identifier >BBIEs such as (Customization Identifier. Identifier) or is this a >special case for Version Identifier. Identifier? > > Best regards, > > Suat & Fulya > > > On 6/7/2010 10:59 AM, Fulya Tuncer wrote: >> Dear Arianna, >> >> Via iSurf eDoCreator we can handle three issues listed below: >> >> 1) this afternoon I was working with eDoCreator on OrderResponse >> document when my internet connection crashed; now the document seems >> be disappeared. >> >> We will try to first restore the OrderResponse. if this is not >> successful, we can upload it from scratch. >> >> 2) in the library there are a lot of BBIEs no more used (for >>example, >> Version Identifier. Identifier was replaced Version. Identifier) ... >> Ken, Fulya, can your applications automatically remove these >> components or create a list of them? >> >> We can detect and remove the unused BBIEs in eDoCreator. >> >> 3) Question for FULYA: can you automatically remove the white space >>at >> the end of each PropertyTermQualifier? >> >> Yes, definitely. >> >> I will inform you, when the mission is completed. >> >> Best regards, >> >> Fulya >> >> >> >> On 6/7/2010 12:24 AM, Arianna Brutti wrote: >>> Dear Ken, Tim and Fulya, >>> >>> a lot of problems detected by Ken's tool have been resolved. >>> >>> Now, I would ask you as follows: >>> >>> - Ken, could you make your check again in order to verify that I >>> resolved all problems? I will not surprise if I forgot something. >>> >>> - Fulya, this afternoon I was working with eDoCreator on >>> OrderResponse document when my internet connection crashed; now the >>> document seems be disappeared. >>> >>> - I suppose that now in the library there are a lot of BBIEs no >>>more >>> used (for example, Version Identifier. Identifier was replaced >>> Version. Identifier) ... Ken, Fulya, can your applications >>> automatically remove these components or create a list of them? >>> >>> - finally I have some questions about the tasks (one question for >>> Fulya, several questions for TIm); Tim, Fulya, please, find your >>>name >>> name below. >>> >>> Thanks to all. >>> >>> Best regards >>> >>> Arianna >>> >>> >>> G. Ken Holman ha scritto: >>>> Below is the complete list, some of which you have already >>>> addressed. Each of the issues has been discussed in a piecemeal >>>> fashion on the list. While we await feedback from Tim on the above, >>>> he has made suggestions already regarding what is below. Please let >>>> me know if you have any questions. >>>> >>>> >>>> Missing old DENs in new model: 3 >>>> Consignment. Transport_ Contract. Contract >>>> Despatch Advice. Document Status Code. Code >>> >>> DONE >>> >>>> Package. Goods Item >>> >>> In UBL 2.1 it has been qualified as Contained >>> >>>> >>>> Bad code type property terms: 16 >>>> "Consignment. Shipping Priority Level. Code" >>>> "Contracting Party. Activity. Code" >>>> "Evaluation Criteria. Expression. Code" >>>> "Event. Type. Code" >>>> "Guarantee Certificate. Constitution. Code" >>>> "Guarantee Certificate. Guarantee Type. Code" >>>> "Item Property Group. Importance. Code" >>>> "Item Property. Importance. Code" >>>> "Item Property. Name. Code" >>>> "Process Justification. Previous_ Cancellation Reason. Code" >>>> "Process Justification. Reason. Code" >>>> "Procurement Project. Sub_ Type. Code" >>>> "Procurement Project. Type. Code" >>>> "Tender Result. Result. Code" >>>> "Tendering Terms. Payment Frequency. Code" >>>> "Transport Execution Status. Operation Status. Code" >>>> >>> >>> DONE: all components have been alligned to Consignment. Shipping >>> Priority Level Code. Code >>> >>>> Duplicated class/qualifier/property terms: 8 >>>> "Awarding Criteria//Maximum" (2) >>>> Awarding Criteria. Maximum. Quantity >>>> Awarding Criteria. Maximum. Amount >>>> "Awarding Criteria//Minimum" (2) >>>> Awarding Criteria. Minimum. Quantity >>>> Awarding Criteria. Minimum. Amount >>>> "Awarding Criteria//Weight" (2) >>>> Awarding Criteria. Weight. Numeric >>>> Awarding Criteria. Weight. Text >>> >>> DONE >>> >>>> "Capability//Value" (2) >>>> Capability. Value. Amount >>>> Capability. Value. Quantity >>> >>> Tim, I am not sure about this ... is "Value" the qualifier for both? >>> >>>> "Evaluation Criteria//Threshold" (2) >>>> Evaluation Criteria. Threshold. Amount >>>> Evaluation Criteria. Threshold. Quantity >>> >>> DONE: they changed for Evaluation Criteria. Threshold_ Amount. >>> Amount and Evaluation Criteria. Threshold_ Quantity . Quantity >>> >>>> "Item Property//Name" (2) >>>> Item Property. Name >>>> Item Property. Name. Code >>>> "Item Property//Value" (2) >>>> Item Property. Value. Text >>>> Item Property. Value. Quantity >>>> "Process Justification//Reason" (2) >>>> Process Justification. Reason. Code >>>> Process Justification. Reason. Text >>>> >>> >>> DONE >>> >>>> Bad name components: 25 >>>> "Consignment. Animal _ Food Indicator. Indicator": >>>> PropertyTermQualifier "Animal ": >>>> "External Reference. Character Set Code. Code": >>>> PropertyTermPossessiveNoun "Character Set ": >>>> "External Reference. Hash Algorithm Method. Text": >>>> PropertyTermPossessiveNoun "Hash Algorithm ": >>>> "Hazardous Item. Hazardous Category Code. Code": >>>> PropertyTermPossessiveNoun "Hazardous Category ": >>>> "Meter Reading. Previous _ Meter Quantity. Quantity": >>>> PropertyTermQualifier "Previous ": >>>> "Meter. Meter Constant. Text": PropertyTermPossessiveNoun "Meter ": >>>> "Pickup. Actual _ Pickup Date. Date": PropertyTermQualifier "Actual >>>>": >>>> "Pickup. Actual _ Pickup Time. Time": PropertyTermQualifier "Actual >>>>": >>>> "Pickup. Latest _ Pickup Date. Date": PropertyTermQualifier "Latest >>>>": >>>> "Pickup. Latest _ Pickup Time. Time": PropertyTermQualifier "Latest >>>>": >>>> "Result Of Verification. Result Code. Code": >>>> PropertyTermPossessiveNoun "Result ": >>>> "Result Of Verification. Validate _ Process. Text": >>>> PropertyTermQualifier "Validate ": >>>> "Result Of Verification. Validate _ Tool Version. Text": >>>> PropertyTermQualifier "Validate ": >>>> "Result Of Verification. Validate _ Tool. Text": >>>> PropertyTermQualifier "Validate ": >>>> "Result Of Verification. Validation _ Date. Date": >>>> PropertyTermQualifier "Validation ": >>>> "Result Of Verification. Validation _ Time. Time": >>>> PropertyTermQualifier "Validation ": >>>> "Service Provider Party. Service Type . Text": PropertyTerm >>>> "Service Type ": >>>> "Tender Preparation. Tender _ Envelope Type Code. Code": >>>> PropertyTermQualifier "Tender ": >>>> "Tenderer Requirement. Tenderer Requirement _ Type Code. Code": >>>> PropertyTermQualifier "Tenderer Requirement ": >>>> "Tendering Process. Original_ Contracting System . Identifier": >>>> PropertyTerm "Contracting System ": >>>> "Tendering Terms. Funding_ Program Code. Code": >>>> PropertyTermPossessiveNoun "Program ": >>>> "Tendering Terms. Variant _ Constraint. Indicator": >>>> PropertyTermQualifier "Variant ": >>>> "Transportation Service. Transportation Service Description. Text": >>>> >>>> PropertyTermPossessiveNoun "Transportation Service ": >>>> "Utility Statement. Accounting Cost . Text": PropertyTerm >>>> "Accounting Cost ": >>>> "Utility Statement. Extended _ Telecommunications Supply. >>>> Telecommunications Supply": PropertyTermQualifier "Extended ": >>>> >>> >>> TO DO. >>> Question for FULYA: can you automatically remove the white space at >>> the end of each PropertyTermQualifier? >>> >>>> Mismatched name components for UBL Name: 34 >>>> "VersionID": inconsistent naming components (11) >>>> Application Response. Version Identifier. Identifier >>>> Catalogue. Version. Identifier ** >>>> Catalogue Deletion. Version. Identifier ** >>>> Catalogue Item Specification Update. Version. Identifier ** >>>> Catalogue Pricing Update. Version. Identifier ** >>>> Certificate Of Origin. Version Identifier. Identifier >>>> Exception Criteria. Version Identifier. Identifier >>>> Forecast. Version Identifier. Identifier >>>> Packing List. Version Identifier. Identifier >>>> Catalogue Reference. Version. Identifier ** >>>> Classification Scheme. Version. Identifier ** >>> DONE: all components have been alligned to Classification >>>Scheme. >>> Version. Identifier >>>> "CopyIndicator": inconsistent naming components (46) >>>> Awarded Notification. Copy_ Indicator. Indicator >>>> Call For Tenders. Copy_ Indicator. Indicator >>>> Contract Award Notice. Copy_ Indicator. Indicator >>>> Contract Notice. Copy_ Indicator. Indicator >>>> Credit Note. Copy_ Indicator. Indicator >>>> Debit Note. Copy_ Indicator. Indicator >>>> Despatch Advice. Copy_ Indicator. Indicator >>>> Document Status . Copy_ Indicator. Indicator >>>> Document Status Request. Copy_ Indicator. Indicator >>>> Exception Criteria. Copy_ Indicator. Indicator >>>> Exception Notification. Copy_ Indicator. Indicator >>>> Forecast. Copy_ Indicator. Indicator >>>> Forecast Revision. Copy_ Indicator. Indicator >>>> Freight Invoice. Copy_ Indicator. Indicator >>>> Guarantee Certificate. Copy_ Indicator. Indicator >>>> Instruction For Returns. Copy_ Indicator. Indicator >>>> Inventory Report. Copy_ Indicator. Indicator >>>> Invoice. Copy_ Indicator. Indicator >>>> Item Information Request. Copy_ Indicator. Indicator >>>> Order. Copy_ Indicator. Indicator >>>> Order Cancellation. Copy_ Indicator. Indicator >>>> Order Change. Copy_ Indicator. Indicator >>>> Order Response. Copy_ Indicator. Indicator >>>> Order Response Simple. Copy_ Indicator. Indicator >>>> Performance History. Copy_ Indicator. Indicator >>>> Prior Information Notice. Copy_ Indicator. Indicator >>>> Product Activity. Copy_ Indicator. Indicator >>>> Quotation. Copy_ Indicator. Indicator >>>> Receipt Advice. Copy_ Indicator. Indicator >>>> Reminder. Copy_ Indicator. Indicator >>>> Remittance Advice. Copy_ Indicator. Indicator >>>> Request For Quotation. Copy_ Indicator. Indicator >>>> Retail Event. Copy_ Indicator. Indicator >>>> Self Billed Credit Note. Copy_ Indicator. Indicator >>>> Self Billed Invoice. Copy_ Indicator. Indicator >>>> Statement. Copy_ Indicator. Indicator >>>> Stock Availability Report. Copy_ Indicator. Indicator >>>> Tender. Copy_ Indicator. Indicator >>>> Tenderer Qualification. Copy_ Indicator. Indicator >>>> Tenderer Qualification Response. Copy_ Indicator. Indicator >>>> Tender Receipt. Copy_ Indicator. Indicator >>>> Trade Item Location Profile. Copy_ Indicator. Indicator >>>> Unawarded Notification. Copy_ Indicator. Indicator >>>> Utility Statement. Copy Indicator. Indicator ** >>>> Document Reference. Copy_ Indicator. Indicator >>>> Order Reference. Copy_ Indicator. Indicator >>> >>> DONE: Utility Statement. Copy Indicator. Indicator changed for >>> Utility Statement. Copy_ Indicator. Indicator ** >>> >>>> "Name": inconsistent naming components (33) >>>> Bill Of Lading. Name >>>> Catalogue. Name >>>> Catalogue Deletion. Name >>>> Catalogue Item Specification Update. Name >>>> Catalogue Pricing Update. Name >>>> Catalogue Request. Name >>>> Forwarding Instructions. Name >>>> Packing List. Name >>>> Transportation Status. Name >>>> Waybill. Name >>>> Activity Property. Name >>>> Branch. Name >>>> Classification Category. Name >>>> Classification Scheme. Name >>>> Contact. Name >>>> Contract Execution Requirement. Name. Text ** >>>> Corporate Registration Scheme. Name >>>> Country. Name >>>> Declaration. Name. Text ** >>>> Evidence. Name. Text ** >>>> Financial Account. Name >>>> Financial Institution. Name >>>> Item. Name >>>> Item Property. Name >>>> Item Property Group. Name >>>> Language. Name >>>> Party Name. Name >>>> Procurement Project. Name >>>> Regulation. Name. Text ** >>>> Tax Category. Name >>>> Tax Scheme. Name >>>> Tender Requirement. Name. Text ** >>>> Tenderer Requirement. Name. Text ** >>> >>> DONE: now all representation terms are "Name" >>> Question for TIM: making the corrections I discovered that the >>> cardinality of Regulation.Name is 1..1. I think it should be 1..n, >>> isn't it? >>> >>>> "DocumentStatusCode": inconsistent naming components (4) >>>> Bill Of Lading. Document Status Code. Code >>>> Despatch Advice. Document Status. Code ** >>>> Forwarding Instructions. Document Status Code. Code >>>> Receipt Advice. Document Status Code. Code >>> >>> DONE: Despatch Advice. Document Status. Code changed for >>> Despatch Advice. Document Status Code. Code >>> >>>> "DocumentCurrencyCode": inconsistent naming components (16) >>>> Credit Note. Document_ Currency Code. Code >>>> Debit Note. Document_ Currency Code. Code >>>> Freight Invoice. Document_ Currency Code. Code >>>> Inventory Report. Document_ Currency Code. Code >>>> Invoice. Document_ Currency Code. Code >>>> Order. Document_ Currency Code. Code >>>> Order Change. Document_ Currency Code. Code >>>> Order Response. Document_ Currency Code. Code >>>> Product Activity. Document_ Currency Code. Code >>>> Reminder. Document_ Currency Code. Code >>>> Remittance Advice. Document_ Currency Code. Code >>>> Self Billed Credit Note. Document_ Currency Code. Code >>>> Self Billed Invoice. Document_ Currency Code. Code >>>> Statement. Document_ Currency Code. Code >>>> Stock Availability Report. Document_ Currency Code. Code >>>> Utility Statement. Document_ Currency Code. Code ** >>> >>> mmm ... no changes were maken ... all seems be right. What should >>>the >>> problem be in the Utility Statement? >>> >>>> "AccountingCost": inconsistent naming components (18) >>>> Credit Note. Accounting Cost. Text >>>> Debit Note. Accounting Cost. Text >>>> Freight Invoice. Accounting Cost. Text >>>> Invoice. Accounting Cost. Text >>>> Order. Accounting Cost. Text >>>> Order Change. Accounting Cost. Text >>>> Order Response. Accounting Cost. Text >>>> Order Response Simple. Accounting Cost. Text >>>> Reminder. Accounting Cost. Text >>>> Self Billed Credit Note. Accounting Cost. Text >>>> Self Billed Invoice. Accounting Cost. Text >>>> Utility Statement. Accounting Cost . Text ** >>>> Allowance Charge. Accounting Cost. Text >>>> Credit Note Line. Accounting Cost. Text >>>> Debit Note Line. Accounting Cost. Text >>>> Invoice Line. Accounting Cost. Text >>>> Line Item. Accounting Cost. Text >>>> Reminder Line. Accounting Cost. Text >>> >>> DONE >>> >>>> "ForecastPurposeCode": inconsistent naming components (3) >>>> Forecast. Forecast_ Purpose Code. Code >>>> Forecast Exception Criteria Line. Forecast Purpose Code. Code ** >>>> Retail Planned Impact. Forecast Purpose Code. Code ** >>> >>> DONE: all components have been alligned to Forecast. Forecast_ >>> Purpose Code. Code >>> >>>> "SequenceNumberID": inconsistent naming components (3) >>>> Forecast Revision. Sequence_ Number. Identifier >>>> Order Change. Sequence_ Number. Identifier >>>> Goods Item. Sequence Number. Identifier ** >>> >>> DONE: all components have been alligned to Goods Item. Sequence >>> Number. Identifier >>> >>>> "GuaranteeTypeCode": inconsistent naming components (2) >>>> Guarantee Certificate. Guarantee Type. Code >>>> >>>> Financial Guarantee. Guarantee Type Code. Code ** >>> >>> DONE: "Guarantee Certificate. Guarantee Type. Code" changed for >>> "Guarantee Certificate. Guarantee Type Code. Code" >>> >>>> "SalesOrderID": inconsistent naming components (5) >>>> Order. Sales Order Identifier. Identifier >>>> Order Change. Sales Order Identifier. Identifier >>>> Order Response. Sales Order Identifier. Identifier >>>> Line Item. Sales_ Order Identifier. Identifier ** >>>> >>>> Order Reference. Sales Order Identifier. Identifier >>> >>> DONE: all components have been alligned to Line Item. Sales_ >>>Order >>> Identifier. Identifier >>> >>>> "CustomerReference": inconsistent naming components (5) >>>> Order. Customer Reference. Text >>>> Order Change. Customer Reference. Text >>>> Order Response. Customer Reference. Text >>>> Order Response Simple. Customer_ Reference. Text ** >>>> Order Reference. Customer_ Reference. Text ** >>> >>> DONE: all components have been alligned to rder Reference. >>>Customer_ >>> Reference. Text >>> >>>> "GrossWeightMeasure": inconsistent naming components (5) >>>> Order Response. Gross_ Weight. Measure >>>> Consignment. Gross_ Weight. Measure >>>> Goods Item. Gross_ Weight. Measure >>>> Shipment. Gross_ Weight. Measure >>>> Transport Equipment. Gross Weight_ Measure. Measure ** >>> >>> DONE: Transport Equipment. Gross Weight_ Measure. Measure changed >>> for Transport Equipment. Gross_ Weight. Measure >>> >>>> "GrossVolumeMeasure": inconsistent naming components (5) >>>> Order Response. Gross_ Volume. Measure >>>> Consignment. Gross_ Volume. Measure >>>> Goods Item. Gross_ Volume. Measure >>>> Shipment. Gross_ Volume. Measure >>>> Transport Equipment. Gross Volume_ Measure. Measure ** >>> >>> DONE: Transport Equipment. Gross Volume_ Measure. Measure changed >>> for Transport Equipment. Gross_ Volume. Measure >>> >>> Question for TIM: in Transport Equipment there is also Transport >>> Equipment. Tare Weight_ Measure. Measure ... should it change for >>> Transport Equipment. Tare_ Weight. Measure? >>> >>>> "SupplyChainActivityTypeCode": inconsistent naming components (4) >>>> Activity Data Line. Supply Chain_ Activity Type Code. Code >>>> Exception Criteria Line. Supply Chain Activity Type Code. Code ** >>>> Exception Notification Line. Supply Chain Activity Type Code. Code >>>>** >>>> Item Information Request Line. Supply Chain Activity Type Code. >>>> Code ** >>> >>> DONE: Activity Data Line. Supply Chain_ Activity Type Code. Code >>> changed for Activity Data Line. Supply Chain Activity Type Code. >>>Code >>> >>>> "MinimumQuantity": inconsistent naming components (6) >>>> Awarding Criteria. Minimum. Quantity >>>> Delivery. Minimum_ Quantity. Quantity ** >>>> Economic Operator Short List. Minimum. Quantity >>>> Item Location Quantity. Minimum_ Quantity. Quantity ** >>>> Line Item. Minimum_ Quantity. Quantity ** >>>> Request For Tender Line. Minimum_ Quantity. Quantity ** >>> >>> DONE: all components have been alligned to Delivery. Minimum_ >>> Quantity. Quantity >>> >>>> "MaximumQuantity": inconsistent naming components (6) >>>> Awarding Criteria. Maximum. Quantity >>>> Delivery. Maximum_ Quantity. Quantity ** >>>> Economic Operator Short List. Maximum. Quantity >>>> Item Location Quantity. Maximum_ Quantity. Quantity ** >>>> Line Item. Maximum_ Quantity. Quantity ** >>>> Request For Tender Line. Maximum_ Quantity. Quantity ** >>> >>> DONE: all components have been alligned to Delivery. Maximum_ >>> Quantity. Quantity >>> >>> Question for TIM: in the Economic Operator Short List there was >>> Economic Operator Short List. Expected. Quantity ... I changed it >>>for >>> Economic Operator Short List. Expected_ Quantity. Quantity ... is it >>>ok? >>> >>>> "TotalAmount": inconsistent naming components (3) >>>> Budget Account Line. Total_ Amount. Amount >>>> Budget Amount. Total. Amount ** >>>> Telecommunications Supply. Total Amount. Amount ** >>> >>> DONE: all components have been alligned to Budget Account Line. >>> Total_ Amount. Amount >>> >>>> "TaxExclusiveAmount": inconsistent naming components (2) >>>> Budget Amount. Tax Exclusive. Amount >>>> Monetary Total. Tax Exclusive Amount. Amount ** >>> >>> DONE: all components have been alligned to Monetary Total. Tax >>> Exclusive_ Amount. Amount >>> >>> TIM, please, confirm that is right because in your mail you wrote >>> that it should be Monetary Total. Tax Exclusive Amount. Amount but I >>> suspect that it was a typing error. >>> Furthermore, in Budget Amount there was Budget Amount. Minimum. >>> Amount ... I changed it for Budget Amount. Minimum_ Amount .. is it >>>ok? >>> >>> >>>> "SequenceID": inconsistent naming components (2) >>>> Consignment. Sequence Identifier. Identifier >>>> Status. Sequence. Identifier ** >>> >>> DONE: Status. Sequence. Identifier changed for Status. Sequence >>> Identifier. Identifier >>> >>>> "ShippingPriorityLevelCode": inconsistent naming components (2) >>>> Consignment. Shipping Priority Level. Code >>>> Shipment. Shipping Priority Level Code. Code ** >>> >>> DONE: Consignment. Shipping Priority Level . Code changed for >>> Consignment. Shipping Priority Level Code. Code >>> >>>> "ConsignmentQuantity": inconsistent naming components (2) >>>> Consignment. Consignment_ Quantity. Quantity >>>> Shipment. Consignment Quantity. Quantity ** >>> >>> DONE: Shipment. Consignment Quantity. Quantity changed for Shipment. >>> Consignment_ Quantity. Quantity >>> >>>> "InvoicedQuantity": inconsistent naming components (2) >>>> Consumption Line. Invoiced Quantity. Quantity >>>> Invoice Line. Invoiced_ Quantity. Quantity ** >>> >>> DONE: Consumption Line. Invoiced Quantity. Quantity changed for >>> Consumption Line. Invoiced_ Quantity. Quantity >>> >>> >>>> "LineExtensionAmount": inconsistent naming components (9) >>>> Consumption Line. Line Extension_ Amount. Amount >>>> Credit Note Line. Line Extension Amount. Amount ** >>>> Debit Note Line. Line Extension Amount. Amount ** >>>> Invoice Line. Line Extension Amount. Amount ** >>>> Line Item. Line Extension Amount. Amount ** >>>> Monetary Total. Line Extension Amount. Amount ** >>>> Quotation Line. Line Extension Amount. Amount ** >>>> Telecommunications Supply Line. Line Extension Amount. Amount ** >>>> Tender Line. Line Extension Amount. Amount ** >>> >>> DONE: all components alligned to Consumption Line. Line Extension_ >>> Amount. Amount >>> >>> Question for TIM :in Monetary Total there are a lot of "Amount" ... >>> should they be qualified like Line Extension Amount? >>> >>>> "DeliveredQuantity": inconsistent naming components (2) >>>> Despatch Line. Delivered_ Quantity. Quantity >>>> Meter Reading. Delivered Quantity. Quantity ** >>> >>> DONE: Meter Reading. Delivered Quantity. Quantity changed for >>> Meter Reading. Delivered_ >>> Quantity. Quantity >>> >>>> "OversupplyQuantity": inconsistent naming components (2) >>>> Despatch Line. Oversupply_ Quantity. Quantity >>>> Receipt Line. Oversupply Quantity. Quantity ** >>> >>> DONE: Receipt Line. Oversupply Quantity. Quantity changed for >>> Receipt Line. Oversupply_ Quantity. Quantity >>> >>>> "ThresholdQuantity": inconsistent naming components (2) >>>> Evaluation Criteria. Threshold. Quantity >>>> Exception Criteria Line. Threshold Quantity. Quantity ** >>> >>> DONE: all components alligned to Exception Criteria Line. Threshold_ >>> Quantity. Quantity >>> >>>> "PackSizeNumeric": inconsistent naming components (2) >>>> Item. Pack Size. Numeric >>>> Utility Item. Pack_ Size Numeric. Text ** >>> >>> Nothing to do, they are different >>> >>>> "PriceAmount": inconsistent naming components (2) >>>> Item Comparison. Price. Amount >>>> Price. Price Amount. Amount ** >>> >>> DONE: Item Comparison. Price. Amount changed for Item >>> Comparison. Price Amount. Amount >>> >>>> "StartDate": inconsistent naming components (2) >>>> Period. Start Date. Date >>>> Tender Result. Start. Date ** >>> >>> DONE: Tender Result. Start. Date changed for Tender Result. >>> Start Date. Date >>> >>>> "ProcurementProjectLotID": inconsistent naming components (3) >>>> Qualification Resolution. Procurement Project Lot Identifier. >>>> Identifier >>>> Tender Preparation. Procurement Project Lot Identifier. Identifier >>>> Tendered Project. Procurement Project Lot. Identifier ** >>> >>> DONE: all componets allegned to Tendered Project. Procurement >>> Project Lot. Identifier >>> >>>> "ValidatorID": inconsistent naming components (2) >>>> Result Of Verification. Validator. Identifier >>>> Signature. Validator Identifier. Identifier ** >>> >>> DONE: Signature. Validator Identifier. Identifier changed for >>> Signature. Validator. Identifier >>> >>>> "ResultCode": inconsistent naming components (2) >>>> Result Of Verification. Result Code. Code >>>> Tender Result. Result. Code ** >>> >>> DONE: Tender Result. Result. Code changed for Tender Result. >>> Result Code. Code >>> >>>> "ValidationDate": inconsistent naming components (2) >>>> Result Of Verification. Validation _ Date. Date >>>> Signature. Validation Date. Date ** >>> >>> DONE: Result Of Verification. Validation _ Date. Date changed >>> for Result Of Verification. >>> Validation Date. Date >>> >>>> "ValidationTime": inconsistent naming components (2) >>>> Result Of Verification. Validation _ Time. Time >>>> Signature. Validation Time. Time ** >>> >>> DONE: Result Of Verification. Validation _ Time . Date changed >>>for >>> Result Of Verification. Validation Time . Time >>> >>>> >>>> Missing old Data Type Qualifications in new model: 2 >>>> "Despatch Advice. Document Status Code. Code" old="Document Status" >>>> new="" >>> >>> Resolved >>> >>>> "Status. Condition Code. Code" old="Transportation Status" new="" >>> >>> "Transportation Status" should be the data type qualifier, so I >>>think >>> that the DEN is right .. may be that I have to chage the data type >>>... >>> >>> I think that a lot of following problems have been resolved thanks >>>to >>> the previous corrections ... I would wait for Ken's test before to >>> proceede. >>> >>>> >>>> Missing new Data Type Qualifications in new data types: 0 >>>> >>>> Cardinalities found in error: 5 >>>> "Catalogue Deletion. Effective Date. Date" old= 0 new= 1 >>>> "Consignment. Transport_ Contract. Contract" old= 0..1 new= >>>> "Despatch Advice. Document Status Code. Code" old= 0..1 new= >>>> "Package. Goods Item" old= 0..n new= >>>> "Request For Quotation. Submission Due Date. Date" old= 0 new= 1 >>>> >>>> Sequences found in error: 3 >>>> "Consignment": >>>> Old order: >>>> 1 Consignment. Details >>>> 2 Consignment. Identifier >>>> 3 Consignment. Summary_ Description. Text >>>> 4 Consignment. Total_ Invoice Amount. Amount >>>> 5 Consignment. Declared Customs_ Value. Amount >>>> 6 Consignment. Tariff Description. Text >>>> 7 Consignment. Tariff Code. Code >>>> 8 Consignment. Insurance Premium Amount. Amount >>>> 9 Consignment. Gross_ Weight. Measure >>>> 10 Consignment. Net_ Weight. Measure >>>> 11 Consignment. Net Net_ Weight. Measure >>>> 12 Consignment. Chargeable_ Weight. Measure >>>> 13 Consignment. Gross_ Volume. Measure >>>> 14 Consignment. Net_ Volume. Measure >>>> 15 Consignment. Loading_ Length. Measure >>>> 16 Consignment. Remarks. Text >>>> 17 Consignment. Hazardous Risk_ Indicator. Indicator >>>> 18 Consignment. Consignee_ Party. Party >>>> 19 Consignment. Exporter_ Party. Party >>>> 20 Consignment. Consignor_ Party. Party >>>> 21 Consignment. Importer_ Party. Party >>>> 22 Consignment. Carrier_ Party. Party >>>> 23 Consignment. Freight Forwarder_ Party. Party >>>> 24 Consignment. Notify_ Party. Party >>>> 25 Consignment. Original Despatch_ Party. Party >>>> 26 Consignment. Final Delivery_ Party. Party >>>> 27 Consignment. Original Departure_ Country. Country >>>> 28 Consignment. Final Destination_ Country. Country >>>> 29 Consignment. Transit_ Country. Country >>>> *30 Consignment. Transport_ Contract. Contract >>>> *31 Consignment. Original Despatch_ Transportation Service. >>>> Transportation Service >>>> *32 Consignment. Final Delivery_ Transportation Service. >>>> Transportation Service >>>> *33 Consignment. Delivery Terms >>>> *34 Consignment. Payment Terms >>>> *35 Consignment. Freight_ Allowance Charge. Allowance Charge >>>> New order (not including newly-introduced optional constructs): >>>> 1 Consignment. Details >>>> 2 Consignment. Identifier >>>> 3 Consignment. Summary_ Description. Text >>>> 4 Consignment. Total_ Invoice Amount. Amount >>>> 5 Consignment. Declared Customs_ Value. Amount >>>> 6 Consignment. Tariff Description. Text >>>> 7 Consignment. Tariff Code. Code >>>> 8 Consignment. Insurance Premium Amount. Amount >>>> 9 Consignment. Gross_ Weight. Measure >>>> 10 Consignment. Net_ Weight. Measure >>>> 11 Consignment. Net Net_ Weight. Measure >>>> 12 Consignment. Chargeable_ Weight. Measure >>>> 13 Consignment. Gross_ Volume. Measure >>>> 14 Consignment. Net_ Volume. Measure >>>> 15 Consignment. Loading_ Length. Measure >>>> 16 Consignment. Remarks. Text >>>> 17 Consignment. Hazardous Risk_ Indicator. Indicator >>>> 18 Consignment. Consignee_ Party. Party >>>> 19 Consignment. Exporter_ Party. Party >>>> 20 Consignment. Consignor_ Party. Party >>>> 21 Consignment. Importer_ Party. Party >>>> 22 Consignment. Carrier_ Party. Party >>>> 23 Consignment. Freight Forwarder_ Party. Party >>>> 24 Consignment. Notify_ Party. Party >>>> 25 Consignment. Original Despatch_ Party. Party >>>> 26 Consignment. Final Delivery_ Party. Party >>>> 27 Consignment. Original Departure_ Country. Country >>>> 28 Consignment. Final Destination_ Country. Country >>>> 29 Consignment. Transit_ Country. Country >>>> *30 Consignment. Original Despatch_ Transportation Service. >>>> Transportation Service >>>> *31 Consignment. Final Delivery_ Transportation Service. >>>> Transportation Service >>>> *32 Consignment. Delivery Terms >>>> *33 Consignment. Payment Terms >>>> *34 Consignment. Freight_ Allowance Charge. Allowance Charge >>>> >>>> "Despatch Advice": >>>> Old order: >>>> 1 Despatch Advice. Details >>>> 2 Despatch Advice. UBL Version Identifier. Identifier >>>> 3 Despatch Advice. Customization Identifier. Identifier >>>> 4 Despatch Advice. Profile Identifier. Identifier >>>> 5 Despatch Advice. Identifier >>>> 6 Despatch Advice. Copy_ Indicator. Indicator >>>> 7 Despatch Advice. UUID. Identifier >>>> 8 Despatch Advice. Issue Date. Date >>>> 9 Despatch Advice. Issue Time. Time >>>> *10 Despatch Advice. Document Status Code. Code >>>> *11 Despatch Advice. Despatch Advice Type Code. Code >>>> *12 Despatch Advice. Note. Text >>>> *13 Despatch Advice. Line Count. Numeric >>>> *14 Despatch Advice. Order Reference >>>> *15 Despatch Advice. Additional_ Document Reference. Document >>>> Reference >>>> *16 Despatch Advice. Signature >>>> *17 Despatch Advice. Despatch_ Supplier Party. Supplier Party >>>> *18 Despatch Advice. Delivery_ Customer Party. Customer Party >>>> *19 Despatch Advice. Buyer_ Customer Party. Customer Party >>>> *20 Despatch Advice. Seller_ Supplier Party. Supplier Party >>>> *21 Despatch Advice. Originator_ Customer Party. Customer Party >>>> *22 Despatch Advice. Shipment >>>> *23 Despatch Advice. Despatch Line >>>> New order (not including newly-introduced optional constructs): >>>> 1 Despatch Advice. Details >>>> 2 Despatch Advice. UBL Version Identifier. Identifier >>>> 3 Despatch Advice. Customization Identifier. Identifier >>>> 4 Despatch Advice. Profile Identifier. Identifier >>>> 5 Despatch Advice. Identifier >>>> 6 Despatch Advice. Copy_ Indicator. Indicator >>>> 7 Despatch Advice. UUID. Identifier >>>> 8 Despatch Advice. Issue Date. Date >>>> 9 Despatch Advice. Issue Time. Time >>>> *10 Despatch Advice. Despatch Advice Type Code. Code >>>> *11 Despatch Advice. Note. Text >>>> *12 Despatch Advice. Line Count. Numeric >>>> *13 Despatch Advice. Order Reference >>>> *14 Despatch Advice. Additional_ Document Reference. Document >>>> Reference >>>> *15 Despatch Advice. Signature >>>> *16 Despatch Advice. Despatch_ Supplier Party. Supplier Party >>>> *17 Despatch Advice. Delivery_ Customer Party. Customer Party >>>> *18 Despatch Advice. Buyer_ Customer Party. Customer Party >>>> *19 Despatch Advice. Seller_ Supplier Party. Supplier Party >>>> *20 Despatch Advice. Originator_ Customer Party. Customer Party >>>> *21 Despatch Advice. Shipment >>>> *22 Despatch Advice. Despatch Line >>>> >>>> "Package": >>>> Old order: >>>> 1 Package. Details >>>> 2 Package. Identifier >>>> 3 Package. Quantity >>>> 4 Package. Returnable Material_ Indicator. Indicator >>>> 5 Package. Package Level Code. Code >>>> 6 Package. Packaging Type Code. Code >>>> 7 Package. Packing Material. Text >>>> 8 Package. Contained_ Package. Package >>>> *9 Package. Goods Item >>>> *10 Package. Measurement_ Dimension. Dimension >>>> *11 Package. Delivery Unit >>>> New order (not including newly-introduced optional constructs): >>>> 1 Package. Details >>>> 2 Package. Identifier >>>> 3 Package. Quantity >>>> 4 Package. Returnable Material_ Indicator. Indicator >>>> 5 Package. Package Level Code. Code >>>> 6 Package. Packaging Type Code. Code >>>> 7 Package. Packing Material. Text >>>> 8 Package. Contained_ Package. Package >>>> *9 Package. Measurement_ Dimension. Dimension >>>> *10 Package. Delivery Unit >>>> >>>> >>>> >>>> -- >>>> XSLT/XQuery training: after http://XMLPrague.cz 2011-03-28/04-01 >>>> Vote for your XML training: http://www.CraneSoftwrights.com/o/i/ >>>> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ >>>> G. Ken Holman mailto:gkholman@CraneSoftwrights.com >>>> Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/o/bc >>>> 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 >>>> >>>> >>>> Nessun virus nel messaggio in arrivo. >>>> Controllato da AVG - www.avg.com Versione: 9.0.819 / Database dei >>>> virus: 271.1.1/2897 - Data di rilascio: 05/26/10 08:25:00 >>>> >>> >> >> > > > -- > PS: Please note the change in the phone/fax numbers... > >Fulya TUNÇER > Software R&D Center > Department of Computer Eng. > Middle East Technical University > 06531 Ankara Turkey > > email: fulya@srdc.metu.edu.tr > Phone: +90 (312) 210 1763 >Fax: +90 (312) 210 1837 > > > --------------------------------------------------------------------- > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]