[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-dev] Creating a new document... where to start?
Ken, I agree with your assessment about using different namespaces. As an example, I have created a simple subset of the UBL PO. This subset simply defines what I want to send to a trading partner. I call it a Profile schema. It contains no changes to the basic UBL Purchase Order. It is a definition of what my company needs. I am not aware of any UBL rules that require that a new namespace be used in such circumstances. If I am wrong, please point me to the document and section that states this requirement. Sylvia -----Original Message----- From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] Sent: Monday, June 21, 2004 8:38 AM To: ubl-dev@lists.oasis-open.org Subject: RE: [ubl-dev] Creating a new document... where to start? At 2004-06-21 08:10 -0700, Scott Wiseman wrote: >I think you should publish your restricted schema under your own >namespace. This should help. How would you assess the impact on existing applications or implementations that rely on instances that use the published namespace? How would you characterize how doing this would help his situation? I'm of the opinion anyone setting out their own namespace would be instantly isolated from an installed base of free and commercial technologies where programs are keyed to manipulating information in the UBL namespace. Unnecessary transliteration would be needed to do any useful work. I see the UBL namespaces and base schemas as sacrosanct and that any parallel or restricted applications will, by economic and technical necessity, not be in a position to introduce additions. Yes, there will be communities who build on UBL with their own extensions, but that is because as a community they will have the support of users and vendors to take advantage of those extensions. But the biggest community of users will be small business users who will be disenfranchised from UBL by any anything other than an absolutely strict subset expression of constraints to meet simple business requirements while simultaneously satisfying the complex business requirements for which UBL was designed. Stephen Green's efforts to pull together a Small Business Profile for UBL are noteworthy and noble, and we should all rally behind him to help him assess what the balance is to meet small business requirements sufficiently with as useful and compact a subset of UBL as possible. Should the original poster use their own namespace, they would not be able to run their instances against freely-available stylesheets or upcoming commercial and free implementations of UBL-based systems, unless they went through a "translation step" to the standard UBL subset. Why not just stick within the subset by using the UBL namespace provided that nothing expressed in the subset is going to violate the constraints of the original? ................... Ken -- Public training 3 days XSLT & 2 days XSL-FO: Phoenix,AZ 2004-08-23 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/u/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995) Male Breast Cancer Awareness http://www.CraneSoftwrights.com/u/bc Legal business disclaimers: http://www.CraneSoftwrights.com/legal
PurchaseOrder-class diagram.gif
<?xml version="1.0" encoding="UTF-8"?> <Order xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:oasis:names:tc:ubl:Order:1:0" xmlns:ccts="urn:oasis:names:tc:ubl:CoreComponentParameters:1:0" xmlns:cbc="urn:oasis:names:tc:ubl:CommonBasicComponents:1:0" xmlns:udt="urn:oasis:names:tc:ubl:UnspecializedDatatypes:1:0" xmlns:cct="urn:oasis:names:tc:ubl:CoreComponentTypes:1:0" xmlns:sdt="urn:oasis:names:tc:ubl:SpecializedDatatypes:1:0" xmlns:cur="urn:oasis:names:tc:ubl:codelist:CurrencyCode:1:0" xmlns:cac="urn:oasis:names:tc:ubl:CommonAggregateComponents:1:0" xmlns:rsn="urn:oasis:names:tc:ubl:codelist:AllowanceChargeReasonCode:1:0" xmlns:chn="urn:oasis:names:tc:ubl:codelist:ChannelCode:1:0" xmlns:chc="urn:oasis:names:tc:ubl:codelist:ChipCode:1:0" xmlns:cnt="urn:oasis:names:tc:ubl:codelist:CountryIdentificationCode:1:0" xmlns:stat="urn:oasis:names:tc:ubl:codelist:DocumentStatusCode:1:0" xmlns:lat="urn:oasis:names:tc:ubl:codelist:LatitudeDirectionCode:1:0" xmlns:lstat="urn:oasis:names:tc:ubl:codelist:LineStatusCode:1:0" xmlns:lon="urn:oasis:names:tc:ubl:codelist:LongitudeDirectionCode:1:0" xmlns:pty="urn:oasis:names:tc:ubl:codelist:PaymentMeansCode:1:0" xmlns:sst="urn:oasis:names:tc:ubl:codelist:SubstitutionStatusCode:1:0" xmlns:res="urn:oasis:names:tc:ubl:codelist:AcknowledgementResponseCode:1:0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:ubl:Order:1:0 PurchaseOrder_1_0.xsd"> <BuyersID identificationSchemeID="XXXXXXXXXX">XXXXXXXXXX</BuyersID> <SellersID identificationSchemeID="XXXXXXXXXX">XXXXXXXXXX</SellersID> <GUID>XXXXXXXXXX</GUID> <cbc:IssueDate>2002-07-01</cbc:IssueDate> <AcknowledgementResponseCode codeListID="Acknowledgement Response">OrderResponse</AcknowledgementResponseCode> <TransactionCurrencyCode>EUR</TransactionCurrencyCode> <PricingCurrencyCode>USD</PricingCurrencyCode> <EarliestDate>2002-07-01</EarliestDate> <cbc:LineExtensionTotalAmount amountCurrencyID="XXXXXXXXXX">23</cbc:LineExtensionTotalAmount> <LineItemCountNumeric>23</LineItemCountNumeric> <cac:BuyerParty> <cac:Party> <cac:PartyIdentification> <cac:ID>XXXXXXXXXX</cac:ID> </cac:PartyIdentification> </cac:Party> </cac:BuyerParty> <cac:SellerParty> <cac:Party> <cac:PartyIdentification> <cac:ID>XXXXXXXXXX</cac:ID> </cac:PartyIdentification> </cac:Party> </cac:SellerParty> <cac:Delivery> <cac:ID>XXXXXXXXXX</cac:ID> <cbc:Quantity quantityUnitCode="XXX">23</cbc:Quantity> <cbc:RequestedDeliveryDateTime>2002-07-01T05:10:10</cbc:RequestedDeliveryDateTime> <cac:DeliveryAddress> <cac:ID>XXXXXXXXXX</cac:ID> <cbc:StreetName>XXXXXXXXXX</cbc:StreetName> <cbc:BuildingNumber>XXXXXXXXXX</cbc:BuildingNumber> <cbc:CityName>XXXXXXXXXX</cbc:CityName> <cbc:PostalZone>XXXXXXXXXX</cbc:PostalZone> <cac:AddressLine> <cbc:Line>XXXXXXXXXX</cbc:Line> </cac:AddressLine> </cac:DeliveryAddress> </cac:Delivery> <cac:DeliveryTerms> <cac:AllowanceCharge> <cbc:ChargeIndicator>true</cbc:ChargeIndicator> <cac:CurrencyCode>AED</cac:CurrencyCode> <cbc:Amount amountCurrencyID="XXXXXXXXXX">23</cbc:Amount> <cac:PaymentMeans> <cac:PaymentMeansTypeCode name="XXXXXXXXXX">1</cac:PaymentMeansTypeCode> <cbc:DuePaymentDate>2002-07-01</cbc:DuePaymentDate> <cac:Payment/> </cac:PaymentMeans> </cac:AllowanceCharge> </cac:DeliveryTerms> <cac:OrderLine> <cac:LineItem> <cac:BuyersID>XXXXXXXXXX</cac:BuyersID> <cac:SellersID>XXXXXXXXXX</cac:SellersID> <cbc:Quantity quantityUnitCode="BX">23</cbc:Quantity> <cbc:TaxTotalAmount amountCurrencyID="USD">23</cbc:TaxTotalAmount> <cac:Item/> </cac:LineItem> </cac:OrderLine> </Order>
UBL-PO-sample-StructureChart-report.rtf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]