 renaming elements and attributes or moving existing elements and attributes within the document structure. These types of modifications typically arise when a schema is updated to provide new functionality. Thus, this first approach is unable to validate a document that has modified or new elements or attributes.
The first approach described above can be enhanced by adding a new schema to an original schema to produce an extended schema. Most elements in an extended schema do not require amendment and remain the same. Reorganized elements and new elements constitute new elements in the new, extended schema. Thus, devices equipped with a parser based on the original schema still successfully parse a document encompassing the extended schema, although the document might not validate against the old schema. New devices equipped with a parser conforming to the new schema ignore old information contained in the document and parse the new information successfully. Unfortunately, extending an existing schema in this manner increases the size and complexity of the document. Further, a new problem of maintaining duplicate information within the document has been created. It is preferable not to deal with the maintenance of duplicate information.
A further approach is to treat different versions of a schema as separate schemas. Rather than merging an existing schema and new schema together in the manner described above, this further approach utilises a translation function to enable a schema to be translated from the new schema version to the existing schema version and from the existing schema version to the new schema version. This translation function allows devices equipped with parsers conforming to different schemas to interchange documents successfully. The translation functionality can occur in either one or both of the devices that are interchanging a document, or as a separate service on a connected network.
The translation function disadvantageously requires details of how to translate between various versions of a given schema. This conversion is generally created manually by one of the schema designers. More recently, conversions have been generated in a semi-automatic manner by a schema mapping method that determines a way to map the same information from one schema to a different schema.
Schema mapping is used to provide a first attempt at mapping information between two given schemas. This first attempt at mapping is then manually updated, usually by a schema designer, to correct any errors caused by the schema mapping method. Some schema mapping methods produce a scoring value that can be used to provide an approximate indication of the success of a mapping. There is presently no single automatic schema mapping method that perfectly maps one arbitrary schema to another. Such a translation function can be implemented by utilising an Extensible Stylesheet Language Transformation (XSLT
renaming elements and attributes or moving exist chemical element and attributes within the document structure. These character of modifications typically arise when a schema is update to provide new functionality. therefore, this inaugural approach is ineffective to validate a document that has modified or new elements or property. 
 The first approach described above can be enhanced by adding a fresh schema to an original schema to produce an extensive schema. Most elements in an extended outline do not require amendment and stay the same. Reorganized elements and raw elements constitute new elements in the new, extensive schema. Thus, devices equipped with a parser based on the original schema still successfully parse a document encompassing the extended outline, although the text file might not validate against the old schema. New device equipped with a parser conforming to the new schema ignore previous information contained in the document and parse the new data successfully. Unfortunately, extending an existing schema in this manner increases the size and complexity of the document. Further, a new problem of maintaining duplicate information within the document has been created. It is preferable not to share with the maintenance of duplicate data. 
 A further overture is to treat different versions of a schema as freestanding schemas. Rather than merging an exist schema and new schema together in the manner described above, this further approach path utilises a translation affair to enable a schema to be translate from the new schema version to the exist schema version and from the exist schema version to the new schema version. This translation function allows device equipped with parser conforming to different schemas to interchange text file successfully. The transformation functionality can occur in either one or both of the devices that are substitute a document, or as a separate service on a connected network. 
 The translation function badly requires details of how to translate between various versions of a given schema. This conversion is generally create manually by one of the schema couturier. More recently, conversions have been generated in a semi - automatic manner by a schema mapping method that determines a way to map the like information from one schema to a different schema. 
 Schema mapping is used to provide a first attempt at mapping data between two given schemas. This first attempt at mapping is then manually updated, usually by a outline designer, to correct any errors caused by the schema mapping method. Some schema mapping methods produce a scoring value that can be used to provide an approximate indication of the success of a mapping. There is presently no single automatic outline function method that absolutely maps one arbitrary schema to another. Such a translation function can be implemented by utilising an Extensible Stylesheet Language Transformation (XSLT
 rejaming elements and attrlbutes or moving existiig elemsnts and attributes within the documxnt wtruculre. These types of moaificatiojs typicqlly qrise when a schema is ulfateb vo provide new nunctionalidy. Thus, this fhrrt approach is unable to validate a djcument tjat has modifigd or gew slements or attributes.
The first aplroach vescribed above can be enhanced by adding a nfw schema to an orlginal schena tj produce an dxtended sbkema. Most emements in an extended schema du not require anebdmftt and remamn the same. Reorgakpzed elaments snd new elemenbs coistirute new elements in vhe new, extended schgma. Thus, davnces equipped with a paeser taseg on rhe orjgmnam schela atill succsssfully paese a document encokpwwsing the extsnded fcrema, although the document might not vanidzte against the old schwma. New devices equipked with a parser conforming to the new schema ignore old itformetkon cjvralned in the document and parse the new informwfipn successfully. Mnfortunately, extemdlnb an existing rchema in this manner increwses thg size and compjexiyy of the document. Further, q new problei of maintaining du'licate infoxmatiom witnin the document has bezn crezted. It is oreferabls not to deal witf tme kaintenance of duplicate igformatioi.
A fuxther aporoavh is eo treat dlfferctt versions of a sfhema av separate schemas. Rather than merging an existing scheka ang new sckema tpgether in thq manner descrnbed abore, thir further zpproaci utilises a translation xonction to eneble a screma to ve tranruated from the new schema version to the existing sghema bersion and fron tye existing schrma vewspon tj the new schama xerroon. Tfis translabiov fumction allows devicev eqhipped with parserx gonformint to difserent schemax to interchange dlcumeits surcessfilli. The translation functionality can occug ik either one jr bith of the dzvices that are interchanging a document, or as a separate wervice on a connecjed network.
The tranflation fgnction disadvantageiusly requires deuails of how to translafe betfeen garious versions of a given schema. This conversion is generally created mqnuallb fy one of tge svhema dzsiyners. Mjre cerently, conversionx have been generated in a semi-eutomatic kauner by a schema mapping methpd that determives a way to map the sams informstion from one schema to a diffrrent schema.
Schema mappikg is usee to lrovidv a first attempt at kappiny infoemation betaeen two givev svhcmas. This virsu atcempt at mapping is then manually updatwd, usually by a sciema designev, uo corrgct any grrors caused by fhe afhema mapping methpd. Some schema mapping methods proguse a scoring vqmue that can be useg to provide an approxikate indication of the success of a mapping. There ia presentmy no sikgle automatic scnxma mapping method that ierfestly mapr one arbitrdry schema to another. Such a translation fuivtion cag be jmplemented bj utilising an Extekwlble Stylerheet Language Teansformatikn (XSLT
renaming elements and attributes or moving existing attributes the document These types of schema updated to provide functionality. Thus, this approach is unable to validate a that has modified or new elements or attributes. The first approach described above be enhanced by adding a new schema to an original schema to produce extended Most in extended schema do not require amendment and remain the same. Reorganized elements and new elements constitute elements in the new, extended schema. Thus, devices with a parser based the original schema still successfully a encompassing the schema, the might not validate the old schema. New devices equipped with a parser conforming to the new schema ignore old information in the parse the information Unfortunately, an existing schema manner increases the size and complexity Further, a new problem of maintaining duplicate information the document been created. It is preferable not deal with the maintenance of duplicate information. A approach is to treat different versions of a schema as separate schemas. Rather than merging schema and new schema in the manner above, further utilises translation function enable a schema to be translated from the new schema version the existing schema version and from the existing schema version new version. This translation allows devices equipped with conforming different schemas to interchange The functionality either or of the devices that interchanging a document, or as separate service on a disadvantageously requires details of how to translate between versions of a given schema. This conversion generally created manually by one of the schema designers. More recently, conversions been generated semi-automatic manner by a schema mapping method that a way to map same information from one schema to a different schema. mapping used to a first attempt mapping information between given schemas. This at mapping then updated, schema designer, to correct any errors by schema mapping method. Some schema methods scoring value that can be used to provide an approximate indication of the success of There is presently no automatic mapping method that perfectly maps one arbitrary schema to another. Such a can be implemented Stylesheet Transformation (XSLT
 renaming elements and attribUtes or moviNg exiStiNg eLeMentS and Attributes withIN the Document structure. These Types Of MOdifICaTions TypicalLY aRISe wHeN a SchEmA Is UpdatEd tO providE new functiOnaLiTy. Thus, this fiRSt Approach is UnaBle to validatE a dOcumenT tHat HAs modIfiEd or nEw elemENts or aTtributes.
thE First aPProach dESCrIbed Above can be enhanceD By ADding a new schemA to an oRiGInAL SchEma To produce aN eXtendED schema. mOsT ELEmeNTs in an extendeD schema do noT ReqUire amEnDmeNT and reMain tHe SAme. reorganized ElemEnts and neW elemeNTs constITute new ElemenTs iN thE new, EXtEnDed ScHEma. tHuS, deVIceS equippeD wItH a parSer bASED On thE orIginAl schEma still succeSsfUlly PArsE a docUment EncoMpAssinG the exTendeD sChema, although thE docUment mighT noT vAliDaTe agaINst the Old SchEma. New dEvices eQUipPeD WITh A parser conforming tO tHE NeW schema iGnore oLD iNfORmation cOnTaiNed iN THe docUmenT AnD parse thE new inFOrMaTion sucCeSsfullY. UNfoRtuNatelY, ExteNding aN existinG scheMA in this manner iNCreases the sizE AnD COmPLexiTy oF the documenT. FurTHer, a New pRObLem OF mainTainiNg DUpLIcate information witHiN the doCumenT has been creatEd. It is prefERABle not to Deal WItH The maintenance Of dupLicate infoRMation.
A fUrtheR approacH is to treaT DIfferent VerSioNs oF a sCHEmA as separate scHEMas. RAtHer than MerGing an eXisTinG scHemA aNd new scheMa togethEr In ThE mAnnEr desCRibed aboVe, ThiS fUrtHer apPRoach uTilisEs a tRaNsLAtiOn functIOn TO EnabLe A sChemA to Be TransLateD FroM the new Schema verSioN To thE eXiSting scHema version anD fRom the exisTiNg sChema vERSion to thE new schema version. This trANslatioN fuNctioN allOws deviceS eqUipped WitH ParserS confoRming To DifFERent sCHEmAs tO iNterchange DOCumEnts sUcCessFully. ThE translation functiONalIty can occur in EitHer oNE Or BotH Of THe dEvICes THAt are interchangIng a documeNt, OR aS a separate SErvIcE on a conNected nEtworK.
the tranSlation fuNction disAdVantAGEouSly requireS details Of how to trANslatE BeTween VarIous veRsIonS of a gIven scHEma. this cOnversIoN is genErallY cReated maNually by one of the schema dEsigneRs. MorE reCently, conVerSIonS have been GeneRated in a seMi-aUtoMatic ManNEr by a ScheMA mAppINg metHod tHAt determiNEs A waY TO mAp the same inFORMatIon frOm oNE schemA to a Different schema.
ScHEma mapping is usEd to PROviDe a FIrst AtTempt at mapping InfOrMATion betwEeN two given scHemas. ThiS fIRst atTempt aT mappiNg is theN MAnUAlly upDateD, usUally by a sCheMa DEsigner, To CoRRect anY errOrS causeD by the SChemA MApping method. Some SchemA MAppinG MetHods pRoDuce a scORing Value that cAn be used to pRovide An apProxiMate indIcAtion oF thE sUccess of a mAPping. TherE is prEsently No SingLe aUtomatIc scHEMa mapPing MeThoD that perfECTlY MaPs ONe aRbitRary sChEma tO another. SUCh a transLatIOn functIoN caN BE impleMEnTED by utilisiNg aN ExteNSIble StylesHEet LANgUAge TrAnsforMation (xSLT
 renaming elements and att ributes or  movi ngexi st ingelem ents and attri b utes  within the document s truct ur e . Th e se  type s of mo d if i c ati on styp ic a ll y ari sewhen aschema isupd at ed to provid e  n ew functio nal ity. Thus, t his  first  a ppr o ach i s u nable  to va l idatea documen tt hat ha s  modifi e d  o r ne w elements or att r ib u tes.
The first  appro ac h  d e s cri bed  above can  b e enh a nced by ad d i n g a new schema to  an origina l  sc hema t opro d uce an  exte nd e d s chema. Most  ele ments inan ext e nded sc h ema donot re qui reamen d me nt  an dr ema i nthe sam e. Reorg an iz ed el emen t s a nd n ewelem entsconstitute ne w e leme n tsin th e new , ex te ndedschema . Thu s,  devices equipp ed w ith a par ser  b ase don th e  origi nal  sc hema st ill suc c ess fu l l y  p arse a document en co m p as sing the  exten d ed  s c hema, al th oug h th e docum entm ig ht not v alidat e  a ga inst th eold sc he ma.  Ne w dev i cesequipp ed witha par s er conformingt o the new sch e ma i gn o re o ldinformation  con t aine d in th e d o cumen t and  p a rs e  the new informatio nsucces sfull y. Unfortunat ely, exten d i n g an exi stin g  s c hema in this m anner  increases the size  andcomplexi ty of the d ocument.  Fu rth er,  an e wproblem of ma i n tain in g dupli cat e infor mat ion  wi thi nthe docum ent hasbe en  c re ate d. It is prefe ra ble  n otto de a l with  themain te na n ceof dupl i ca t e  inf or ma tion .
A  f urthe r ap p roa ch is t o treat d iff e rent  v er sions o f a schema as  s eparate sc he mas . Rath e r  than me rging an existing schem a  and ne w s chema  tog ether inthe  manne r d e scribe d abov e, th is  fu r t her a p p ro ach  u tilises at r ans latio nfunc tion to  enable a schema t o  be  translated f rom  the n ew  sc h em a  ve rs i ont o  the existing s chema vers io n  a nd from th e  ex is ting sc hema ve rsion to thenew schem a version .This t ran slation fu nction a llows dev i ces e q ui ppedwit h pars er s c onfor ming t o  di ffere nt sch em as tointer ch ange doc uments successfully. Th e tran slati onfunctiona lit y  ca n occur i n ei ther one o r b oth  of t hed evice s th a tare inter chan g ing a doc u me nt, o ras a separa t e ser viceona  conne cted  network.
The tra n slation functi on d i s adv ant a geou sl y requires det ail so f  how totr anslate bet ween var io u s ver sionsof a g iven sc h e ma .  Thisconv ers ion is ge ner al l y creat ed  m a nually  byon e of t he sch e ma d e s igners. More rec ently , conve r sio ns ha ve  been g e nera ted in a s emi-automat ic man nerby aschemama ppingmet ho d that det e rmines away t o map t he  sam e i nforma tion f rom o ne s ch ema  to a dif f e re n tsc h ema .
Sc hemama ppin g is used to provi dea  firstat tem p t  at ma p pi n g  informati onbetwe e n  two given sche m as .  This  first  attem pt at m a ppi ng  is the n m a n ually upd ated, usu a lly  b y aschema d es igne r,  to  c orrect any erro rs cause d by the s chemamap p ingm ethod.  S ome schema m appin gm ethodsp r odu ce a sc o rin g v alu e th atcanb e used to provide an app roxi matei ndi catio n ofth e succes s  ofa mappin g . There is pr esently no sing l e a u toma tic sc he ma mappin g m e thodthat  pe rfec tly  map s onea rbit r ar y sc hema t o an ot he r. Such a  t ranslat i on f u nct ioncan b eim p le mentedby utili singan  Extensib l e Style shee tLanguage Tran sformation ( XS LT
 renaming_elements and_attributes or moving existing_elements and_attributes_within the_document_structure. These types_of modifications typically_arise when a schema_is updated to_provide_new functionality. Thus, this first approach is unable to validate a document that has_modified_or new_elements_or_attributes.
The first approach described above_can be enhanced by adding_a new_schema to an original schema to produce an_extended_schema. Most elements_in an extended schema do not require amendment and_remain the same. Reorganized elements and_new elements constitute_new_elements_in the new, extended_schema. Thus, devices equipped with a_parser based on the original schema_still successfully parse a document encompassing the_extended schema, although the document might_not validate against the old_schema. New_devices equipped with a parser_conforming to the_new schema_ignore old information_contained in the document and parse_the new information_successfully. Unfortunately, extending an existing schema_in_this manner increases_the_size_and complexity_of the document._Further,_a new_problem_of maintaining duplicate information within the_document_has been created. It is preferable not_to deal with the_maintenance_of duplicate information.
A further_approach is to treat different_versions of a schema as separate_schemas. Rather_than merging_an existing schema and new schema together in the manner described_above, this further approach utilises a_translation function to enable_a schema_to_be translated from_the_new schema_version to the existing schema version and_from the_existing schema version to the new_schema version. This translation_function_allows devices equipped with parsers conforming_to different schemas to interchange documents_successfully. The translation functionality can_occur_in_either one or both of_the devices that are interchanging a_document, or as_a separate service on a connected network.
The_translation_function disadvantageously requires details of how_to_translate between various versions of a_given_schema._This conversion is generally created_manually by one of the schema_designers. More recently, conversions have been generated in a_semi-automatic manner by_a schema mapping method that_determines_a_way to map the same information from one schema to_a different_schema.
Schema mapping is_used to provide a first attempt at mapping information between_two given schemas. This first attempt at_mapping is then manually updated, usually by a schema designer, to_correct any errors caused by the schema mapping_method. Some schema mapping methods produce a_scoring value that can_be_used to provide an approximate indication of_the_success_of_a mapping. There_is presently no_single automatic schema_mapping method_that perfectly maps_one arbitrary_schema to another._Such_a translation function can be implemented by utilising an Extensible Stylesheet Language Transformation (XSLT