WO2002075533A1 - Method and apparatus for processing information - Google Patents

Method and apparatus for processing information Download PDF

Info

Publication number
WO2002075533A1
WO2002075533A1 PCT/FI2002/000212 FI0200212W WO02075533A1 WO 2002075533 A1 WO2002075533 A1 WO 2002075533A1 FI 0200212 W FI0200212 W FI 0200212W WO 02075533 A1 WO02075533 A1 WO 02075533A1
Authority
WO
WIPO (PCT)
Prior art keywords
source data
rules
processing
xml
data
Prior art date
Application number
PCT/FI2002/000212
Other languages
English (en)
French (fr)
Inventor
Antti Jokipii
Original Assignee
Republica Jyväskylä Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Republica Jyväskylä Oy filed Critical Republica Jyväskylä Oy
Publication of WO2002075533A1 publication Critical patent/WO2002075533A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/34Browsing; Visualisation therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs

Definitions

  • the invention relates to the processing of data in the form of XML (Extensible Markup Language), so that the information contained in said data is obtained to be available for existing program components.
  • the invention relates to a centralized management of the definitions made in order to be able to process the data.
  • the employed program component needs the input information in a certain form. Between the program components, there is no uniform input format, but each program component has its own requirements as regards the input information.
  • the interface of the program component defines in which form and in which order said program component needs the input information.
  • the data described by XML must be modified into a form required by the program component.
  • additional information of the XML language can be found in the address http://www.w3.org/XML/.
  • the XML to be fed in is not particularly designed for said program component, it must also be possible to fetch the necessary pieces of information from their respective locations in a given order.
  • XML-based messaging systems there are only used certain parts of the XML data that was fed in.
  • XML parsers When reading the source data, there are utilized XML parsers that organize the input data in a form where the program components can use it. In addition, the utilization of the input data requires a remarkable amount of programming work in order to render the required parsers and the data produced by said parsers to be put to proper use in the internal logic of the program component in question.
  • XML parsers there are two main types: event-based (SAX, Simple API for XML; API, Application Programming Interface) and tree-based (DOM, Document Object Model).
  • SAX Simple API for XML
  • API Application Programming Interface
  • DOM Document Object Model
  • An event-based parser is SAX, the operation whereof is illustrated in figure 1.
  • the source data 101 is read in the SAX parser 102, which arranges the original source data into various parsing events, including for example the beginning and end of the elements.
  • Said events SAX then transmits directly to the event-processing classes of the employed program components 103.
  • the events are not arranged in an internal structure, but they are processed after the events have been triggered, which means that the processing is light.
  • the source data 101 can only be processed event by event.
  • Events are processed through so-called handles 103a of the programs. Said handles 103a must be separately produced in each event-processing program.
  • the processing proper of the events in the program components 103 is very similar to the processing of events in a graphical user interface.
  • FIG. 2 An example of a parser producing a tree structure is illustrated in figure 2.
  • the parser illustrated in figure 2 represents the type DOM 202.
  • An application using the DOM 202 definition creates an application programming interface (API) for instance to source data 201 in the XML language.
  • API application programming interface
  • DOM interface 203 By means of the DOM interface 203, the contents and structure of the source data 201 can be accessed, and said features can then be modified.
  • DOM includes a number of objects that represent XML documents, as well as a model describing how said objects can be combined and an application programming interface through which the objects can be handled.
  • DOM 202 defines the logical structure of the documents, as well the way in which the documents can be processed. Any kind of data contained in an XML document can be processed, transformed, removed or added by means of DOM 202. DOM 202 collects the source data into an internal tree structure 203 and allows the employed program 204 to navigate in said structure. As regards the program components 204, each of them includes a separate part 204a that can fetch the required data from the tree structure 203 created by DOM.
  • a drawback of the event-based arrangement is the management of complex structures as well as references to certain locations, for instance by means of XPath. At the priority date of the present application, there is found additional information of such XPath references at the address http://www.w3.org/TR/xpath. Moreover, in event-based structures, the events collected in the parser are transmitted to the program components only once, whereafter they cannot be further processed. Both of the above described arrangements have the drawback that reprogramming is always required when there are changes in the data to be fed in.
  • JSR-31 XML Data Binding
  • JSR-31 XML Data Binding
  • JSR-31 Java Community Process
  • XML is modified so that there are created Java classes corresponding to the XML structure.
  • additional information is found, at the priority date of the present application, at the address http://java.sun.co ⁇ j7aboutJava/communityprocess/jsr/jsr_031_x ⁇ .html.
  • This technique makes it easier to use XML, but it neither solves the problem of changing XML nor that of using several different formats for the same program components.
  • An object of the invention is to parse source data in the XML form so that it can be reprocessed by reusable program components.
  • a particular object of the invention is to provide said reusability of the program components when the source data is in the XML form. Moreover, an object of the invention is a centralized management of the data processing. Yet another object of the invention is to facilitate fast parsing and use of the source data in the XML form and thus to enable real-time processing of the source data with the defined program components.
  • the object is realized by generating the required definitions only once in one location, so that they can be managed in a centralized way.
  • a processing component that has at its disposal said definition as to what is the input source data in the XML form like, and how and with what program components said data should be processed.
  • the processing rate can be increased by loading as many program components as possible in the memory in advance, prior to parsing the source data in the XML form, and by using a special parser that only reads the required information of the source data.
  • program components When developing programs, it is economical and effective to use already existing program components as much as possible. In order to maintain effectiveness and functionality, also the new features are advantageously realized, as far as possible, in the form of program components.
  • the advantage of program components is that the same functionality need not be realized many times, but the ready-made, already existing embodiments can be reused. Thus the quality of the programs is improved, because there can be used already tested program components, and only their compatibility must be tested. Moreover, projects can be realized with a schedule that is more accurate and faster than before, because less programming and testing is needed in the production of the programs.
  • MAP includes an illustration of the employed source data, information as to how the source data should be processed by the program components, illustrations of the necessary parts of all interfaces of the employed program components, as well as information of how said program components are put to use.
  • the processed program components can be completely separate and unaware of each other. Program components are always used through an interface that defines the data required for using the program component in question.
  • MAP can exist so that is written inside the processing component, or MAP can be loaded to be used for example from an XML file or database containing the definition when starting the processing component.
  • MAP tells unambiguously how the data is processed and what program components are used for processing the data, as well as what kind of interfaces or parts thereof are used. Because MAP illustrates the functions as uses of existing interfaces, the employed program components need not be modified. This lightens the process as a whole and remarkably increases the modifiability of the system.
  • MAP In MAP, there are defined all employed program components and interfaces required for the use thereof.
  • employed source data In addition, in MAP there is illustrated the employed source data and defined to what kind of procedures the source data is subjected at each step. Thus MAP illustrates only those parts of the source data that are employed, not necessarily the whole of the source data. Consequently, when creating MAP, it must be known exactly what program components should be used and what is the input information. In order to facilitate this process, it is possible to create a graphical user interface that identifies the existing program components and automatically finds out the interfaces used by them.
  • the processing component operates so that first the source data is fed to the processing component. Then the defined program components, their interfaces, a description of the source data and operational instructions are read from MAP. The parsing of the source data is started on the basis of the MAP information, and simultaneously the source data is converted, into a program that can be run according to the MAP instructions. Thereafter the running of the program components proper is performed.
  • the running order is defined in MAP, and it can contain for instance conditions, jumps or calls, by which the performing order during the run can be affected. Thus there can be created for example internal loop structures for MAP.
  • the obtained end result is a program defined by the source data and MAP, which program is easily run and can use the required program components for processing the desired tasks.
  • the source data fed in during the processing controls the running of the program component. Moreover, external parameters can be given for controlling the process or as the data to be used in the processing.
  • MAP can be dynamically modified, which means that the processing component can be used dynamically.
  • the description as to what should be done to the components is only realized at one location, i.e. in MAP, the probability of errors is reduced.
  • the logic of the application is programmed in the employed program components, and the application logic and the required XML data are separate, it is not necessary to modify the program components. Because the employed program components are generally tested in advance, there is now tested only the system composed by means of MAP and the input data.
  • This kind of processing component and connected MAP are easily realized in several different environments and applications. All definitions can be reused. The operation is more reliable, because the probability of errors is reduced, when the definitions and instructions are created in one location only. The application is effective, and the data-specific part need not be included in the program components. This means an essential reduction in the work of programmers and designers and clarifies the structure of the designed program components and programs as well as improves their reusability.
  • figure 1 illustrates an arrangement according to the prior art
  • figure 2 illustrates an arrangement according to the prior art
  • figure 3 illustrates an arrangement according to the invention
  • figure 4 illustrates an arrangement according to an embodiment of the invention.
  • the term 'program component' means an independent unit with a given function and unambiguously defined interfaces and other dependencies with respect to its surroundings according to what is agreed on. Program components can be distributed irrespective of each other, and third parties can use them for compiling their programs. Program components are used through a given interface. In this application, the term 'interface' describes the way a certain service is used, but not how it is implemented. An interface should be understood as a number of operations that can be called when using a program component. By means of an interface, the features offered by a program component can be used. In practice, the features described in the interface must be available and ready to be called during processing.
  • the calls can be direct calls, such as for example Java Reflection and C# Reflection, or remote calls, RPC (Remote Procedure Call), with any possible structure, for instance CORBA/IIOP (Common Object Request Broker Architecture/Internet Inter-ORB Protocol) or RMI (Remote Method Invocation).
  • RPC Remote Procedure Call
  • CORBA/IIOP Common Object Request Broker Architecture/Internet Inter-ORB Protocol
  • RMI Remote Method Invocation
  • the information transmitted to the program components can be for instance parsed source data or static data, fed in the program component, or it can be a program call without parameters or some information indirectly connected to the source data, such as the size of the source data.
  • the source data 301 that should be treated in the program component 304 is fed to the processing component 303.
  • the source data 301 means, according to the invention, data in the XML form.
  • the processing component 303 also needs the information contained by MAP 302.
  • MAP 302 there are defined the employed program components 304 and their interfaces. MAP 302 also contains the description of the employed source data 301. The program to be run is created by means of MAP 302, and MAP contains the information that tells the processing component 303 how the source data 301 is run for each program component 304.
  • the processing of the source data 301 proper according to the instructions of MAP 302 is performed so that the processing component 303 transmits to each program component 304 separately the part that is meant for it.
  • the program components 304 are not necessarily bound to each other in any way.
  • the processing component 303 also takes care of error processing and of transmitting data and events between the program components. Consequently, during a run, the arrangement according to the invention takes care of the processing of the source data 302 and feeds, on the basis of the information contained in MAP 302, the desired information in the desired form to the program components 304 and uses the program components 304 in a desired way for processing this information. Owing to this structure, in the processing of the data there can be used program components that were not originally designed for processing said source data.
  • new program components can be designed so that they only contain an application logic that is independent of the source data, by which application logic the data should then be processed. This again improves the reusage prospects of the program components and thus improves the effectiveness of the program construction and the quality of said programs.
  • a given part of MAP always deals with a given program component. If there should be added new parts to be processed by the program component or the program, it is possible, by modifying MAP, to obtain for instance a new XML document to be processed, wherefore there are not needed any heavy applications in between. It is also possible to add new features for processing source data in an existing program only by changing MAP.
  • MAP MAP-like program components
  • the definition can be for instance the following XML definition, where the class to be used is defined as a "java.lang.StringBuffer", i.e. a character string in the Java language, its constructor and one method "append" for this class as follows:
  • 'Class' is an abstract concept, and 'instance' is its practical occurrence, i.e. an available occurrence of a class.
  • 'instance' is its practical occurrence, i.e. an available occurrence of a class.
  • the method "append” adds the character string to the instance of the Stringbuffer class.
  • Next MAP defines the structure of the source data, i.e. gives an exact description of the source data to be fed in.
  • source data in the XML language, there is defined an element called "stringdata” and an attribute called “value” contained therein, as follows:
  • MAP contains detailed information as to how the above defined source data in the XML language should be processed.
  • MAP there also is collected the running order and the mutual relations of the program components in a tree structure.
  • MAP also reports all classes and files used in the processing.
  • MAP is a kind of meta-ini file of the program and tells what program components the program uses and how.
  • MAP contains information of how the running of the program should be controlled.
  • the functions can be defined as follows:
  • MAP Owing to MAP, in the employed program components there can be fed information in the required form irrespective of the form of the original source data.
  • MAP must be defined separately for each application. If MAP is stored in the XML file, parts of the MAP description can be used when making a new MAP description.
  • a graphic user interface can be constructed in order to facilitate the creation of MAP.
  • DTD document type definition
  • the init element contained in the example includes all such object elements that are common for all program components to be run.
  • the object elements to be loaded for each program component separately are included in the enginelnit element.
  • This kind of object element represents the form
  • the described object element records the object restored by the element contained therein and stores its attribute in a location defined by the value of the attribute "id" thereof. Thus the information can, on the basis of the name defined in the attribute "id", be retrieved for further usage.
  • the element class restores the class definition, i.e. the class constructor restored by the constructor element, by means of which there can later be created new instances of said class.
  • the method element restores the method of a given class that is desired to be put to use. By means of said object, the method in question can also be used later on.
  • the instance element returns the desired class instance as an object.
  • the methodCall element returns the result of a method call.
  • the lifetime of the objects in the memory is defined on the basis of the element under which the object element is defined.
  • Objects defined under the init element are kept in the memory as long as the processing component (engine) exists.
  • Objects defined under the enginelnit element are kept in the memory as long as a single source data is being processed.
  • Objects defined under the element elements live as long as the element in question is being processed, i.e. as long as the element still has left action elements to be processed.
  • a described element element could be for instance as follows:
  • an element element contains object elements and action elements needed by the element in question.
  • the action elements there are defined the procedures performed by the element in different situations.
  • the element element returns the values returned by the action element.
  • the attribute "name” defines for which element said rules apply.
  • the attribute "name " may contain a path reference (XPath) instead of a mere element name.
  • XPath path reference
  • Now different elements can be referred to, so that their logical connection is taken into account. For example, a distinction can be made whether the attribute "name " is located under the element receiver or under the element transmitter.
  • the action element contains the actions that are performed with the element in question.
  • MAP 404 there is created MAP 404.
  • the original MAP information can be contained in the processing component, or it can be loaded from an external source, for instance from the XML document 401 as is illustrated in figure 4.
  • the MAPfactory 402 reads the MAP information 401 provided in XML form.
  • all original MAP information 401 is put to use by means of the parser 403.
  • the type of the employed parser is not important from the point of view of the invention, which means that it can be any type of parser that is best suited for the purpose in question, for instance a SAX parser.
  • the MAP 404 proper is created by means of the original MAP information 401, the MAPfactory 402 and the parser 403.
  • the lower row in the drawing describes in more detail the operation of the invention which was already discussed with reference to figure 3.
  • the source data 405 in XML form is first fed to the EngineFactory 406, which forms the tree to be run, i.e. the EngineTree 407. Now the EngineFactory 406 obtains at its disposal the desired parts of the source data 405 by means of the employed parser 407. If a SAX parser is used at step 407, the EngineFactory 406 must first collect a sufficient amount of SAX events in order to know which pieces of the MAP information are needed.
  • the parser 407 can be replaced by a particular speed-optimized parser that fetches, on the basis of the information contained by MAP 404, only those parts of the source data 405 in the XML form that are needed in order to run the desired program components.
  • Speed is important for example in real-time systems, such as in mobile services.
  • MAP 404 transmits to the EngineFactory 406 information as to what kind of program the program to be run should be. On the basis of the obtained information, the EngineFactory 406 forms an EngineTree 408, which is a tree-like structure. Thereafter the program contained by the EngineTree 408 can be run by means of the EngineRunner 409. MAP 404 transmits to the EngineTree 408 a pointer to itself. By means of said pointer, the EngineTree 408 can point directly to MAP 404. When the EngineTree 408 has pointers to the elements of MAP 404, the EngineTree 408 receives the required running code directly from MAP 404.
  • the source data 405 in the XML form is parsed according to the created MAP 404.
  • the parsing of the source data 405 and MAP 404 operate together, so that there is first searched the root element of the XML source data 405, and then the MAP 404 is asked how it should be processed and what information of the source data 405 there is next required.
  • the parsing is continued as far as this information, and always when the right piece of information is found, an inquiry is sent to the MAP 404 in order to find out how it should be processed.
  • Parts of the source data 405 can be run by the EngineRunner 409 already before the whole of the source data 405 is available and parsed. This means that as the source data 405, there can be processed for instance a data flow in the XML form.
  • the program contained by the EngineTree 408 can be run by the EngineRunner 409 simultaneously as the preceding EngineFactory 406 is only creating the EngineTree 408.
  • the EngineTree 408 waits for running instructions and the process continues, when the necessary information is at hand.
  • the EngineTree 408 transmits information further to chosen program components, which can be any suitable programs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)
