www.archive-net-2013.com » NET » X » XMLOPERATOR

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 23 . Archive date: 2013-02.

  • Title: xmloperator : an XML editor
    Descriptive info: .. English.. |.. Français.. xmloperator.. : an XML editor.. News.. Description.. Links.. Contact.. Download.. History.. User guide.. Sub-projects :.. InstanceToSchema.. JavaSkeleton.. LambdaAPI.. LambdaAPI2.. ReactiveMachine.. 2012-01-04.. release 2.. 1.. xmloperator is an XML editor, suitable for editing data oriented documents.. The software is.. open source.. , Java written, released under a BSD-style.. license.. It requires J2SE 1.. 4 and uses Xerces-J and Xalan-J from the Apache Software Fondation.. xmloperator displays a tree view of the nodes of the document.. When you select one node of the document, it appears in a detailed view, adjacent to the tree view.. You can open several instances of the tool in order to work simultaneously on several documents.. Features.. Any  ...   services.. Document transformations using either a.. transformer.. or an XSLT stylesheet (the XSLT engine and the XPath evaluator are provided by Xalan-J).. Documents comparison without taking into account the ordering of elements.. Specifications.. http://www.. w3c.. org/.. : Word Wide Web Consortium (XML, XHTML, XPATH, XSLT,.. ).. relaxng.. : RELAX NG.. Software.. apache.. : Apache Software Fondation (Xerces, Xalan, Ant,.. garshol.. priv.. no/download/xmltools/.. : an invaluable repertory of free XML tools.. org/#software.. : RELAX NG related tools.. http://dmoz.. org/Computers/Data_Formats/Markup_Languages/XML/Tools/.. : a usefull entry point.. For more information, please send a mail to "info" at "xmloperator.. net" using a subject starting with "[xmloperator]".. Project's Individual(s) : Didier Demany.. Last update : 2012-01-04.. Copyright (c) 2000 - 2012 The_xmloperator_project..

    Original link path: /
    Open archive

  • Title: xmloperator : un éditeur XML
    Descriptive info: : un éditeur XML.. Nouveautés.. Liens.. Sous-projets :.. version 2.. xmloperator est un éditeur XML, adapté à l'édition de document portant essentiellement des données.. Le logiciel est au.. source ouvert.. , écrit en Java, fournit sous.. licence.. de type BSD.. Il nécessite J2SE 1.. 4 et utilise Xerces-J et Xalan-J de l'Apache Software Fondation.. xmloperator présente une vue arborescente des noeuds du document.. Quand on sélectionne un des noeuds du document, il apparaît en détail dans une vue adjacente à la première.. Il est possible d'ouvrir plusieurs instances de l'outil pour travailler simultanément sur plusieurs documents.. Caractéristiques.. N'importe quel schéma RELAX NG ou DTD peut être utilisé pour  ...   de l'édition de façon à ne rien perdre en cas de défaillance du système.. Capacité à éditer des documents de grande taille.. Services annexes.. Transformations sur documents, utilisant soit un.. transformateur.. soit une feuille de style XSLT (le moteur XSLT et l'évaluateur XPath sont fournis par Xalan-J).. Comparaison de documents sans tenir compte de l'ordre des éléments.. Spécifications.. org.. Logiciels.. : un précieux inventaire d'outils XML gratuits.. : outils relatifs à RELAX NG.. : un utile point d'entrée.. Pour plus d'information, veuillez envoyer un mèl à "info" à "xmloperator.. net" avec "[xmloperator]" en début de sujet.. Individu(s) attaché(s) au projet : Didier Demany.. Dernière mise à jour : 2012-01-04..

    Original link path: /index_fr.html
    Open archive

  • Title: xmloperator download
    Descriptive info: Home.. xmloperator download.. Releases.. Installation and running.. G for "Generation", R for "Revision", C for "Correction".. See in.. history.. section what is changed in each release.. G.. R.. C.. Date.. Third-party.. Executable.. Source.. 3.. 0.. 2003-11-06.. xx_0306.. zip.. (3035Kb).. xmloperator_3_0_0.. (867Kb).. xmloperator_3_0_0_src.. (1057Kb).. 2.. 2003-08-30.. xmloperator_2_3_0.. (826Kb).. xmloperator_2_3_0_src.. (979Kb).. 1.. 2003-02-22.. xx_2_2_1.. zip (1738Kb).. xmloperator_2_2_1.. zip (1070Kb).. xmloperator_2_2_0_src.. zip (921Kb).. 2002-12-04.. xmloperator_2_1_1.. zip (1024Kb).. xmloperator_2_1_1_src.. zip (907Kb).. 2002-09-22.. xx_2_0_1.. zip (1474Kb).. xmloperator_2_0_0.. zip (922Kb).. xmloperator_2_0_0_src.. zip (895Kb).. 11.. 2002-03-17.. xmloperator_1_11_1.. zip (854Kb).. xmloperator_1_11_1_src.. zip (785Kb).. 10.. xx_1_4_0.. zip (1451Kb).. xmloperator_1_10_2.. zip (834Kb).. xmloperator_1_10_2_src.. zip (761Kb).. 9.. 2001-12-20.. xmloperator_1_9_0.. zip (826Kb).. xmloperator_1_9_0_src.. zip (764Kb).. 8.. 2001-09-12.. xmloperator_1_8_1.. zip (748Kb).. xmloperator_1_8_1_src.. zip (677Kb).. 7.. 2001-07-04.. xmloperator_1_7_0.. zip (2147Kb).. xmloperator_1_7_0_src.. zip (600Kb).. 6.. 2001-05-31.. xmloperator_1_6_1.. zip (1775Kb).. xmloperator_1_6_1_src.. zip (585Kb).. 5.. 2001-04-23.. xmloperator_1_5_0.. zip (1117Kb).. xmloperator_1_5_0_src.. zip (539Kb).. 4.. 2001-03-26.. xmloperator_1_4_1.. zip (1087Kb).. xmloperator_1_4_1_src.. zip (510Kb).. 2001-02-22..  ...   Xerces-J 2.. 0.. xx_1_4_0 : Xerces-J 1.. Executable archive content.. jar.. : xmloperator Java classes archive.. bat.. : script for running on Windows.. sh.. : script for running on Unix.. doc/.. : HTML documentation.. data/.. : XML documents and DTDs.. relaxng/.. : RELAX NG schemas.. style/.. : style sheets.. integration/.. : examples of Java integration.. legal/.. : licences.. Download the run-time environment from.. J2SE 1.. and install it in accordance with the instructions provided.. Download an executable archive file and the relative third-party archive file.. Decompress the two archive files in a directory dedicated to the tool instance.. Run the tool from this installation directory :.. on Windows :.. on Unix :.. , using some environment variables to define.. The method.. main.. of the class.. org.. xmloperator.. Tool.. is executed.. A window titled.. is opening.. Last update : 2004-09-06.. Copyright (c) 2000 - 2004 The_xmloperator_project..

    Original link path: /download.htm
    Open archive
  •  

  • Title:
    Descriptive info: xmloperator history.. Release.. ,.. 6.. 7.. 8.. 9.. 10.. 11.. Release 3.. 0.. (2003-11).. This release has capability for editing large documents, which cannot stay entirely in memory space.. This capability is based on an intermediary document storage format, which has been called "BRXI/0" for "Binary format for Randomly accessed XML Infoset, variant zero".. This binary format has the following characteristics:.. Standalone.. No DOCTYPE.. Encoding UTF-16BE.. Each Node is streamed with its length in order to be easily skiped.. Namespace unaware.. As the tool is based on DOM, the release contains a BRXI DOM implementation.. This implementation is limited to just what the tool uses, which is about 80% of DOM level 1 and 10% of DOM level 2.. It is thread safe, as required by the GUI.. Release 2.. 3.. (2003-08).. Enhancements.. For each element name, the element labelling in the tree panel may be modified.. It may use attributes (as before) or element childs that contains only a text child.. One attribute or single element may be selected.. Indentation capability (but not for mixed content) has been reintroduced.. The document comparison algorithm has been improved.. The position and size of dialogs are made persistent during a tool session.. XML version 1.. 0 and 1.. 1 are supported (depending on Xerces for parsing).. At the source level, a better isolation has been made between operations and document view.. An Ant build file is provided with sources.. Bugs fixed.. The XPath evaluation wizzard didn't work with J2SE 1.. This is fixed.. The task cancel button didn't appear any more with J2SE 1.. A bug on refreshing some combo-box (attribute value enumeration, entity reference name) is fixed.. A bug in localizing an element at (line, row) is fixed.. A bug on the condition for an element to be inserted repeatdly, when using some RELAX NG schemas, is fixed.. Deprecation.. Tool dependencies and the "Depend" schema have been removed.. They are deprecated by using.. 2.. (2003-01).. Distribution error fixed.. The.. relaxng/xmloperator_2_2_*.. rng.. files were missing.. Thanks to.. John Dubery.. who has revealed the problem.. The document comparison design has been enhanced.. It is namespace aware and doesn't depend any more on the order of the elements.. New operation for replacing the selected nodes by the document fragment.. Support of the system clipboard additionaly to the document's fragments.. A content model view is created.. A long, character data, attribute can be selected in the attribute table in order to be edited in a text area that occupy the detail view.. On packing one text node whose a fragment is selected, only the selected fragment is packed.. The text is first splited at start and end of selection.. A namespace prefix pair list is proposed for adding xmlns:*** attributes on root element.. A missing prefix is represented by the namespace URI between parenthesis.. Importing nodes was not possible with RELAX NG and not the lazy mode.. A bug at guiding editing for an interleave content model is fixed.. 1.. (2002-12).. Fixes a null pointer exception at inserting a child element (regression).. Schemas relative enhancements.. RELAX NG "externalRef" and "include" elements are now supported.. Invalid attributes make the content not valid.. The bug on parsing a relax ng param element is fixed.. The bug on aggregating relax ng choice patterns is fixed.. Using a DTD, the attributes are added to the displayed content model.. Using a DTD, a missing required attribute makes the content not valid.. The last reference DTDs are migrated to RELAG NG.. The namespace URIs on xmloperator.. org are moved to xmloperator.. net in order to be dereferencable.. Document types and converters.. A document type info is no more required to specify the root element name.. Converters are replaced par Transformers using the TraX API.. A transformer from CSSXML 1.. 0 to CSS is provided as a demonstration of plain text production.. CSSXML is defined using a RELAX NG schema.. It supports only CSS 1.. One can define a transformation's group for executing as a batch.. Miscellaneous.. The "xml:base" attributes are taken into account for entity reference resolution.. At inserting an new element, a list of possible element names is now systematically proposed even if the content model allows to repeat the name of the selected element.. The bug of the blank detail view on J2SE 1.. 4 is fixed.. (2002-09).. This release offers some support for the.. RELAX NG.. schema language.. It has required a lot of work :.. new framework for providing equal support for DTDs and RELAX NG,.. RELAX NG syntax processing,.. full namespace support,.. empowered attributes managing,.. The tool has quite the same look.. Notable differences are the following:.. Only the actual attributes of an element are displayed, then there is no more "All attr.. " checkbox.. The element name combo-box in the detail view is replaced by a button.. The field under the element name button becomes an indicator for content (superficial) validity.. There is no more options file by document type.. Too complex, not enough usefull.. The user guide has been enhanced.. It uses a "what do you want to do" approach.. Format is XHTML.. The "doc" format has been abandoned.. James Clark.. and.. MURATA Makoto.. for their so well designed schema language !.. Release 1.. 11.. (2002-03).. Doctor Watson's bug fix.. This release is based on Xerces-J 2.. x and Xalan-J 2.. Enhances lazy mode :.. Set lazy mode automatically when selecting nodes whose siblings are not DTD conformant.. When seting normal mode (not lazy), adds as many siblings as necessary for making the selected nodes sequence DTD conformant.. Bug fix about valid insert.. Inserting an element.. b.. between the elements.. a.. c.. was proposed in case of an.. ((a|b),(b|c)).. content model.. When creating an element, the element name may be either selected in a list by the user either chosen automatically by the tool.. It depends on an option.. Displays content models by using tool tips on the element name combo-box and on a new read-only field named "content model".. Shows the options default values in the options dialog box.. Minor GUI enhancements.. 10.. (2002-01).. Bug fix : to select an entity reference node which has child element(s) but no sibling element caused a null pointer exception.. Randy Watson.. who has revealed the bug.. Historization bug fixed.. The third-party archives are packaged within a separated file.. Text searched and XPath expression evaluated are historized.. Tool options pathname can be specified in the command line.. As options, prefered directory paths can be specified for XML, XSL, DTD, options and operations files.. Empty value has been added to the value list of an implied enumeration attribute.. When an element is automatically inserted in a document in order to keep the document valid relatively to its DTD, the element  ...   supported encodings has been extended.. A DTD can be loaded.. If a document is loaded at this time then its DTD is overloaded else the loaded DTD is global for all tool instances.. When there is a global DTD, each local DTD is hided by the global DTD.. A checkbox, labelled "DTD kept" indicates the global DTD existence.. Setting this checkbox make global the current local DTD.. A new checkBox labelled "All attr.. " allows displaying only attributes whose value is not empty.. Some attributes that must be always shown can be specified by a display option.. An attribute which gets its default value will be not displayed, like an empty value attribute.. Additional menu items can be created and added to the Options menu.. Attached actions consist of launching processes by calling "exec" commands.. The tool can be launched using a document System Id as first parameter and, optionally, a DTD System Id as second parameter.. The document and the DTD will be loaded immediatly.. Text join operation reversibility.. Saving operation for setting values including double quotes.. Inserting a fragment including an internal forward reference.. 5.. (2001-04).. Another document comparison algorithm is proposed.. It is more efficient in time than the old one but cannot resolve some cases that the old one can.. A comparison option specify which one to use (the new one by default).. The old one works.. by element name.. The new one works.. from leaves.. Associated documents can be merged to a new document.. The documents must have the same type.. The first attribute names used for labeling elements within the document tree view can be specified.. The option.. FirstAttributeNames.. of the.. display label.. category is responsible of that.. Element interval with the same name can be reordered (ascending or descending) according to the value of the first attributes names which are defined above.. File menu is splited to File menu and Document menu.. Edit menu is splited to Edit menu and Move menu.. 4.. (2001-03).. This release fixes a bug in documents comparison.. Comparison of two documents.. is proposed.. Each document must be opened within a tool instance.. Document comparison consist in creating associations between the mappings elements.. Document tree display enhances comparison in this way : exactly mapping elements are displayed using normal font, approximative mapping elements are displayed using italic font, elements with no mapping are displayed using bold font.. Distant move can be executed in two steps.. The first step consists in selecting nodes to be moved.. The second step consists in executing the move before, after or as childs of a selected node.. Between the two steps the node detail view display the first and the last node to be moved and any other editing operation is forbiden.. The second step can be cancelled.. At saving a document, a document type info is created using the DOCTYPE properties of the document, if such a document type info doesn't exists.. Document type info is no more created at document loading.. Background tasks are strictly sequenced in order to avoid swing reentrancy.. Background tasks such as document load or documents comparison are cancelable.. (2001-02).. Document conversion is available throw a general.. DocumentConverter.. interface.. A converter class can be attached to a document type at run time.. Converter implementations for.. simple doc.. 1,.. dependencies.. 0 and.. object oriented schema.. 0 are provided.. Changes about DTD conformance.. A "Lazy" check box at the bottom of the main frame replaces the option "DTDConformant".. A non empty element can be replaced (by changing its node type or its node name).. Childs are kept if they conform to the DTD or in lazy mode, elsewhere childs are removed.. DTD conformance is completed for moving and packing.. A message informs the user when the element sequence which contains the selected node is not DTD conformant.. Some errors in building the "children content" are fixed.. Other changes.. Edit.. menu is splited to.. menu and.. Fragment.. menu.. Formating and cleaning options are removed.. Removing empty texts is proposed by file menu.. No more confirmation for multiple node removing.. A Browsing history frame keeps trace of browsed nodes.. Search result frame is updated at any operation concerning a node from the list.. A few bugs about operation saving are fixed.. (2001-01).. DTD conformance is applied (by default).. This causes changes on :.. inserting, deleting, replacing and pasting nodes,.. proposing nodes types and element names,.. automatic child and sibling nodes creation after inserting or replacing nodes or creating a new document,.. grouping operations in order to maintain the document valid.. Other changes are :.. Operation design is revisited.. A special operation (with no effect on the document) is inserted between operations which must be executed together.. Editing comments, processing instructions, CData sections and entity references can be allowed or not by setting options.. Removing an element referenced by itself is allowed.. Operation file.. "xxxx.. ope".. is removed if it is empty at document closing.. An HTTP system id is redirected to the user relative system id which maps to the same public id.. Option "Advanced use".. For a standard use, the user interface is simplified.. Messages are cleared after a few seconds.. Searched text is selected within text node detail view.. Distinction is made between.. READONLY_SWITCHABLE.. READONLY_NOTSWICHABLE.. (2000-12).. This is the first release including source code.. It is based on Xerces-J 1.. It contains the following changes :.. Documents can be loaded from the Web, using or not an http proxy.. A prefix is used to distinguish document types using the same document element name.. The following File menu items are added : "Save and reload" and "Save DTD as.. ".. The options management is redesigned.. Each option value is defined or not for the document type and for the tool.. If the option value is defined for the document type then this option value apply.. Else, if the option value is defined for the tool then this option value apply.. Else default option value apply.. Options whose values are undefined are not writed in the option files.. New Load options, Parsing options and Save options are defined.. Parsing options are.. features.. implemented by Xerces.. The edit status -.. read only.. or.. ready for edit.. - can be set by a switch.. The switch is disabled if the document is modified.. encoding=xxx.. xmloperator processing instruction is suppressed.. The corresponding option is used.. DTDInternal.. DTD will be writed out as internal subset if and only if no DTD system id is specified for the document type.. (2000-11).. This release fixes a bug on saving a document including an internal DTD.. The element content specifications was incorrectly writed out.. Michael Altenhofen.. This is the first public release.. Last update : 2003-11-06.. Copyright (c) 2000 - 2003 The_xmloperator_project..

    Original link path: /history.htm
    Open archive

  • Title:
    Descriptive info: xmloperator - User Guide.. This is the xmloperator user guide.. It aims to help you in using the tool or in deciding if it could be useful to you.. First section ".. Getting started.. " gives an introduction to the tool and some entry points to this guide.. Second one ".. How to do that.. " is a list of question / answer for using the tool, in an arbitrary order.. Third one ".. Tool description.. " is a description of the tool, in a hierarchical order.. How to do that ?.. xmloperator is an XML editor, a tool that allows you to create, read, and modify documents in XML format.. Main characteristics of the tool are the following :.. It displays exclusively a tree view of your document.. Editing is guided by any DTD (Document Type Definition) or RELAX NG schema.. It can edit documents that cannot stay intirely in memory, by using an intermediary document storage format.. According to these characteristics, it is suited for editing very small to very large, data oriented documents, using a large variety of schemas.. At this point, you can start learning the tool use from one of the following links.. about documents :.. To load a document.. To navigate a document.. To create a new document.. To transform a document.. To compare two documents.. about schemas :.. To use DTDs.. To use RELAX NG.. about (reversible) operations :.. To modify text or attribute values.. To add and remove nodes.. To add and remove attributes.. To move nodes.. To copy nodes.. This section is a list of question and answer about using the tool.. To use DTDXML.. A document is loaded by an.. instance of the tool.. You can open several documents in the same time by opening several instances of the tool.. A distinction is done between small documents, which can sit in memory, and large documents, which cannot stay into memory or which are preferably not entirely loaded into memory.. Typically, documents whose size is greater than may be 100 Ko, may be more, should be considered as large documents.. For loading a small document, use the.. File / Load document.. For loading a large document, use the.. File / Load large document.. The two menus propose to load the document from your local disk or from a standard URL.. In the first case, use the.. Browse.. menu item (shortkey is Alt-O for a small document, Ctrl-O for a large one).. In the second case, use the.. Enter.. menu item.. You will have to enter or select the identifier of the XML document and, if it is a large document, you will have also to validate a path name for the intermediary binary file, so called.. BRXI.. file.. After these validations, document loading will start and you will be able to follow the following steps of the loading process in the message bar :.. Each entity required by the document is loaded.. The tree view of the document is displayed.. Nodes at the lowest level are expanded.. The schema associated to the document type is loaded.. IDs and IDREF(S)s are scanned and memorized for later quick reference.. Step 1 doesn't exist for large documents because the BRXI format doesn't support entities.. Step 4 may, for a large document, use a too long time or use too much memory.. There is an option for skiping this step.. You obtain a.. tree view.. of the opened document.. This view corresponds to the Document Object Model of the W3C.. At one time, you can select one or more nodes.. When only one node is selected (this is the most common case), information relative to the selected node is displayed in the.. detail view.. There may be a lot of nodes in your document, then you need some mechanisms for finding them.. The most common method to find a node is by content : you know some fragment of a text node or an attribute value.. You can then use the ".. View / Search.. " menu item (shortkey is Ctrl+F) to find the node(s) from its (or their) content.. For a more sophisticated criterion, you can use the ".. View / Evaluate.. " menu item (shortkey is Ctrl+Shift+E) which uses an XPath expression.. This tool supports also.. ID navigation.. , based on any DTD or any RELAG NG schema that conforms to the DTD compatibility specification.. Suppose you have selected an element that has a non-empty IDREF attribute.. You can double-click on the attribute or use the.. goto.. menu item from the contextual menu (obtained by right mouse click on the element in the tree view) to select the target element, which has an ID attribute with the same value.. Another thing is to remember some nodes you have selected before.. You can do that by double clicking on nodes that you want remember.. Their are added on the navigation list, accessible through the ".. View / Browsing.. " menu item.. Once your document.. loaded.. , you can modify text and attribute values after selecting them.. For a text node, the text value is display both as a line in the tree view and as an editing area in the detail view.. The tree view line is truncated and doesn't support editing.. Editing occurs in the editing area where the text is fully accessible.. You place your cursor at the location you desire and write your text.. Your change is stored without you need to do an action for that.. The text on the tree view is continually updated.. For an attribute, you have to select it in the attribute table of the element detail view.. Then, if it is CDATA, you edit it, like for a text node, by placing your cursor somewhere in the value field and writing your value.. No validation is required in this case.. This is different for an ID, IDREF or IDREFS attribute.. A button then occupies the value field.. The button action opens a dialog window.. For an ID, you enter the value and validate.. For an IDREF or IDREFS attributes, you select the referenced element(s).. For an enumeration, the value selection occurs directly in the attribute value field.. Using ID, IDREF, IDREFS and enumeration works as well with a RELAX NG schema than with a DTD.. Once you have realized some changes on your document, you should.. save.. it.. You can use the.. File / Save document.. Shortkey is Ctrl+S.. If you forget to do that and close the document or the tool without saving the document, there will be no message to prevent you to do so.. When you will reload the document, may be by re-launching the tool, you will have the surprise, after the loading of your document, to be proposed the execution of some operations.. They correspond to the changes you forgot to save before closing the document.. By accepting the operations, you apply your changes.. By rejecting them you cancel your changes and will not be able any more to recover them.. So, if you don't know what to do, the best is to accept the changes since you will be able to undo them later.. For adding or removing a node in your document you can use the contextual menu (right click on the context node in the tree view), the.. Edit menu.. , or a shortkey.. You can select a node (the context node) for inserting a node.. before.. it (shortkey is Ctrl+P) or.. after.. it (shortkey is Ctrl+N).. The choice of the context node is not indifferent since it is generally used as pattern for the new node.. If the context node is a text node then a text node will be inserted.. It would be the same for cdata section node, comment node or processing instruction node.. If the context node is an element and if the schema of the document allows the element to be repeated then an element with the same name than the context element is inserted elsewhere a list of possible names for the new element is proposed.. If the list contains an only name then an element with that name is immediately inserted.. You can also add a.. descendant.. to an element.. The shortkey is Ctrl+D.. If the element has already descendants then it will be the last.. If the element accept text node as descendant then a text node will be added else an element will be added.. You will select the element name from a list of possible names or an element will be immediately added if there is only one possible element name.. Adding an element (from sibling or parent) may require adding more elements in order to maintain the document validity.. The tool manages this aspect by proposing recursively to insert an element at each place where it is missing.. At each time, you have to select an element name if there are several possible element names.. When only one element name is possible then the element is inserted immediately.. If you cancel some element name selection then the document will be kept in an invalid state.. It's not a problem since you can.. an invalid document and make corrections later.. Removing.. a node requires selecting it and asks for remove.. The shortkey is Ctrl+Delete.. The operation is not allowed if the element removing would make the element sequence invalid.. In that case, you could have to select several nodes or to use the ".. Lazy.. " mode.. By using the lazy mode you make the choice to make temporally the document invalid.. Replacing.. a node is equivalent to removing the node and inserting another node at the same place.. If you want to change the node type of your node to another node type than element type then select this node type in the node type field of the detail view.. Elsewhere, for changing to element type then use the.. Edit / Replace.. The shortkey is Ctrl+R.. If an element is replaced by another element then the descendants, if any, are kept.. For adding an attribute to a selected document of your document you can use the.. New attribute.. menu item of the context menu (right click on the table attribute header) or the one of the.. or the shortkey Ctrl+U.. This action opens a dialog window for selecting an attribute name.. Names of attribute already in the element are excluded.. For removing an attribute from an element that you have selected in your document you have to select the attribute and ask for removing.. You can either use the.. Remove attribute.. menu item of the contextual menu (right click on the attribute name or value in the attribute table) or the one of the Edit menu or the shortkey Alt+Delete.. The operation will be not allowed if the attribute is required.. You can move one or more nodes at a time.. Moving several nodes require they have the same parent node.. Once you have selected your node(s) you can execute moves using one or two step(s).. A one step move is a local move.. The following operations are proposed by the.. Move menu.. and the contextual menu (right click on one selected node).. Menu item.. Shortkey.. Action.. Move previous.. Ctrl+Shift+Up.. The selected nodes are moved before the previous sibling node.. Move next.. Ctrl+Shift+Down.. The selected nodes are moved after the next sibling node.. Move child.. Ctrl+Shift+D.. The selected nodes are moved to the place of last descendant of the previous element.. Move parent.. Ctrl+Shift+T.. The selected nodes are moved after their parent element.. The two steps move works as follows :.. You select the node(s) to move and action the.. To be moved.. menu item of the Move menu or the contextual menu.. Sortkey is Ctrl+Shift+M.. Then the first node and the last node (if several nodes are selected) of the selected nodes interval are displayed in the detail view.. There is also a "Cancel" button for canceling the operation.. You select a node in your document for using as a mark for the move.. Then you execute one of the commands already examined for a local move.. For copying a node (or a sequence of nodes from the same parent node) from one document to the same document or to another document, the tool uses ".. fragment.. s".. There is one fragment by opened document, i.. e.. tool instance.. A fragment is a container for a node or a sequence of nodes.. The nodes are not in the document but are always attached to the document.. Fragment relatives operations are the following :.. Cut.. Ctrl+X.. The selected nodes are removed from the document and put into the fragment attached to the document.. Copy.. Ctrl+G.. The selected nodes are copied into the fragment attached to the document.. Import.. Ctrl+Shift+F.. The nodes selected in another.. opened document.. are copied into the fragment attached to the current document.. Paste before.. Ctrl+V.. The node(s) contained in the fragment attached to the document are copied before the first selected node of the document.. Paste after.. Ctrl+W.. The node(s) contained in the fragment attached to the document are copied after the last selected node of the document.. Paste under.. Ctrl+Y.. The node(s) contained in the fragment attached to the document are copied as last descendant of the selected element of the document.. Replace.. Ctrl+Shift+R.. The selected node(s) are replaced by the ones of the fragment.. Copy to clipboard.. Alt+G.. The selected node(s) are copied into the fragment attached to the document and into the system clipboard.. Entities (if any) are expanded for the system clipboard.. Copy fragment to clipboard.. Ctrl+T.. The node(s) contained in the fragment attached to the document are copied into the system clipboard.. Copy clipboard to fragment.. Alt+T.. The system clipboard is parsed as a fragment, which is copied to the fragment attached to the document.. Paste clipboard before.. Alt+V.. The system clipboard is parsed as a fragment, which is copied to the fragment attached to the document and copied before the first selected node of the document.. Paste clipboard after.. Alt+W.. The system clipboard is parsed as a fragment, which is copied to the fragment attached to the document and copied after the last selected node of the document.. Paste clipboard under.. Alt+Y.. The system clipboard is parsed as a fragment, which is copied to the fragment attached to the document and copied as last descendant of the selected element of the document.. Copying elements is not equivalent to moving elements since they contain IDs, because IDs cannot be duplicated in the document.. The tool takes care of changing the IDs of duplicated elements and keeping consistence of their references, if any.. For creating a new document, use the.. Document / new document.. This action opens a dialog window, titled "New document", asking you for a.. document type.. and a file name.. If the document type of your future document is already defined then select it in the list.. If it is not then click the.. New.. button at the right of the document type field.. This action opens a dialog window for defining a new document type.. You have to set the following information :.. name.. is the name of the document element.. It is not required but you should type it if there is only one possible document element name.. additional key.. is useful for distinguishing two document types using the same document element name.. It is optional but greatly recommended.. You may have to set DTD information or/and RELAX NG information.. RELAX NG is more flexible and should be preferred for editing.. But you may need to reference a DTD from your document because, as an example, the document references external entities.. When DTD and RELAX NG schema are set in the document type it is assumed that this is the RELAX NG schema which drives editing.. See details on.. using DTDs.. using RELAX NG.. namespace identifier.. is optional.. If it is set then an "xmlns" attribute with that value will be added to the document element.. The ".. shortcut used for empty elements.. " flag has only an effect on writing out the document.. The only justification of this flag is the bad interpretation of xhtml documents by old browsers.. default transformer.. " field allows setting a default.. for the document.. You enter the file name end validates.. A minimal document conforming to the document type is created, saved using the file name and re.. The following DTD relative information is (optionally) attached to a document type :.. DTD Public Id.. is destined to the DOCTYPE node of a new document.. Document relative System Id.. HTTP DTD System Id.. is an absolute URI for referencing the document.. User relative DTD System Id.. is an URI where the DTD will be accessed for editing.. In your documents with DTD, you have to choose between a DTD internal subset and a DTD external subset.. The reason is this one.. Suppose you load a document which has a document type declaration with an internal subset and a reference to an external subset.. The tool read a monolithic DTD, making no difference between the DTD internal subset and the external subset.. It's cool for editing but when you will save your document the DTD internal subset will be lost.. So you have to choose between the two following cases :.. Your document refers to an external DTD and contains no internal subset.. You have defined the document relative System Id information consistently.. You may have defined the DTD Public Id.. You may have defined the user relative DTD System Id in order to access it.. The document type declaration of your document contains a DTD internal subset and doesn't refer to an external subset.. The DTD relative document type information is not set.. In this case the DTD will be saved with the document, as DTD internal subset.. If your document has or refers to a DTD and you want to remove completely the document type declaration from it, you can do that by clearing the saving option "DOCTYPE if DTD".. You can use a DTD to edit a document without document type declaration.. You have simply to set the.. and not set the.. Document relative DTD System Id.. The DTD will be loaded after the document.. At some time you might be asked for associating the document to a document type.. If your document type information includes the user relative DTD System Id then you have two methods for modifying the DTD : you can edit it as text by using the.. Selected type / Edit DTD / as DTD.. menu item of the.. Document types window.. , ) or you can.. use DTDXML.. The tool offers some RELAX NG support.. RELAX NG is used for guiding editing.. The tool helps you to make your document valid but it doesn't verify all the constraints that a document must conform to be valid.. Also you need an external RELAX NG validation tool for validating your document after editing with this tool.. The following RELAX NG relative information is (optionally) attached to a document type :.. RNG full syntax System Id.. is an URI where the RELAX NG schema will be accessed for editing.. RNG simple syntax System Id.. is an URI where should be available the RELAX NG schema in its simplified form.. The tool contains a full syntax to simple syntax translator.. You can launch the translator by using the.. Build.. button in the RELAG NG panel of the document type dialog (see the.. ).. The input is the schema referenced by the.. The output will be referenced by the.. Another way to simplify a RELAX NG schema is to load it in a tool window and using the.. File / Simplify RELAX NG schema.. There are three menu items that map to three possible modes of simplification :.. Simple syntax.. This mode produces the simple syntax as defined by the RELAX NG specification.. Group with more than two children.. Using this mode, all the simplification steps are executed except the §4.. 12 one that reduces the number of child elements.. This is the mode used by the document type dialog.. Ref resolution only.. This mode executes minimal simplification.. Its purpose is only to resolve the.. externalRef.. include.. elements before transforming the schema to HTML for being browsed by the user.. If you load a document associated to a document type whose the.. is set then the RELAX NG schema will be loaded immediately after and you will be allowed to edit your document using this schema.. DTDXML is an XML dialect for representing DTDs.. By editing a DTDXML document then compiling it to a DTD, you have a best control of the production of DTD.. However there is no DTDXML specification, only a DTD.. It's not a standard.. You want yet use it ? OK, we continue.. The pathname of the DTD that you have to produce is given as document type information.. You can attach a DTDXML document to the document type by setting the.. DTDXML System Id.. Then you can use the.. in two steps :.. For editing the DTDXML document, use the.. Selected type / Edit DTD / As DTDXML.. The document will be loaded in a free tool instance.. You will be guided by its DTD for editing.. For producing the DTD, use the.. Selected type / Build DTD / DTDXML - DTD.. The DTD is written out to the.. (which must refer to a file).. For transforming a document, you can use the.. File / Transform document as.. You enter a pathname for the destination file.. If several transformers are available for this type of document then you will be asked for selecting one.. The transformation is launched.. Once this task finishes, you can open the resulting document.. It is proposed at first position in the Reopen list.. But what is a transformer ?.. A transformer is used for translating documents from an XML format to another XML format or to text format.. This section considers particularly XSLT transformers.. For defining a transformer you have to proceed as follows.. First you opens the.. Transformers window.. by using the.. Document / Transformers.. Then you use the "New" menu item on this window.. This action will open a dialog window titled "Transformer" whose you will set the fields in that way :.. You have to give a.. Name.. to the  ...   two documents.. They take on their normal traits.. Merge as.. menu item merges two documents currently associated, and saves the resulting document under a new name.. The Options menu is dedicated to managing the settings.. Settings / Modify.. menu item opens the settings dialog window.. This window allows easy modification of the most current settings.. The window is organized in sections, selectable by tab.. Not all the settings are represented in this window.. The absent settings must be edited in the options document.. Settings / Save.. menu item saves the current settings in the options file.. This action is not required since it is automatically executed at tool closing.. Settings / Reload.. menu item reloads the saved settings.. This action is useful after a modification is made to the options file.. This modification would actually be lost after the automatic saving of the settings when the tool is closed.. Settings / Edit.. menu item opens a new instance of the tool if the current one is not free and loads the settings document in that new instance for editing purposes.. About.. menu item opens a dialog window displaying the tool version, the copyright and acknowledgement of outside contributions.. The tree view takes up the left part (or upper, depending on the orientation selected) of the central area in a tool instance window.. This view displays the document while editing.. The document is decomposed using the Document Object Model (DOM) of the W3C.. The nodes that have descendants are represented by a folder.. The nodes without descendant are represented by a bullet.. The nodes with descendant(s) can be expanded by clicking on the "+" icon in front of the folder icon.. The detail view takes up the right part or the lower part of the central area in a tool instance window.. This is the detail view of the selected node in the tree view.. You can modify the selected node through it.. The detail view content depends on the type of the selected node but the node type always appears on top of it.. The node type can or cannot be modifiable, depending of context, as explained in the following paragraphs.. If the document is read-only then nothing in the document is modifiable.. DOCUMENT node.. view contains the document system identifier, the encoding name, the standalone indicator, the document type and its additional key.. The node type, document system identifier and document type cannot be changed.. The encoding name and standalone indicator can be changed.. The additional key can be changed.. Each proposed additional key comes with the same document type name or with no specified document type name.. DOCTYPE node.. view contains the DTD public identifier, and the DTD System Identifier.. The node type, DTD public identifier and DTD system identifier cannot be changed.. ELEMENT node.. view contains the element name, a field about (superficial) content validity and either a table of its attributes either a text area for the value of one of its attributes.. The node type cannot be changed if the element has descendants.. Neither the node type nor the element name can be changed if the element is the document element or if the element is required for the content validity of its parent element.. Otherwise node type or element name can be changed.. attribute table.. contains the attribute names and values.. The selection of an attribute (by clicking on its name or value, or using the up and down arrow keys), displays the line in reverse video and shows the location of the attribute value an editing field adapted to the type of this attribute.. A popup list is displayed for an enumeration.. A button is displayed for ID, IDREF or IDREFS type of attribute.. Action of this button opens a dialog window whose purpose is to entry the ID value in the case of ID type, to select an existing ID in the case of IDREF type, to select zero or more existing IDs in the case of IDREFS type.. An entry field is displayed for all other types of attribute.. By a rigth clic on the attribute table heading, a contextual menu popups with the following item :.. for adding a new attribute to the selected element.. By a rigth clic on an attribute name, a contextual menu popups with the following items :.. Select attribute.. for opening the full text area for the selected attribute.. You will be allowed to return to the attribute table mode by using the button that is labelled with the attribute name.. for removing this attribute.. TEXT node.. view contains an editing area.. The node type is modifiable except if the document is read-only.. The editing area keeps the text between its vertical limits by going to the line if necessary, and preferably to spaces so as not to cut words.. These line jumps do not make up part of the text (only those that are entered are part of the text).. CDATA SECTION node.. COMMENT node.. view content are the same as the text node view content.. ENTITY REFERENCE node.. view contains the name of the entity.. You can select the entity from a list of declared or predefined entities.. PROCESSING INSTRUCTION node.. view is similar to that of the text node view, except it includes a supplementary "Target" field.. A special case is when one or several nodes have been selected to be moved.. In this case, the detail view displays the first and the last node (or only the first if there is only one).. It also displays a button that can be used to cancel the move.. The status bar, located on the bottom of the window, is made up of the following fields (from left to right): a document status indicator, an edit mode indicator and a message line.. All indicators can be removed, see the options dialog, Status bar tab.. document status indicator.. is a combo-box that can show the following: empty (grayed out), "Ready" (accessible), "Read-only" (accessible or grayed out), and "Modified" (grayed out).. The indicator is empty when no document is open.. The indicator is in "Ready" state if the open document can be edited and was not yet modified.. The indicator shows "Read-only" if the open document is read-only.. The status is "Modified" if the document was modified and has not been saved since.. edit mode indicator.. is a check-box called "Lazy".. In the regular mode (not "lazy"), all of the realized operations (without breaking down the linked operations) should respect the schema or DTD.. In "lazy" mode, they can make the document not valid.. Clearing the check-box while the content including the selected node is not valid has the effect of adding as many elements as necessary in order to make the content (superficially) valid.. Certain actions conclude with a message displayed in the.. message bar.. Such a message is a simple reminder.. An important and unexpected message such as an error always appears in a modal dialog window, because it must be accepted.. The message is erased with each new action or at the end of a fixed amount of time.. An instance secondary window depends on the instance main window.. In particular it is automatically closed when the instance main window is closed.. They are listed in the following lines.. Some of them are unique for the instance, some others are multiple.. Navigation window.. Operations window.. Fragment window.. Content model window.. Referencing elements window.. Errors on loading window.. Search results window.. This window displays the list of nodes that were selected by double clicking.. This window displays the list of operations realized with the tool since the document was loaded.. It also allows the undoing or redoing of a group of operations.. The operations list is built from top to the bottom.. When there are no operations to undo, the last operation in the list is the last operation to be realized.. When there are operations to redo, but also to undo, they appear in the following order: the operations to undo, a separation line, and the operations to redo.. When all of the operations are to be redone, the first operation is preceded by a separation line.. Each operation is always expressed as having been realized or to be realized.. The reverse operation is never expressed this way.. The operation wording generally consists of: a verb (Insert, Set value,.. ), an object (element, TEXT,.. ), and a context (within.. A special operation, named "and", has no effect on the document.. It links operations of which the indissociable execution ensures that the validity of the document is maintained.. Undo all.. menu item undoes all the operations that can be undone.. Redo all.. menu item redoes all the operations that can be redone.. Clear undo.. menu item clears all the operations that can be undone.. All that is left are possible operations to redo.. Clear redo.. menu item clears all the operations that can be redone.. All that is left are possible operations to undo.. Load.. menu item opens an operations file selection window.. If an operations file is actually open, its operations are run and added to the operations to be undone, with the possible operations to be redone being cleared.. Save.. menu item opens a window for the entry of the name of the operations file.. If the entry is validated, the operations that can be undone are saved in this operation file.. This window displays the fragment resulting from a cut or copy.. It also enables the importing of a fragment from another document.. A checkbox allows you to choice between erasure of the fragment or not, after paste.. Clear.. menu item clears the fragment.. menu item allows you to import selected nodes from another opened document in the current one.. If several other instances are open, a dialog window opens so that you can select the instance from which to import.. The action is abandoned if no other instances are open.. The imported fragment replaces the current fragment, if there is one.. This window displays the content model of the selected element when an element is selected.. The notation is a mixed of DTD syntax and RELAX NG compact syntax.. Attributes are present, prefixed by the '@' character.. A default namespace of an nsName is represented by the 'D' character if no prefix is available for this namespace.. This notation is destined to be interpreted by human, not by machine.. An help is provided for localizing parenthesis : When you clic at some position within the content model string, the text area between the corresponding left parenthesis and the corresponding rigth parenthesis is selected.. This window displays the list of elements for which an IDREF or IDREFS points to this element, considered as the target.. Clicking on one of the referencing elements selects it in the tree view of the instance main window.. Using the.. Target.. menu item, the target element is again selected in the tree view of the instance main window.. One can open as many referencing element windows as there are elements with ID in the document.. The windows are updated according to the changes made to the document.. A window from which the target element is deleted disappears by its own.. The loading error window opens during document loading if errors or warnings are triggered.. Subsequently, this window can be re-opened using the.. menu item of the instance main window.. The window displays the list of errors and warnings.. By selecting a line, the element in which the error appears is selected in the tree view of the main window.. Double clicking on a line opens a source text editing window for the document (if it is not already open) and the line in the source text is selected.. The search results window opens at the conclusion of a search for a text extract in the document that is being edited.. This search is launched by the.. This window displays the list of nodes containing the text extract being searched for.. The extract can be in the text of a node, or in an attribute value.. The selection of a node in this list selects this node in the tree view of the main window.. If this node includes an edit field (TEXT, PROCESSING INSTRUCTION and CDATA SECTION) then the first occurrence of the required text is selected.. If this node is an element then the attribute containing the required text is selected.. A new search reopens the same results window, and erases the preceding search.. The position and dimensions of the window are maintained.. There are two global windows : the.. They are unique, can be opened from any instance main window and are closed when the last instance main window is closed.. This window defines the document types as well as their associated files.. The window displays a table with a menu bar on top.. The document types table contains the following columns: Document type, additional key, and schema type (nothing, DTD, RNG or DTD + RNG).. Select a line by clicking on it or by pressing the up or down arrow button.. Double clicking on a line has the same effect as the.. Modify.. menu item opens a dialog window for entering the new document type characteristics.. That includes the document type name, the additional key, the DTD public identifier, the DTD reference HTTP URL, the DTD URL as it should appear in the "DOCTYPE" node of the document, the DTD user path, the DTDXML user path, the RELAX NG full syntax schema URL, the RELAX NG simplified schema URL, the namespace identifier, the flag for using shortcut for empty elements, and the reference transformer name.. All the fields are optional, including the document type name.. menu item opens a dialog window allowing the modification of the document type selected.. The dialog window is the same as that which defines a new document type.. Duplicate.. menu item has the same effect than the.. menu item with this difference that the entry fields get the values corresponding to the currently selected document type.. menu item removes the selected document type.. DTDXML - DTD.. menu is about building a DTD from DTDXML.. The first menu item translates each pattern element of the DTDXML document by a parameter entity declaration in the DTD.. The second one applies these patterns without using parameter entities.. Nothing is done if there is no DTDXML system Id in the document type information.. Edit DTD / As DTD.. menu item opens an editing window for the DTD content.. The window title is the user DTD System id.. The text is read-only if the DTD is not in a file.. Edit DTD / As DTDXML.. menu item opens a new tool instance or uses the current instance if it is free, for loading the DTDXML document.. Nothing is done if the document type information contains no DTDXML system Id.. Edit RNG / Full syntax.. menu item opens a new tool instance or uses the current instance if it is free, for loading the RELAX NG full syntax document.. Nothing is done if the document type information contains no RELAX NG full syntax System Id.. Edit RNG / Simple syntax.. menu item opens a new tool instance or uses the current instance if it is free, for loading the RELAX NG simple syntax document.. Nothing is done if the document type information contains no RELAX NG simple syntax System Id.. This window defines the document transformers.. The transformers table contains the following columns: transformer name, full name of implementation Java class, and System Id of its style sheet if it is an XSL Transformation.. Double clicking on the line has the same effect than the.. menu item opens a dialog window for entering a new transformer.. That includes the transformer name, the full Java class name, the System Id of the style sheet for an XSL Transformation, the destination DTD public identifier, the destination DTD System Id, the encoding name, a check box for standalone document and a check box for using or not the empty element shortcut.. It is only possible to validate if the transformer name is entered.. menu item has the same effect than the New menu item with this difference that the entry fields get the values corresponding to the currently selected transformer.. menu item opens a dialog window allowing the modification of the transformer selected.. The dialog window is the same as that which defines a new transformer.. menu item removes the selected transformer.. The tool keeps, for each document type, some relative information.. A document type is identified by the document element name and an additional key.. If you want use different document element names with the same document type then keep the document element name empty.. You can have several document types with the same document element name but with different additional keys.. An additional key represents nothing by itself when creating a document.. The information attached to a document type includes: the DTD public identifier, the reference HTTP URL of the DTD, the URL of the DTD as it appears in the "DOCTYPE" node of the document, the path to the user DTD, the path to the XML version of the DTD, the RELAX NG full syntax System Id, the RELAX NG simple syntax System Id, the namespace identifier, the flag about using shortcut for empty elements, and the reference transformer name.. This information is that which is used during a document save.. When the.. is absent then, the document DTD, if any, is inserted directly into the document.. An action that could use some time is managed as a task.. Examples of tasks are : loading a document, saving a document or transforms a document.. During a task, all the menus are disabled and the indicators in the status bar are replaced by a.. Cancel.. button.. An operation is any atomic alteration made to a document, realized with the help of the tool.. With each action of the tool that results in a change to the document in memory, an operation is created, run and added to a stack of operations.. The operations already run can be cancelled.. You can undo or redo any operation.. The stack of operations can be consulted in the.. The operations can be kept for being rerun later in operations files.. A special operation, labeled "and", has no effect on the document.. This operation joins two operations.. It signifies that the operations linked in this way must be considered indissociable, in order to maintain the validity of the document.. A sequence of operation can be saved in an.. operations file.. to be rerun later, in an equivalent context.. An operations file has the suffix ".. The operations file relative to a document file carry the name of the document file in which the suffix is replaced by ".. For this reason, an operations file cannot be attached to an operations file.. Editing an operations file uses a schema called xmloperator_x_y_operations.. rng where x and y map to the release x.. y.. z of the tool.. At the conclusion of loading a document, if it exists an operations file attached to it then you will be prompted to rerun the operations it contains.. An operation that cannot be run in a given document context will be rejected.. You should to choose whether or not to run the subsequent operations.. An.. operator.. is an additional code, linked at run-time, implementing a given Java interface and realizing a special (and generally complex) sequence of operations.. A transformer is used for producing a document from another document.. The documents generally have not the same schema or DTD.. The tool uses a standard transformer interface.. You can create a Java class that implements this interface and dynamically link this class to the tool.. You can also write an XSLT stylesheet.. The XSLT engine is provided by the Xalan-J software of the Apache Software Foundation.. The information attached to a transformer includes : the transformer name, the full Java class name, the style sheet path name for an XSL Transformation and the output format depending information.. The output format is either XML document or text.. For an XML output, the public identifier and the system identifier of a destination DTD can be defined with the encoding names, the standalone flag and the shortcut enabling flag.. All the settings of the tool are designated by options.. Certain options may be modified by using the options dialog, the others can be modified by editing the options document.. Options are loaded at tool launching and saved at tool closing.. The tool.. options file.. is named "xmloperator.. xin".. The path can be specified as parameter in the command line.. If the path is not specified then the file is created in the tool's launch directory.. Editing this document uses a schema called "xmloperator_x_y_options.. rng" where x and y map to the release x.. The tool defines a.. processing instruction target.. , named.. , but without case distinction.. processing instruction is supposed to be only interpreted by the xmloperator tool.. All other document-processing tools are supposed to ignore this instruction.. The tool uses these instructions to attach certain processing options to document instances.. An instruction is made up of one or more space separated commands.. Only the processing instructions whose parent node is the document element are interpreted.. There is only one instruction currently defined : the "ReadOnly" instruction.. The "ReadOnly" instruction opens a document in read only mode.. This doesn't prevent you from switching immediately to the "Ready" mode and editing the document.. There will be always bugs.. We have simply to reduce their effects and manage their fixing.. A bug appears on an unexpected case and generally raises an exception.. The exception is intercepted by the tool (but some ones are not) and is reported to you by a persistent message "SEE EXCEPTION TRACE" in the message bar.. Then you have to use the.. View / Exception trace.. menu item for reading and accepting the exception.. Accepting the exception means only that the "SEE EXCEPTION TRACE" message will be cleared.. The exception trace contains the date, the tool version, and the exception(s) that have arisen.. Each exception appears as a call stack.. For bug fixing, you should send a copy of this trace to the tool developer (info@xmloperator.. net).. Additional comments would be welcome.. Last update : 2003-08-25..

    Original link path: /user_guide.htm
    Open archive

  • Title:
    Descriptive info: Running.. Design.. InstanceToSchema is a.. schema generator from XML instances.. It is a command line tool.. There is no user interface.. It is written in java and needs J2SE 1.. 3 or 1.. 4 and a JAXP compliant SAX parser for running.. A typical use case consists to obtain a description of the structure of one or several (combined) XML files.. It must be noted that the tool make use of only a little part of the RELAX NG language.. InstanceToSchema is developed inside.. the xmloperator project.. and shares its.. but is packaged and can be used independently from the XML editor.. 2003-10-30.. i2s_1_0_2.. (51Kb).. i2s_1_0_2_src.. (94Kb).. There is one java archive :.. i2s.. The main class is.. i2s.. SchemaGenerator.. Command line arguments are the XML instance URIs.. The resulting RELAX NG schema is produced as standard output.. The first argument may be preceded by a "-stat" option for adding to each element definition of the resulting schema a comment that contains the occurrence count.. As an example, the following.. Windows.. command builds a.. schema.. file (stats included) from a.. test.. xml.. file, by using a.. Xerces.. parser :.. java.. exe -cp i2s.. jar;xml-apis.. jar;xercesImpl.. jar org.. SchemaGenerator -stat test.. xml schema.. The software  ...   elements but with the same name.. There may also be attributes and/or texts.. GroupPatternCategory.. represents ordered contents or choice between ordered contents.. InterleavePatternCategory.. represents unordered contents.. Some element names may appear several times, some others may not.. All these pattern categories consider elements and attributes as independent.. However the tool framework doesn't require that.. New pattern categories could correlate elements and attributes.. Another thing the tool does not is inferencing datatypes.. The tool is suitable for processing large documents.. It uses only one SAX parsing pass.. The required memory space depends on the element name count and the complexity of patterns, not the document size.. The set of pairs (element name, pattern category) is translated to a RELAX NG simple syntax data model (the same is used by the XML editor), which is converted to a more readable full syntax and writed out with indentation.. 2 (2003-10-30).. This release fixes a bug on.. PatternExtractor.. : the last character of any piece of text was not taken into account.. Another thanks to.. Mike.. for the test case.. 1 (2003-10-22).. This release fixes two bugs on.. GroupPatternCategoryImpl.. Mike Brown.. whose test case has revealed the two bugs.. 0 (2003-02-13).. First public release.. Last update : 2003-10-30..

    Original link path: /i2s/
    Open archive

  • Title:
    Descriptive info: Related software.. JavaSkeleton is a command line tool that builds a report about dependencies between java classes.. It needs J2SE 1.. 4 or 1.. 3 with a JAXP compliant SAX parser for running.. The tool's job consists in first analyzing java classes from source files and then producing an XML document that reports the dependencies between the outer one classes.. The structure of the XML document is given by.. this RELAX NG schema.. An XSL style-sheet is also provided in order to produce an HTML report from the XML document.. As an example of result, take a look at.. JavaSkeleton_1_0_skeleton.. , which has been obtained from the JavaSkeleton source files.. Dependencies are elaborated from class name references through declarations or statements (not in literals).. In order to not have to do the whole job of a Java compiler, the tool makes some assumptions about naming : all class names - by speaking about classes, we include interfaces - are supposed to start with an upper case and all package, field and method names are supposed to start with a lower case.. In the same way, a list of primary package identifier is used for control.. The default list is (.. javax.. net.. com.. edu.. It may be enriched.. All theses pseudo-rules allow some simplifications and make compiling more efficient.. A warning is written out when a non respect of one of this rules can be detected.. For the predefined.. lang.. package and for some packages that some sources may reference in import-on-demand declarations  ...   warning : no warning will be written out.. -ppi xxx.. n.. will add.. xxx.. to the list of primary package identifier.. -import xxx.. will import the.. file in order to be able to resolve some import-on-demand declarations.. -si.. self import : will add a first compilation pass in order to be able to resolve some import-on-demand declarations that reference the analyzed packages.. -fi.. for import : running purpose is building an import file, which will contain the package contents but no dependencies between classes.. -pu.. package use : will consolidate the class dependencies at the package level.. -output xxx.. will use this pathname for report output.. will analyze this java source file.. will analyze all the java source files that this archive contains.. directory>.. will analyze all the java source files that this directory contains, recursively.. will merge this previously obtained skeleton.. As an example, the following command builds a.. skeleton.. report file from the.. jsk_src.. source archive file :.. java -cp javaSkeleton.. Compiler -import import_j2se_1_4_java.. xml -import import_xml_sax_2.. xml -output skeleton.. xml jsk_src.. You could be interested by the following tools, whose object is near that this one.. Both of them analyze the compiled class files rather than the source files, which presents some advantages.. Classycle.. : reports the cyclic dependencies between classes, including the one where inner classes are concerned.. JDepend.. : generates.. design quality metrics.. at the package level.. This helps.. to effectively manage and control package dependencies.. Java is a trademark of Sun Microsystems, Inc.. Last update : 2003-07-16..

    Original link path: /jsk/
    Open archive

  • Title: LambdaAPI
    Descriptive info: LambdaAPI is a java-written implementation of lambda-calculus.. Its aim is to support applications of lambda-calculus.. It makes use of the.. Lambdascope.. normalization technique, which guarantees.. optimality.. The software is provided in source form exclusively and depends on nothing but the JRE System Library (jdk 1.. 4 or later).. Its.. is free.. LambdaAPI is developed within.. but has no special connection with XML (until now).. The software is described by the two following  ...   LambdaAPI).. Both documents contain links to the javadoc that don't work on-line because the javadoc is zipped (it must be downloaded).. For more information, please send a mail to "info at xmloperator.. net" using a subject starting with "[LambdaAPI]".. Source 1.. Documentation 1.. 2004-09-06.. First public release : 1.. 2004-09-11.. Documentation correction (english usage).. Laurent.. for his help.. 2004-09-13.. Another documentation correction pass (1.. 2).. Last update : 2004-09-14.. Copyright (c) 2004 The_xmloperator_project..

    Original link path: /lambda/
    Open archive

  • Title: LambdaAPI2
    Descriptive info: LambdaAPI2 is another java-written implementation of pure lambda-calculus.. LambdaAPI2 is based on constructs described in.. Compiling the Lambda-calculus into Interaction Combinators.. , which, associated to the.. weak reduction to interface normal form.. , provides a competitive implementation of lambda-calculus.. LambdaAPI2 design.. (deals with LambdaAPI2 design).. Playing with LambdaAPI2.. (invites to experiment with LambdaAPI2).. Both documents contain links to the javadoc that don't work on line because the javadoc is zipped and must be downloaded.. net" using a subject starting with "[LambdaAPI2]".. 2005-12-13.. Last update : 2005-12-13.. Copyright (c) 2005 The_xmloperator_project..

    Original link path: /lambda2/
    Open archive

  • Title: ReactiveMachine
    Descriptive info: ReactiveMachine is a java-written.. reactive.. framework.. It implements.. agents.. , which interact in a.. deterministic.. way, by using the.. paradigm.. Version.. Last update.. Sources.. Documentation.. reactive_machine_src_2_1.. TheReactiveMachine_2_1.. 2011-10-04.. reactive_machine_src_2_0_1.. TheReactiveMachine_2_0.. 2008-08-21.. reactive_machine_src_1_0.. TheReactiveMachine_1_0.. net" using a subject starting with "[ReactiveMachine]".. Copyright (c) 2008, 2012 The_xmloperator_project..

    Original link path: /reactive/
    Open archive

  • Title:
    Descriptive info: /* * The_xmloperator_project Software License, Version 1.. 7 * * Copyright (c) 2000 - 2003 The_xmloperator_project.. All rights reserved.. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1.. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer.. * * 2.. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution.. * * 3.. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes or uses software developped * by The_xmloperator_project (http://www.. net/).. " * Alternately, this acknowledgment may appear  ...   administrator.. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED.. IN NO EVENT SHALL THE_XMLOPERATOR_PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE.. * ==================================================================== * * Further information can be found on the project's site * (http://www.. */..

    Original link path: /license.txt
    Open archive



  •  


    Archived pages: 23