Schema U4IS_IM_Customer.xsd

Size: px
Start display at page:

Download "Schema U4IS_IM_Customer.xsd"

Transcription

1 Schema U4IS_IM_Customer.xsd schema location: attributeformdefault: elementformdefault: targetnamespace: qualified Complex types Customer Attributes version schema location: attributeformdefault: elementformdefault: targetnamespace: CommonTypes/1/U4IS_IM_CommonTypes.xsd qualified Complex types AccountType BasicAddressType IndexedTextType InvoiceInformationType LocationType PartyBasicInformationType PaymentInformationType PhoneType QualifiedTextType RelatedInformationType schema location: attributeformdefault: elementformdefault: targetnamespace: qualified Complex types SystemType UserAreaType

2 complextype Customer namespace children CustomerID CustomerGroupID CustomerGroupName CustomerBasicInformation Location RelatedInformation UserArea Generic schema for the customer entity source <xs:complextype name="customer"> <xs:>generic schema for the customer entity</xs:> <xs:sequence> <xs:element name="customerid" type="u4is:qualifiedtexttype" minoccurs="0" maxoccurs="unbounded">

3 <xs:>identity of the customer. Recommended values for the qualifier are: GLN - (Global Location Number) DUNS - (Data Universal Numbering System) SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus) ApArId - (Agresso specific identifier )</xs:> <xs:element name="customergroupid" type="u4is:qualifiedtexttype" minoccurs="0"> <xs:>identity for a group of customers.</xs:> <xs:element name="customergroupname" type="xs:string" minoccurs="0"> <xs:>name for a group of custumers.</xs:> <xs:element name="customerbasicinformation" type="u4is:partybasicinformationtype"> <xs:>information that typically is found in a customer master file.</xs:> <xs:element name="location" type="u4is:locationtype" minoccurs="0" maxoccurs="unbounded"> <xs:>information on where a customer is located.</xs:> <xs:element name="relatedinformation" type="u4is:relatedinformationtype" minoccurs="0" maxoccurs="unbounded"> <xs:>extra information on a customer.</xs:> <xs:element name="userarea" type="u4ext:userareatype" minoccurs="0"> <xs:>segment intended for system specific information not applicable to the standard schema.</xs:> </xs:sequence> </xs:complextype>

4 element Customer/CustomerID namespace type QualifiedTextType maxocc unbounded attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identity of the customer. Recommended values for the qualifier are: GLN - (Global Location Number) DUNS - (Data Universal Numbering System) SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus) ApArId - (Agresso specific identifier ) source <xs:element name="customerid" type="u4is:qualifiedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>identity of the customer. Recommended values for the qualifier are: GLN - (Global Location Number) DUNS - (Data Universal Numbering System) SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus) ApArId - (Agresso specific identifier )</xs:>

5 element Customer/CustomerGroupID namespace type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identity for a group of customers. source <xs:element name="customergroupid" type="u4is:qualifiedtexttype" minoccurs="0"> <xs:>identity for a group of customers.</xs:> element Customer/CustomerGroupName namespace Name for a group of custumers. source <xs:element name="customergroupname" type="xs:string" minoccurs="0"> <xs:>name for a group of custumers.</xs:>

6 element Customer/CustomerBasicInformation

7 namespace type PartyBasicInformationType children Name NameShort Status ExpiryDate HeadQuarterLocation CountryCode OrgNo VATNo Reference Description Note InvoiceInformation PaymentInformation UserArea Information that typically is found in a customer master file. source <xs:element name="customerbasicinformation" type="u4is:partybasicinformationtype"> <xs:>information that typically is found in a customer master file.</xs:>

8 element Customer/Location namespace type LocationType maxocc unbounded children LocationID LocationName LocationCategory Address SubLocationID WarehouseID ContactName ContactPosition

9 GLN Phone Website Information on where a customer is located. source <xs:element name="location" type="u4is:locationtype" minoccurs="0" maxoccurs="unbounded"> <xs:>information on where a customer is located.</xs:> element Customer/RelatedInformation namespace type RelatedInformationType maxocc unbounded children InformationCode InformationID InformationName InformationValue InformationValidFrom InformationValidTo Extra information on a customer. source <xs:element name="relatedinformation" type="u4is:relatedinformationtype" minoccurs="0" maxoccurs="unbounded"> <xs:>extra information on a customer.</xs:>

10 element Customer/UserArea namespace type UserAreaType children System Segment intended for system specific information not applicable to the standard schema. source <xs:element name="userarea" type="u4ext:userareatype" minoccurs="0"> <xs:>segment intended for system specific information not applicable to the standard schema.</xs:> attribute version namespace Used to notify the recipient on the schema version a specific XML-file is based on source <xs:attribute name="version" type="xs:string"> <xs:>used to notify the recipient on the schema version a specific XML-file is based on</xs:> </xs:attribute>

11 complextype AccountType children PaymentMethod AccountNo PaymentRef FinancialInstitution ClearingCode used by element PaymentInformationType/Account source <xs:complextype name="accounttype"> <xs:sequence> <xs:element name="paymentmethod" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier to the payment method. Valid values if the qualifier is set to SFTI are: BK - Bankgiro PO - Plusgiro IBAN - Bank account </xs:> <xs:element name="accountno" type="xs:string" minoccurs="0"> <xs:>account number.</xs:> <xs:element name="paymentref" type="xs:string" minoccurs="0"> <xs:>reference to the payment.</xs:>

12 <xs:element name="financialinstitution" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier for the financial institution that holds the account. Qualifier describes the type of identifier. </xs:> <xs:element name="clearingcode" type="xs:string" minoccurs="0"> <xs:>related to IBAN and/or Swift. Holds the branch code for the bank. </xs:> </xs:sequence> </xs:complextype> element AccountType/PaymentMethod type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identifier to the payment method. Valid values if the qualifier is set to SFTI are: BK - Bankgiro PO - Plusgiro IBAN - Bank account source <xs:element name="paymentmethod" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier to the payment method. Valid values if the qualifier is set to SFTI are: BK - Bankgiro

13 PO - Plusgiro IBAN - Bank account </xs:> element AccountType/AccountNo Account number. source <xs:element name="accountno" type="xs:string" minoccurs="0"> <xs:>account number.</xs:> element AccountType/PaymentRef Reference to the payment. source <xs:element name="paymentref" type="xs:string" minoccurs="0"> <xs:>reference to the payment.</xs:>

14 element AccountType/FinancialInstitution type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identifier for the financial institution that holds the account. Qualifier describes the type of identifier. source <xs:element name="financialinstitution" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier for the financial institution that holds the account. Qualifier describes the type of identifier. </xs:> element AccountType/ClearingCode Related to IBAN and/or Swift. Holds the branch code for the bank. source <xs:element name="clearingcode" type="xs:string" minoccurs="0"> <xs:>related to IBAN and/or Swift. Holds the branch code for the bank. </xs:>

15 complextype BasicAddressType children Addressline ZipCode City Province Country CountryCode used by element LocationType/Address source <xs:complextype name="basicaddresstype"> <xs:sequence> <xs:element name="addressline" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>text(s) describing the address</xs:> <xs:element name="zipcode" type="xs:string" minoccurs="0"> <xs:>postal code for the address</xs:> <xs:element name="city" type="xs:string" minoccurs="0"> <xs:>city in which the address is situated</xs:> <xs:element name="province" type="xs:string" minoccurs="0"> <xs:>province for the address if applicable</xs:>