PCT/FI2002/000212 2001-03-16 2002-03-15 Method and apparatus for processing information WO2002075533A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20010536A FI20010536A (sv) 2001-03-16 2001-03-16 Metod och apparatur för att handla information
FI20010536 2001-03-16

Publications (1)

Publication Number Publication Date
WO2002075533A1 true WO2002075533A1 (en) 2002-09-26

Family

ID=8560763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2002/000212 WO2002075533A1 (en) 2001-03-16 2002-03-15 Method and apparatus for processing information

Country Status (2)

Country Link
FI (1) FI20010536A (sv)
WO (1) WO2002075533A1 (sv)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1903452A1 (en) * 2006-09-25 2008-03-26 Software Ag Method and system for processing the input in an XML form
AU2003291909B2 (en) * 2002-12-26 2008-11-20 Citrix Systems International Gmbh System and method of creating and communicating with component based wireless applications

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5953526A (en) * 1997-11-10 1999-09-14 Internatinal Business Machines Corp. Object oriented programming system with displayable natural language documentation through dual translation of program source code
US6012098A (en) * 1998-02-23 2000-01-04 International Business Machines Corp. Servlet pairing for isolation of the retrieval and rendering of data
US6083276A (en) * 1998-06-11 2000-07-04 Corel, Inc. Creating and configuring component-based applications using a text-based descriptive attribute grammar
WO2001035218A1 (en) * 1999-11-09 2001-05-17 Bear River Associates Inc. Method for modifying data and/or code represented in one language by a computer program written in a second language
WO2002005089A1 (en) * 2000-07-10 2002-01-17 Canon Kabushiki Kaisha Delivering multimedia descriptions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5953526A (en) * 1997-11-10 1999-09-14 Internatinal Business Machines Corp. Object oriented programming system with displayable natural language documentation through dual translation of program source code
US6012098A (en) * 1998-02-23 2000-01-04 International Business Machines Corp. Servlet pairing for isolation of the retrieval and rendering of data
US6083276A (en) * 1998-06-11 2000-07-04 Corel, Inc. Creating and configuring component-based applications using a text-based descriptive attribute grammar
WO2001035218A1 (en) * 1999-11-09 2001-05-17 Bear River Associates Inc. Method for modifying data and/or code represented in one language by a computer program written in a second language
WO2002005089A1 (en) * 2000-07-10 2002-01-17 Canon Kabushiki Kaisha Delivering multimedia descriptions

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2003291909B2 (en) * 2002-12-26 2008-11-20 Citrix Systems International Gmbh System and method of creating and communicating with component based wireless applications
US8402432B2 (en) 2002-12-26 2013-03-19 Research In Motion Limited System and method of creating and communicating with component based wireless applications
EP1903452A1 (en) * 2006-09-25 2008-03-26 Software Ag Method and system for processing the input in an XML form
US9229921B2 (en) 2006-09-25 2016-01-05 Software Ag Method and system for processing the input in a XML form

