MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ubl] WD 2.0 code list summary usage
see my comments inline...
G. Ken Holman wrote:
> Hello all,
>
> In my analysis today I determined the actual use of code list data
> types across the document types declared in the WD UBL 2.0 schemas.
>
> Note that I do not detect a single use of the ATG2-prescribed
> LanguageCodeContentType data type defined in
> CodeList_LanguageCode_ISO_7_04.xsd ... is there a reason why we have it?
>
we don't use it and neither does the ATG2 schemas. Both UBL and ATG2
use Identifier for language. I suspect its a relic from an older ATG2
version.
> I also do not detect a single use of the specialized datatypes
> AcknowledgementResponseCodeType and CountryIdentificationCodeType
> defined in UBL-SpecializedDatatypes-2.xsd ... is this an oversight?
>
AcknowledgementResponseCodeType was left in the Specialized/Qualified
Data Types even though we dropped it from the documents - sorry.
CountryIdentificationCodeType is now just a plain CodeType (no enumerations)
We know we have work to do on the Specialized/Qualified Data Type
spreadsheets (and schemas)
> Finally, the "generic" lists (is there a better name for these? these
> are not derived from specialized datatypes) ... my initial analysis
> indicates that only 73 are actually in use ... yet I detect that the
> following six are declared but not used anywhere:
> AllowanceChargeReasonCodeType, AuthorizationCodeType (because
> AuthorizationCode is not used), CodeValueType, CostCodeType (because
> CostCode is not used), and EventCodeType (because EventCodeType is not
> used).
>
We do use AllowanceChargeReasonCodeType (in the AllowanceCharge
ComplexType) but is now just a plain CodeType (no enumerations). Like
CountryIdentificationCodeType it shouldn't be in the
Specialized/Qualified Data Types.
Actually we do use CodeValue but it is a TextType not a CodeType and is
used by the Catalogue Request document as part of a Classification
Category.
The rest are ATG2 codes lists for BBIEs that we don't use.
> The summary of data types that are actually in use somewhere in the
> document models follows.
>
> I hope this is helpful.
>
> . . . . . . . . . . . . . . . Ken
>
> ATG types (3):
>
> BinaryObjectMimeCodeContentType
> CurrencyCodeContentType
> UnitCodeContentType
>
> Derived from SDT types (12):
>
> ChannelCodeType
> CurrencyCodeType
> DocumentCurrencyCodeType
> DocumentStatusCodeType
> LatitudeDirectionCodeType
> LongitudeDirectionCodeType
> PricingCurrencyCodeType
> RequestedInvoiceCurrencyCodeType
> SourceCurrencyCodeType
> TargetCurrencyCodeType
> TaxCurrencyCodeType
> TransactionCurrencyCodeType
>
> Generic code lists not derived from anything special (73):
>
> AccountingCostCodeType
> AccountTypeCodeType
> ActionCodeType
> CardTypeCodeType
> CargoTypeCodeType
> CategoryCodeType
> ChipCodeType
> CommodityCodeType
> ContractTypeCodeType
> CoordinateSystemCodeType
> CorporateRegistrationTypeCodeType
> CountrySubentityCodeType
> CustomsStatusCodeType
> DescriptionCodeType
> DespatchAdviceTypeCodeType
> DirectionCodeType
> DispositionCodeType
> DocumentQualifierCodeType
> EmergencyProceduresCodeType
> FreightRateClassCodeType
> FullnessIndicationCodeType
> HandlingCodeType
> IdentificationCodeType
> InhalationToxicityZoneCodeType
> InspectionMethodCodeType
> InvoiceTypeCodeType
> ItemClassificationCodeType
> LifeCycleStatusCodeType
> LineStatusCodeType
> LocaleCodeType
> LocationTypeCodeType
> LossRiskResponsibilityCodeType
> MedicalFirstAidGuideCodeType
> NatureCodeType
> OperatorCodeType
> OwnerTypeCodeType
> PackageLevelCodeType
> PackagingTypeCodeType
> PackingCriteriaCodeType
> PackLevelCodeType
> ParentDocumentQualifierCodeType
> PaymentChannelCodeType
> PaymentMeansCodeType
> PositionCodeType
> PreferenceCriterionCodeType
> PriorityLevelCodeType
> ProviderTypeCodeType
> ReasonCodeType
> ReferenceEventCodeType
> RegulationCodeType
> RejectActionCodeType
> RejectReasonCodeType
> ResponseCodeType
> RoleCodeType
> SealIssuerTypeCodeType
> SealStatusCodeType
> ServiceCodeType
> ShortageActionCodeType
> SizeTypeCodeType
> StatusCodeType
> SubstitutionStatusCodeType
> TariffClassCodeType
> TariffCodeType
> TaxLevelCodeType
> TaxTypeCodeType
> TimingComplaintCodeType
> TransitDirectionCodeType
> TransportAuthorizationCodeType
> TransportEmergencyCardCodeType
> TransportHandlingUnitTypeCodeType
> TransportMeansTypeCodeType
> TransportModeCodeType
> UNDGCodeType
>
>
> --
> Upcoming XSLT/XSL-FO hands-on courses: Washington,DC 2006-03-13/17
> World-wide on-site corporate, govt. & user group XML/XSL training.
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
> Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
> Male Cancer Awareness Aug'05 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. You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160
DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
http://www.docengineering.com/
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]