16 <xs:element name="country" type="xs:string" minoccurs="0"> <xs:>country in which the address resides</xs:> <xs:element name="countrycode" type="xs:string" minoccurs="0"> <xs:>country code in accordance with ISO alpha- 2</xs:> </xs:sequence> </xs:complextype> element BasicAddressType/Addressline type IndexedTextType maxocc unbounded attributes Name Type Use index xs:string optional Default Fixed Annotation The attribute shows the index of the string value. Text(s) describing the address source <xs:element name="addressline" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>text(s) describing the address</xs:> element BasicAddressType/ZipCode

17 Postal code for the address source <xs:element name="zipcode" type="xs:string" minoccurs="0"> <xs:>postal code for the address</xs:> element BasicAddressType/City City in which the address is situated source <xs:element name="city" type="xs:string" minoccurs="0"> <xs:>city in which the address is situated</xs:> element BasicAddressType/Province Province for the address if applicable source <xs:element name="province" type="xs:string" minoccurs="0"> <xs:>province for the address if applicable</xs:>

18 element BasicAddressType/Country Country in which the address resides source <xs:element name="country" type="xs:string" minoccurs="0"> <xs:>country in which the address resides</xs:> element BasicAddressType/CountryCode Country code in accordance with ISO alpha-2 source <xs:element name="countrycode" type="xs:string" minoccurs="0"> <xs:>country code in accordance with ISO alpha-2</xs:> complextype IndexedTextType type extension of xs:string base xs:string

19 used by elements BasicAddressType/Addressline InvoiceInformationType/AttentionNote PartyBasicInformationType/Note attributes Name Type Use Default Fixed Annotation index xs:string optional The attribute shows the index of the string value. source <xs:complextype name="indexedtexttype"> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="index" type="xs:string" use="optional"> <xs:>the attribute shows the index of the string value.</xs:> </xs:attribute> </xs:extension> </xs:simplecontent> </xs:complextype> attribute use optional The attribute shows the index of the string value. source <xs:attribute name="index" type="xs:string" use="optional"> <xs:>the attribute shows the index of the string value.</xs:> </xs:attribute>

20 complextype InvoiceInformationType

21 children TaxCode TaxCodeDescription TaxSystem TaxSystemDescription TermsOfPayment TermsOfPaymentDescription PaymentPlanTemplate PaymentPlanTemplateDescription DiscountCode DiscountCodeDescription CreditLimit CurrencyCode LanguageCode SupplierReference HeadOfficeCustomerID HeadOfficeOrgNo HeadOfficeVATNo CreditCheckOnHeadOffice AttentionNote FilingRequirement used by element PartyBasicInformationType/InvoiceInformation source <xs:complextype name="invoiceinformationtype"> <xs:sequence> <xs:element name="taxcode" type="qualifiedtexttype" minoccurs="0"> <xs:>code that identifies the tax code used for the party.</xs:> <xs:element name="taxcodedescription" type="xs:string" minoccurs="0"> <xs:>description for the tax code.</xs:> <xs:element name="taxsystem" type="qualifiedtexttype" minoccurs="0"> <xs:>code that identifies the tax system used for the party</xs:> <xs:element name="taxsystemdescription" type="xs:string" minoccurs="0"> <xs:>description for the tax system.</xs:> <xs:element name="termsofpayment" type="qualifiedtexttype" minoccurs="0"> <xs:>code for the default terms of payment for the party.</xs:> <xs:element name="termsofpaymentdescription" type="xs:string" minoccurs="0"> <xs:>description of the terms of payment.</xs:> <xs:element name="paymentplantemplate" type="qualifiedtexttype" minoccurs="0"> <xs:>code for default payment plan.</xs:> <xs:element name="paymentplantemplatedescription" type="xs:string" minoccurs="0"> <xs:>description of the payment plan.</xs:> <xs:element name="discountcode" type="qualifiedtexttype" minoccurs="0"> <xs:>code for the default discount to be used for the party.</xs:> <xs:element name="discountcodedescription" type="xs:string" minoccurs="0">

22 <xs:>description of the discount.</xs:> <xs:element name="creditlimit" type="xs:string" minoccurs="0"> <xs:>credit limit for the party.</xs:> <xs:element name="currencycode" type="qualifiedtexttype" minoccurs="0"> <xs:>default currency. ISO-4217 is recommended as the qualifier.</xs:> <xs:element name="languagecode" type="qualifiedtexttype" minoccurs="0"> <xs:>default language for invoice titles. ISO is recommended as the qualifier.</xs:> <xs:element name="supplierreference" type="xs:string" minoccurs="0"> <xs:>reference as supplier if applicable.</xs:> <xs:element name="headofficecustomerid" type="qualifiedtexttype" minoccurs="0"> <xs:>customerid for the headoffice if applicable.</xs:> <xs:element name="headofficeorgno" type="xs:string" minoccurs="0"> <xs:>organisation number for the head office if applicable.</xs:> <xs:element name="headofficevatno" type="xs:string" minoccurs="0"> <xs:>vat number for the head office if applicable.</xs:> <xs:element name="creditcheckonheadoffice" type="xs:boolean" minoccurs="0"> <xs:>set to true if credit check is supposed to be made at the head office level.</xs:> <xs:element name="attentionnote" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>any extra information pertaining the party.</xs:> <xs:element name="filingrequirement" type="xs:string" minoccurs="0">

23 <xs:>information concerning special filing requirements.</xs:> </xs:sequence> </xs:complextype> element InvoiceInformationType/TaxCode type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Code that identifies the tax code used for the party. source <xs:element name="taxcode" type="qualifiedtexttype" minoccurs="0"> <xs:>code that identifies the tax code used for the party.</xs:> element InvoiceInformationType/TaxCodeDescription Description for the tax code. source <xs:element name="taxcodedescription" type="xs:string" minoccurs="0"> <xs:>description for the tax code.</xs:>

24 element InvoiceInformationType/TaxSystem type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Code that identifies the tax system used for the party source <xs:element name="taxsystem" type="qualifiedtexttype" minoccurs="0"> <xs:>code that identifies the tax system used for the party</xs:> element InvoiceInformationType/TaxSystemDescription Description for the tax system. source <xs:element name="taxsystemdescription" type="xs:string" minoccurs="0"> <xs:>description for the tax system.</xs:>

25 element InvoiceInformationType/TermsOfPayment type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Code for the default terms of payment for the party. source <xs:element name="termsofpayment" type="qualifiedtexttype" minoccurs="0"> <xs:>code for the default terms of payment for the party.</xs:> element InvoiceInformationType/TermsOfPaymentDescription Description of the terms of payment. source <xs:element name="termsofpaymentdescription" type="xs:string" minoccurs="0"> <xs:>description of the terms of payment.</xs:>

26 element InvoiceInformationType/PaymentPlanTemplate type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Code for default payment plan. source <xs:element name="paymentplantemplate" type="qualifiedtexttype" minoccurs="0"> <xs:>code for default payment plan.</xs:> element InvoiceInformationType/PaymentPlanTemplateDescription Description of the payment plan. source <xs:element name="paymentplantemplatedescription" type="xs:string" minoccurs="0"> <xs:>description of the payment plan.</xs:>

27 element InvoiceInformationType/DiscountCode type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Code for the default discount to be used for the party. source <xs:element name="discountcode" type="qualifiedtexttype" minoccurs="0"> <xs:>code for the default discount to be used for the party.</xs:> element InvoiceInformationType/DiscountCodeDescription Description of the discount. source <xs:element name="discountcodedescription" type="xs:string" minoccurs="0"> <xs:>description of the discount.</xs:>

28 element InvoiceInformationType/CreditLimit Credit limit for the party. source <xs:element name="creditlimit" type="xs:string" minoccurs="0"> <xs:>credit limit for the party.</xs:> element InvoiceInformationType/CurrencyCode type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Default currency. ISO-4217 is recommended as the qualifier. source <xs:element name="currencycode" type="qualifiedtexttype" minoccurs="0"> <xs:>default currency. ISO-4217 is recommended as the qualifier.</xs:>