Also Published As

Publication number Publication date
FI20010536A0 (sv) 2001-03-16
FI20010536A (sv) 2002-09-17

Similar Documents

Publication Publication Date Title
US7650590B2 (en) Flexible code generation
US6941560B1 (en) XML-based integrated services event system
US7194683B2 (en) Representing and managing dynamic data content for web documents
CN111459889B (zh) 一种用于物联网平台的设备数据模型生成方法和装置
US5953526A (en) Object oriented programming system with displayable natural language documentation through dual translation of program source code
US7574692B2 (en) Method for building component-software for execution in a standards-compliant programming environment
US9575939B2 (en) Linked code generation report
Röttger et al. Cqml+: Enhancements to cqml
Thöne et al. Process-oriented, flexible composition of web services with UML
Neumann et al. {XOTcl—An}{Object-Oriented} Scripting Language
US7426723B1 (en) Classfile conversion into an organization of objects, and modification thereof, to effect bytecode modification
CA2598317C (en) Mobile device having extensible software for presenting server-side applications, software and methods
Braem et al. Isolating process-level concerns using Padus
EP1116105A1 (en) Text object compilation method and system
Pessemier et al. A component-based and aspect-oriented model for software evolution
Vieira et al. Analyzing dependencies in large component-based systems
US7743367B1 (en) Registration method for supporting bytecode modification
US6829758B1 (en) Interface markup language and method for making application code
Südholt A model of components with non-regular protocols
JP2006510955A (ja) Xml処理タスクの管理および実行のためのコンテキスト独立フレームワークのシステムおよび方法
US20040153871A1 (en) Automatic analysis of the properties of a system based on runtime logs
WO2002075533A1 (en) Method and apparatus for processing information
Gschwind Adaptation and composition techniques for component-based software engineering
KR100420103B1 (ko) 엑스엠엘 기반의 웹 어플리케이션 구현 시스템 및 방법
JP2006236375A (ja) Webアプリケーション開発方法、開発支援システム、および該方法に係るプログラム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP