Ȩ > Ç¥ÁØÈ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ
Ç¥ÁعøÈ£ | TTAK.KO-10.1471 | ±¸Ç¥ÁعøÈ£ | |
---|---|---|---|
Á¦°³Á¤ÀÏ | 2023-12-06 | ÃÑÆäÀÌÁö | 28 |
ÇѱÛÇ¥Áظí | OOXML ¹®¼ ¸ÞŸµ¥ÀÌÅ͸¦ µ¥ÀÌÅͺ£À̽º ½ºÅ°¸¶¿¡ ¸ÅÇÎÇϱâ À§ÇÑ º¯È¯ ÀýÂ÷ | ||
¿µ¹®Ç¥Áظí | Transformation Procedure for Mapping OOXML Document Metadata to a Database Schema | ||
Çѱ۳»¿ë¿ä¾à | ÇöÀç È°¿ëµÇ°í ÀÖ´Â »ó¿ë ¹®¼ ½ºÆåÀ¸·Î´Â OOXML(Office Open XML; ISO/IEC 29500), OWPML(Open Word-Processor Markup Language; KS X 6101) µîÀÌ ÀÖ´Ù. °¢ ½ºÆåÀ» ±â¹ÝÀ¸·Î ÇÏ°í ÀÖ´Â ¼ÒÇÁÆ®¿þ¾î¿¡¼ ÀÛ¼ºµÈ ¹®¼´Â ½ºÆåÀÇ ÀÇ¹Ì °ªÀ̳ª ´ÜÀ§ µî ´Ù¼ö ¿ä¼Ò°¡ Ÿ ½ºÆå°ú ȣȯ¼ºÀÌ ¶³¾îÁø´Ù. ½ÉÁö¾î ±âÁ¸ÀÇ ½ºÆåÀº ¹®¼ ³»¿¡ Á¸ÀçÇÏ´Â °´Ã¼º°·Î µ¥ÀÌÅÍ°¡ ÀúÀåµÇ´Â ±¸Á¶ÀÌ°í, ¼ÒÇÁÆ®¿þ¾îº° ÃÖÀûÈ ¹æ½ÄÀÌ »óÀÌÇϹǷΠ¹®¼ÀÇ ¿øÈ°ÇÑ °øÀ¯ ¹× ÀÛ¾÷À» À§Çؼ´Â ÇØ´ç ¹®¼°¡ ÀÛ¼ºµÈ ¼ÒÇÁÆ®¿þ¾î¸¦ °ÅÃľ߸¸ ¿ÂÀüÇÏ°Ô È°¿ëÇÒ ¼ö ÀÖ´Ù.
À§¿Í °°Àº ¹®Á¦ »óȲÀ» ÇØ°áÇϱâ À§ÇØ, ÀÌ Ç¥ÁØ¿¡¼´Â »óÀÌÇÑ ½ºÆå ±â¹ÝÀÇ ¹®¼µéÀ» À¯¿¬ÇÏ°Ô È°¿ëÇÒ ¼ö Àִ ü°è¸¦ Á¦¾ÈÇÏ°íÀÚ ÇÑ´Ù. ¿ì¼± ±âÁ¸ »ó¿ë ¹®¼ÀÇ ¸ÞŸµ¥ÀÌÅÍ ¿ä¼Ò¸¦ ºÐ¼® ¹× Á¤ÀÇÇÏ°í ´ÜÀÏ ½ºÆåÀ¸·Î º´ÇÕ¡¤È°¿ëÇÒ ¼ö ÀÖµµ·Ï º¯È¯ °úÁ¤À» ¼³°èÇÑ´Ù. ÀÌ Ç¥ÁØ¿¡¼ Á¦¾ÈÇÒ ÀÇ¹Ì ´ÜÀ§·Î ºÐÀýµÈ ´ÜÀÏ ½ºÆå ±â¹Ý ¹®¼ ¿ä¼Ò¸¦ Åä´ë·Î, ±âÁ¸ »ó¿ë ¹®¼ ¿ä¼Ò¸¦ µ¥ÀÌÅͺ£À̽ºÈ µÈ Á¤º¸·Î º¯È¯ÇÒ ¼ö ÀÖ°Ô µÈ´Ù. »ý¼º ½ºÆå¿¡ ±¸¾Ö¹ÞÁö ¾Êµµ·Ï º¯È¯ °úÁ¤À» °ÅÃÄ µ¥ÀÌÅͺ£À̽ºÈµÈ Á¤º¸¸¦ ¹ÙÅÁÀ¸·Î, ¸ÞŸµ¥ÀÌÅ͸¦ ÃßÃ⡤Á¤º¸ÈÇÏ°í À̸¦ ´Ù¾çÇÑ ºÐ¾ßÀÇ ¼ºñ½ºµé°ú ¿¬°èÇÒ ¼ö ÀÖµµ·Ï ÇÏ¿© ¹®¼¾È ÄÜÅÙÃ÷ÀÇ È°¿ëµµ¸¦ ³ôÀÏ ¼ö ÀÖ´Ù. À§¿Í °°Àº Áö½Ä ÆÄÀÌÇÁ¶óÀÎÀ» ÅëÇØ ¹®¼ÀÇ ¸ÞŸµ¥ÀÌÅÍ¿Í ¿ÜºÎ µ¥ÀÌÅÍ ±â¹Ý Áö½Ä ±×·¡ÇÁ¸¦ ±¸ÃàÇÏ´Â µî È¿À²¼º Áõ´ë ÀÛ¾÷À» ¼öÇàÇÒ ¼ö ÀÖ°Ô µÇ¸ç, ¹®¼ ÀÛ¾÷ ȯ°æÀÇ È¿À²¼ºÀ» °íÃëÇÒ ¼ö ÀÖ´Ù. |
||
¿µ¹®³»¿ë¿ä¾à | The current commercial document specifications include OOXML (Office Open XML; ISO/IEC 29500), OWPML (Open Word-Processor Markup Language; KS X 6101) and so on. However, documents created by specific software based on each specification often lack compatibility with other specifications in terms of values and units of meaning, among other elements. Furthermore, existing specifications store data for each object in a document and the optimization methods for each software are different, making it necessary to use the software in which the document was created to fully utilize the document for smooth sharing and collaboration.
To address these problems, this standard proposes a system that can flexibly utilize documents based on different specifications. Firstly, the elements of existing document specifications are analyzed and defined, and a conversion process is designed to merge and utilize them as a single specification. Based on the single specification-based document elements segmented by the proposed meaning units in this standard, the elements of existing documents can be converted into information stored in a database. By undergoing the transformation process, information that has been database-stored serves as the foundation, allowing extraction and digitization of metadata. This enables linkage with services across various domains, enhancing the utility of document content. Through this knowledge pipeline, it will be possible to perform tasks that increase efficiency, such as constructing meta-data for documents and external data-based knowledge graphs, thereby enhancing the efficiency of electronic document work environments. |
||
±¹Á¦Ç¥ÁØ | |||
°ü·ÃÆÄÀÏ | TTAK.KO-10.1471 (1).pdf |
- ÀÌÀü
- 3rd Generation Partnership Project;Technical Specification Group Radio Access Network;User Equipment (UE) conformance specification for UE positioning; Part 5: Test scenarios and assistance data(Release 17)
- ´ÙÀ½
- 3rd Generation Partnership Project;Technical Specification Group Radio Access Network;NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone(Release 16)