[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-dev] Catalogue for ubl pricelist validation ?
Datatypes are unchanged though, so my example in http://lists.oasis-open.org/archives/ubl-dev/200702/msg00041.html is abbreviated and should allow all the UBL attributes for the respective leaf elements/types. Is this going to be a problem? It might be you want to prune out many of the attributes, say for Codes (general, not schema defined codes) and Identifiers at least. Maybe listID on a code and schemeID on an identifier are sufficient. This might be problematic, as ubl-dev discussed before, if the rules of CCTS are to be adhered to. It would require a bit of extra work to create the CCTS-compliant qualified datatype schema module and point the other schemas to it (needing editing of the common basic schema as well). If that is too onerous (and it seems, as we said before, to rule out XSD redefine which seems to be a problem to use anyway for this situation so no big deal) maybe just edit the unqualified datatypes schema to remove the unwanted attributes. Again, this seems to me to be a job best defered to CAM. The reason I say that is there may be a limit to how much editing of the schemas one can do (while keeping the same namespaces and element names) without breaking interoperability and producing something that isn't really UBL. I just don't know for sure at what point to draw the line. Jon's rule is 'It's UBL if the instance validates against the standard UBL schema' in its received text (docs.oasis- open.org/ubl/...) existence. I'm not sure how far that carries within the detail though when it comes to datatypes. CAM seems to preserve the UBL-ness of the customization when a subset with the UBL namespaces is concerned. This it does by applying a mask without the need for another schema (unless applications require such - that is orthogonal). Of course such a CAM mask could break UBL conformance but it doesn't have to. How would this apply to PreisShare I wonder? All the best Stephen Green >>> "Stephen Green" <stephen.green@bristol.gov.uk> 05/02/07 11:22:31 >>> Sorry, I did miss Party subset <xsd:complexType name="PartyType"> <xsd:sequence> <xsd:element ref="PartyIdentification" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="PartyName" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="PostalAddress" minOccurs="0"/> </xsd:sequence> </xsd:complexType> >>> "Stephen Green" <stephen.green@bristol.gov.uk> 05/02/07 10:40:59 >>> Hi David, Why not go the whole way and send to list some subset schema frags to match, me thinks. So here goes, sorry for the length of the email. It might be sufficient to copy and paste these into Catalogue and CommonAggregate UBL files to get a subset set of schema files. CAM may be preferable though. Compliments, Stephen Green Subset For Catalogue Document: <?xml version="1.0" encoding="UTF-8"?> <!-- id="systml-preisshare-maindoc-CatalogueForPriceList-2" --> <!-- Document Type: Catalogue Customization: SystML for PreisShare Date: Jan 2007 --> <xsd:schema targetNamespace="urn:oasis:names:specification:ubl:schema:xsd:Catalogue-2" xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2" xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" xmlns:ccts="urn:un:unece:uncefact:documentation:2" xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns="urn:oasis:names:specification:ubl:schema:xsd:Catalogue-2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.0"> <!-- ===== Imports ===== --> <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="../common/UBL-CommonAggregateComponents-2.0.xsd"/> <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" schemaLocation="../common/UBL-CommonBasicComponents-2.0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" schemaLocation="../common/UnqualifiedDataTypeSchemaModule-2.0.xsd"/> <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" schemaLocation="../common/UBL-CommonExtensionComponents-2.0.xsd"/> <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2" schemaLocation="../common/UBL-QualifiedDatatypes-2.0.xsd"/> <!-- ===== Root Element ===== --> <xsd:element name="Catalogue" type="CatalogueType"/> <xsd:complexType name="CatalogueType"> <xsd:sequence> <xsd:element ref="cbc:UBLVersionID" minOccurs="0"/> <xsd:element ref="cbc:CustomizationID" minOccurs="0"/> <xsd:element ref="cbc:ProfileID" minOccurs="0"/> <xsd:element ref="cbc:ID"/> <xsd:element ref="cbc:IssueDate"/> <xsd:element ref="cac:ProviderParty"/> <xsd:element ref="cac:ReceiverParty"/> <xsd:element ref="cac:CatalogueLine" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> <!-- ===== Element Declarations ===== --> <!-- ===== Type Definitions ===== --> <!-- ===== Basic Business Information Entity Type Definitions ===== --> </xsd:schema> relevant aggregate portions (I hope I've not missed any in haste) <xsd:complexType name="AddressType"> <xsd:sequence> <xsd:element ref="cbc:ID" minOccurs="0"/> <xsd:element ref="cbc:CityName" minOccurs="0"/> <xsd:element ref="cbc:PostalZone" minOccurs="0"/> <xsd:element ref="cbc:CountrySubentity" minOccurs="0"/> <xsd:element ref="AddressLine" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="Country" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="CatalogueLineType"> <xsd:sequence> <xsd:element ref="cbc:ID"/> <xsd:element ref="RequiredItemLocationQuantity" minOccurs="0" maxOccurs="1"/> <xsd:element ref="Item"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ItemType"> <xsd:sequence> <xsd:element ref="cbc:Description" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="cbc:Name" minOccurs="0"/> <xsd:element ref="SellersItemIdentification" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ItemLocationQuantityType"> <xsd:sequence> <xsd:element ref="Price" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="PriceType"> <xsd:sequence> <xsd:element ref="cbc:PriceAmount"/>qece:uncefact:data:specification:Unqu <xsd:element ref="cbc:BaseQuantity" minOccurs="0"/> </xsd:sequence> </xsd:complexType> ______________________________________________________________________ Please note the new simpler name for our website: http://www.bristol.gov.uk Our email addresses have also changed - visit http://www.bristol.gov.uk/bigchange for further details. Sign-up for our email bulletin giving news, have-your-say and event information at: http://www.bristol.gov.uk/newsdirect --------------------------------------------------------------------- To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org ______________________________________________________________________ Please note the new simpler name for our website: http://www.bristol.gov.uk Our email addresses have also changed - visit http://www.bristol.gov.uk/bigchange for further details. Sign-up for our email bulletin giving news, have-your-say and event information at: http://www.bristol.gov.uk/newsdirect ______________________________________________________________________ Please note the new simpler name for our website: http://www.bristol.gov.uk Our email addresses have also changed - visit http://www.bristol.gov.uk/bigchange for further details. Sign-up for our email bulletin giving news, have-your-say and event information at: http://www.bristol.gov.uk/newsdirect --------------------------------------------------------------------- To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org ______________________________________________________________________ Please note the new simpler name for our website: http://www.bristol.gov.uk Our email addresses have also changed - visit http://www.bristol.gov.uk/bigchange for further details. Sign-up for our email bulletin giving news, have-your-say and event information at: http://www.bristol.gov.uk/newsdirect ______________________________________________________________________ Please note the new simpler name for our website: http://www.bristol.gov.uk Our email addresses have also changed - visit http://www.bristol.gov.uk/bigchange for further details. Sign-up for our email bulletin giving news, have-your-say and event information at: http://www.bristol.gov.uk/newsdirect
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]