W3C XML Document Type Definition (DTD) 1.0 - Import
Availability-note
AWS
AWS-only features are available at any of the following URLs: us.cloud.talend.com, eu.cloud.talend.com, ap.cloud.talend.com
Bridge Requirements
This bridge:is only supported on Microsoft Windows.
Bridge Specifications
| Vendor | World Wide Web Consortium |
| Tool Name | XML Document Type Definition (DTD) |
| Tool Version | 1.0 |
| Tool Web Site | http://www.w3.org/TR/2000/REC-xml-20001006 |
| Supported Methodology | [XML Modeling] Data Store (Physical Data Model) via XML DTD File |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting | |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: World Wide Web Consortium / XML Document Type Definition (DTD) version 1.0 via XML DTD File
See http://www.w3.org/TR/2000/REC-xml-20001006
Metadata: [XML Modeling] Data Store (Physical Data Model)
Component: W3cXmlDtd version 11.2.0
OVERVIEW
The bridge utilizes the DTD file as input directly.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||||
| File | The bridge uses an XML DTD file as input. | FILE | *.dtd | Mandatory | ||||||
| Elements content name | XML elements can carry some textual data, in addition to carrying named attributes and sub-elements. The XML DTD specification refers to this mixed content data as #PCDATA. The bridge will map this concept into an attribute with a name that can be customized using this option. | STRING | #PCDATA | Mandatory | ||||||
| Collapse level | By default, the bridge creates a Class for every DTD element. To reduce the number of objects you can collapse multiple Classes together. Allows you to specify when to collapse a Class: 'None' No collapsing: every DTD Element becomes a class and every DTD Attribute becomes an attribute. 'Empty' Only empty Classes (i.e. without Attributes) should be collapsed into their parent classes. 'Single Attribute' Only DTD elements with a single attribute and no children should be collapsed into their parent class. 'No Children' Any DTD element that has no child element will be collapsed into its parent class. 'All' All DTD elements for which it is possible will be collapsed into their parent class. |
ENUMERATED |
|
None | ||||||
| Collapse star | Determines whether DTD elements with an incoming '*' link should be collapsed. 'True' Collapse into their parent class. 'False' Do not collapse into their parent class. |
BOOLEAN | False | |||||||
| Class type | This parameter defines how relationships between elements should be interpreted. If you are converting the DTD into a UML object model, you may use this option to determine whether a Class type (UML concept) should be created when collapsing an Element into its parent Element. 'True' Create UML ClassTypes whenever possible. You can set this value when converting to a UML object modeling tool. 'False' Insert the Attributes of the Element about to be collapsed into its parent's Element. Set this value when converting to a relational data modeling tool. |
BOOLEAN | False | |||||||
| Any | Determines whether to create a Class/Entity for the 'ANY' pseudo-element. 'True' Represent 'ANY' by creating a Class/Entity. 'False' Ignore 'ANY' altogether. In the following DTD fragment, e.g. <!ELEMENT tag ANY > the ANY content can be represented or skipped entirely. |
BOOLEAN | True | |||||||
| Strict Multiplicity | Determines how '(a|b|c)*' should be interpreted: 'True' To the letter interpretation: 'a', 'b' or 'c' can be repeated zero or more times in any order. 'False' Interpret it as '(a?,b?,c?)' except that the order does not matter. |
BOOLEAN | True | |||||||
| Generate IDs | Determines whether additional attributes should be generated to create Primary and Foreign Keys. 'True' Generate an Artificial Attribute for each DTD element to represent this primary key - Foreign key relationship, 'False' The model will not contain keys. |
BOOLEAN | False | |||||||
| HL7 | Set this option to 'True' if you are importing HL7 DTD and you want to perform HL7 specific treatments. | BOOLEAN | False |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"W3C XML Document Type Definition (DTD) 1.0" Metamodel W3cXmlDtd |
Mapping Comments |
| Association | Element Content | each time the element is not a PCDATA or occurs more than once in an element list |
| Aggregation | True | |
| AssociationRole | Element Content | |
| Multiplicity | element occurrence | +', '*', '?' or none |
| Source | based on Elements hierarchy | |
| Attribute | Element/Attribute | An Element imported as a class type, a PCDATA element used with an occurrence "zero or one" or a REQUIRED attribute |
| Name | Element Name | For HL7 the HL7_name property |
| PhysicalName | For HL7 the element name | |
| Position | Order in the element list | |
| DataType | SQL_LONG_VARCHAR, SQL_VARCHAR | |
| Name | Text (for PCDATA Elements), CDATA (for Attributes) | |
| CandidateKey | No equivalent in XML DTD. A Primary key is created if artificial attributes are generated. | |
| Class | Element | |
| Name | Element Name | For HL7 the HL7_name property |
| PhysicalName | For HL7 the element name | |
| ClassDiagram | No equivalent in XML. A main class diagram "Main" will be created to contain all elements. | |
| ClassType | Element | when the Element is imported as an Attribute of its parent (depends on the bridge options). |
| Name | Element Name | For HL7 the HL7_name property |
| DerivedType | Only in HL7 | |
| DataType | Data Type | See datatype conversion array |
| Name | Name | based on the T property in the attribute list for a PCDATA element |
| UserDefined | True | |
| DesignPackage | No equivalent in XML. A main package "Logical View" will be created to contain all elements. | |
| ForeignKey | No equivalent in XML DTD. Foreign Keys are created based on Associations if artificial attributes are generated. | |
| Grouping | Element Content | |
| GroupingType | element type | ,' , '|' or none (leaf) |
| Multiplicity | element occurrence | +', '*', '?' or none |
| Position | Position of sub-element in element content | |
| Index | No equivalent in XML DTD. An index is created for each generated key. | |
| IndexMember | No equivalent in XML DTD. An index member is created for each key attribute. | |
| StoreModel | DTD | The model is built using the elements contained in the XML file. The Entity will be expanded when used. |
| Name | Computed from the XML DTD file name. | |
| TypeValue | Enumerated Attribute Type | |
| Name | Name | Name in the list, e.g, red. |
| Position | Order in the file | |
| Value | Name |