29 element InvoiceInformationType/LanguageCode type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Default language for invoice titles. ISO is recommended as the qualifier. source <xs:element name="languagecode" type="qualifiedtexttype" minoccurs="0"> <xs:>default language for invoice titles. ISO is recommended as the qualifier.</xs:> element InvoiceInformationType/SupplierReference Reference as supplier if applicable. source <xs:element name="supplierreference" type="xs:string" minoccurs="0"> <xs:>reference as supplier if applicable.</xs:>

30 element InvoiceInformationType/HeadOfficeCustomerID type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. CustomerId for the headoffice if applicable. source <xs:element name="headofficecustomerid" type="qualifiedtexttype" minoccurs="0"> <xs:>customerid for the headoffice if applicable.</xs:> element InvoiceInformationType/HeadOfficeOrgNo Organisation number for the head office if applicable. source <xs:element name="headofficeorgno" type="xs:string" minoccurs="0"> <xs:>organisation number for the head office if applicable.</xs:>

31 element InvoiceInformationType/HeadOfficeVATNo VAT number for the head office if applicable. source <xs:element name="headofficevatno" type="xs:string" minoccurs="0"> <xs:>vat number for the head office if applicable.</xs:> element InvoiceInformationType/CreditCheckOnHeadOffice type xs:boolean Set to true if credit check is supposed to be made at the head office level. source <xs:element name="creditcheckonheadoffice" type="xs:boolean" minoccurs="0"> <xs:>set to true if credit check is supposed to be made at the head office level.</xs:> element InvoiceInformationType/AttentionNote

32 type IndexedTextType maxocc unbounded attributes Name Type Use index xs:string optional Default Fixed Annotation The attribute shows the index of the string value. Any extra information pertaining the party. source <xs:element name="attentionnote" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>any extra information pertaining the party.</xs:> element InvoiceInformationType/FilingRequirement Information concerning special filing requirements. source <xs:element name="filingrequirement" type="xs:string" minoccurs="0"> <xs:>information concerning special filing requirements.</xs:>

33 complextype LocationType children LocationID LocationName LocationCategory Address SubLocationID WarehouseID ContactName ContactPosition GLN Phone Website used by element Customer/Location source <xs:complextype name="locationtype"> <xs:sequence> <xs:element name="locationid" type="qualifiedtexttype" minoccurs="0">

34 <xs:>identity of the location. </xs:> <xs:element name="locationname" type="xs:string" minoccurs="0"> <xs:>name for the location.</xs:> <xs:element name="locationcategory" type="qualifiedtexttype" minoccurs="0"> <xs:>category for the location.</xs:> <xs:element name="address" type="basicaddresstype" minoccurs="0"/> <xs:element name="sublocationid" type="xs:string" minoccurs="0"> <xs:>identifier to a sublocation if applicable.</xs:> <xs:element name="warehouseid" type="xs:string" minoccurs="0"> <xs:>identifier to a warehouse if applicable.</xs:> <xs:element name="contactname" type="xs:string" minoccurs="0"> <xs:>name to the responsible contact.</xs:> <xs:element name="contactposition" type="xs:string" minoccurs="0"> <xs:>position of the contact.</xs:> <xs:element name="gln" type="xs:string" minoccurs="0"> <xs:>a valid EAN code for the location if applicable.</xs:> <xs:element name="phone" type="phonetype" minoccurs="0" maxoccurs="unbounded"> <xs:>phone number(s) associated with this location.</xs:> <xs:element name=" " type="xs:string" minoccurs="0"> <xs:> associated with this location.</xs:> <xs:element name="website" type="xs:string" minoccurs="0"> <xs:>url associated with this location.</xs:> </xs:sequence>

35 </xs:complextype> element LocationType/LocationID type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identity of the location. source <xs:element name="locationid" type="qualifiedtexttype" minoccurs="0"> <xs:>identity of the location. </xs:> element LocationType/LocationName Name for the location. source <xs:element name="locationname" type="xs:string" minoccurs="0"> <xs:>name for the location.</xs:>

36 element LocationType/LocationCategory type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Category for the location. source <xs:element name="locationcategory" type="qualifiedtexttype" minoccurs="0"> <xs:>category for the location.</xs:>

37 element LocationType/Address type BasicAddressType children Addressline ZipCode City Province Country CountryCode source <xs:element name="address" type="basicaddresstype" minoccurs="0"/> element LocationType/SubLocationID Identifier to a sublocation if applicable. source <xs:element name="sublocationid" type="xs:string" minoccurs="0"> <xs:>identifier to a sublocation if applicable.</xs:>

38 element LocationType/WarehouseID Identifier to a warehouse if applicable. source <xs:element name="warehouseid" type="xs:string" minoccurs="0"> <xs:>identifier to a warehouse if applicable.</xs:> element LocationType/ContactName Name to the responsible contact. source <xs:element name="contactname" type="xs:string" minoccurs="0"> <xs:>name to the responsible contact.</xs:> element LocationType/ContactPosition

39 Position of the contact. source <xs:element name="contactposition" type="xs:string" minoccurs="0"> <xs:>position of the contact.</xs:> element LocationType/GLN A valid EAN code for the location if applicable. source <xs:element name="gln" type="xs:string" minoccurs="0"> <xs:>a valid EAN code for the location if applicable.</xs:> element LocationType/Phone type PhoneType maxocc unbounded attributes Name Type Use property xs:string optional Default Fixed Annotation The attribute shows the type of phone connected with this number.

40 Phone number(s) associated with this location. source <xs:element name="phone" type="phonetype" minoccurs="0" maxoccurs="unbounded"> <xs:>phone number(s) associated with this location.</xs:> element LocationType/ associated with this location. source <xs:element name=" " type="xs:string" minoccurs="0"> <xs:> associated with this location.</xs:> element LocationType/Website URL associated with this location. source <xs:element name="website" type="xs:string" minoccurs="0"> <xs:>url associated with this location.</xs:>

41 complextype PartyBasicInformationType

42

43 children Name NameShort Status ExpiryDate HeadQuarterLocation CountryCode OrgNo VATNo Reference Description Note InvoiceInformation PaymentInformation UserArea used by element Customer/CustomerBasicInformation source <xs:complextype name="partybasicinformationtype"> <xs:sequence> <xs:element name="name" type="xs:string" minoccurs="0"> <xs:>name of the party</xs:> <xs:element name="nameshort" type="xs:string" minoccurs="0"> <xs:>unique short name of the party. Used when searching a customer master file.</xs:> <xs:element name="status" type="qualifiedtexttype" minoccurs="0"> <xs:>status of party record. Valid values when qualifier is set to Agresso are: N - Normal P - Parked C - Closed</xs:> <xs:element name="expirydate" type="xs:datetime" minoccurs="0"> <xs:>a property telling when the party is no longer a valid party if applicable.</xs:> <xs:element name="headquarterlocation" type="xs:string" minoccurs="0"> <xs:>location of a party's headquarter as registered with the tax office.</xs:> <xs:element name="countrycode" type="xs:string" minoccurs="0"> <xs:>country code for the headquarter in accordance with ISO alpha- 2</xs:> <xs:element name="orgno" type="qualifiedtexttype" minoccurs="0"> <xs:>organisation number for the party. Recommended values for the qualifier includes: SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus)</xs:> <xs:element name="vatno" type="xs:string" minoccurs="0">

