Schema XSD opisująca typy dokumentów obsługiwane w Systemie invooclip
|
|
|
- Aleesha George
- 10 years ago
- Views:
Transcription
1 Krajowa Izba Rozliczeniowa S.A. Schema XSD opisująca typy dokumentów obsługiwane w Systemie invooclip Wersja 1.1
2 <?xml version="1.0" encoding="utf-8"?> <!-- edited with XMLSpy v2007 ( by Pawel Bartuzi (Krajowa Izba Rozliczeniowa S.A.) --> <xs:schema xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> <xs:simpletype name="nipvaluetype"> <xs:restriction base="xs:string"> <xs:pattern value="[\s ]{1,14}"/> </xs:restriction> </xs:simpletype> <xs:complextype name="niptype"> <xs:simplecontent> <xs:extension base="nipvaluetype"> <xs:attribute name="type"> <xs:simpletype> <xs:restriction base="xs:token"> <xs:enumeration value="pl"/> <xs:enumeration value="europe"/> <xs:enumeration value="other"/> </xs:restriction> </xs:simpletype> </xs:attribute> </xs:extension> </xs:simplecontent> </xs:complextype> <xs:simpletype name="regontype"> <xs:union> <xs:simpletype> <xs:restriction base="xs:string"> <xs:pattern value="\d{9}" /> </xs:restriction> </xs:simpletype> <xs:simpletype> <xs:restriction base="xs:string">
3 <xs:pattern value="\d{14}" /> </xs:restriction> </xs:simpletype> </xs:union> </xs:simpletype> <xs:simpletype name=" type"> </xs:simpletype> <xs:restriction base="xs:string"> </xs:restriction> <xs:pattern <xs:complextype name="documenttype" abstract="true"> <xs:documentation>typ abstrakcyjny, stanowiący podstawę dla wszystkich innych typów dokumentów. Zawiera pola wspólne dla wszystkich typów dokumentów.</xs:documentation> <xs:sequence> <xs:element name="description" type="xs:string" minoccurs="0"> dokumentu</xs:documentation> document</xs:documentation> xml:lang="pl">opis xml:lang="en">description of <xs:element name="lastmodified" type="xs:datetime" minoccurs="0"> modyfikacji</xs:documentation> modified</xs:documentation> xml:lang="pl">data ostatniej xml:lang="en">last <xs:element name="filename" type="xs:anyuri" minoccurs="0"> xml:lang="pl">nazwa</xs:documentation>
4 xml:lang="en">name</xs:documentation> <xs:element name="filesize" type="xs:integer" minoccurs="0"> bajtach)</xs:documentation> byte)</xs:documentation> xml:lang="pl">rozmiar (w xml:lang="en">size (in </xs:sequence> </xs:complextype> <xs:complextype name="genericdocumenttype"> xml:lang="pl">dokument</xs:documentation> xml:lang="en">document</xs:documentation> pól.</xs:documentation> fields.</xs:documentation> <xs:documentation source="helptext" xml:lang="pl">podstawowa forma dokumentu bez dodatkowych <xs:documentation source="helptext" xml:lang="en">the basic form of the document without additional <xs:complexcontent> <xs:extension base="documenttype"/> </xs:complexcontent> </xs:complextype> <xs:complextype name="invoicetype"> xml:lang="pl">faktura</xs:documentation> xml:lang="en">invoice</xs:documentation> <xs:complexcontent> <xs:extension base="documenttype"> <xs:sequence> <xs:element name="invnumber" type="xs:string">
5 faktury</xs:documentation> number</xs:documentation> xml:lang="pl">numer xml:lang="en">invoice <xs:element name="invrecipient" type="xs:string" minoccurs="0"> xml:lang="pl">odbiorca faktury</xs:documentation> recipient</xs:documentation> xml:lang="en">invoice <xs:element name="nettoamount" minoccurs="0"> netto</xs:documentation> amount</xs:documentation> xml:lang="pl">kwota xml:lang="en">net <xs:simpletype> <xs:restriction base="xs:decimal"> <xs:fractiondigits value="2"/> </xs:restriction> </xs:simpletype> <xs:element name="bruttoamount" minoccurs="0"> brutto</xs:documentation> amount</xs:documentation> xml:lang="pl">kwota xml:lang="en">gross <xs:simpletype> <xs:restriction base="xs:decimal"> <xs:fractiondigits value="2"/> </xs:restriction>
6 </xs:simpletype> <xs:element name="currency" type="xs:string" minoccurs="0"> xml:lang="pl">waluta</xs:documentation> xml:lang="en">currency</xs:documentation> <xs:element name="nip" type="niptype"> xml:lang="pl">nip</xs:documentation> xml:lang="en">nip</xs:documentation> <xs:documentation source="helptext" xml:lang="pl">dla pola NIP aplikacja obsługuje atrybut type o następujących wartościach: PL, Europe, Other</xs:documentation> <xs:element name="regon" type="regontype" minoccurs="0"> xml:lang="pl">regon</xs:documentation> xml:lang="en">regon</xs:documentation> <xs:element name=" " type=" type"> xml:lang="pl"> </xs:documentation> xml:lang="en"> </xs:documentation> <xs:element name="ordernumber" type="xs:string" minoccurs="0">
7 zamówienia</xs:documentation> number</xs:documentation> xml:lang="pl">numer xml:lang="en">order <xs:element name="recipientnumber" type="xs:string" minoccurs="0"> odbiorcy</xs:documentation> xml:lang="en">recipient's number</xs:documentation> xml:lang="pl">numer <xs:element name="adddescription" type="xs:string" minoccurs="0"> xml:lang="pl">dodatkowy opis</xs:documentation> xml:lang="en">additional description</xs:documentation> <xs:element name="invoicekind" type="xs:string" minoccurs="0"> faktury</xs:documentation> kind</xs:documentation> korekty, proformy, zaliczki</xs:documentation> xml:lang="pl">rodzaj xml:lang="en">invoice <xs:documentation source="helptext" xml:lang="pl">duplikaty, <xs:element name="typeinvoice" type="xs:string" minoccurs="0"> faktury</xs:documentation> type</xs:documentation> sprzedażowa lub zakupowa</xs:documentation> xml:lang="pl">typ xml:lang="en">invoice <xs:documentation source="helptext" xml:lang="pl">faktura
8 <xs:element name="typepayment" type="xs:string" minoccurs="0"> płatności</xs:documentation> xml:lang="en">payment type</xs:documentation> sprzedażowa lub zakupowa</xs:documentation> xml:lang="pl">rodzaj <xs:documentation source="helptext" xml:lang="pl">faktura <xs:element name="nameissuer" type="xs:string" minoccurs="0"> wystawcy</xs:documentation> xml:lang="pl">nazwa <xs:element name="cityissuer" type="xs:string" minoccurs="0"> wystawcy</xs:documentation> xml:lang="pl">miasto <xs:element name="postcodeissuer" type="xs:string" minoccurs="0"> pocztowy wystawcy</xs:documentation> xml:lang="pl">kod <xs:element name="streetissuer" type="xs:string" minoccurs="0"> wystawcy</xs:documentation> xml:lang="pl">ulica
9 <xs:element name="numstreetissuer" type="xs:string" minoccurs="0"> wystawcy</xs:documentation> xml:lang="pl">numer <xs:element name="dateissueinvoice" type="xs:string" minoccurs="0"> wystawienia</xs:documentation> xml:lang="pl">data <xs:element name="datesales" type="xs:string" minoccurs="0"> sprzedaży</xs:documentation> xml:lang="pl">data <xs:element name="dateintroduceinvoice" type="xs:string" minoccurs="0"> wprowadzenia faktury</xs:documentation> xml:lang="pl">data <xs:element name="recipientcountry" type="xs:string" minoccurs="0"> odbiorcy</xs:documentation> xml:lang="pl">kraj
10 <xs:element name="placeregistrationinvoices" type="xs:string" minoccurs="0"> rejestracji faktury</xs:documentation> xml:lang="pl">miejsce <xs:element name="placeoriginalarchive" type="xs:string" minoccurs="0"> przechowywania oryginału</xs:documentation> xml:lang="pl">miejsce <xs:element name="numcorrinv" type="xs:string" minoccurs="0"> faktury korygującej</xs:documentation> xml:lang="pl">numer <xs:element name="numcorrinvinitial" type="xs:string" minoccurs="0"> faktury do której wystawiona jest korekta</xs:documentation> xml:lang="pl">numer <xs:element name="invoicevalue" type="xs:string" minoccurs="0"> faktury</xs:documentation> xml:lang="pl">wartość <xs:element name="valuewords" type="xs:string" minoccurs="0">
11 faktury słownie</xs:documentation> xml:lang="pl">wartość <xs:element name="paydeadline" type="xs:string" minoccurs="0"> płatności</xs:documentation> xml:lang="pl">termin <xs:element name="nipissuer" type="xs:string" minoccurs="0"> Wystawcy</xs:documentation> xml:lang="pl">nip <xs:element name="namemerch" type="xs:string" minoccurs="0"> towaru</xs:documentation> xml:lang="pl">nazwa <xs:element name="numaccountissuer" type="xs:string" minoccurs="0"> rachunku wystawcy</xs:documentation> xml:lang="pl">nr <xs:element name="payaccount" type="xs:string" minoccurs="0"> xml:lang="pl">zaliczka</xs:documentation>
12 <xs:element name="deposit" type="xs:decimal" minoccurs="0"> xml:lang="pl">kaucja</xs:documentation> <xs:element name="netto23" type="xs:decimal" minoccurs="0"> 23</xs:documentation> xml:lang="pl">netto <xs:element name="vat23" type="xs:decimal" minoccurs="0"> 23</xs:documentation> xml:lang="pl">vat <xs:element name="netto8" type="xs:decimal" minoccurs="0"> 8</xs:documentation> xml:lang="pl">netto <xs:element name="vat8" type="xs:decimal" minoccurs="0"> 8</xs:documentation> xml:lang="pl">vat
13 <xs:element name="netto5" type="xs:decimal" minoccurs="0"> 5</xs:documentation> xml:lang="pl">netto <xs:element name="vat5" type="xs:decimal" minoccurs="0"> 5</xs:documentation> xml:lang="pl">vat <xs:element name="netto7" type="xs:decimal" minoccurs="0"> 7</xs:documentation> xml:lang="pl">netto <xs:element name="vat7" type="xs:decimal" minoccurs="0"> 7</xs:documentation> xml:lang="pl">vat <xs:element name="netto3" type="xs:decimal" minoccurs="0"> 3</xs:documentation> xml:lang="pl">netto <xs:element name="vat3" type="xs:decimal" minoccurs="0">
14 3</xs:documentation> xml:lang="pl">vat <xs:element name="netto0" type="xs:decimal" minoccurs="0"> 0</xs:documentation> xml:lang="pl">netto <xs:element name="vat0" type="xs:decimal" minoccurs="0"> 0</xs:documentation> xml:lang="pl">vat <xs:element name="nettozw" type="xs:decimal" minoccurs="0"> ZW</xs:documentation> xml:lang="pl">netto <xs:element name="vatzw" type="xs:decimal" minoccurs="0"> ZW</xs:documentation> xml:lang="pl">vat <xs:element name="iddocument" type="xs:string" minoccurs="0"> xml:lang="pl">identyfikator dokumentu</xs:documentation>
15 <xs:element name="idpayment" type="xs:string" minoccurs="0"> xml:lang="pl">identyfikator płatności</xs:documentation> <xs:element name="addfiled1" type="xs:string" minoccurs="0"> zapasowe 1</xs:documentation> xml:lang="pl">pole <xs:element name="addfiled2" type="xs:string" minoccurs="0"> zapasowe 2</xs:documentation> xml:lang="pl">pole <xs:element name="addfiled3" type="xs:string" minoccurs="0"> zapasowe 3</xs:documentation> xml:lang="pl">pole <xs:element name="addfiled4" type="xs:string" minoccurs="0"> zapasowe 4</xs:documentation> xml:lang="pl">pole
16 </xs:sequence> </xs:extension> </xs:complexcontent> </xs:complextype> <xs:complextype name="deliverydoctype"> xml:lang="pl">edokument dostawy</xs:documentation> xml:lang="en">edelivery document</xs:documentation> <xs:complexcontent> <xs:extension base="documenttype"> <xs:sequence> <xs:element name="deliverynumber" type="xs:string" minoccurs="0"> dokumentu dostawy</xs:documentation> document number</xs:documentation> xml:lang="pl">numer xml:lang="en">delivery <xs:element name="invoicenumber" type="xs:string" minoccurs="0"> faktury</xs:documentation> number</xs:documentation> xml:lang="pl">numer xml:lang="en">invoice <xs:element name="invrecipient" type="xs:string" minoccurs="0"> xml:lang="pl">odbiorca faktury</xs:documentation> recipient</xs:documentation> xml:lang="en">invoice <xs:element name="nip" type="niptype">
17 xml:lang="pl">nip</xs:documentation> xml:lang="en">nip</xs:documentation> <xs:documentation source="helptext" xml:lang="pl">dla pola NIP aplikacja obsługuje atrybut type o następujących wartościach: PL, Europe, Other</xs:documentation> <xs:element name=" " type=" type"> xml:lang="pl"> </xs:documentation> xml:lang="en"> </xs:documentation> <xs:element name="regon" type="regontype" minoccurs="0"> xml:lang="pl">regon</xs:documentation> xml:lang="en">regon</xs:documentation> <xs:element name="recipientnumber" type="xs:string" minoccurs="0"> odbiorcy</xs:documentation> xml:lang="en">recipient's number</xs:documentation> xml:lang="pl">numer </xs:sequence> </xs:extension> </xs:complexcontent> </xs:complextype> <xs:complextype name="lukasdoctype"> xml:lang="pl">umowa LukasBank</xs:documentation>
18 xml:lang="en">lukasbank Contract</xs:documentation> <xs:complexcontent> <xs:extension base="documenttype"> <xs:sequence> <xs:element name="logowanieidentyfikator" type="xs:string"> xml:lang="pl">identyfikator umowy</xs:documentation> xml:lang="en">contract id</xs:documentation> <xs:element name="logowaniehaslo" type="xs:string"> uzytkownika</xs:documentation> Password</xs:documentation> xml:lang="pl">haslo xml:lang="en">user <xs:element name=" " type=" type" nillable="true" minoccurs="0"> xml:lang="pl"> </xs:documentation> xml:lang="en"> </xs:documentation> <xs:appinfo source="emptyvalue">true</xs:appinfo> <xs:element name="okresprzechowywania" type="xs:date"> przechowywania</xs:documentation> xml:lang="en">expiration time</xs:documentation> xml:lang="pl">okres </xs:sequence>
19 </xs:extension> </xs:complexcontent> </xs:complextype> <xs:complextype name="edocumenttype"> xml:lang="pl">edokument</xs:documentation> xml:lang="en">edocument</xs:documentation> <xs:complexcontent> <xs:extension base="documenttype"> <xs:sequence> <xs:element name="invnumber" type="xs:string" minoccurs="0"> faktury</xs:documentation> number</xs:documentation> xml:lang="pl">numer xml:lang="en">invoice <xs:element name="invrecipient" type="xs:string" minoccurs="0"> xml:lang="pl">odbiorca faktury</xs:documentation> recipient</xs:documentation> xml:lang="en">invoice <xs:element name="nettoamount" minoccurs="0"> netto</xs:documentation> amount</xs:documentation> xml:lang="pl">kwota xml:lang="en">net <xs:simpletype> <xs:restriction base="xs:decimal"> <xs:fractiondigits value="2"/> </xs:restriction>
20 </xs:simpletype> <xs:element name="kinddocument" type="xs:string" minoccurs="0"> dokumentu</xs:documentation> xml:lang="en">document kind</xs:documentation> xml:lang="pl">rodzaj <xs:element name="numdocument" type="xs:string"> dokumentu</xs:documentation> xml:lang="en">document number</xs:documentation> xml:lang="pl">numer <xs:element name="niprecipient" type="niptype"> odbiorcy</xs:documentation> xml:lang="en">recipient NIP</xs:documentation> xml:lang="pl">nip <xs:documentation source="helptext" xml:lang="pl">dla pola NIP aplikacja obsługuje atrybut type o następujących wartościach: PL, Europe, Other</xs:documentation> <xs:element name="regon" type="regontype" minoccurs="0"> xml:lang="pl">regon</xs:documentation> xml:lang="en">regon</xs:documentation> <xs:element name=" " type=" type"> xml:lang="pl"> </xs:documentation>
21 xml:lang="en"> </xs:documentation> <xs:element name="recipientnumber" type="xs:string" minoccurs="0"> odbiorcy</xs:documentation> xml:lang="en">recipient's number</xs:documentation> xml:lang="pl">numer <xs:element name="adddescription" type="xs:string" minoccurs="0"> xml:lang="pl">dodatkowy opis</xs:documentation> xml:lang="en">additional description</xs:documentation> <xs:element name="archiperiod" type="xs:string" minoccurs="0"> archiwizacji</xs:documentation> xml:lang="pl">okres <xs:element name="dateissue" type="xs:date" minoccurs="0"> wystawienia</xs:documentation> xml:lang="pl">data <xs:element name="namerecipient" type="xs:string" minoccurs="0"> odbiorca</xs:documentation> xml:lang="pl">nazwa
22 <xs:element name="typecorrespondence" type="xs:string" minoccurs="0"> korespondencji</xs:documentation> xml:lang="pl">typ <xs:element name="iddocument" type="xs:string" minoccurs="0"> xml:lang="pl">identyfikator dokumentu</xs:documentation> <xs:element name="addfiled1" type="xs:string" minoccurs="0"> zapasowe 1</xs:documentation> xml:lang="pl">pole <xs:element name="addfiled2" type="xs:string" minoccurs="0"> zapasowe 2</xs:documentation> xml:lang="pl">pole <xs:element name="addfiled3" type="xs:string" minoccurs="0"> zapasowe 3</xs:documentation> xml:lang="pl">pole
23 </xs:sequence> </xs:extension> </xs:complexcontent> </xs:complextype> <xs:element name="subject" type="xs:string"> xml:lang="pl">temat dokumentu</xs:documentation> xml:lang="en">subject of document</xs:documentation> </xs:schema>
Archivio Sp. z o.o. Schema XSD opisująca typy dokumentów obsługiwane w Systemie Invo24
Archivio Sp. z o.o. Schema XSD opisująca typy dokumentów obsługiwane w Systemie Invo24 Wersja 1.0 Archivio Sp. z o.o. Strona 1
COM_2006_023_02.xsd <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" elementformdefault="qualified">
+ <xs:element name="productsubtype" type="xs:string" minoccurs="0"/>
otcd.ntf.001.01.auctiondetail.. otcd.ntf.001.01.auctionresult - + otcd.ntf.001.01.automaticterminationsummary
Service Description: NIH GovTrip - NBS Web Service
8 July 2010 Page 1 Service Description: NIH GovTrip - NBS Web Service Version # Change Description Owner 1.0 Initial Version Jerry Zhou 1.1 Added ISC Logo and Schema Section Ian Sebright 8 July 2010 Page
<!--=========================================--> <!--=========================================-->
User manual for e-line DNB: the XML import file. User manual for e-line DNB: the XML import file
User manual for e-line DNB: the XML import file version 1.2 dated 19 February 2015 1 1. Contents 1. Contents... 2 2. e-line DNB... 3 2.1 Submitting your reports to De Nederlandsche Bank... 3 2.3 Entering
Security for industrial automation and control systems: Patch compatibility information
Security for industrial automation and control systems: Patch compatibility information A Progress Report for Review and Comment From ISA99 Work Group 6 (Patch Management) The material in this report has
Advanced PDF workflows with ColdFusion
Advanced PDF workflows with ColdFusion and LiveCycle Outline About PDF Generating PDF from ColdFusion Working with PDF forms in ColdFusion Workflows with XFA forms Designing XFA forms with LC Designer
Gplus Adapter 8.0. for Siebel CRM. Developer s Guide
Gplus Adapter 8.0 for Siebel CRM Developer s Guide The information contained herein is proprietary and confidential and cannot be disclosed or duplicated without the prior written consent of Genesys Telecommunications
Agency to System Infrastructure Provider Interface Specification
Agency to System Infrastructure Provider Interface Specification Version 1.0.0 November 8, 2006 FINAL Document History Status Release Date Comment Audience Draft 0.1.0 08/31/06 Posted for public review
DMP ESB Stanlab Interface vejledning i anvendelse.
DMP ESB Stanlab Interface vejledning i anvendelse. Dette interface anvendes til enten at kalde PULS eller JUPITER stanlab Interfaces. Via interface kaldes enten PULS eller JUPITER. Som styrekode anvendes
PEPPOL Deliverable D1.1 Requirements for Use of Signatures in Public Procurement Processes Part 5: XKMS v2 Interface Specification
PEPPOL Deliverable D1.1 Requirements for Use of Signatures in Public Procurement Processes Part 5: XKMS v2 Interface Specification Profiling and Extensions Specification Version 1.2 PEPPOL WP1 2009-04-30
An Empirical Study on XML Schema Idiosyncrasies in Big Data Processing
An Empirical Study on XML Schema Idiosyncrasies in Big Data Processing Dmitry Vasilenko, Mahesh Kurapati Business Analytics, IBM, Chicago, USA {dvasilen, mkurapati}@us.ibm.com Abstract The design and maintenance
[MS-FSDAP]: Forms Services Design and Activation Web Service Protocol
![[MS-FSDAP]: Forms Services Design and Activation Web Service Protocol](/thumbs/26/7786145.jpg "[MS-FSDAP]: Forms Services Design and Activation Web Service Protocol")
[MS-FSDAP]: Forms Services Design and Activation Web Service Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications
DocuSign Connect Guide
Information Guide 1 DocuSign Connect Guide 2 Copyright 2003-2014 DocuSign, Inc. All rights reserved. For information about DocuSign trademarks, copyrights and patents refer to the DocuSign Intellectual
DATE DOCUMENT CONTACT MAIL PHONE. 9th February 2015 Appendix 3A1 Peter Holst HerzbergPeter Holst Herzberg [email protected]
DATE DOCUMENT CONTACT MAIL PHONE 9th February 2015 Appendix 3A1 Peter Holst HerzbergPeter Holst Herzberg [email protected] NEW TRAFFIC MAP APPENDIX 3A1: INTERFACES TO OTHER IT-SYSTEMS - DOCUMENTATION Niels Juels
Appendix 1 Technical Requirements
1 av 13 Appendix 1 Technical Requirements Version 2.4.7 Technical requirements for membership in the Skolfederation The Skolfederation has, like many other federation initiatives, the goal to use the following
Authentication Context for the OASIS Security Assertion Markup Language (SAML) V2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 Authentication Context for the OASIS Security Assertion Markup Language (SAML)
EFSOC Framework Overview and Infrastructure Services
EFSOC Framework Overview and Infrastructure Services Infolab Technical Report Series INFOLAB-TR-13 Kees Leune Id: infraserv.tex,v 1.12 2003/10/23 10:36:08 kees Exp 1 Contents 1 Introduction 4 1.1 Notational
keyon Luna SA Monitor Service Administration Guide 1 P a g e Version Autor Date Comment
Luna SA Monitor Service Administration Guide Version Autor Date Comment 1.1 Thomas Stucky 25. July 2013 Update installation instructions. 1 P a g e Table of Contents 1 Overview... 3 1.1 What is the keyon
Modernize your NonStop COBOL Applications with XML Thunder September 29, 2009 Mike Bonham, TIC Software John Russell, Canam Software
Modernize your NonStop COBOL Applications with XML Thunder September 29, 2009 Mike Bonham, TIC Software John Russell, Canam Software Agenda XML Overview XML Thunder overview Case Studies Q & A XML Standard
Argos Web Service Interface Specification
ARGOS Reference: Nomenclature: CLS-DT-NT-10-165 ARG-IF-22-1427-CLS Issue: 1. 4 Date: Mar. 19, 13 CLS-DT-NT-10-165 ARG-IF-22-1427-CLS V 1.4 Mar. 19, 13 i.1 Chronology Issues: Issue: Date: Reason for change:
The New System of Accounts Message structure: Cash settlement balances derivatives (demt.smc.001.01)
The New System of Accounts Message structure: Cash settlement balances derivatives (demt.smc.001.01) Document date: 01.02.2007 : This message includes a statement of financial liabilities and receivables
CAS Protocol 3.0 specification
CAS Protocol 3.0 specification Contents CAS Protocol 3.0 Specification 5 Authors, Version 5 1. Introduction 5 1.1. Conventions & Definitions.................... 5 1.2 Reference Implementation....................
Modello dati regionale d interscambio del Piano Strutturale Comunale (PSC) Allegato A Formato GML-XML
Modello dati regionale d interscambio del Piano Strutturale Comunale (PSC) Allegato A Formato GML-XML In attuazione della deliberazione del Consiglio Regionale 28 maggio 2003, n. 484 "Atto di indirizzo
Schema Developer s Guide
E-Filing Page 1 of 104 INTRODUCTION...3 OVERVIEW OF E-FILING PROCESS...4 DETAILS OF THE DATA CONNECTIVITY TEST...4 INTERMEDIARY CLIENT APPLICATION TO PREPARE THE RETURNS IN XML FORMAT...4 WHY XML SCHEMA...7
Tecnologie per XML. Sara Comai Politecnico di Milano. Tecnologie legate a XML
Tecnologie per XML Sara Comai Politecnico di Milano Tecnologie legate a XML DTD XHTML: riformulazione di HTML in XML Namespaces CSS: style sheets per visualizzare documenti XML XSD: XML schema XLink: linguaggio
[MS-DVRD]: Device Registration Discovery Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
![[MS-DVRD]: Device Registration Discovery Protocol. Intellectual Property Rights Notice for Open Specifications Documentation](/thumbs/27/12044814.jpg "[MS-DVRD]: Device Registration Discovery Protocol. Intellectual Property Rights Notice for Open Specifications Documentation")
[MS-DVRD]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
[MS-QoE]: Quality of Experience Monitoring Server Protocol Specification
![[MS-QoE]: Quality of Experience Monitoring Server Protocol Specification](/thumbs/24/3479626.jpg "[MS-QoE]: Quality of Experience Monitoring Server Protocol Specification")
[MS-QoE]: Quality of Experience Monitoring Server Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications
XML and Tools. Muhammad Khalid Sohail Khan Mat #: 745783 University of Duisburg Essen Germany
XML and Tools Muhammad Khalid Sohail Khan Mat #: 745783 University of Duisburg Essen Germany 1 Tables of Contents 1 Main Topics... 2 1.1 What is XML?... 3 1.2 XML Syntax... 3 1.3 Namespace... 5 2 XML Schema...
The Direct Project. Implementation Guide for Direct Project Trust Bundle Distribution. Version 1.0 14 March 2013
The Direct Project Implementation Guide for Direct Project Trust Bundle Distribution Version 1.0 14 March 2013 Version 1.0, 14 March 2013 Page 1 of 14 Contents Change Control... 3 Status of this Guide...
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-EDCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
How To Write An Eplsi.Org (For Free) For A Free Download
TS 102 818 V1.5.1 (2013-08) Technical Specification Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM); XML Specification for Electronic Programme Guide (EPG) European Broadcasting Union Union
DRAFT. Standard Definition. Extensible Event Stream. Christian W. Günther Fluxicon Process Laboratories [email protected]
Extensible Event Stream Standard Definition Christian W. Günther Fluxicon Process Laboratories [email protected] XES Version: 1.0 Revision: 1 November 25, 2009 DRAFT Introduction Event logs, as they
3GPP TS 24.239 v9.0.0 (2009-12)
TS 24.239 v9.0.0 (2009-12) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Flexible Alerting (FA) using IP Multimedia (IM) Core Network
ETSI TS 102 818 V1.4.1 (2008-06) Technical Specification
TS 102 818 V1.4.1 (2008-06) Technical Specification Digital Audio Broadcasting (DAB); Digital Radio Mondial (DRM); XML Specification for Electronic Programme Guide (EPG) European Broadcasting Union Union
Best Practices for Designing and Building the Services of an SOA
Best Practices for Designing and Building the Services of an SOA Guido Schmutz Technology Manager, Oracle ACE Director for FMW & SOA Trivadis AG, Switzerland Abstract This session will present best practices
Session Initiation Protocol (SIP) Registration Extensions
[MS-SIPREGE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
Chapter 4. Sharing Data through Web Services
Chapter 4. Sharing Data through Web Services Data sharing would seem to be a simple task. Agencies have been making their data publicly available through the Internet since the 1980s. The World Wide Web
Domain-Specific Development
1 Domain-Specific Development Introduction This book describes the Microsoft Domain-Specific Language Tools (the DSL Tools). The DSL Tools are part of the Visual Studio SDK, and may be downloaded from
[MS-QoE]: Quality of Experience Monitoring Server Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
![[MS-QoE]: Quality of Experience Monitoring Server Protocol. Intellectual Property Rights Notice for Open Specifications Documentation](/thumbs/24/3480316.jpg "[MS-QoE]: Quality of Experience Monitoring Server Protocol. Intellectual Property Rights Notice for Open Specifications Documentation")
[MS-QoE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
Data Integration Hub for a Hybrid Paper Search
Data Integration Hub for a Hybrid Paper Search Jungkee Kim 1,2, Geoffrey Fox 2, and Seong-Joon Yoo 3 1 Department of Computer Science, Florida State University, Tallahassee FL 32306, U.S.A., [email protected],
Integration of an XML electronic dictionary with linguistic tools for natural language processing
Information Processing and Management xxx (2006) xxx xxx www.elsevier.com/locate/infoproman Integration of an XML electronic dictionary with linguistic tools for natural language processing Octavio Santana
Oracle Java CAPS Message Library for EDIFACT User's Guide
Oracle Java CAPS Message Library for EDIFACT User's Guide Part No: 821 2607 March 2011 Copyright 2008, 2011, Oracle and/or its affiliates. All rights reserved. License Restrictions Warranty/Consequential
YAZ proxy User s Guide and Reference. YAZ proxy User s Guide and Reference
YAZ proxy User s Guide and Reference i YAZ proxy User s Guide and Reference Copyright 1998-2015 Index Data Aps YAZ proxy User s Guide and Reference iii COLLABORATORS TITLE : YAZ proxy User s Guide and
D4.1.2 Cloud-based Data Storage (Prototype II)
< ADVENTURE WP 4 D4.1.2 Cloud-based Data Storage (Prototype II) D4.1.2 Cloud-based Data Storage (Prototype II) Authors: ASC, TUDA Delivery Date: 2013-10-01 Due Date: 2013-08-31 Dissemination Level: PU
ASPIRE Programmable Language and Engine
ASPIRE Programmable Language and Engine Athens Information Technology Agenda ASPIRE Programmable Language (APDL) ASPIRE Programmable Engine (APE) 2 ASPIRE Programmable Language ASPIRE Programmable Language
XEP-0337: Event Logging over XMPP
XEP-0337: Event Logging over XMPP Peter Waher mailto:[email protected] xmpp:[email protected] http://www.linkedin.com/in/peterwaher 2015-11-09 Version 0.2 Status Type Short Name Experimental
General Information. Standards MX. Standards
Standards Standards MX General Information This document describes the SWIFT Standards MX messages (MXs) and explains the concept of XML for MX messages and the structure and function of these messages.
Liberty ID-WSF Authentication, Single Sign-On, and Identity Mapping Services Specification
: Version: v2.0 Liberty ID-WSF Authentication, Single Sign-On, and Identity Mapping Services Specification Version: v2.0 Editors: Jeff Hodges, NeuStar, Inc. Robert Aarts, Hewlett-Packard Paul Madsen, NTT
Junos Pulse Secure Access Service. DMI Solutions Guide. Release 7.1. Published: 2011-01-31
Junos Pulse Secure Access Service DMI Solutions Guide Release 7.1 Published: 2011-01-31 Juniper Networks, Inc. 1194 North Mathilda Av enue Sunny v ale, Calif ornia 94089 408-745-2000 www.juniper.net Juniper
XIII. Service Oriented Computing. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
XIII. Service Oriented Computing Laurea Triennale in Informatica Corso di Outline Enterprise Application Integration (EAI) and B2B applications Service Oriented Architecture Web Services WS technologies
Advanced Information Management
Anwendersoftware a Advanced Information Management Chapter 1: Introduction Holger Schwarz Universität Stuttgart Sommersemester 2009 Overview Basics Terms Database Management Systems Database Design Query
XML. Document Type Definitions XML Schema
XML Document Type Definitions XML Schema 1 Well-Formed and Valid XML Well-Formed XML allows you to invent your own tags. Valid XML conforms to a certain DTD. 2 Well-Formed XML Start the document with a
Web Services Metadata Exchange (WS- MetadataExchange)
Web Services Metadata Exchange (WS- MetadataExchange) September 2004 Authors Keith Ballinger, Microsoft Don Box, Microsoft Francisco Curbera (Editor), IBM Srinivas Davanum, Computer Associates Don Ferguson,
CA ERwin Data Modeler
CA ERwin Data Modeler Creating Custom Mart Reports Using Crystal Reports Release 9.6.0 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred
Secure Password-Based Authenticated Key Exchange. for Web Services
Secure Password-Based Authenticated Key Exchange for Web Services Liang Fang 1,2, Samuel Meder 4, Olivier Chevassut 3, and Frank Siebenlist 1 Abstract. This paper discusses an implementation of an authenticated
Model-driven Rule-based Mediation in XML Data Exchange
Model-driven Rule-based Mediation in XML Data Exchange Yongxin Liao, Dumitru Roman, Arne J. Berre SINTEF ICT, Oslo, Norway October 5, 2010 ICT 1 Outline Intro to XML Data Exchange FloraMap: Flora2-based
MedBiquitous Web Services Design Guidelines
MedBiquitous Web Services Design Guidelines Version 2.0 13 May 2009 MedBiquitous Technical Steering Committee Revision History Date Version Description Author 17 Dec 2003 0.9 Draft for Technical Steering
BACHELOR S THESIS. Roman Betík XML Data Visualization
Charles University in Prague Faculty of Mathematics and Physics BACHELOR S THESIS Roman Betík XML Data Visualization Department of Software Engineering Supervisor: RNDr. Irena Mlýnková, Ph.D. Study program:
Call Center Solution Guide
Call Center Solution Guide Technical Solution Guide Document Version 1 220 Perry Parkway Gaithersburg, MD USA 20877 Tel +1 301.977.9440 Fax +1 301.977.8846 WWW.BROADSOFT.COM BroadWorks Guide Copyright
Extraction of standardized archetyped data from Electronic Health Record Systems based on the Entity- Attribute-Value Model
Extraction of standardized archetyped data from Electronic Health Record Systems based on the Entity- Attribute-Value Model Georg Duftschmid, Thomas Wrba, Christoph Rinner Center for Medical Statistics,
FUSE ESB. Getting Started with FUSE ESB. Version 4.1 April 2009
FUSE ESB Getting Started with FUSE ESB Version 4.1 April 2009 Getting Started with FUSE ESB Version 4.1 Publication date 22 Jul 2009 Copyright 2001-2009 Progress Software Corporation and/or its subsidiaries
Integrating CRM into IBM WebSphere Portal with Digital Data Connector
Introduction 1 Integrating CRM into IBM WebSphere Portal with Digital Data Connector Table of Contents Introduction... 2 The Sample solution... 3 Components... 3 IBM WebSphere Portal including IBM Web
DESIGNING XML PIVOT MODELS FOR MASTER DATA INTEGRATION VIA UML PROFILE
DESIGNING XML PIVOT MODELS FOR MASTER DATA INTEGRATION VIA UML PROFILE Ludovic Menet, Myriam Lamolle Laboratoire d INformatique et Communication (LINC) IUT de Montreuil, Université Paris8 140 rue de la
WTP-101 Developing Web Applications with Standards. using W3C org standard technologies such as, HTML, CSS, XML, XSD and XSL
WTP-101 Developing Web Applications with Standards using W3C org standard technologies such as, HTML, CSS, XML, XSD and XSL Attributions World Wide Web Consortium http://www.w3c.org Sandra Clark CSS for
APolicy Framework for Collaborative WebService Customization
APolicy Framework for Collaborative Web Haiqi Liang, Wei Sun, Xin Zhang, Zhongbo Jiang IBM China Research Lab {lianghq; weisun; zxin; jiangzb}@cn.ibm.com Abstract: A web service usually serves many consumers,
. g .,, . . , Applicability of Can I Make XML Go Faster?
Can I Make XML Go Faster? Presented to: Presented by: John Jay King King Training Resources [email protected] Download this paper from: Objectives Understand XML document processing Understand how
Preface... iv I. Introduction... 1 1. What is Spring Web Services?... 2 1.1. Introduction... 2 1.2. Runtime environment... 2 2.
Copyright 2005-2007 Preface... iv I. Introduction... 1 1. What is Spring Web Services?... 2 1.1. Introduction... 2 1.2. Runtime environment... 2 2. Why Contract First?... 4 2.1. Introduction... 4 2.2.
Balisage: The Markup Conference
Balisage: The Markup Conference Secure Publishing using Schema-level Role-based Access Control Policies for Fragments of XML Documents Tomasz Müldner Professor Jodrey School of Computer Science, Acadia
MASTER DATA INTEGRATION
MASTER DATA INTEGRATION Managing product data exchange in an electronic commerce environment Aleksander Śmierciak Bachelor's Thesis May 2013 Degree Programme in Software Engineering Technology, Communication
Web-Programmierung (WPR)
Web-Programmierung (WPR) Vorlesung X. Web Services Teil 2 mailto:[email protected] 1 21 Web Service World Wide Web seit Anfang 1990er Jahren Mensch Web-Browser Applikation HTTP XML over HTTP Web-Server Geschäftslogik
Attacking Web Services
Attacking Web Services The Next Generation of Vulnerable Enterprise Applications Alex Stamos [email protected] cansecwest/core06 Information Security Partners, LLC isecpartners.com Talk Agenda Introduction
Bridging the Browser and the Server
Bridging the Browser and the Server Miguel Raposo and José Delgado, Instituto Superior Técnico, Universidade Técnica de Lisboa, Av. Prof. Cavaco Silva, Porto Salvo, Portugal [email protected],
How To Run The Envirment Performance Agent On A Pc Or Mac Or Mac (For Linux)
CA Applicati Performance Management Envirment Performance Agent Implementati Guide Release 9.6 This Documentati, which includes embedded help systems and electrically distributed materials, (hereinafter
RECIP-E INTEGRATION SPECIFICATION DRAFT
RECIP-E INTEGRATION SPECIFICATION DRAFT DOCUMENT CONTROL Document revision history Version Date Author Comments 0.1 01/06/2010 Thibaut Henry Draft 1.0 21/06/2010 Thibaut Henry Version for review 1.1 30/06/2010
RECIP-E INTEGRATION SPECIFICATION DRAFT
RECIP-E INTEGRATION SPECIFICATION DRAFT DOCUMENT CONTROL Document revision history Version Date Author Comments 0.1 01/06/2010 Thibaut Henry Draft 1.0 21/06/2010 Thibaut Henry Version for review 1.1 30/06/2010
XML in programming. Patryk Czarnik. XML and Modern Techniques of Content Management 2012/13
XML in programming Patryk Czarnik Institute of Informatics University of Warsaw XML and Modern Techniques of Content Management 2012/13 Introduction XML in programming XML in programming what for? To
CERTIFICATION POLICY OF KIR for TRUSTED NON-QUALIFIED CERTIFICATES
Krajowa Izba Rozliczeniowa S.A. CERTIFICATION POLICY OF KIR for TRUSTED NON-QUALIFIED CERTIFICATES Version 1.5 Document history Version Number Status Date of Issue 1.0 Document approved by the Management