WO2007045084A1 - Systeme et procede de creation, de distribution et d'utilisation d'un format de connaissances portatif - Google Patents

Systeme et procede de creation, de distribution et d'utilisation d'un format de connaissances portatif Download PDF

Info

Publication number
WO2007045084A1
WO2007045084A1 PCT/CA2006/001703 CA2006001703W WO2007045084A1 WO 2007045084 A1 WO2007045084 A1 WO 2007045084A1 CA 2006001703 W CA2006001703 W CA 2006001703W WO 2007045084 A1 WO2007045084 A1 WO 2007045084A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
data structure
metadata
items
demo
Prior art date
Application number
PCT/CA2006/001703
Other languages
English (en)
Inventor
Julian Bourne
Dennis Wu
Jeff Bonnell
Eric Kar
David Gray
Kevin Moon
Original Assignee
Nrx Global Corporation
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
Priority claimed from US11/332,778 external-priority patent/US20070088704A1/en
Priority claimed from US11/354,584 external-priority patent/US20070168325A1/en
Application filed by Nrx Global Corporation filed Critical Nrx Global Corporation
Publication of WO2007045084A1 publication Critical patent/WO2007045084A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems

Definitions

  • unstructured electronic documents For organizations that rely on such content, a substantial amount of time is wasted searching for information, whether through hard copy file systems or electronic file systems.
  • unstructured electronic documents users currently receive extremely large files, or a grouping of files. While unstructured electronic documents allow a user to store documentation electronically, thereby reducing the amount of physical space in a warehouse or other storage facility, users are still presented with a large quantity of unorganized information making efficient retrieval of specific information difficult.
  • unstructured electronic documentation distributed to users often comprises a variety of file formats, thereby requiring users to maintain applications capable of finding and viewing the distributed documentation. Structured content commonly lacks the metadata that adequately describes the context for the information or how it will be used in the context of a work process.
  • the present invention provides a system and method for facilitating the movement of content (both digital and analog data) in a hierarchal, structured, and easily accessible structure.
  • Content includes files and other media capable of being stored in an accessible memory structure including, but not limited to, text files, audio files and video files.
  • Content may be stored on a variety of memory structures including databases, storage libraries, file systems and DMS applications.
  • Content from a plurality of memory structures may be added to a PKF from an authoring environment.
  • the content itself resides in the PKF.
  • the PKF stores links and metadata, accessing content over a network, such as the Internet, as required.
  • An authoring environment may be used to define file characteristics of and associations between content.
  • the PKF may be generated directly from the memory structures through electronic means. Automated checking may be accomplished by processing for conformance with a predefined structure or schema.
  • Characteristics of and associations between content are created and stored as metadata that conforms to open standards, such as XML.
  • the metadata are expressed in RDF, which is built upon XML technology.
  • An index may also be created, which may include varying combinations of the content and metadata, to provide for efficient searching of the content and metadata.
  • the index, metadata and content are packaged into a Portable Knowledge Format ("PKF") for delivery to a user environment.
  • PPF Portable Knowledge Format
  • a viewing environment provides a user with the capabilities to dynamically search and view data in an organized and hierarchal context with use of the metadata structures.
  • a workflow process may be defined external to a PKF, allowing enterprise applications to retrieve information from a PKF in conjunction with a given step in a workflow.
  • a workflow process permits the retrieval of content from one or more PKFs for specific tasks, providing for the delivery of content to specified locations.
  • Embodiments of the present invention provide for extraction and/or definition of metadata that describes content to facilitate delivery of content in an indexed, hierarchal, and associated format.
  • metadata users are able to view dependencies and relationships between various content.
  • embodiments of the present invention permit users to add, update, suppress, annotate or delete (within any defined context or role for a given user that may be expressed in the metadata) content and metadata, as well as deliver updated content and metadata to additional users and systems.
  • embodiments of the present invention permit users to retrieve and review only content relevant to a specific use or need.
  • Embodiments of the present invention further provide systems and methods for the efficient retrieval and delivery of content to users in a format that provides users with efficient access to information.
  • indices may be created to provide users with structured searching capabilities across a plurality of items of content created according to a plurality of file formats.
  • Embodiments of the present invention further provide for the structured completion of work processes.
  • the present invention allows for the use of a workflow or work process to retrieve and deliver relevant content to a specified location, process or user.
  • FIG. 1 is a high-level block diagram depicting a system for the creation and delivery of a PKF according to one embodiment of the present invention
  • FIG. 2 is block diagram depicting a PKF and its contents according to one embodiment of the present invention
  • FIG. 3 is a block diagram depicting a system for the extraction of a PKF into a DMS according to one embodiment of the present invention
  • Fig. 4 is a block diagram depicting a system for the delivery and viewing of a PKF according to one embodiment of the present invention
  • FIG. 5 is a flow diagram illustrating a method for the creation of a PKF in an authoring environment according to one embodiment of the present invention
  • Fig 6. is a flow diagram illustrating a method for the delivery, viewing, and storage of a PKF in a user environment according to one embodiment of the present invention
  • Fig. 7 is a flow diagram illustrating a method for the for the creation, delivery and use of a workflow in conjunction with a PKF according to one embodiment of the present invention
  • FIG. 8 is a screen diagram illustrating a user interface for the authoring environment for the creation of a PKF according to one embodiment of the present invention
  • FIG. 9 is a screen diagram illustrating a user interface for the addition of content to a PKF according to one embodiment of the present invention.
  • Fig. 10 is a screen diagram illustrating a user interface for the presentation of metadata, hierarchies among data and contents of a PKF in an authoring environment according to one embodiment of the present invention.
  • Fig. 1 1 is a screen diagram illustrating a user interface for the content comprising a PKF and hierarchies among the data according to one embodiment of the present invention.
  • a high-level block diagram depicts one embodiment of a system in accordance with the present invention for generating a Portable Knowledge Format ("PKF") from a collection of digital data content to be delivered to a user or application.
  • PPF Portable Knowledge Format
  • a PKF provides for the storage of content comprising various file formats in a structured, hierarchal, and indexed manner.
  • the PKF comprises content, metadata that describes the content and an index that provides for searching the metadata and content.
  • a recipient of a PKF may access the content that a PKF maintains through the use of an index and metadata.
  • Dependencies and associations among content in a PKF are maintained through the use of metadata.
  • an index comprised of metadata is maintained to facilitate efficient searching. Recipients of a PKF may search the metadata index to locate and retrieve content rather than searching individual files.
  • content to be stored in a PKF may be stored according to variety of formats, structured or unstructured, from a plurality of disparate data content sources 102a, 102b and 102c.
  • Data content sources 102a, 102b and 102c are accessible memory structures such as a database, CD-ROM, tape, digital storage library, etc.
  • Content sources 102a, 102b and 102c may be implemented as databases or any other type of storage structures capable of providing for the storage and retrieval of content.
  • Data content sources 102a, 102b and 102c store a variety of file formats, including text files, graphical files, audio files, video files or other types of files known in the art and capable of being stored in an accessible memory structure.
  • Data content sources 102a, 102b and 102c may also store files in an unstructured or structured manner.
  • structured content may comprise an entire manual for a given pump, stored in a single file in a data content source 102a with associated metadata.
  • unstructured content may comprise various files stored in a plurality of content sources 102a, 102b and 102c in multiple file formats with no associated metadata.
  • Content sources 102a, 102b and 102c are communicatively coupled to a content manager 104 (e.g., over a network, such as the Internet) that receives requests from an authoring environment 106.
  • a content manager 104 e.g., over a network, such as the Internet
  • requests for content stored on various content sources 102a, 102b and 102c may be delivered to the content manager 104.
  • the request for content from the authoring environment 106 is delivered to a content manager 104, which locates and retrieves the desired content from a respective content source 102a, 102b and 102c.
  • the content manager 104 is capable of retrieving a variety of file formats, including graphical files, audio files, text files, or other types files known in the art.
  • the content manager 104 delivers the content retrieved from content sources 102a, 102b and 102c to the authoring environment 106.
  • the metadata which exposes associations and hierarchies among files and file elements, is created using open standards such as the Extensible Markup Language (“XML").
  • XML is a markup language that may be used to document metadata.
  • the metadata defined by an RDF schema is written in an XML format and enforced by a Document Type Definition (“DTD”), which is referenced by other applications or systems to understand the semantics of the metadata.
  • DTD Document Type Definition
  • the PKF DTD provides a description of the structure of the PKF XML.
  • Enterprise applications that understand that structure may extract metadata (XML-encoded RDF) for included content and presentation structures, such as nodes and filters.
  • the RDF references RDF schemas that describe the relationships expressed in the metadata with a high degree of precision, helping machines to understand the data in a way that XML alone cannot.
  • RDF schemas for common uses may be registered and available to users. Additionally, users may create their own RDF schemas to facilitate standardized use of the PKF within a unique environment.
  • One or more schemas may be associated with the content included in a given PKF and may be used to provide users with a plurality of views of the content within a PKF.
  • a mapping is identified between the one or more schemas associated with the content included within a given PKF, or in some cases between schemas within the PKF and other schemas external to the PKF into which data from the PKF may be exported.
  • the one or more data elements comprising the Integration of Industrial Data for Exchange Access and Sharing schema may be mapped to the data elements comprising the Common Industry Material Identification Standard schema (CIMIS).
  • CIMIS Common Industry Material Identification Standard schema
  • relationships between one or more data elements in the plurality of schemas associated with the content comprising a PKF are mapped according to a predetermined or newly created mapping.
  • the authoring environment 106 may identify a mapping between the data elements associated with the Dublin Core schema and the XmpLant schema, which may be based upon metadata in a PKF.
  • a user of the authoring environment 106 may identify a mapping between the one or more schemas associated with a PKF.
  • the one or more schemas that may be used by a PKF include, but are not limited to, the schemas illustrated in Table A.
  • Mapping can either be deployed with a PKF is the mapping exists at the time of creation of the PKF, or generated subsequent to the authoring of the PKF. Furthermore, the mapping may be deployed outside the authoring environment, for example, to maintain ongoing synchronization when changes occur to one or more items of content.
  • one or more custom schemas may be generated for a given PKF.
  • one or more custom schemas may be constructed using a combination of elements identified by one or more common standard schema in conjunction with and incorporating registry elements identified by a user of the authoring environment 106.
  • a user of the authoring environment 106 may supplement the CIMIS schema illustrated in Table A with one or more data elements to generate a schema comprising the elements desired by the user.
  • one or more existing schemas such as the plurality of common standard schemas illustrated in Table A, may be combined to construct a customized schema, which may incorporated user identified elements.
  • parsed files and file elements are stored in the original content source 102a, 102b, and 102c or may alternatively be stored in another database or accessible memory structure communicatively coupled to the authoring and/or viewing environment.
  • only metadata generated in the authoring environment 106 is stored.
  • the authoring environment 106 examines the metadata of the file(s) retrieved and allows a user to view the plurality of files and file elements to be included with the PKF. According to one embodiment of the invention, the authoring environment 106 automatically extracts repeatedly used metadata items, such as metadata items identified in a schema or a hybrid of multiple schemas, e.g., the Dublin Core Metadata Element Set. For example, a given item may be requested from content sources 102a, 102b and 102c for inclusion in a given PKF. Upon receiving the item of content, the authoring environment 106 may automatically extract metadata items identified in one or more schemas. According to another embodiment of the invention, the authoring environment 106 provides the capability to supplement existing metadata or add new metadata to the content retrieved from a content source 102a, 102b and 102c.
  • metadata items such as metadata items identified in a schema or a hybrid of multiple schemas, e.g., the Dublin Core Metadata Element Set.
  • a given item may be requested from content sources
  • the authoring environment 106 may further provide structured data models or templates to specify how information is to be presented when delivered to a user 1 14.
  • the authoring environment 106 further permits a user to define views based on a schema, as well as generate one or more customized schemas, to allow recipients of the PKF to view a subset of the content delivered.
  • a PKF author using the authoring environment 106 may allow for the creation of views (e.g., subsets of content and metadata in a PKF) using keywords, word strings, Boolean logic, etc.
  • Users of the viewing environment may define views through ad-hoc filters that apply Boolean or other logic to content, metadata and/or combinations of metadata and content.
  • An index is created using the metadata retrieved and/or supplemented from data sources 102a, 102b and 102c, which may include accessing combinations of public and private data sources. Alternatively, the index may be created from the content itself. For example, the index may comprise a word/location index. Accordingly, content is indexed against the location in which the word or phrase appears.
  • the metadata, structured content, and index are maintained as a PKF 108.
  • a PKF 108 may be delivered via a communication means, such as the Internet, to a content manager, e.g., an Asset Content Manager ("ACM”) 110, described in U.S. Patent Serial No.
  • ACM Asset Content Manager
  • the content manager 110 Upon receiving a PFK 108, the content manager 110 stores the PKF 108 in its entirety.
  • the contents of the PKF 108, including the metadata, are extracted into one or more DMS applications 1 12.
  • the DMS 112 is communicatively coupled to one or more users 1 14a, 114b and 1 14c, which may request content from a PKF 108 or entire PKFs.
  • a mapping may be maintained between the ACM system and one or more PKFs to allow a user to interact with the PKFs and obtain information updated from the ACM system.
  • the inter-schema mapping may also be used for the purpose of causing the automatic or systematic updating of the information in the PKF to reflect changes in the ACM system data.
  • the metadata associated with a given PKF may be utilized to extract or map data within a given PKF to the ACM system.
  • a mapping may be maintained between one or more PKFs and the master data associated with one or more applications maintaining content.
  • a mapping may be maintained between the one or more schema elements comprising a given schema associated with a PKF and the master data associated with one or more applications maintaining content.
  • the mapping maintained between a PKF and the master data associated with one or more applications allows a user to interact with the PKF in order to retrieve information that may be updated or modified within an application's master data.
  • Content may be displayed on user terminals 114a, 114b and 114c by means of a viewer application 116a, 116b, and 116c.
  • a viewer application 116a, 116b, and 116c examines the metadata associated with content requested from a PKF.
  • a viewer application 1 16a, 116b, and 1 16c retrieves the requested content, which may include the retrieval of any associated content as indicated by the metadata to thereby allow for the retrieval of related content.
  • the viewer 1 16a, 116b, and 116c invokes enterprise applications 118a, 118b, and 118c available to a user to display content.
  • enterprise applications 118a, 118b, and 118c available to a user to display content.
  • a viewer 1 16a, 1 16b, and 1 16c may invoke Adobe Acrobat, and display the PDF file within the viewer application.
  • plug- in modules are used to supply functionality for rendering the content, delivering the rendered content to a viewer 1 16a, 116b, and 116c for display in the viewing application.
  • a block diagram illustrates one embodiment of a PKF 201.
  • PKF 201 maintains content 202 comprising data to be delivered to a user.
  • the content 202 of a PKF 201 contains files encoded according to various file formats, including, but not limited to, text files, audio files, PDF files, HTML file, XML files, video files, etc.
  • An authoring environment whereby metadata 203 is extracted from the content or defined by a user of the authoring environment, retrieves the content 202 contained within a PKF 201.
  • the authoring environment may automatically extract commonly used metadata elements, such as title, creator, subject, description, date, etc.
  • the schemas associated with a PKF may be supplied as part of the PKF or referenced externally. Additionally, a mapping may be generated between the one or more schemas associated with a PKF to provide for a plurality of views of the content within a PKF.
  • the metadata 203 comprises the metadata extracted from the digital data content as well as metadata specified by a user of the authoring environment.
  • the metadata 203 corresponds to given items of content 202, providing information on associations and hierarchies among the content items 202.
  • Each file or file element delivered with a PKF 201 has associated metadata 203 in order to display the file or file element in a proper context.
  • Viewing and enterprise applications in a user environment access the metadata 203 delivered with a PKF 201.
  • the metadata 203 may be used to properly display content 202 to users in a structured manner. For example, using one or more schemas associated with a PKF, a user may view all content delivered with a PKF 201 in a graphical tree structure, indicating relationships and dependencies among the content.
  • a user may request content on a specific topic and the viewer and enterprise applications, accessing the PKF metadata 203 and the one or more schemas associated with a PKF display content from the PKF pertaining to the topic requested, which may also include content associated with the content requested.
  • a user may alter (e.g., add, change, suppress, delete) the associations between files and file elements, as well as add, change, suppress, annotate or delete content and associated metadata.
  • the metadata 203 component of a PKF 201 is used to store user updates to file associations.
  • user authorization levels may determine what specific functions or alterations a given user may perform.
  • the index 204 contains information to provide a recipient of the PKF 201, which may be a user or an application, with the ability to efficiently search the PKF 201.
  • the index 205 comprises terms and phrases found in the metadata 203, for example, the index elements 205 comprise word/location pairs indicating the files in which a given word appears.
  • the index elements 205 comprise a combination of metadata 203 and words from the content 202.
  • the index 204 comprises links, allowing a user to access both content 202 within a PKF 201, as well as information outside a PKF 201, such as information contained in other PKFs.
  • the index 204 provides a recipient of the PKF 201 the ability to search the digital data content 202 at a PKF level rather than at an individual file level, thereby allowing for efficient searching and rapid retrieval of content. Moreover, changes made by a user to the metadata 203 may be propagated to the index 204 in order to maintain a proper record of associations between files and file elements.
  • FIG. 3 provides a block diagram depicting one embodiment of a content manager storing a PKF.
  • a PKF 302, 308 is delivered to a content manager 318 which determines whether to extract the components of the PKF 302, 308 into a DMS 311 or whether to store a PKF 302, 308 in its entirety.
  • the content 304, metadata 301 and index 303 of PKF 302 are extracted into a DMS 311. Storing the elements comprising a PKF 302, specifically, the content 304, metadata 301 and index 303, preserves relationships and dependencies 314 among content files 312 when extracted to the DMS 31 1.
  • storage of the metadata 301 and 307 preserves associations between multiple PKFs, e.g., PKF 302 and PKF 308. Additionally, storage of the index 303 allows a user seeking information stored in a PKF 302, 308 to gain access to the desired content with speed and efficiency.
  • the index 303 delivered with a PKF 302 provides a user with the ability to search at the PKF level rather than searching among the numerous content files individually.
  • the maintenance and storage of the metadata 301 permits a PKF 302 to be reconstituted if needed.
  • a PKF 302 to be reconstituted if needed.
  • relationships and dependencies 314 among content files 304 are preserved.
  • Enterprise applications have access to the PKF DTD that describes the PKF XML format, as well as to the RDF schemas referenced by the PKF, thereby allowing the enterprise applications to read the metadata 301 and acquire knowledge about relationships among the various content files 304.
  • Access and maintenance of metadata 301 allows for the distribution of the content 304 in an organized, structured, and hierarchal manner.
  • a PKF may also be delivered directly to a user.
  • a user environment may store the elements comprising a PKF, including the metadata, content, and index.
  • a user environment has access to the PKF DTD and to RDF schemas referenced by the PKF, allowing applications within a user environment to process and maintain associations among content files.
  • a PKF may also be delivered directly to a user environment while maintaining a mapping with a content management system.
  • a content management system may utilize the metadata within a PKF to maintain a mapping with the PKF.
  • the mapping may be used to update content items within the PKF, modify associations or dependencies among the content items within the PKF, etc.
  • the mapping maintained between a given PKF and a content management system comprises an indication to copy relevant information maintained within the content management system to the PKF.
  • the mapping maintained between a PKF and a content management system comprises one or more links within the PKF to information maintained in the content management system.
  • the mapping maintained by a PKF to information that resides in a content management system allows a recipient of a PKF to interact with the local PKF in order to obtain desired information.
  • a given PKF may contain content on a manufacturer's recommended steps for performing proper maintenance on a given vehicle.
  • the PKF maintains a mapping to the relevant information in the content management system, which may be delivered to a user environment.
  • the vehicle manufacturer may thereafter modify the content associated with the recommended maintenance steps in the content management system.
  • the mapping maintained by the PKF allows the user to retrieve the manufacturer's modified information.
  • Fig. 4 provides a block diagram depicting one embodiment of a system for viewing and updating the contents and metadata of a PKF.
  • a PKF 402 may be delivered to a content manager, and thereafter, extracted into a DMS 420.
  • a PKF may be delivered directly to a user within the context of a work process (automated discovery on the basis of metadata interpretation) or upon request (manual request with electronic delivery).
  • User environments 414 communicatively coupled 416 to the DMS 420, may make requests for content to the DMS 420 using a viewer located in the user environment 414.
  • a user request is processed using the index 403 delivered with a PKF 402.
  • a search of the index 403 is performed to locate content that is responsive to a user request 404.
  • the content 412 located is delivered to a user via a communication means 416.
  • the content 404 delivered to a user 414 may be comprised of various file types, each requiring different applications to properly display the content.
  • the viewer reviews the metadata structures 401 associated with the respective content 404 to determine the type of content delivered and the application(s) needed to properly display the content 404 to a user 414.
  • the viewer invokes the necessary application and displays the requested content to a user within the viewer application.
  • a plug-in module is used to apply rendering to the requested content and deliver the rendered content to the viewer for display to a user.
  • a viewer allows a user to graphically expose the relationships or associations 411 among the content in a PKF 402 to gain knowledge as to the structure, hierarchies, and associations of the digital data content 404.
  • a user presented with the requested content may review and modify the content received, including associated metadata.
  • a user may modify the metadata 401 associated with the content received to define new descriptions of the content, as well as associations and hierarchies 411 among the content.
  • the modifications made to the content 404 or metadata 401 may be stored in a PKF or in the DMS 420. Additionally, changes made to the metadata 401 are reflected in the index 403 in order to maintain efficient access and retrieval of content 404.
  • Content can be added, updated, suppressed and deleted, and additional metadata may be added, updated, suppressed and deleted.
  • a PKF 402 is reconstituted, the updated content 404, index 403, and metadata 401 are incorporated within the reconstituted PKF 402 and may be delivered to additional DMS 420 environments. Additionally, a user communicatively coupled 418 to other users, for example via a LAN, may send the updated PKF to additional users 414.
  • a user of the authoring environment may browse and retrieve digital data content from various data storage facilities including databases, indexes of hard copy files, CD-ROMs, servers, the Internet, DMS applications, or hard disks, step 500. In accordance with the embodiment of Fig.
  • a request is received for digital data content using an authoring environment, step 501.
  • a request may be manually entered by a user, generated by an application or automatically generated according to systems and methods described below, or a combination thereof.
  • the authoring environment delivers the request to a content manager, step 502.
  • the content manager determines the location of the requested content among the plurality of content sources, step 503.
  • the content is delivered to the authoring environment, step 504.
  • Content delivered to the authoring environment may be structured or unstructured content.
  • structured content may comprise an entire manual in PDF format consisting of several hundred pages with associated metadata (a parts book is one example of structured content)
  • unstructured content may comprise numerous image files, text files, audio files, hardcopy files, etc., stored in separate locations, which may or may not contain associated metadata.
  • the authoring environment includes many functions/features for processing the data to extract and define metadata.
  • the processing performed in the authoring environment includes the extraction and definition of metadata and creation of hierarchies and dependencies.
  • the authoring environment parses files and file elements to determine whether metadata exists, step 505. If metadata exists for the file being parsed, the relevant metadata is extracted, step 507.
  • a file may contain many different types of elements such as graphical elements and textual elements that require different processing to convert into structured content.
  • the authoring environment extracts and associates metadata with a graphical element to indicate, for example, the name of the graphical element, the description of the graphical element, a description of where or how the element is typically used, links to other documents or other parsed elements, associations with other elements or files, etc.
  • the authoring environment may provide for the automatic extraction of frequently used or user specified metadata items.
  • the authoring environment may provide for the automatic extraction of Dublin Core Metadata elements.
  • the one or more Dublin Core Metadata elements extracted from a given file may be utilized to identify the content within a PKF, as well as the relationships and dependencies among the one or more items of content in the PKF, or to references external to the PKF.
  • the authoring environment may automatically map the one or more metadata elements extracted from a given file to one or more schemas, providing recipients of the PKF with a plurality of views of the content within a PKF.
  • the authoring environment prompts a user or application to define metadata, step 506.
  • a user of the authoring environment may also define associations between files and file elements, as well as specify how data is to be displayed in a user environment. Metadata structures and conventions from multiple disparate sources may also be accessed and used by the authoring environment.
  • elements may be stored in a content database or other accessible memory structure.
  • the authoring environment may store only metadata associated with a parsed file or file element.
  • metadata is extracted from the data received from a content source or defined by user input, step 507 and 506, respectively.
  • the metadata extracted, step 507, or input, step 506 is written to an XML file, the structure of which may be defined by a DTD or one or more RDF schemas.
  • an index is created, step 508.
  • an index is created using the extracted and defined metadata.
  • a word/location index is created, whereby content is indexed against the location in which a word or phrase appears. The index provides a user with the ability to search content at a PKF- level in addition to searching at an individual file-level.
  • the index, metadata, and content are packaged into a PKF, step 509.
  • the authoring environment detennines whether to deliver the PKF to a content manager or user environment or whether to store the PKF in a storage facility, step 510.
  • the authoring environment upon creation of the PKF the authoring environment delivers the PKF to a content manager, user environment, or other user storage facility, step 512.
  • the authoring environment stores the PKF in an OEM's storage facilities, step 511, and upon receipt of a user request, delivers the PKF to the appropriate user.
  • requests for documentation may be received from users or purchasers of an OEM's equipment via a communication medium such as the Internet. If a request is received from a user, and a PKF for a user's request has already been constructed, the PKF corresponding to a user's request may be retrieved from a storage facility and delivered to the user via a communication means such as the Internet. Alternatively, if an OEM receives a request, and a PKF has not previously been constructed for the user's specific request or equipment, a PKF can be dynamically constructed using the authoring environment system and method described above.
  • the purchaser of equipment provides a PKF "template” with metadata "slots" to be filled out by the OEM for a given item of contracted equipment.
  • Each metadata slot is described by a reference to a property in one or more RDF Schemas whereby the one or more schema properties determine what a given slot may validly contain (a schema property is a combination of textual description and syntactic prescription).
  • Schemas may be supplied in the PKF, or the PKF may reference an external schema.
  • One or more mappings may be generated to associate the one or more schemas associated with a given PKF.
  • the OEM returns the PKF to the purchaser with metadata supplied in these slots - typically describing and qualifying the content that the OEM has inserted into the PKF.
  • the one or more schemas may provide the purchaser with a plurality of views of the content within the PKF.
  • the OEM may use a PKF editing tool to fill in these slots. Because the PKF format is defined using open standards, however, the OEM may also generate the PKF. For example, the OEM may generate the PKF with other software that automatically inserts the required content and metadata into the purchaser's "template". Accordingly, the resulting document comprises self-validating properties as it contains all of the information necessary to ensure that the returned PKF constitutes a valid response to the original request.
  • Fig. 6 provides a detailed flow diagram depicting one embodiment of a method for viewing a PKF in accordance with the present invention.
  • the components of a PKF may be extracted into a DMS.
  • a PKF may provide linkages to content found elsewhere to thereby allow the use of a single master set of content and eliminate the need for publishing "files”.
  • a viewer module a user communicatively coupled to the DMS makes requests for content to the DMS system.
  • a user can search content stored in the DMS.
  • content stored in a DMS is delivered to a user, step 601.
  • the user may search the index of the PKF to directly access the content contained in the PKF.
  • the PKF comprises links to content
  • a given link may be traversed to locate the linked content.
  • the viewer module upon receiving the requested content, reviews the metadata structures associated with the content delivered 602.
  • the metadata delivered with the content from a PKF permits the viewer module to determine the type of file requested, associations with other files in the PFK, as well as associations with other PKFs, step 602.
  • the content delivered with a PKF may contain PDF files, Microsoft Word files, GIF files, XML files, HTML files, etc.
  • the viewer using the metadata structures associated with a file or a plurality of files, invokes a universal viewer or the relevant application to display the content requested, step 603, and provides a user with the ability to navigate and retrieve associated files.
  • the viewer invokes the relevant enterprise application to display the content requested in the viewing environment.
  • a plug-in rendering module is used to render the content and display the content in the viewer.
  • a user is capable of reviewing and modifying the content 604
  • a user may locate additional content associated with the content received 604 Additional content may be located using the associations defined with the metadata delivered with a PKF
  • a user may add, update, annotate or remove content received, as well as add, suppress and delete file views and metadata for a given PKF
  • annotations do not affect the original content unless autho ⁇ zations allow for such
  • a workflow process enables annotations to be routed back to authors for updating of original content as required
  • a user may modify the associations defined by the metadata, creating new associations, dependencies, and hierarchies
  • the associations defined by the metadata creating new associations, dependencies, and hierarchies
  • Fig. 7 presents a flow diagram depicting one embodiment of a method according to the present invention for using a PKF in the context of a work process or workflow.
  • a workflow component is incorporated in a user environment, which may be incorporated via the use of a plug-in or a helper application.
  • a user inputs steps to be executed in a workflow, step 701.
  • a workflow is automatically generated for a particular task or series of tasks.
  • a workflow contains a series of steps defining a work process.
  • a work process may indicate the type of data needed for a work process, a location to deliver the relevant data, or a time for data to be delivered.
  • a workflow is delivered to a workflow component, step 703.
  • enterprise applications can retrieve a PKF(s) or content from a PKF related to a particular task, step 704, and deliver the PKF or content to the location specified in a workflow, step 705.
  • a workflow may be created with a variety of enterprise applications or through the use of a plug-in.
  • a workflow component receives a workflow and examines the contents to determine the process to execute, step 703.
  • a workflow may specify data to be retrieved from a PKF or a particular PKF to retrieve, step 704.
  • content stored in a DMS or the PKF may be retrieved and delivered to a user environment for display in a viewer, step 705.
  • content may be retrieved and delivered using one or more links in the PKF.
  • a user or recipient of content in the workflow process can alter the workflow.
  • a user may receive content from a PKF and determine that a step in the workflow is not needed or must be added.
  • a user can modify the workflow, inserting or removing the work process as needed.
  • the workflow proceeds to execute the next process in the workflow, step 706.
  • a workflow may specify a particular PKF to retrieve from the DMS and to deliver the PKF to a specified user.
  • a workflow may further instruct a first user to deliver content or an entire PKF to a second user based upon the first user's interaction with the PKF.
  • a workflow may execute according to decisions or interactions a user has with a PKF. For example, if a user modifies a particular PKF, the workflow may deliver the relevant PKF to a manager for approval. Alternatively, if user merely reviews and annotates a PKF, the workflow returns the annotated PKF to the DMS or delivers the PKF to another user.
  • a workflow may also retrieve a particular PKF based upon the respective step or task being processed or executed in the workflow.
  • a workflow created for an assembly line may specify the particular PKF to retrieve based upon the product being constructed and the particular task being executed.
  • a workflow is executed as a hidden process. Content is delivered to a user, however, any user in the workflow process, according to one embodiment, cannot modify the work process.
  • a workflow is executed until all steps in the workflow process are complete, step 707.
  • a workflow may grant control to a select group of users. For example, managers or system administrators may have authority to modify a workflow.
  • Fig. 8 presents a screen diagram illustrating one embodiment of an interface to an authoring environment for a PKF.
  • the authoring environment 800 allows a user to retrieve content from content sources and extract and define metadata associated with the content retrieved.
  • a user can create a hierarchy among the content retrieved by adding a node 801.
  • hierarchies may be automatically identified by the authoring environment 800 based upon metadata, which may be metadata associated with the one or more items of content retrieved.
  • a node represents a dependency or association with a parent node or child node.
  • creation of a node 801 allows a user to specify the association and dependency with respect to a particular file or file element.
  • the authoring environment 800 automatically identifies associations and dependencies upon creation of a node 801.
  • a user may also add content to a PKF using a toolbar button or menu item 802. When a user selects this function, he or she is able to browse a plurality of content sources to retrieve a specified file or file element. The content retrieved is delivered to the authoring environment and parsed, which may be accomplished using the authoring environment.
  • the authoring environment extracts metadata associated with the file or file element.
  • the metadata extracted is displayed to a user of the authoring environment 803. Additionally, a user may specify additional metadata to be added to a file or file element.
  • As content is selected for inclusion in a PKF the contents are presented to the user of the authoring environment in the display area, 804.
  • Fig. 9 presents a screen diagram illustrating one embodiment of an interface to an authoring environment for viewing the content added to a particular PKF.
  • the authoring environment 900 displays the contents added 902 to a PKF. Selecting the "Data" tab 901 allows a user to view the metadata 901 extracted from or added to the content retrieved from a content source.
  • a user of the authoring environment may also view the dependencies and associations 903 among the content added to a PKF.
  • “Toyota Fork truck” is the parent node of "Frame” and “Drivetrain.”
  • “Frame” and “Drivetrain” comprise sub-contents of "Toyota Fork truck.”
  • a user may view the type of content added to the PKF 904.
  • Various icons 904 may be displayed according to the type of file or file element. Icons are representative of file or element type.
  • Fig. 10 provides a screen diagram illustrating one embodiment of an interface for displaying the contents of a PKF in an authoring environment.
  • a user of the authoring environment 1000 can display the metadata associated with a particular file or file element by selecting the "Data" tab 1001. As shown, metadata associated with the selected node 1002, title and creator 1003, is displayed by selecting the "Data" tab 1001.
  • the authoring environment further provides a user with the ability to add additional metadata.
  • Fig. 10 further depicts the various file formats that are incorporated in a given PKF. As shown, icons displayed reflect content type 1004. Additionally, associations among files are depicted in a hierarchal manner. A user of the authoring environment may click on the '+' symbol to display associated files 1005. [0076] As shown in Fig. 1 1, a user of the authoring environment 1100 may view the contents included in a PKF. Selecting the "Content" 1101 tab displays the contents of the file or folder selected 1102. Additionally, file elements, such as images, which are associated with certain content through the use of metadata, may be displayed in the authoring environment 1 103.
  • Mobility Wheeled Vehicle HMMWV ⁇ /dc:t ⁇ tle> ⁇ demo: Model >M996 ⁇ /demo:Model> ⁇ /rdf:RDF>
  • Mobility Wheeled Vehicle ⁇ /dc:t ⁇ tle> ⁇ demo: Model>M998 ⁇ /demo: Model > ⁇ /rdf:RDF>
  • ⁇ dc:t ⁇ tle>Operator's and Unit Maintenance Manual Including Repair Parts and Special Tools List for Shop Equipment Contact Maintenance (SECM) Mounted On High Mobility Multipurpose Wheeled Vehicle (HMMWV) Heavy (HVY) Model M1097A2 ⁇ /dc:t ⁇ tle> ⁇ dc:Date>2003-09-02 ⁇ /dc:Date> ⁇ demo: Pages> 143 ⁇ /demo:Pages> ⁇ demo: Model > M lO97A2 ⁇ /demo: Model > ⁇ /rdf: Description > ⁇ /rdf:RDF> presentation resourceURI "hmmwv_TM 1-4940-355-
  • ⁇ dc:t ⁇ tle>Transportability Guidance, M998 Series High Mobility Multipurpose Wheeled Vehicle (HMMWV) ⁇ /dc:t ⁇ tle> ⁇ dc: Date> 1988-08-OK/dc: Date> ⁇ demo:Pages>44 ⁇ /demo:Pages> ⁇ demo: Model >M998 ⁇ /demo: Model > ⁇ /rdf:Desc ⁇ pt ⁇ on> ⁇ /rdf:RDF> presentation resourceURI "hmmwv_TM 55-2320-280- 14.pdf /> ⁇ /contentNode>
  • Model >M966 ⁇ /demo Model > ⁇ /rdf:Descr ⁇ pt ⁇ on> ⁇ /rdf:RDF> ⁇ /express ⁇ on> ⁇ /f ⁇ lter>
  • Model >M996 ⁇ /demo Model > ⁇ /rdf: Description > ⁇ /rdf:RDF> ⁇ /express ⁇ on> ⁇ /f ⁇ lter> ⁇ ⁇ f ⁇ lter>
  • Model >M997 ⁇ /demo Model > ⁇ /rdf:Desc ⁇ pt ⁇ on> ⁇ /rdf:RDF> ⁇ /express ⁇ on> ⁇ /f ⁇ lter>
  • Model >M998 ⁇ /demo Model > ⁇ /rdf:Descr ⁇ pt ⁇ on> ⁇ /rdf:RDF> ⁇ /express ⁇ on> ⁇ /f ⁇ lter>
  • Model >MlO42 ⁇ /demo Model > ⁇ /rdf: Description > ⁇ /rdf:RDF> ⁇ /express ⁇ on> ⁇ /f ⁇ lter>

Abstract

L'invention concerne des systèmes et des procédés facilitant la distribution de contenu dans une structure de données accessible. Le procédé de l'invention comporte les étapes consistant à: sélectionner un ou plusieurs articles de contenu provenant d'une ou de plusieurs sources de contenu; extraire des métadonnées associées à l'article ou aux articles de contenu; construire un index correspondant à l'article ou aux articles de contenu; stocker le(s) article(s) de contenu, les métadonnées associées et l'index dans une structure de données accessible selon une hiérarchie; distribuer la structure de données accessible et afficher le contenu de la structure de données accessible.
PCT/CA2006/001703 2005-10-17 2006-10-17 Systeme et procede de creation, de distribution et d'utilisation d'un format de connaissances portatif WO2007045084A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US72804105P 2005-10-17 2005-10-17
US60/728,041 2005-10-17
US11/332,778 2006-01-13
US11/332,778 US20070088704A1 (en) 2005-10-17 2006-01-13 System and method for creation, distribution, and utilization of portable knowledge format
US11/354,584 US20070168325A1 (en) 2006-01-13 2006-02-14 System and method for workflow processing using a portable knowledge format
US11/354,582 US20070168374A1 (en) 2006-01-13 2006-02-14 Portable knowledge format for the distribution of content
US11/354,582 2006-02-14
US11/354,584 2006-02-14

Publications (1)

Publication Number Publication Date
WO2007045084A1 true WO2007045084A1 (fr) 2007-04-26

Family

ID=37962156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2006/001703 WO2007045084A1 (fr) 2005-10-17 2006-10-17 Systeme et procede de creation, de distribution et d'utilisation d'un format de connaissances portatif

Country Status (1)

Country Link
WO (1) WO2007045084A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030210821A1 (en) * 2001-04-20 2003-11-13 Front Porch Digital Inc. Methods and apparatus for generating, including and using information relating to archived audio/video data
WO2005055093A2 (fr) * 2003-11-26 2005-06-16 Veritas Operating Corporation Systeme et procede pour la generation de metadonnees de systeme de fichiers extensible et le traitement de contenu de systeme de fichiers
WO2005065166A2 (fr) * 2003-12-19 2005-07-21 Sonic Solutions, Inc. Services de personnalisation pour entites provenant de sources multiples
WO2005072191A2 (fr) * 2004-01-22 2005-08-11 Rosetta Solutions, Inc. Systeme et procede permettant de recueillir et de convertir des ensembles de documents et des metadonnees associees en une pluralite de sous-ensembles de documents/metadonnees

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030210821A1 (en) * 2001-04-20 2003-11-13 Front Porch Digital Inc. Methods and apparatus for generating, including and using information relating to archived audio/video data
WO2005055093A2 (fr) * 2003-11-26 2005-06-16 Veritas Operating Corporation Systeme et procede pour la generation de metadonnees de systeme de fichiers extensible et le traitement de contenu de systeme de fichiers
WO2005065166A2 (fr) * 2003-12-19 2005-07-21 Sonic Solutions, Inc. Services de personnalisation pour entites provenant de sources multiples
WO2005072191A2 (fr) * 2004-01-22 2005-08-11 Rosetta Solutions, Inc. Systeme et procede permettant de recueillir et de convertir des ensembles de documents et des metadonnees associees en une pluralite de sous-ensembles de documents/metadonnees

Similar Documents

Publication Publication Date Title
US20070168325A1 (en) System and method for workflow processing using a portable knowledge format
US20070088704A1 (en) System and method for creation, distribution, and utilization of portable knowledge format
US10545981B2 (en) Virtual repository management
Erl Service-oriented architecture
US8307012B2 (en) Schema mapping and data transformation on the basis of a conceptual model
US7624114B2 (en) Automatically generating web forms from database schema
US8856645B2 (en) Generating formatted documents based on collected data content
US7483879B2 (en) System and method for accessing non-compatible content repositories
US8234312B2 (en) Schema mapping and data transformation on the basis of layout and content
US7043488B1 (en) Method and system for storing hierarchical content objects in a data repository
US20070192374A1 (en) Virtual repository management to provide functionality
US20040153968A1 (en) Method and system for user customizable asset metadata generation in a web-based asset management system
US20100318511A1 (en) Techniques for connectors in a system for collaborative work
US20110145712A1 (en) Information exchange using generic data streams
WO2004112301A2 (fr) Systeme d'auteur de langage de balisage
US20040143588A1 (en) Database model system and method
JP2002538553A (ja) デジタル・メディア・アセット管理システムおよびプロセス
KR100436702B1 (ko) 가상문서 제공 시스템 및 그 방법
Ramalho et al. Metamorphosis–a topic maps based environment to handle heterogeneous information resources
WO2007045084A1 (fr) Systeme et procede de creation, de distribution et d'utilisation d'un format de connaissances portatif
Gourley et al. A sustainable repository infrastructure for digital humanities: the DHO experience
Nutter et al. An artefact repository to support distributed software engineering
Dhillon et al. Data intensive computing for biodiversity
Van den Hoven Database Management System and XML: Interchange of Data.
Kiemle et al. Providing context-sensitive access to the earth observation product library

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06804633

Country of ref document: EP

Kind code of ref document: A1