XML to LDAP Schema Conversion via Automated Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of LDAP directories makes it difficult for XML developers without knowledge of LDAP to create schemas that are compatible with LDAP servers, as they need to understand fully qualified names, globally unique identifiers, and attribute types, which is a barrier to using LDAP servers effectively.

Innovation Solution

A computer-based process that takes an input schema, possibly in XML format, and automatically generates a schema that conforms to the LDAP directory access protocol by copying, translating, or adding necessary information, allowing the output schema to be in LDIF or DSML format, thus enabling use of LDAP servers without requiring LDAP knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If LDAP schema requirements (fully qualified names, globally unique identifiers, attribute types) are enforced, then LDAP protocol compliance is improved, but ease of operation deteriorates because XML developers must learn LDAP specifics

Engineering Contradiction:
ImproveLDAP protocol complianceVSAvoidSchema creation ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary conversion tool that translates XML schemas into LDAP-compatible schemas. This mediator automatically handles the complexity of LDAP requirements (fully qualified names, globally unique identifiers, attribute types) while allowing XML developers to work with familiar XML syntax, thus maintaining both LDAP compliance and ease of operation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The conversion tool performs self-service by automatically generating the necessary LDAP schema elements without requiring manual intervention from the XML developer. The tool itself handles the complex transformations needed to meet LDAP requirements, eliminating the need for developers to learn LDAP specifics

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If LDAP-specific knowledge (fully qualified names, globally unique identifiers, attribute types) is required, then manufacturing precision is improved, but device complexity increases due to additional learning requirements

Engineering Contradiction:
ImproveSchema compliance accuracyVSAvoidDevelopment complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent uses copying by taking the familiar XML schema structure and automatically transforming it into the corresponding LDAP schema format. The conversion tool copies the essential structural information from XML while automatically adding the required LDAP-specific elements, thus maintaining precision without increasing development complexity

Inventive Principle:
Principle #26Copying

3Reliability

If XML developers must learn LDAP specifics to create compatible schemas, then reliability is improved, but productivity deteriorates due to increased learning time and complexity

Engineering Contradiction:
ImproveLDAP schema compatibilityVSAvoidSchema creation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The automatic conversion tool performs the complex transformation from XML to LDAP schema without requiring developer intervention or learning. This self-service approach maintains high reliability by ensuring proper LDAP compliance while significantly improving productivity by eliminating the learning curve and manual schema conversion work

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7873678B2Lightweight directory access protocol (LDAP) schema definition using extensible markup language (XML)
Publication Date: 2011.01.18 ORACLE INT CORP
  • US7873678B2 patent drawing
  • US7873678B2 patent drawing
  • US7873678B2 patent drawing

AI summary

A computer receives a schema that lacks information required by a directory access protocol (e.g. LDAP) and automatically generates information that conforms to the directory access protocol and supplies the generated information as output in a new schema. Such automatic schema transformation allows a human who is creating the schema, to enable usage of the directory access protocol to interface with a directory implementing the schema, without knowing the directory access protocol. The computer of some embodiments receives the schema being input, in a predetermined human-readable language (e.g. XML). Hence, an XML developer who lacks knowledge of LDAP can use traditional XML tools to prepare an LDAP-incompatible schema, for use in implementing a directory (e.g. address book) that is accessed by an LDAP client (e.g. cell phone) via an LDAP server. The new schema can be output in any form (e.g. text/binary) and in any language.