44 <xs:>the VAT registration number for party's company.</xs:> <xs:element name="reference" type="xs:string" minoccurs="0"> <xs:>party level reference.</xs:> <xs:element name="description" type="xs:string" minoccurs="0"> <xs:>string describing the Party.</xs:> <xs:element name="note" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>any extra free text with information about the party.</xs:> <xs:element name="invoiceinformation" type="invoiceinformationtype" minoccurs="0"> <xs:>information about how to invoice the party as a customer.</xs:> <xs:element name="paymentinformation" type="paymentinformationtype" minoccurs="0"> <xs:>information about how to pay the party as a supplier.</xs:> <xs:element name="userarea" type="u4ext:userareatype" minoccurs="0"> <xs:>segment intended for system specific information not applicable to the standard schema.</xs:> </xs:sequence> </xs:complextype> element PartyBasicInformationType/Name Name of the party source <xs:element name="name" type="xs:string" minoccurs="0"> <xs:>name of the party</xs:>

45 element PartyBasicInformationType/NameShort Unique short name of the party. Used when searching a customer master file. source <xs:element name="nameshort" type="xs:string" minoccurs="0"> <xs:>unique short name of the party. Used when searching a customer master file.</xs:> element PartyBasicInformationType/Status type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Status of party record. Valid values when qualifier is set to Agresso are: N - Normal P - Parked C - Closed

46 source <xs:element name="status" type="qualifiedtexttype" minoccurs="0"> <xs:>status of party record. Valid values when qualifier is set to Agresso are: N - Normal P - Parked C - Closed</xs:> element PartyBasicInformationType/ExpiryDate type xs:datetime A property telling when the party is no longer a valid party if applicable. source <xs:element name="expirydate" type="xs:datetime" minoccurs="0"> <xs:>a property telling when the party is no longer a valid party if applicable.</xs:> element PartyBasicInformationType/HeadQuarterLocation Location of a party's headquarter as registered with the tax office. source <xs:element name="headquarterlocation" type="xs:string" minoccurs="0"> <xs:>location of a party's headquarter as registered with the tax office.</xs:>

47 element PartyBasicInformationType/CountryCode Country code for the headquarter in accordance with ISO alpha-2 source <xs:element name="countrycode" type="xs:string" minoccurs="0"> <xs:>country code for the headquarter in accordance with ISO alpha- 2</xs:> element PartyBasicInformationType/OrgNo type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Organisation number for the party. Recommended values for the qualifier includes: SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus) source <xs:element name="orgno" type="qualifiedtexttype" minoccurs="0">

48 <xs:>organisation number for the party. Recommended values for the qualifier includes: SKV - (Swedish organisation number) SFS - (Finnish organisation number, Y-tunnus)</xs:> element PartyBasicInformationType/VATNo The VAT registration number for party's company. source <xs:element name="vatno" type="xs:string" minoccurs="0"> <xs:>the VAT registration number for party's company.</xs:> element PartyBasicInformationType/Reference Party level reference. source <xs:element name="reference" type="xs:string" minoccurs="0"> <xs:>party level reference.</xs:>

49 element PartyBasicInformationType/Description String describing the Party. source <xs:element name="description" type="xs:string" minoccurs="0"> <xs:>string describing the Party.</xs:> element PartyBasicInformationType/Note type IndexedTextType maxocc unbounded attributes Name Type Use index xs:string optional Default Fixed Annotation The attribute shows the index of the string value. Any extra free text with information about the party. source <xs:element name="note" type="indexedtexttype" minoccurs="0" maxoccurs="unbounded"> <xs:>any extra free text with information about the party.</xs:>

50 element PartyBasicInformationType/InvoiceInformation

51 type InvoiceInformationType children TaxCode TaxCodeDescription TaxSystem TaxSystemDescription TermsOfPayment TermsOfPaymentDescription PaymentPlanTemplate PaymentPlanTemplateDescription DiscountCode DiscountCodeDescription CreditLimit CurrencyCode LanguageCode SupplierReference HeadOfficeCustomerID HeadOfficeOrgNo HeadOfficeVATNo CreditCheckOnHeadOffice AttentionNote FilingRequirement Information about how to invoice the party as a customer. source <xs:element name="invoiceinformation" type="invoiceinformationtype" minoccurs="0"> <xs:>information about how to invoice the party as a customer.</xs:> element PartyBasicInformationType/PaymentInformation type PaymentInformationType children PaymentRecipient InterestRuleID InterestRuleDescription Account Information about how to pay the party as a supplier. source <xs:element name="paymentinformation" type="paymentinformationtype" minoccurs="0"> <xs:>information about how to pay the party as a supplier.</xs:>

52 element PartyBasicInformationType/UserArea type UserAreaType children System Segment intended for system specific information not applicable to the standard schema. source <xs:element name="userarea" type="u4ext:userareatype" minoccurs="0"> <xs:>segment intended for system specific information not applicable to the standard schema.</xs:> complextype PaymentInformationType children PaymentRecipient InterestRuleID InterestRuleDescription Account used by element PartyBasicInformationType/PaymentInformation source <xs:complextype name="paymentinformationtype">

53 <xs:sequence> <xs:element name="paymentrecipient" type="xs:string" minoccurs="0"> <xs:>name of the recipient.</xs:> <xs:element name="interestruleid" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier for a rule set regarding interest for unpaid invoices for this recipient if applicable.</xs:> <xs:element name="interestruledescription" type="xs:string" minoccurs="0"> <xs:>text describing the rule set regarding interest for unpaid invoices for this recipient if applicable.</xs:> <xs:element name="account" type="accounttype" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> </xs:complextype> element PaymentInformationType/PaymentRecipient Name of the recipient. source <xs:element name="paymentrecipient" type="xs:string" minoccurs="0"> <xs:>name of the recipient.</xs:> element PaymentInformationType/InterestRuleID

54 type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. Identifier for a rule set regarding interest for unpaid invoices for this recipient if applicable. source <xs:element name="interestruleid" type="qualifiedtexttype" minoccurs="0"> <xs:>identifier for a rule set regarding interest for unpaid invoices for this recipient if applicable.</xs:> element PaymentInformationType/InterestRuleDescription Text describing the rule set regarding interest for unpaid invoices for this recipient if applicable. source <xs:element name="interestruledescription" type="xs:string" minoccurs="0"> <xs:>text describing the rule set regarding interest for unpaid invoices for this recipient if applicable.</xs:>

55 element PaymentInformationType/Account type AccountType maxocc unbounded children PaymentMethod AccountNo PaymentRef FinancialInstitution ClearingCode source <xs:element name="account" type="accounttype" minoccurs="0" maxoccurs="unbounded"/> complextype PhoneType type extension of xs:string base xs:string

56 used by element LocationType/Phone attributes Name Type Use property xs:string optional Default Fixed Annotation The attribute shows the type of phone connected with this number. source <xs:complextype name="phonetype"> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="property" type="xs:string" use="optional"> <xs:>the attribute shows the type of phone connected with this number.</xs:> </xs:attribute> </xs:extension> </xs:simplecontent> </xs:complextype> attribute use optional The attribute shows the type of phone connected with this number. source <xs:attribute name="property" type="xs:string" use="optional"> <xs:>the attribute shows the type of phone connected with this number.</xs:> </xs:attribute> complextype QualifiedTextType type extension of xs:string base xs:string used by elements InvoiceInformationType/CurrencyCode Customer/CustomerGroupID Customer/CustomerID InvoiceInformationType/DiscountCode AccountType/FinancialInstitution InvoiceInformationType/HeadOfficeCustomerID RelatedInformationType/InformationCode PaymentInformationType/InterestRuleID InvoiceInformationType/LanguageCode LocationType/LocationCategory LocationType/LocationID PartyBasicInformationType/OrgNo AccountType/PaymentMethod InvoiceInformationType/PaymentPlanTemplate PartyBasicInformationType/Status InvoiceInformationType/TaxCode

57 InvoiceInformationType/TaxSystem InvoiceInformationType/TermsOfPayment attributes Name Type Use Default Fixed Annotation qualifier xs:string optional The attribute shows the qualifier for the string value. source <xs:complextype name="qualifiedtexttype"> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="qualifier" type="xs:string" use="optional"> <xs:>the attribute shows the qualifier for the string value.</xs:> </xs:attribute> </xs:extension> </xs:simplecontent> </xs:complextype> attribute use optional The attribute shows the qualifier for the string value. source <xs:attribute name="qualifier" type="xs:string" use="optional"> <xs:>the attribute shows the qualifier for the string value.</xs:> </xs:attribute>

58 complextype RelatedInformationType children InformationCode InformationID InformationName InformationValue InformationValidFrom InformationValidTo used by element Customer/RelatedInformation source <xs:complextype name="relatedinformationtype"> <xs:sequence> <xs:element name="informationcode" type="qualifiedtexttype" minoccurs="0"> <xs:>a code identifying the type of information. The qualifier identifies the type of the code.</xs:> <xs:element name="informationid" type="xs:string" minoccurs="0"> <xs:>unique identifier to the information.</xs:> <xs:element name="informationname" type="xs:string" minoccurs="0"> <xs:>name for the type of information if applicable.</xs:> <xs:element name="informationvalue" type="xs:string" minoccurs="0"> <xs:>the information itself.</xs:>

59 <xs:element name="informationvalidfrom" type="xs:datetime" minoccurs="0"> <xs:>first valid date for the information if applicable.</xs:> <xs:element name="informationvalidto" type="xs:datetime" minoccurs="0"> <xs:>last valid date for the information if applicable.</xs:> </xs:sequence> </xs:complextype> element RelatedInformationType/InformationCode type QualifiedTextType attributes Name Type Use qualifier xs:string optional Default Fixed Annotation The attribute shows the qualifier for the string value. A code identifying the type of information. The qualifier identifies the type of the code. source <xs:element name="informationcode" type="qualifiedtexttype" minoccurs="0"> <xs:>a code identifying the type of information. The qualifier identifies the type of the code.</xs:>

60 element RelatedInformationType/InformationID Unique identifier to the information. source <xs:element name="informationid" type="xs:string" minoccurs="0"> <xs:>unique identifier to the information.</xs:> element RelatedInformationType/InformationName Name for the type of information if applicable. source <xs:element name="informationname" type="xs:string" minoccurs="0"> <xs:>name for the type of information if applicable.</xs:> element RelatedInformationType/InformationValue The information itself. source <xs:element name="informationvalue" type="xs:string" minoccurs="0">

61 <xs:>the information itself.</xs:> element RelatedInformationType/InformationValidFrom type xs:datetime First valid date for the information if applicable. source <xs:element name="informationvalidfrom" type="xs:datetime" minoccurs="0"> <xs:>first valid date for the information if applicable.</xs:> element RelatedInformationType/InformationValidTo type xs:datetime Last valid date for the information if applicable. source <xs:element name="informationvalidto" type="xs:datetime" minoccurs="0"> <xs:>last valid date for the information if applicable.</xs:>

62 complextype SystemType namespace used by element UserAreaType/System attributes Name Type Use Default Fixed Annotation property xs:string optional source <xs:complextype name="systemtype"> <xs:sequence> <xs:any processcontents="skip" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="property" type="xs:string" use="optional"/> </xs:complextype> attribute use optional source <xs:attribute name="property" type="xs:string" use="optional"/> complextype UserAreaType namespace children System used by elements Customer/UserArea PartyBasicInformationType/UserArea source <xs:complextype name="userareatype"> <xs:sequence> <xs:element name="system" type="systemtype" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> </xs:complextype>

63 element UserAreaType/System namespace type SystemType maxocc unbounded attributes Name Type Use Default Fixed Annotation property xs:string optional source <xs:element name="system" type="systemtype" minoccurs="0" maxoccurs="unbounded"/> XML Schema generated by XMLSpy Schema Editor

How to interface external application to WIN UR

How to interface external application to WIN UR XML Interfaces How to interface external application to WIN UR Version 1.0 Le 4 juillet 2007 ADE Page 1 XML INTERFACE OVERWIEW... 5 WHAT IS IT?... 5 WHO IS IT FOR, AND HOW TO IMPLEMENT IT?... 5 DOCUMENTS

More information

Schema schema-for-json.xsd

Schema schema-for-json.xsd Schema schema-for-json.xsd schema location: attributeformdefault: elementformdefault: targetnamespace:..\schema-for-json.xsd qualified http://www.w3.org/2015/exi/json Elements Complex types Simple types

More information

XML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28

XML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28 1 / 28 XML Schema Mario Alviano University of Calabria, Italy A.Y. 2017/2018 Outline 2 / 28 1 Introduction 2 Elements 3 Simple and complex types 4 Attributes 5 Groups and built-in 6 Import of other schemes

More information

Restricting complextypes that have mixed content

Restricting complextypes that have mixed content Restricting complextypes that have mixed content Roger L. Costello October 2012 complextype with mixed content (no attributes) Here is a complextype with mixed content:

More information

BBPS API Sepcifications

BBPS API Sepcifications BBPS API Sepcifications v11.0 BBPS API Sepcifications v11.0 Page 1 Table of Contents 1 Bill Fetch Request 4 Sample Bill Fetch Request API 4 Bill Fetch Request Tag Details 5 Bill Fetch Request XSD 6 2 Bill

More information

So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it?

So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it? XML Page 1 XML and web services Monday, March 14, 2011 2:50 PM So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it? XML Page 2 Where

More information

Introducing our First Schema

Introducing our First Schema 1 di 11 21/05/2006 10.24 Published on XML.com http://www.xml.com/pub/a/2000/11/29/schemas/part1.html See this if you're having trouble printing code examples Using W3C XML By Eric van der Vlist October

More information

Service Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation

Service Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation Service Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation 1 Outline Introduction to SML SML Model Inter-Document References URI scheme deref() extension function Schema-based

More information

2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1)

