аЯрЁБс>ўџ -ўџџџўџџџ,џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ ўЭЩ€сАСт\pc1 BАaР=œЏМ=ёџёџт;ў8е@"Зк1ШџArial1ШџArial1ШџArial1ШџArial1ДџArial1ДџМArial1Ш Arial1Ш$Arial1 QTahoma1 QМTahoma1ШџМArial"$"#,##0_);\("$"#,##0\)!"$"#,##0_);[Red]\("$"#,##0\)""$"#,##0.00_);\("$"#,##0.00\)'""$"#,##0.00_);[Red]\("$"#,##0.00\)7*2_("$"* #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_).))_(* #,##0_);_(* \(#,##0\);_(* "-"_);_(@_)?,:_("$"* #,##0.00_);_("$"* \(#,##0.00\);_("$"* "-"??_);_(@_)6+1_(* #,##0.00_);_(* \(#,##0.00\);_(* "-"??_);_(@_)Є"$"#,##0;\-"$"#,##0Ѕ"$"#,##0;[Red]\-"$"#,##0І"$"#,##0.00;\-"$"#,##0.00#Ї"$"#,##0.00;[Red]\-"$"#,##0.005Ј0_-"$"* #,##0_-;\-"$"* #,##0_-;_-"$"* "-"_-;_-@_-,Љ'_-* #,##0_-;\-* #,##0_-;_-* "-"_-;_-@_-=Њ8_-"$"* #,##0.00_-;\-"$"* #,##0.00_-;_-"$"* "-"??_-;_-@_-4Ћ/_-* #,##0.00_-;\-* #,##0.00_-;_-* "-"??_-;_-@_-Ќ dd\-mmm\-yy­"Yes";"Yes";"No"Ў"True";"True";"False"Џ"On";"On";"Off"рѕџ Р рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР р Р р+ѕџ јР р)ѕџ јР р,ѕџ јР р*ѕџ јР рєџєР рєџєР р ѕџ јР рР рЌР р1Р рЌ Р р Р р8 Р р*x 3 рЌ*| 3 р1*| 3 р  Р рР “€џ“€џ“€џ“€џ“€ џ“€џ“€џ“€џ`… UBL LCSC…н1ReadMeŒЎ!  ;EСС€8ыZ№R№3 №П Р@@ё  їќы+#UBL UID ReferencesProposalComment Disposition Subject/TopicFeedback ReferenceReviewer/ contact Input DateArtifact Version ReviewedDisposition DateSeverityPriority Actioned-By Actioned-Date Model RelatedApproach Related BIE RelatedContext RelatedExtra Comments CCT RelatedOther - explainpThe first column will help you figure out what the comment is about, it should have one of the following topics:Order Bill Burcham9Recommendation: if what is wanted is the ability to attach some number [0..*] of DateTimes or ReferenceId's to an OrderHeader, where the meaning of those is situation-specific and not specified by UBL then each should carry some markup that allows the application specifying the value to identify that value. One way to do this would be to create e.g. in the case of OtherDateTime, a new type called "ExternalDateTime". The content model for that type would include a DateTime and an element (probably an Identifier) to specify the meaning of that date time. So an instance that required attached DateTimes with externally-ascribed meaning might look like: The Date On Which It First Occurred To Me That UBL Had Some Great Examples Of The Need For What Costello Calls Open Content 8-28-2002:9:41GMT+5 Where the type of ExternalId is cct:Identifier perhaps, and the type associated with OtherDateTimes allows for one or more ExternalDateTimes. _Some of the object classes in our model contain "external keys". An external key is used by "external systems" to identify records (in the system). Examples of external keys are LineItemType.SellerId and OrderHeaderType.BuyerId, SellerId. It would be useful to me as a reader of the model, if external identifiers were explicitly denoted as such. {Recommendation: in the model documentation, adopt a practice of identifying (in some consistent way), external identifiers.žIf identifying external keys is useful, it seems perhaps even more useful to define internal keys. Is it the case the cct:Identifier is always sufficient to define the identifying properties of an object class, or will it sometimes be the case that compound keys will be necessary? (a compound key consists of two or more properties, which when taken together constitute a unique identifier for an object/entity) ‡Recommendation: I suggest that the model adopt a practice of denoting in some consistent way identifying (or in XML terms, "key") properties. I don't think this is as simple as noting that a property of (CCT) type cct:Identifier is always the identifying key for the object class that contains it. I don't think so, since some object classes have more than one property of type Identifier.In OrderHeaderType, OtherDateTime and OtherReferenceId seem fishy since their multiplicity is 0..*, yet they carry no description information. So I could have five OtherDateTimes... and how would an applicaiton know what each meant, or which one was which? Same for OtherReferenceId.  !&6MIn many cases, BIEDictionaryEntryName will include the same RT or type. In addition, this starts to show the patterns of each object class (across object classes) to its properties. For example, in many cases, Address, Transport Details, Delivery Terms, etc. have should have the same RTs: Name, Identifier or Code, Details, etc. This might be a good consistency check across object classes and UBL names (packaging of like types across object classes). This may assist us in identifying some gaps (patterns of form, perhaps). Could we eventually see a template to ensure we are complete in defining the complex type? Monica MartinAllџ*є g ч џЦ оžЖ ўЭЩ€ Wпч%/,Н.  dќЉёвMbP?_*+‚€%№Сƒ„MHP LaserJet 6Pм0Cя€ъ odXXLetterџџџџDINU"0Ъ вPЁ"dќџXр?р?U} Ж } ’} m }  }  } Ж } &} I} Ж*} ’ } $ } m } m&} $ Reviewer/ contact?W*РЪ@Ќ@Л@@,@,@,@,@ ,@ ,@ ,@ ,@ ,@,@,@ № № @ @ @ @ @ @ @ @ @ @ @ @ @ @§ § § § §  § § § § § §  §  §  §  § § § § ~ !рOт@§ § §  § § ~ !рOт@§ § §  § § ~ !рOт@§ § §  § § !~ !`Qт@§ "§ §   О О О О О  О  О  О  О  О О О О О О О О О О О О О О О О О О зDєlрhhhh  @! @" @# @$ @% @& @' @( @) @* @+ @, @- @. @/ @0 @1 @2 №3 №4 џ@5 џ@6 џ@7 џ@8 џ@9 џ@: џ@; џ@< џ@= џ@> џ@? џ@О  О!! О"" О## О$$ О%% О&& О'' О(( О)) О** О++ О,, О-- О.. О// О00 О11 О22 О33 О44 О55 О66 О77 О88 О99 О:: О;; О<< О== О>> О?? зDl@џ@Aџ@Bџ@Cџ@Dџ@Eџ@Fџ@Gџ@Hџ@Iџ@Jџ@Kџ@Lџ@Mџ@Nџ@Oџ@P џ@Q џ@R џ@S џ@T џ@U џ@V џ@О@@ ОAA ОBB ОCC Eз2FИ ьШ№H№№0№( № №№xЂ № “ №6€м*7ПXPƒPП?П № § € №]4@м*7<‘ еЁы„ЬурF‚Mб*П Цьь №Ж < A, B, or C. < Q ьx№xЂ № “ №6€@+7ПXPƒPП?П № K € №]4@@+7Œ‘ Т(Ї)|CЌEЂ3ТLЌфyсXь №Ж<High, Medium, Low < š   Tim McGrath  Tim McGrath>О@A @я7 ўЭЩ€  Ћ5Б6  dќЉёвMbP?_*+‚€%џСƒ„MHP LaserJet 6Pм0Cя€ъ odXXLetterџџџџDINU"0Ъ вPЁ"dXXр?р?U џџџџ џ џ џ§ §  §  §  § § § зюx>Ж@  я7 ўџр…ŸђљOhЋ‘+'Гй0дHPxœ Д РЬфDistribution_Comments-0p3.xlsof Lisa SeaburgComc1aMicrosoft Excel@€хй3тцС@€k\]^ТўџеЭеœ.“—+,љЎ0д PXh px€ˆ  АфDMSiReэ  UBL LCSCReadMe  Worksheets ўџџџ !"#ўџџџ%&'()*+ўџџџ§џџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ РFўџџџWorkbookџџџџџџџџџџџџў6SummaryInformation(џџџџDocumentSummaryInformation8џџџџџџџџџџџџ$