KR20040043290A - BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML - Google Patents
BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML Download PDFInfo
- Publication number
- KR20040043290A KR20040043290A KR1020020071511A KR20020071511A KR20040043290A KR 20040043290 A KR20040043290 A KR 20040043290A KR 1020020071511 A KR1020020071511 A KR 1020020071511A KR 20020071511 A KR20020071511 A KR 20020071511A KR 20040043290 A KR20040043290 A KR 20040043290A
- Authority
- KR
- South Korea
- Prior art keywords
- markup language
- module
- bml
- stowage plan
- xml
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Document Processing Apparatus (AREA)
Abstract
Description
본 발명은 XML(eXtensible Markup Language) 기반의 적부도(Stowage Plan;積付圖) 파일을 생성하기 위하여, 적부도(Stowage Plan; 積付圖)를 위한 적부도(Stowage Plan; 積付圖) 마크업 언어를 XML Schema(eXtensible Markup Language Schema) 로 설계한 기술에 관한 것이다.The present invention relates to a Stability Plan (Stowage Plan) mark for a Stability Plan (Stewage Plan) file, in order to generate a suitability plan file based on XML (eXtensible Markup Language). It is about a technique for designing a language up to XML Schema (eXtensible Markup Language Schema).
종래 기술로는 SMDG(Shipping Message Development Group) 라는 단체에서 적부도(Stowage Plan; 積付圖)에 관한 파일의 구조를 정의한 BAPLIE 라는 파일 포맷(File Format)이 개발되어 있고, X12 라는 단체에서 적부도(Stowage Plan; 積付圖)에 관한 파일 구조를 정의한 TDCC 324 라는 파일 포맷(File Format) 이 존재한다. 하지만 이 두가지 종래 기술 모두, 표준 문서를 기술할 수 있는 메타 언어(Meta Language; 언어를 기술하는 언어)가 아닌 자체적인 룰(rule)에 의해 파일 구조를 정의하고 있기 때문에, 여러 소프트웨어 개발 회사에서 이를 응용한 소프트웨어(Software)를 개발하기는 쉽지 않은 실정이다. 또한, 그 구조에 맞게 생성된 파일들이 올바르게 생성되었는지를 확인할 수 있는 방법을 제공하지 못하기 때문에, 정해진 룰(rule)에 맞게 파일이 생성되었다고 보장하기도 힘들다.In the prior art, a file format called BAPLIE has been developed by a group called SMDG (Shipping Message Development Group), which defines a structure of a file related to a stowage plan. There is a file format called TDCC 324 which defines a file structure for a (Stowage Plan). However, because both of these prior arts define the file structure by their own rules, rather than the meta-language for describing standard documents, many software development companies do so. Developing software is not easy. In addition, since it does not provide a method for checking whether the files generated according to the structure are correctly generated, it is difficult to guarantee that the files are generated according to a predetermined rule.
현존하는 표준 메타 언어(Meta Language)로는 DTD(Document Type Definition)와 XML Schema(eXtended Markup Language Schema)가 대표적이다. 이 두가지 기술은 XML(eXtended Markup Language) 문서를 생성하기 위한 구조를 정의하는데 사용되며, 플랫폼(Platform)과 개발언어(Development Language)에 독립적이다. 또한, 생성된 문서의 유효성(Validation)을 검사할 수 있는 구조로 되어 있어 파일 구조를 기술하는데 적합하다. 하지만, DTD(Document Type Definition)는 문법 자체가 XML Schema(eXtended Markup Language Schema)에 비해상당히 복잡하고, XML Schema(exTensible Markup Language Schema)에 비해 제공되는 데이터 타입(Data Type)도 적으며, 확장 마크업 언어(XML; eXtensible Markup Language) 형태로 되어 있지 않으므로, 이를 다루기 위한 별도의 지식이 필요하다는 것이 가장 큰 단점이다.Existing standard meta languages include Document Type Definition (DTD) and XML Schema (eXtended Markup Language Schema). These two techniques are used to define the structure for generating XML (eXtended Markup Language) documents, and are independent of the platform and development language. In addition, it is a structure that can check the validity (Validation) of the generated document is suitable for describing the file structure. However, the DTD (Document Type Definition) has a grammar that is considerably more complicated than XML Schema (eXtended Markup Language Schema), and also provides fewer data types than XML Schema (exTensible Markup Language Schema). The biggest drawback is that it does not have the form of XML (eXtensible Markup Language), which requires additional knowledge to deal with it.
본 발명은 상기와 같은 종래 기술의 문제점을 해결하기 위하여 안출된 것으로서, XML Schema(eXtended Markup Language Schema) 기반의 적부도(Stowage Plan; 積付圖) 마크업 언어를 설계함으로써, 확장 마크업 언어(XML; eXtended Markup Language) 기반의 적부도(Stowage Plan; 積付圖) 파일의 생성 방법을 제공하는데 그 목적이 있다.The present invention has been made to solve the above problems of the prior art, by designing a Markup Language (Stowage Plan) markup language based on XML Schema (eXtended Markup Language Schema), An object of the present invention is to provide a method of generating a Stowage Plan (XML) file based on eXtended Markup Language (XML).
[도 1] High Level Class Diagram of BML™ (적부도 마크업 언어의 상위 레벨 클래스 다이어그램)Figure 1 High Level Class Diagram of BML ™ (high level class diagram of adequacy markup language)
적부도 마크업 언어인 BML™(Bayplan Markup Language)은 크게 interchangerHeader, message, interchangeTrailer 의 세부분으로 구성되어 있으며, 이 중 핵심인 message 부분은 다시 messageHeader, messageBody, messageTrailer 나뉘어져 있다.Bayplan Markup Language (BML ™), an aptitude markup language, is composed of three parts: interchangerHeader, message, and interchangeTrailer, and the message part, which is the core, is divided into messageHeader, messageBody and messageTrailer.
[도 2] Detailed view of messageBody (messageBody 모듈의 상세 뷰 다이어그램)Figure 2 Detailed view of messageBody (detailed view diagram of the messageBody module)
message 의 주요 구성 요소인 messageBody 는 주요 정보들을 담고 있는 tranport 와 containers, 그리고 부가적인 정보를 담고 있는 beginningOfMessage, dateTimePeriod, reference, nameAndAddress 로 구성되어 있다.The main component of message, messageBody, consists of a tranport and containers that contain key information, beginningOfMessage, dateTimePeriod, reference, and nameAndAddress that contain additional information.
[도 3] Detailed view of transport (transport 모듈의 상세 뷰 다이어그램)[Figure 3] Detailed view of transport (detailed view diagram of the transport module)
transport 모듈은 placeLocationIdentification, detailsOfTransport,dateTimePeriod, reference, freeText 로 나뉘어져 있고, placeLocationIdentification 은 1~9번, dateTimePeriod 는 1~99번, reference 는 0~1번, freeText 는 0~1번까지 반복되며 나타날 수 있다.The transport module is divided into placeLocationIdentification, detailsOfTransport, dateTimePeriod, reference, and freeText.The placeLocationIdentification can be repeated 1 ~ 9 times, dateTimePeriod 1 ~ 99 times, reference 0 ~ 1 times, and freeText 0 ~ 1 times.
[도 4] Detailed view of containers (containers 모듈의 상세 뷰 다이어그램)Figure 4 Detailed view of containers (detailed view diagram of the containers module)
containers 는 container 하나로 구성되어 있고, container 는 다시 placeLocationIdentification, goodsItemsDetails, natureOfCargo, reference, ,equipment, dangerousGoodsInformation, rangeDetails, temperature, dimensions, measurements, freeText 로 구성되어 있다. 또한, placeLocationIdentification 은 0~9번, goodsItemDetails 는 0~1번, natureOfCargo 는 0~9번, reference 는 1~9번, equipment 는 1~9번, dangerousGoodsInformation 은 0~999번, rangeDetails 는 0~1번, temperature 는 0~1번, dimensions 는 0~9번, measurement 는 1~9번까지 반복되며 나타날 수 있다.The containers consist of one container, which in turn consists of placeLocationIdentification, goodsItemsDetails, natureOfCargo, reference,, equipment, dangerousGoodsInformation, rangeDetails, temperature, dimensions, measurements, and freeText. Also, placeLocationIdentification is 0 ~ 9, goodsItemDetails 0 ~ 1, natureOfCargo 0 ~ 9, reference 1 ~ 9, equipment 1 ~ 9, dangerousGoodsInformation 0 ~ 999, rangeDetails 0 ~ 1 The temperature can be repeated 0 ~ 1 times, the dimensions 0 ~ 9 times and the measurement 1 ~ 9 times.
[도 5] BML™ Design Specification (적부도 마크업 언어 설계 명세)FIG. 5 BML ™ Design Specification (Adequacy Markup Language Design Specification)
BML™ (적부도 마크업 언어) 설계 명세의 전체이며, 또 다른 언어를 기술할 수 있는 meta language 인 XML Schema 문법에 맞게 작성되었다.BML ™ (Adequacy Markup Language) A complete specification of the design, written in XML Schema syntax, a meta language for describing another language.
앞서 설명한 바와 같은 목적을 달성하기 위한 본 발명에 따르면, 적부도(Stowage Plan; 積付圖) 마크업 언어의 구조는 아래의 35가지 모듈(Module)들로 구성된다. 이 모듈은 UN/Edifact directory D00B 의 구조와 일치하며, 이 구조를 적부도(Stowage Plan; 積付圖) 마크업 언어 설계에 매핑(mapping) 함으로서 종래 기술인 BAPLIE 파일에서 적부도(Stowage Plan; 積付圖) 마크업 언어로 기술된 파일로의 이전을 용이하게 한다. 또한, 적부도(Stowage Plan; 積付圖) 마크업 언어로 생성된 적부도 파일이 플랫폼(Platform) 과 개발 언어(Development Language)에 의존적이지 않게 하기 위하여, 확장 마크업 언어(XML; eXtensible Markup Language) 기반의 적부도(Stowage Plan; 積付圖) 파일을 생성하고 있다.According to the present invention for achieving the object as described above, the structure of the Stowage Plan markup language is composed of the following 35 modules (Module). This module is consistent with the structure of UN / Edifact directory D00B and maps this structure to the Stowage Plan markup language design by mapping the Stowage Plan in the prior art BAPLIE file. V) Facilitate the transfer to files written in markup language. In addition, in order to ensure that aptitude files created in the Stowage Plan markup language are not dependent on the Platform and Development Language, an eXtensible Markup Language (XML) is used. We are creating a stochastic plan file.
이 발명의 주요 구성 요소인 적부도(Stowage Plan; 積付圖) 마크업 언어를 구성하고 있는 35가지 모듈의 내용은 다음과 같다. (도5 참조)The contents of the 35 modules that make up the Stowage Plan markup language, which is the main component of the present invention, are as follows. (See Fig. 5)
(1) InterchangeHeader 모듈(1) InterchangeHeader Module
interchangeHeader, syntaxInformation, senderIdentification, recipientIdentification, preparationInformation, interchangeControlReference, communicationsAgreementId 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements: interchangeHeader, syntaxInformation, senderIdentification, recipientIdentification, preparationInformation, interchangeControlReference, and communicationsAgreementId.
(2) Message 모듈(2) Message module
message 엘리먼트(Element) 하나로 구성되어 있다.It consists of one message element.
(3) Message Header 모듈(3) Message Header Module
messageHeader, messageReferenceNumber, messageTypeInformation 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: messageHeader, messageReferenceNumber, and messageTypeInformation.
(4) Message Body 모듈(4) Message Body Module
messageBody 엘리먼트(Element) 하나로 구성되어 있다.messageBody It consists of one element.
(5) Beginning Of Message 모듈(5) Beginning Of Message Module
beginningOfMessage, documentMessageName, documentMessageIdentification, messageFunctionCode, responseTypeCode 의 5개의 엘리먼트(Element)로 구성되어 있다.It consists of five elements: beginningOfMessage, documentMessageName, documentMessageIdentification, messageFunctionCode, and responseTypeCode.
(6) Date/Time/Period 모듈(6) Date / Time / Period Module
dateTimePeriod 엘리먼트(Element) 하나로 구성되어 있다.dateTimePeriod Consists of one element.
(7) Referendce 모듈(7) Referendce module
reference 엘리먼트(Element) 하나로 구성되어 있다.It consists of one reference element.
(8) Name And Address 모듈(8) Name And Address Module
nameAndAddress 엘리먼트(Element) 하나로 구성되어 있다.nameAndAddress Consists of one element.
(9) Transport 모듈(9) Transport module
transport 엘리먼트(Element) 하나로 구성되어 있다.It consists of one transport element.
(10) Details Of Transport 모듈(10) Details Of Transport Module
detailsOfTransport, transportStageCodeQualifier, meansOfTransportJourneyIdentifier, carrier, transitDirectionIndicatorCode, excessTransportInformation, transportIdentification 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements: detailsOfTransport, transportStageCodeQualifier, meansOfTransportJourneyIdentifier, carrier, transitDirectionIndicatorCode, excessTransportInformation, and transportIdentification.
(11) Place/Location Identification 모듈(11) Place / Location Identification Module
placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, relatedLocationTwoIdentification relationCode 의 6개의 엘리먼트(Element)로 구성되어 있다.It consists of six elements: placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, and relatedLocationTwoIdentification relationCode.
(12) Date/Time/Period 모듈(12) Date / Time / Period Module
dateTimePeriod 엘리먼트(Element) 하나로 구성되어 있다.dateTimePeriod Consists of one element.
(13) Reference 모듈(13) Reference module
reference 엘리먼트(Element) 하나로 구성되어 있다.It consists of one reference element.
(14) Free Text 모듈(14) Free Text Module
freeText 엘리먼트(Element) 하나로 구성되어 있다.It consists of a single freeText element.
(15) Containers 모듈(15) Containers Module
containers 엘리먼트(Element) 하나로 구성되어 있다.It consists of a single container element.
(16) Container 모듈(16) Container Module
container 엘리먼트(Element) 하나로 구성되어 있다.It consists of a single container element.
(17) Place/Location Identification 모듈(17) Place / Location Identification Module
placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, relatedLocationTwoIdentification, relationCode 의 6개의 엘리먼트(Element)로 구성되어 있다.It consists of six elements: placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, relatedLocationTwoIdentification, and relationCode.
(18) Goods Item Details 모듈(18) Goods Item Details Module
goodsItemDetails, goodsItemNumber, numberAndTypeOfPackages1, numberAndTypeOfPackages2, numberAndTypeOfPackages3, numberAndTypeOfPackages4, numberAndTypeOfPackages5 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements of goodsItemDetails, goodsItemNumber, numberAndTypeOfPackages1, numberAndTypeOfPackages2, numberAndTypeOfPackages3, numberAndTypeOfPackages4, and numberAndTypeOfPackages5.
(19) Nature of Cargo 모듈(19) Nature of Cargo Module
natureOfCargo 엘리먼트(Element)로 구성되어 있다.Consists of the natureOfCargo element.
(20) Free Text 모듈(20) Free Text Module
freeText, textSubjectCodeQualifier, freeTextFunctionCode, textReference, textLiteral, languageNameCode, freeTextFormatCode 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements: freeText, textSubjectCodeQualifier, freeTextFunctionCode, textReference, textLiteral, languageNameCode, and freeTextFormatCode.
(21) Measurements 모듈(21) Measurements module
measurements, measurementPurposeCodeQualifier, measurementDetails, valueRange, surfaceOrLayerCode 의 5개의 엘리먼트(Element)로 구성되어 있다.It consists of five elements: measurement, measurementPurposeCodeQualifier, measurementDetails, valueRange, and surfaceOrLayerCode.
(22) Dimensions 모듈(22) Dimensions module
dimensions, dimensionTypeCodeQualifier, dimensionValue 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: dimensions, dimensionTypeCodeQualifier, and dimensionValue.
(23) Temperature 모듈(23) Temperature module
temperature, temperatureTypeCodeQualifier, temperatureSetting 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: temperature, temperatureTypeCodeQualifier, and temperatureSetting.
(24) Range Details 모듈(24) Range Details Module
rangeDetails, rangeTypeCodeQualifier, range 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: rangeDetails, rangeTypeCodeQualifier, and range.
(25) Place/Location Identification 모듈(25) Place / Location Identification Module
placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, relatedLocationTwoIdentification, relationCode 의 6개의 엘리먼트(Element)로 구성되어 있다.It consists of six elements: placeLocationIdentification, locationFunctionCodeQualifier, locationIdentification, relatedLocationOneIdentification, relatedLocationTwoIdentification, and relationCode.
(26) Reference 모듈(26) Reference Module
reference 엘리먼트(Element) 하나로 구성되어 있다.It consists of one reference element.
(27) Equipment 모듈(27) Equipment Module
equipment 엘리먼트(Element) 하나로 구성되어 있다.equipment It consists of one element.
(28) Equipment Details 모듈(28) Equipment Details Module
equipmentDetails, equipmentTypeCodeQualifier, equipmentIdentification, equipmentSizeAndType, equipmentSupplierCode, equipmentStatusCode, fullOrEmptyIndicatorCode 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements: equipmentDetails, equipmentTypeCodeQualifier, equipmentIdentification, equipmentSizeAndType, equipmentSupplierCode, equipmentStatusCode, and fullOrEmptyIndicatorCode.
(29) Equipment Attached 모듈(29) Equipment Attached Module
equipmentAttached, equipmentTypeCodeQualifier, equipmentIdentification 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: equipmentAttached, equipmentTypeCodeQualifier, equipmentIdentification.
(30) Name And Address 모듈(30) Name And Address Module
nameAndAddress, partyFunctionCodeQualifier, partyIdentificationDetails, nameAndAddressDescription, partyName, street, cityName, countrySubEntityDetails, postalIdentificationCode, countryNameCode 의 10개의 엘리먼트(Element)로 구성되어 있다.It consists of ten elements: nameAndAddress, partyFunctionCodeQualifier, partyIdentificationDetails, nameAndAddressDescription, partyName, street, cityName, countrySubEntityDetails, postalIdentificationCode, countryNameCode.
(31) Dangerous Goods Information 모듈(31) Dangerous Goods Information Module
dangerousGoodsInformation 엘리먼트(Element) 하나로 구성되어 있다.dangerousGoodsInformation Consists of one element.
(32) Dangerous Goods 모듈(32) Dangerous Goods Module
dangerousGoods, dangerousGoodsRegulationCode, hazardCode, UNDGInformation, dangerousGoodsShipmentFlashpoint, packingDangerLevelCode, emergencyProcedureForShipsIdentifier, hazardMedicalFirstAidGuideIdentifier, transportEmergencyCardIdentifier, hazardIdentificationPlacardDetails,dangerousGoodsLevel, hazardMedicalFirstAidGuideIdentifier, packingInstructionTypeCode, hazardousMeansOfTransportCategoryCode, hazardousCargoTransportAuthorisationCode 의 15개의 엘리먼트(Element)로 구성되어 있다.DangerGoods, dangerousGoodsRegulationCode, hazardCode, UNDGInformation, dangerousGoodsShipmentFlashpoint, packingDangerLevelCode, emergencyProcedureForShipsIdentifier, hazardMedicalFirstAidGuideIdentifier, transportEmergencyCardIdentifier, hazardIdentificationPlacardDetails, dangerousGoodsLevel, hazardMedication
(33) Free Text 모듈(33) Free Text Module
freeText, textSubjectCodeQualifier, freeTextFunctionCode, textReference, textLiteral, languageNameCode, freeTextFormatCode 의 7개의 엘리먼트(Element)로 구성되어 있다.It consists of seven elements: freeText, textSubjectCodeQualifier, freeTextFunctionCode, textReference, textLiteral, languageNameCode, and freeTextFormatCode.
(34) Message Trailer 모듈(34) Message Trailer Module
messageTrailer, numberOfSegments, messageReferenceNumber 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: messageTrailer, numberOfSegments, and messageReferenceNumber.
(35) Interchange Trailer 모듈(35) Interchange Trailer Module
interchangeTrailer,interchangeControlCount, interchangeControlReference 의 3개의 엘리먼트(Element)로 구성되어 있다.It consists of three elements: interchangeTrailer, interchangeControlCount, and interchangeControlReference.
각각의 모듈(Module)은 하나 이상의 엘리먼트(Element)로 구성되어 있고, 각각의 엘리먼트(Element)들은 값(Value), 값 타입(Value Type), 속성(Attributes), 주석(Remarks) 등으로 구성된다. 또한, 도면에 표시되어 있는 것과 같이 각 모듈의 출현(Occurrence) 순서 및 반복 회수를 가지고 있다.Each module consists of one or more elements, and each element consists of a Value, Value Type, Attributes, Remarks, etc. . In addition, as shown in the figure, each module has an order of occurrence (Occurrence) and the number of iterations.
앞서 상세히 설명한 바와 같이 본 발명은 XML Schema 기반의 적부도(Stowage Plan; 積付圖) 마크업 언어의 설계 기술에 대한 것으로서, 이 언어의 문법에 따라 생성된 적부도(Stowage Plan; 積付圖) 파일들은 운영체제(Operating System), 데이터베이스(Database), 개발도구(Development Tools), 웹브라우져(Web Browser) 등에 의존하지 않고 중립적으로 사용될 수 있다.As described in detail above, the present invention relates to a design technique of an XML Schema-based suitability plan markup language, and is generated according to the grammar of the language. The files can be used neutrally without depending on the operating system, database, development tools, web browser, etc.
또한, 기존의 전자 문서 교환(EDI; Electronic Data Interchange)을 대치(代置)할 수 있는 XML/EDI 또는 ebXML 의 기반이 되는 전자 문서로써 활용할 수 있다.In addition, it can be used as an electronic document that is the base of XML / EDI or ebXML that can replace the existing Electronic Data Interchange (EDI).
Claims (3)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020020071511A KR20040043290A (en) | 2002-11-18 | 2002-11-18 | BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020020071511A KR20040043290A (en) | 2002-11-18 | 2002-11-18 | BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| KR20040043290A true KR20040043290A (en) | 2004-05-24 |
Family
ID=37339772
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020020071511A KR20040043290A (en) | 2002-11-18 | 2002-11-18 | BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML |
Country Status (1)
| Country | Link |
|---|---|
| KR (1) | KR20040043290A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH052574A (en) * | 1991-06-25 | 1993-01-08 | Nippon Steel Corp | Automatic preparation system for ship stowage plan of steel material |
| US6083276A (en) * | 1998-06-11 | 2000-07-04 | Corel, Inc. | Creating and configuring component-based applications using a text-based descriptive attribute grammar |
| KR20020017669A (en) * | 2000-08-31 | 2002-03-07 | 양준호 | XML-based application providing system and XML-based application recorded in computer-readable media |
| KR20020061888A (en) * | 2001-01-18 | 2002-07-25 | 박철만 | Method for developing xml application program |
| WO2002084480A2 (en) * | 2001-04-17 | 2002-10-24 | Schneider Automation | Method for graphically visualizing an automatism application and computer terminal for carrying out said method |
-
2002
- 2002-11-18 KR KR1020020071511A patent/KR20040043290A/en not_active Application Discontinuation
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH052574A (en) * | 1991-06-25 | 1993-01-08 | Nippon Steel Corp | Automatic preparation system for ship stowage plan of steel material |
| US6083276A (en) * | 1998-06-11 | 2000-07-04 | Corel, Inc. | Creating and configuring component-based applications using a text-based descriptive attribute grammar |
| KR20020017669A (en) * | 2000-08-31 | 2002-03-07 | 양준호 | XML-based application providing system and XML-based application recorded in computer-readable media |
| KR20020061888A (en) * | 2001-01-18 | 2002-07-25 | 박철만 | Method for developing xml application program |
| WO2002084480A2 (en) * | 2001-04-17 | 2002-10-24 | Schneider Automation | Method for graphically visualizing an automatism application and computer terminal for carrying out said method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Portele | Opengis® geography markup language (GML) encoding standard. Version 3.2. 1. | |
| Chaudhri et al. | XML data management: native XML and XML-enabled database systems | |
| CN104881275B (en) | A kind of electronic report forms generation method and device | |
| Williams et al. | Professional XML databases | |
| Manola et al. | RDF primer | |
| Wood | Minimising Simple XPath Expressions. | |
| Phillips et al. | CD-ROM document database standard | |
| US7139975B2 (en) | Method and system for converting structured documents | |
| US6959416B2 (en) | Method, system, program, and data structures for managing structured documents in a database | |
| Harold | Processing XML with Java: a guide to SAX, DOM, JDOM, JAXP, and TrAX | |
| US8381090B2 (en) | Dynamic expansion of data calculation scopes | |
| NZ531175A (en) | Method for adding metadata to data | |
| US7600186B2 (en) | Generating a synonym dictionary representing a mapping of elements in different data models | |
| US20130326336A1 (en) | Generating semantic structured documents from text documents | |
| US20040210881A1 (en) | Method of generating an application program interface for resource description framwork (RDF) based information | |
| KR20040043290A (en) | BML(Bayplan Markup Language) Design based on XML Schema and the media written by BML | |
| Bierman | Using XML as an Object Interchange Format | |
| Shrestha | XML Database Technology and Its Use for GML. | |
| Chase | XML primer plus | |
| Santos et al. | XBRL and the Multidimensional Data Model. | |
| Cuthbert et al. | Geography markup language (GML) v1 | |
| CN102831228A (en) | Format conversion method for isomerous extensible markup language document | |
| Moujabbir et al. | New method to parse invoice as a type the document | |
| Duda | XML models for legal documents: current polish practices and international standards | |
| Richesson et al. | Conceptual models: Definitions, construction, and applications in public health surveillance |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| A201 | Request for examination | ||
| E902 | Notification of reason for refusal | ||
| E601 | Decision to refuse application |