2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1) Data-centric XML XML Schema (Part 1) Schema and DTD Disadvantages of DTD: separate, non-xml syntax very limited constraints on data types (just ID, IDREF, ) no support for sets (i.e. each element type

More information

Oracle Hospitality OPERA Message Specification for 2-Way Interface between External Activity Scheduler and OPERA Hotel Version 5.1.

Oracle Hospitality OPERA Message Specification for 2-Way Interface between External Activity Scheduler and OPERA Hotel Version 5.1. Oracle Hospitality OPERA Message Specification for 2-Way Interface between External Activity Scheduler and OPERA Hotel Version 5.1 January 2018 Copyright 1987, 2018, Oracle and/or its affiliates. All rights

More information

Trustmark Framework Technical Specification

Trustmark Framework Technical Specification Trustmark Framework Technical Specification Version 1.2 November 6, 2017 Published by the Georgia Tech Research Institute under the Trustmark Initiative https://trustmarkinitiative.org/ Table of Contents

More information

Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017

Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017 Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related

More information

XML Schema Element and Attribute Reference

XML Schema Element and Attribute Reference E XML Schema Element and Attribute Reference all This appendix provides a full listing of all elements within the XML Schema Structures Recommendation (found at http://www.w3.org/tr/xmlschema-1/). The

More information

Messages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.

Messages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers. May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which

More information

Intellectual Property Rights Notice for Open Specifications Documentation

Intellectual Property Rights Notice for Open Specifications Documentation [MS-SSISPARAMS-Diff]: Intellectual Property Rights tice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,

More information

Cisco Prime Central 1.0 API Guide

Cisco Prime Central 1.0 API Guide Cisco Prime Central 1.0 API Guide Cisco Prime Central API Cisco Prime Central Information Model and API's to support the following features. Managed Elements and Equipment Inventory Object Create, Delete

More information

Introduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML

Introduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying

More information

Mailtips Extensions to Web Service Protocol Specification

Mailtips Extensions to Web Service Protocol Specification [MS-OXWMT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,

More information

Fall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions

Fall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery

More information

Oracle Hospitality OPERA Electronic Distribution Systems (OEDS) Activity Web Service Specifications Version 5.1

Oracle Hospitality OPERA Electronic Distribution Systems (OEDS) Activity Web Service Specifications Version 5.1 Oracle Hospitality OPERA Electronic Distribution Systems (OEDS) Activity Web Service Specifications Version 5.1 January 2018 Copyright 1987, 2018, Oracle and/or its affiliates. All rights reserved. This

More information

Altova XMLSpy 2007 Tutorial

Altova XMLSpy 2007 Tutorial Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage

More information

Altova XMLSpy 2013 Tutorial

Altova XMLSpy 2013 Tutorial Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage

More information

XML. Part II DTD (cont.) and XML Schema

XML. Part II DTD (cont.) and XML Schema XML Part II DTD (cont.) and XML Schema Attribute Declarations Declare a list of allowable attributes for each element These lists are called ATTLIST declarations Consists of 3 basic parts The ATTLIST keyword

More information

[MS-SSISPARAMS-Diff]: Integration Services Project Parameter File Format. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-SSISPARAMS-Diff]: Integration Services Project Parameter File Format. Intellectual Property Rights Notice for Open Specifications Documentation [MS-SSISPARAMS-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for

More information

SYNDICATING HIERARCHIES EFFECTIVELY

SYNDICATING HIERARCHIES EFFECTIVELY SDN Contribution SYNDICATING HIERARCHIES EFFECTIVELY Applies to: SAP MDM 5.5 Summary This document introduces hierarchy tables and a method of effectively sending out data stored in hierarchy tables. Created

More information

XML and Web Services

XML and Web Services XML and Web Services Lecture 8 1 XML (Section 17) Outline XML syntax, semistructured data Document Type Definitions (DTDs) XML Schema Introduction to XML based Web Services 2 Additional Readings on XML

More information

Work/Studies History. Programming XML / XSD. Database

Work/Studies History. Programming XML / XSD. Database Work/Studies History 1. What was your emphasis in your bachelor s work at XXX? 2. What was the most interesting project you worked on there? 3. What is your emphasis in your master s work here at UF? 4.

More information

XEP-0298: Delivering Conference Information to Jingle Participants (Coin)

XEP-0298: Delivering Conference Information to Jingle Participants (Coin) XEP-0298: Delivering Conference Information to Jingle Participants (Coin) Emil Ivov mailto:emcho@jitsi.org xmpp:emcho@jit.si Enrico Marocco mailto:enrico.marocco@telecomitalia.it xmpp:enrico@tilab.com

More information

XEP-0104: HTTP Scheme for URL Data

XEP-0104: HTTP Scheme for URL Data XEP-0104: HTTP Scheme for URL Data Matthew Miller mailto:linuxwolf@outer-planes.net xmpp:linuxwolf@outer-planes.net 2004-01-20 Version 0.3 Status Type Short Name Deferred Standards Track N/A This document

More information

Supplier Guide: How to register as a supplier in Lavante

Supplier Guide: How to register as a supplier in Lavante Supplier Guide: How to register as a supplier in Lavante Shared Services Center Americas May 2018 Registering as a Shire Supplier Shire s Shared Services Centre Americas (SSCA), based in Exton, PA is responsible

More information

SUPPLIER REGISTRATION DEFINITION ON EXTERNAL LINK

SUPPLIER REGISTRATION DEFINITION ON EXTERNAL LINK SUPPLIER REGISTRATION DEFINITION ON EXTERNAL LINK When Supplier Registration is accessed from an external link, a screen will appear where you can enter the supplier summary information. On this screen,

More information

IODEF Data Model Status (progress from 03) <draft-ietf-inch-iodef-03>

IODEF Data Model Status (progress from 03) <draft-ietf-inch-iodef-03> IODEF Data Model Status (progress from 03) tracked @ https://rt.psg.com : inch-dm queue Roman Danyliw Wednesday, March 9. 2005 IETF 62, Minneapolis, USA Progress

More information

NEW SUPPLIER REGISTRATION GUIDE

NEW SUPPLIER REGISTRATION GUIDE Aug 2016 Version 5 NEW SUPPLIER REGISTRATION GUIDE This guide is to help registering to Zonescorp supplier portal to allow suppliers to list their products and services and to allow Zonescorp procurement

More information

Chapter 11 XML Data Modeling. Recent Development for Data Models 2016 Stefan Deßloch

Chapter 11 XML Data Modeling. Recent Development for Data Models 2016 Stefan Deßloch Chapter 11 XML Data Modeling Recent Development for Data Models 2016 Stefan Deßloch Motivation Traditional data models (e.g., relational data model) primarily support structure data separate DB schema

More information

[MS-OXWSGTZ]: Get Server Time Zone Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-OXWSGTZ]: Get Server Time Zone Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation [MS-OXWSGTZ]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

Chapter 3 Brief Overview of XML

Chapter 3 Brief Overview of XML Slide 3.1 Web Serv vices: Princ ciples & Te echno ology Chapter 3 Brief Overview of XML Mike P. Papazoglou & mikep@uvt.nl Slide 3.2 Topics XML document structure XML schemas reuse Document navigation and

More information

Altova XMLSpy 2014 Tutorial

Altova XMLSpy 2014 Tutorial Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage

More information

Schema XACML v0.11c.xsd

Schema XACML v0.11c.xsd Schema XACML v0.11c.xsd schema location: targetnamespace: C:\temp\XACML v0.11c.xsd Elements Complex s Simple s and ActionsType EffectType attributefunction AndType divide equal greaterorequal lessorequal

More information

Altova XMLSpy Tutorial

Altova XMLSpy Tutorial Altova XMLSpy 2018 Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or

More information

MWTM 6.1 NBAPI WSDL and XSD Definitions

MWTM 6.1 NBAPI WSDL and XSD Definitions APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-5 ProvisionAPI.wsdl, page

More information

Markup Languages. Lecture 4. XML Schema

Markup Languages. Lecture 4. XML Schema Markup Languages Lecture 4. XML Schema Introduction to XML Schema XML Schema is an XML-based alternative to DTD. An XML schema describes the structure of an XML document. The XML Schema language is also

More information

Antenna Data Exchange File Format (ADX)

Antenna Data Exchange File Format (ADX) Antenna Data Exchange File Format (ADX) Technical Reference Version 1.2 Implementation Approval: : Tony Paul Position: RF Safety Compliance Coordinator Process Owner: : Mike Wood Position: Chairman - MCF

More information

[MS-TSWP]: Terminal Services Workspace Provisioning Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-TSWP]: Terminal Services Workspace Provisioning Protocol. Intellectual Property Rights Notice for Open Specifications Documentation [MS-TSWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

XML extensible Markup Language

XML extensible Markup Language extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object

More information

Software Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1

Software Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1 extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object

More information

extensible Markup Language

extensible Markup Language What is XML? The acronym means extensible Markup Language It is used to describe data in a way which is simple, structured and (usually) readable also by humans Developed at the end of the ninenties by

More information

Trade Mark Data Model

Trade Mark Data Model Please Send Your Comments To: TM-XML-WG@oami.europa.eu Trade Mark Data Model Version: 1.3 Date: October 23th, 2009 Document : TM-XML-DM-V1-3 Editor: TM-XML Working Group TM-XML Version 1.3 TM-XML Version

More information

MWTM NBAPI WSDL and XSD Definitions

MWTM NBAPI WSDL and XSD Definitions APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1.4 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page

More information

Annex I: Compiled Data Dictionary of ASEAN ATIGA Form D

Annex I: Compiled Data Dictionary of ASEAN ATIGA Form D Annexes Annex I: Compiled Data Dictionary of ASEAN ATIGA Form D Document Title Document Purpose Name of Document Owner ASEAN ATIGA FORM D A Certificate of Origin is a document/message identifying goods,

More information

Instant Order Notification API Guide

Instant Order Notification API Guide Instant Order Notification API Guide A reference guide for developers who want to automate order notifications. Steve Matlock Annika Munz 2 Checkout by Amazon Introduction Checkout by Amazon TOC 3 Contents

More information

Big Data 9. Data Models

Big Data 9. Data Models Ghislain Fourny Big Data 9. Data Models pinkyone / 123RF Stock Photo 1 Syntax vs. Data Models Physical view Syntax this is text. 2 Syntax vs. Data Models a Logical view

More information

ONVIF. XML Schema Version and Extension Handling White Paper

ONVIF. XML Schema Version and Extension Handling White Paper ONVIF 1 XML Schema Extension Handling ONVIF XML Schema Version and Extension Handling White Paper Version 1.2 December, 2015 1 Background 1.1 Purpose Version and extensions handling for XML schemas are

More information

Copyright Basware Corporation. All rights reserved. User Guide Basware Network

Copyright Basware Corporation. All rights reserved. User Guide Basware Network Copyright 1999-2016 Basware Corporation. All rights reserved. User Guide Basware Network About Basware Network Support Documentation The following documentation is available for Basware Network users:

More information

:PRIA_DOCUMENT_v2_4_1.XSD

:PRIA_DOCUMENT_v2_4_1.XSD ==================================================================

More information

The following is a sample XML code from the HCSProductCatalog.wsdl file.

The following is a sample XML code from the HCSProductCatalog.wsdl file. APPENDIXA This appendix contains sample WSDL and XSD files. It includes the following sections: HCSProductCatalog.wsdl File, page A-1 HCSProvision.xsd File, page A-27 HCSProvisionAsyncResponse.wsdl File,

More information

Modelling XML Applications

Modelling XML Applications Modelling XML Applications Patryk Czarnik XML and Applications 2013/2014 Lecture 2 14.10.2013 XML application (recall) XML application (zastosowanie XML) A concrete language with XML syntax Typically defined

More information

Brief guide for XML, XML Schema, XQuery for YAWL data perspective

Brief guide for XML, XML Schema, XQuery for YAWL data perspective Brief guide for XML, XML Schema, XQuery for YAWL data perspective Carmen Bratosin March 16, 2009 1 Data perspective in YAWL YAWL engine files are XML based. Therefore, YAWL uses XML for data perspective

More information

Hewlett Packard Enterprise Supplier Setup Instructions:

Hewlett Packard Enterprise Supplier Setup Instructions: Hewlett Packard Enterprise Supplier Setup Instructions: How to Register Your Company in Hewlett Packard Enterprise s Supplier Database Global Procurement Last Updated: 1 November 2015 1 Contents Topic

More information

CP Visualizer Format

CP Visualizer Format CP Visualizer Format February, 00 Helmut Simonis email: h.simonis@c.ucc.ie homepage: http://c.ucc.ie/~hsimonis Cork Constraint Computation Centre Computer Science Department University College Cork Ireland

More information

XEP-0171: Language Translation

XEP-0171: Language Translation XEP-0171: Language Translation Boyd Fletcher mailto:boyd.fletcher@us.army.mil Keith Lirette mailto:keith.lirette@tridsys.com Daniel LaPrade mailto:dlaprade@echostorm.net Brian Raymond mailto:braymond@echostorm.net

More information

TCG. TCG Infrastructure Working Group Security Qualities Schema. TCG PUBLISHED Copyright TCG 2007

TCG. TCG Infrastructure Working Group Security Qualities Schema. TCG PUBLISHED Copyright TCG 2007 TCG Infrastructure Working Group Security Qualities Schema Revision 7 21 May 2007 Published Contacts: admin@trustedcomputinggroup.org Copyright TCG 2007 TCG Copyright 2007 Trusted Computing Group, Incorporated.

More information

TS SIGNATURE VALIDATION REPORT

TS SIGNATURE VALIDATION REPORT TS 119 102 2 SIGNATURE VALIDATION REPORT An introduction Presented by Peter Lipp for the esignature and eseal validation workshop, Jan 10 2018 Agenda Scope Relation to EN 319 102 1 Approach Report structure

More information

PTC Integrity 10.7 Web Services Reference

PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation

More information

XEP-0293: Jingle RTP Feedback Negotiation

XEP-0293: Jingle RTP Feedback Negotiation XEP-0293: Jingle RTP Feedback Negotiation Olivier Crête mailto:olivier.crete@collabora.co.uk xmpp:olivier.crete@collabora.co.uk 2015-08-11 Version 1.0 Status Type Short Name Draft Standards Track NOT_YET_ASSIGNED

More information

Released to: TSCP Architecture Committee

Released to: TSCP Architecture Committee Business Authorization Identification and Labeling Scheme Version 1 (BAILS v.1.0) Prepared by: TSCP ILH Team Lead Author: Jean-Paul Buu-Sao, TSCP Released to: TSCP Architecture Committee Edition: 1.4 Published:

More information

XEP-0333: Chat Markers

XEP-0333: Chat Markers XEP-0333: Chat Markers Spencer MacDonald mailto:im@spencermacdonald.com xmpp:im@spencermacdonald.com 2017-09-11 Version 0.3 Status Type Short Name Deferred Standards Track NOT_YET_ASSIGNED This specification

More information

a public domain XML format for exchanging electronic addresses between service providers

a public domain XML format for exchanging electronic addresses between service providers eaddress a public domain XML format for exchanging electronic addresses between service providers version 1.0 2016-09-16 Apix: After comments from VLF the format is ready for version 1.0 version 0.4 2016-09-02

More information

XSD Reference For EXPRESS XML language

XSD Reference For EXPRESS XML language VTT-TEC-ADA-08 Page 1 SECOM Co., Ltd. / VTT Building and Transport Yoshinobu Adachi E-Mail: yoshinobu.adachi@vtt.fi VTT-TEC-ADA-08 XSD Reference For EXPRESS XML language 2002/02/11 1. INTRODUCTION... 2

More information

[MS-OXWSATT]: Attachment Handling Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-OXWSATT]: Attachment Handling Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation [MS-OXWSATT]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

The Instant Order Processing Notification API Guide

The Instant Order Processing Notification API Guide The Instant Order Processing Notification API Guide A reference guide for developers who want to automate order notifications with their Checkout by Amazon orders. The Instant Order Processing Notification

More information

Big Data Exercises. Fall 2018 Week 8 ETH Zurich. XML validation

Big Data Exercises. Fall 2018 Week 8 ETH Zurich. XML validation Big Data Exercises Fall 2018 Week 8 ETH Zurich XML validation Reading: (optional, but useful) XML in a Nutshell, Elliotte Rusty Harold, W. Scott Means, 3rd edition, 2005: Online via ETH Library 1. XML

More information

OpenTravel Alliance Best Practices

OpenTravel Alliance Best Practices OpenTravel Alliance Best Practices OpenTravel Alliance, Inc. 333 John Carlyle Street, Suite 600 Alexandria, Va. 22314 USA +1 703-548-7005 Fax +1 703-548-1264 opentravel@disa.org http://www.opentravel.org/

More information

1 9/8/2009 5:05 PM

1 9/8/2009 5:05 PM http://www.pesc.org/library/docs/standards/h... 1 9/8/2009 5:05 PM This XML file does not appear to have any style information associated with it. The document tree is shown below. edited with XMLSpy v2006

More information

Notes. Any feedback/suggestions? IS 651: Distributed Systems

Notes. Any feedback/suggestions? IS 651: Distributed Systems Notes Grading statistics Midterm1: average 10.60 out of 15 with stdev 2.22 Total: average 15.46 out of 21 with stdev 2.80 A range: [18.26, 23] B range: [12.66, 18.26) C or worse range: [0, 12.66) The curve

More information

OCIMF. SIRE Crew Web Services 2.0

OCIMF. SIRE Crew Web Services 2.0 OCIMF SIRE Crew Web Services 2.0 v1.0.03 1 March 2012 Introduction OCIMF SIRE Web Services V2 are available at the following URLs: http://wsv2.ocimf-sire.com/ocimfservices.asmx https://wsv2.ocimf-sire.com/ocimfservices.asmx

More information

[MS-MSL]: Mapping Specification Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-MSL]: Mapping Specification Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation [MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

XEP-0009: Jabber-RPC

XEP-0009: Jabber-RPC XEP-0009: Jabber-RPC DJ Adams mailto:dj.adams@pobox.com xmpp:dj@gnu.mine.nu 2011-11-10 Version 2.2 Status Type Short Name Final Standards Track jabber-rpc This specification defines an XMPP protocol extension

More information

Ibuy Source to Contract. Quick Reference Guide Self-Registration For Suppliers

Ibuy Source to Contract. Quick Reference Guide Self-Registration For Suppliers Ibuy Source to Contract Quick Reference Guide Self-Registration For Suppliers Version 1.6, June 2018 1 1 Supplier Self Registration This document will guide you through the Self-Registration which is a

More information

[MS-OXWSMTRK]: Message Tracking Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-OXWSMTRK]: Message Tracking Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation [MS-OXWSMTRK]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,

More information

XEP-0357: Push Notifications

XEP-0357: Push Notifications XEP-0357: Push Notifications Kevin Smith mailto:kevin@kismith.co.uk xmpp:kevin@doomsong.co.uk Lance Stout mailto:lance@andyet.com xmpp:lance@lance.im 2017-08-24 Version 0.3 Status Type Short Name Experimental

More information

HOW TO SEND PDF E-INVOICES TO ROBERTSHAW CORPORATION

HOW TO SEND PDF E-INVOICES TO ROBERTSHAW CORPORATION Robertshaw Corporation Supplier Kit for HOW TO SEND PDF E-INVOICES TO ROBERTSHAW CORPORATION 2 (7) SPECIFIC INFORMATION REGARDING ROBERTSHAW CORPORATION AS A PDF E-INVOICE RECEIVER A. Signing Up for Basware

More information

USER GUIDE FOR SUPPLIERS. OpusCapita Business Network

USER GUIDE FOR SUPPLIERS. OpusCapita Business Network USER GUIDE FOR SUPPLIERS OpusCapita Business Network Contents 1. Introduction... 3 2. Finalizing registration and changing your password... 4 2.1 Finalize your registration... 4 2.2 Change your forgotten

More information

Solution Sheet 5 XML Data Models and XQuery

Solution Sheet 5 XML Data Models and XQuery The Systems Group at ETH Zurich Big Data Fall Semester 2012 Prof. Dr. Donald Kossmann Prof. Dr. Nesime Tatbul Assistants: Martin Kaufmann Besmira Nushi 07.12.2012 Solution Sheet 5 XML Data Models and XQuery

More information

MANAGING INFORMATION (CSCU9T4) LECTURE 2: XML STRUCTURE

MANAGING INFORMATION (CSCU9T4) LECTURE 2: XML STRUCTURE MANAGING INFORMATION (CSCU9T4) LECTURE 2: XML STRUCTURE Gabriela Ochoa http://www.cs.stir.ac.uk/~goc/ OUTLINE XML Elements vs. Attributes Well-formed vs. Valid XML documents Document Type Definitions (DTDs)

More information

!" DTDs rely on a mechanism based on the use of. !" It is intended to specify cross references" !" Reference to a figure, chapter, section, etc.!

! DTDs rely on a mechanism based on the use of. ! It is intended to specify cross references ! Reference to a figure, chapter, section, etc.! MULTIMEDIA DOCUMENTS! XML Schema (Part 2)"!" DTDs rely on a mechanism based on the use of attributes (ID et IDREF) to specify links into documents"!" It is intended to specify cross references"!" Reference

More information

saml requesting attributes v1.1 wd01 Working Draft January 2016 Standards Track Draft Copyright OASIS Open All Rights Reserved.

saml requesting attributes v1.1 wd01 Working Draft January 2016 Standards Track Draft Copyright OASIS Open All Rights Reserved. Standards Track Draft Copyright OASIS Open 2015. All Rights Reserved. Page 1 of 10 SAML v2.0 Protocol Extension for Requesting Attributes in AuthnRequest Version 1.1 Working Draft 02 19 January 2016 Technical

More information

Coupa Guidance for New Suppliers

Coupa Guidance for New Suppliers Coupa Guidance for New Suppliers Welcome to the Pearson Supplier Onboarding Process! This document is designed to help you through the onboarding process by joining the Coupa Supplier Portal. May 2018

More information

X3D Unit Specification Updates Myeong Won Lee The University of Suwon

X3D Unit Specification Updates Myeong Won Lee The University of Suwon X3D Unit Specification Updates Myeong Won Lee The University of Suwon 1 Units Specification ISO_IEC_19775_1_2008_WD3_Am1_2011_04_14 PDAM in ISO progress UNIT statement Defined in Core component UNIT statements

More information

a public domain XML format for exchanging electronic addresses between service providers

a public domain XML format for exchanging electronic addresses between service providers eaddress a public domain XML format for exchanging electronic addresses between service providers version 1.1 2017-10-23 VLF: Added support for authorization key (for Feeniks project) VLF: Added BATCH

More information

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. [MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,

More information

/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC)

/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC) /// Rapport / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC) / Maart 2017 www.vlaanderen.be/informatievlaanderen Informatie Vlaanderen /// Aanpassingen aan de webservices Dit

More information

Big Data for Engineers Spring Data Models

Big Data for Engineers Spring Data Models Ghislain Fourny Big Data for Engineers Spring 2018 11. Data Models pinkyone / 123RF Stock Photo CSV (Comma separated values) This is syntax ID,Last name,first name,theory, 1,Einstein,Albert,"General, Special

More information

XEP-0033: Extended Stanza Addressing

XEP-0033: Extended Stanza Addressing XEP-0033: Extended Stanza Addressing Joe Hildebrand mailto:jhildebr@cisco.com xmpp:hildjj@jabber.org Peter Saint-Andre mailto:xsf@stpeter.im xmpp:peter@jabber.org http://stpeter.im/ 2017-01-11 Version

More information

Validation Language. GeoConnections Victoria, BC, Canada

Validation Language. GeoConnections Victoria, BC, Canada Validation Language Submitted To: Program Manager GeoConnections Victoria, BC, Canada Submitted By: Jody Garnett Brent Owens Refractions Research Inc. Suite 400, 1207 Douglas Street Victoria, BC, V8W-2E7

More information

BBPS API SPECIFICATIONS

BBPS API SPECIFICATIONS BBPS API SPECIFICATIONS Version 12.0 Date: 07.02.2018 Abstract This document contains information pertaining to different APIs used in BBPS and some considerations which will be beneficial while designing

More information

[MS-OXWSMSG]: Message Types Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-OXWSMSG]:  Message Types Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation [MS-OXWSMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation [MS-SSDL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information