VDA Annex A KBL XML Schema
|
|
- Diana McCarthy
- 6 years ago
- Views:
Transcription
1 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 1 of 20 Harness Description List (KBL) VDA Annex A KBL XML Schema 4964 This current recommendation is not binding and describes the information needed to exchange harness design data within car manufacturers and suppliers. The recommendation defines the required objects with their descriptions and attributes, a formal information model, the mapping to ISO Electrical Design and Installation and the representation in XML. This annex defines the representation in XML. 1 st Edition, April 2005 Project Group "Car Electric" of VDA Working Group "CAD/CAM" Published by: Verband der Automobilindustrie Copyright Westendstraße 61 Copies or any other duplications Postfach must include a correct citation of Frankfurt the source. Phone 069/ Fax 069/ Internet: www@vda.de
2 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 2 of 20 Disclaimer The VDA recommendation "Harness Description List (KBL)" is a recommendation, which is freely available in the public domain. Anybody applying this recommendation is responsible for ensuring that it is correctly applied in the case in hand. It takes account of the current state of the art in technology at the time each edition is issued. The use of the VDA recommendations does not exonerate anybody from the responsibility for their own actions. In this respect, each person acts at his own risk. No liability can be accepted by the VDA and by those involved in producing the VDA recommendations. Readers and users are requested to inform the VDA immediately if they notice any inaccuracies or statements, which can be interpreted incorrectly while using this VDA recommendation in order that any errors may be corrected.
3 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 3 of 20 <?xml version="1.0" encoding="utf-8"?> <!-- Mit XMLSpy v2005 rel. 3 U bearbeitet ( von PROSTEP AG (PROSTEP AG) --> <!--KBL XML Schema Version 2.3 VDA, ProSTEP ivip > <!--Changes from V2.3 to V2.3: Namespace " added complextype and element KBL_schema renamed to KBL_container KBLcontainer: xs:choice removed KBLcontainer: containment of Module_configuration and Module_family deleted Harness: containment of Moduel_family added Accessory_occurrence: type of Reference_element changed from IDREF to IDREFS General template for containment simplified: changed from: <xs:element name="name" minoccurs="0"> <xs:complextype> <xs:element name="type" type="type" to: <xs:element name="name" type="type" minoccurs="0" Attribute "Description" (optional) added for occurences which have an "ID" attribute Wrong handling of IDREFS corrected: If there are IDREFS, no unbounded is necessary V2.2: <xs:element name="name" type="xs:idrefs" maxoccurs="unbounded"> V2.3: <xs:element name="name" type="xs:idrefs"> Assembly_part: containment of Assembly_part_occurrence, Component_occurrence, Connection added B_spline_curve: Control_points changed from containment to IDREFS Improvement of Cavity concept: - Cavity renamed to Cavity_occurrence, reference to Cavity (Part) added - New cavity part master added with name Cavity - Slot_occurrence added - Connector_occurrence containment of Cavity replaced by containment of Slot_occurrence New complextype Contact_point introduced: - Connection.extremities: IDREFS (to Cavity) replaced by containment of Contact_point - attribute Position_on_wire moved from Cavity to Contact_point - Type of Position_on_wire changed from Numerical_value to Double - Cavity.Associated_parts replaced by Associated_pug with just reference to Cavity_plug_occurrence Cavity_plug_occurrence, Cavity_seal_occurrence: containment of Part_substitution deleted Component, Component_occurrence added Connector_occurence: attribute Reference_element with IDREFS to Connector_occurrence added New complextype Cross_section_area added for use with Segment New complextype Dimension_specification, Tolerance added to allow the specification of tolerances General_wire: attribute Cross_section_area changed from optional to mandatory Harness: Explicit containment of Specified_xxx_occurrence removed Harness_configuration: Extension changed from Part to Part_with_title_block Harness_part deleted Node, Segment: Alias_id added Node: Attribute Coordinates_3D renamed to Cartesian-point New class Value_with_unit: Numerical_value and Value_range defined as extensions Part_substitution: Containment changed from "replaced" to "replacing" Protection_area: Attribute "Taping" changed "Taping_direction" Segment: - Grouping of Start_vector and end_vector by xs:sequence deleted - Attribute "Form" added - Attribute Real_length renamed to "Physical_length" - Attribute "Represented_length" renamed to "Virtual_length" - Attribute "Cross_section_area_information" added Transformation: - Attribute "Coordinates_3D" renamed to "Cartesian_point" - Grouping of u and v by xs:sequence deleted Value_range: Attribute Unit_component changed from containment to IDREF New complextype Wiring_group added Part/PArt_with_title_block: Attribute "Company_name" moved from Part_with_title_block to Part Alias_part: replaced by new complextype Alias_identification with attributes "Alias_id", "Scope" and "Description" Alias_id: Type changed from "String" to "Alias_identification" Connector_housing: type of attribute "Usage" changed from String to enumeration "Connector_usage" Harness: type of attribute "Content" changed from String to enumeration "Harness_content" Module: type of attribute "Content" changed from String to enumeration "Module_content" Module: type of attribute "Configuration_type" changed from String to enumeration "Module_configuration_type"
4 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 4 of 20 Unit: type of attribute "SI_unit_name" changed from String to enumeration "SI_unit_name" Unit: type of attribute "SI_prefix" changed from String to enumeration "SI_prefix" Connection: Reference to "External_reference" added Node: Attribute Bend_radius added --> <xs:schema xmlns:xs=" xmlns:kbl=" targetnamespace=" <xs:documentation> KBL XML Schema </xs:documentation> <xs:appinfo source=" <kbl:schemainfo name="kbl.xsd" date=" " version="2.3" status="release"/> </xs:appinfo> <xs:complextype name="accessory"> <xs:element name="accessory_type" type="xs:string" minoccurs="0"/> <xs:complextype name="accessory_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="placement" type="kbl:transformation" minoccurs="0"/> <xs:documentation>ref to Accessory</xs:documentation> <xs:element name="reference_element" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to Connector_occurrence</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:complextype name="alias_identification"> <xs:element name="alias_id" type="xs:string"/> <xs:element name="scope" type="xs:string" minoccurs="0"/> <xs:complextype name="approval"> <xs:element name="name" type="xs:string" minoccurs="0"/> <xs:element name="department" type="xs:string" minoccurs="0"/> <xs:element name="date" type="xs:string"/> <xs:element name="type_of_approval" type="xs:string"/> <xs:element name="is_applied_to" type="xs:idrefs"> <xs:documentation>ref to Part_with_title_block</xs:documentation> <xs:complextype name="assembly_part">
5 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 5 of 20 <xs:element name="part_type" type="xs:string" minoccurs="0"/> <xs:element name="accessory_occurrence" type="kbl:accessory_occurrence" minoccurs="0" <xs:element name="assembly_part_occurrence" type="kbl:assembly_part_occurrence" minoccurs="0" <xs:element name="cavity_plug_occurrence" type="kbl:cavity_plug_occurrence" minoccurs="0" <xs:element name="cavity_seal_occurrence" type="kbl:cavity_seal_occurrence" minoccurs="0" <xs:element name="co_pack_occurrence" type="kbl:co_pack_occurrence" minoccurs="0" <xs:element name="component_occurrence" type="kbl:component_occurrence" minoccurs="0" <xs:element name="connection" type="kbl:connection" minoccurs="0" <xs:element name="connector_occurrence" type="kbl:connector_occurrence" minoccurs="0" <xs:element name="fixing_occurrence" type="kbl:fixing_occurrence" minoccurs="0" <xs:element name="general_wire_occurrence" type="kbl:general_wire_occurrence" minoccurs="0" <xs:element name="special_terminal_occurrence" type="kbl:special_terminal_occurrence" minoccurs="0" <xs:element name="terminal_occurrence" type="kbl:terminal_occurrence" minoccurs="0" <xs:element name="wire_protection_occurrence" type="kbl:wire_protection_occurrence" minoccurs="0" <xs:element name="wiring_group" type="kbl:wiring_group" minoccurs="0" <xs:complextype name="assembly_part_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="placement" type="kbl:transformation" minoccurs="0"/> <xs:documentation>ref to Assembly_part</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:complextype name="b_spline_curve"> <xs:element name="degree" type="xs:integer"/> <xs:element name="control_points" type="xs:idrefs"> <xs:documentation>ref to Cartesian_point</xs:documentation> <xs:appinfo>there shall be at least 2 elements referenced.</xs:appinfo> <xs:complextype name="cartesian_point"> <xs:element name="coordinates" type="xs:double" minoccurs="2" maxoccurs="3"/> <xs:complextype name="cavity"> <xs:element name="cavity_number" type="xs:string"/> <xs:complextype name="cavity_occurrence">
6 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 6 of 20 <xs:element name="associated_plug" type="xs:idref" minoccurs="0"> <xs:documentation>ref to Cavity_plug_occurrence</xs:documentation> <xs:documentation>ref to Cavity</xs:documentation> <xs:complextype name="cavity_plug"> <xs:element name="colour" type="xs:string" minoccurs="0"/> <xs:element name="plug_type" type="xs:string" minoccurs="0"/> <xs:complextype name="cavity_plug_occurrence"> <xs:documentation>ref to Cavity_plug</xs:documentation> <xs:complextype name="cavity_seal"> <xs:element name="colour" type="xs:string" minoccurs="0"/> <xs:element name="seal_type" type="xs:string" minoccurs="0"/> <xs:element name="wire_size" type="kbl:value_range" minoccurs="0"/> <xs:complextype name="cavity_seal_occurrence"> <xs:documentation>ref to Cavity_seal</xs:documentation> <xs:element name="replacing" type="kbl:part_substitution" minoccurs="0" <xs:complextype name="change"> <xs:element name="id" type="xs:string" minoccurs="0"/> <xs:element name="change_request" type="xs:string" minoccurs="0"/> <xs:element name="change_date" type="xs:string" minoccurs="0"/> <xs:element name="responsible_designer" type="xs:string"/> <xs:element name="designer_department" type="xs:string"/> <xs:element name="approver_name" type="xs:string" minoccurs="0"/> <xs:element name="approver_department" type="xs:string" minoccurs="0"/> <xs:complextype name="co_pack_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0"
7 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 7 of 20 <xs:documentation>ref to Co_pack_part</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:complextype name="co_pack_part"> <xs:element name="part_type" type="xs:string" minoccurs="0"/> <xs:complextype name="component"> <xs:extension base="kbl:part"/> <xs:complextype name="component_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0"/> <xs:element name="mounting" type="xs:idrefs"> <xs:documentation>ref to Cavity_occurrence, Connector_occurrence, Slot_occurrence</xs:documentation> <xs:documentation>ref to Component</xs:documentation> <xs:complextype name="connection"> <xs:element name="id" type="xs:string" minoccurs="0"/> <xs:element name="signal_name" type="xs:string" minoccurs="0"/> <xs:element name="external_references" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to External_reference</xs:documentation> <xs:element name="wire" type="xs:idref"> <xs:documentation>ref to Core_occurrence, Wire_occurrence</xs:documentation> <xs:element name="extremities" type="kbl:contact_point" minoccurs="2" <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:element name="processing_information" type="kbl:processing_instruction" minoccurs="0" <xs:complextype name="connector_housing"> <xs:element name="housing_colour" type="xs:string" minoccurs="0"/> <xs:element name="housing_code" type="xs:string" minoccurs="0"/> <xs:element name="housing_type" type="xs:string" minoccurs="0"/> <xs:element name="slots" type="kbl:slot" minoccurs="0"
8 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 8 of 20 <xs:complextype name="connector_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="usage" type="kbl:connector_usage" minoccurs="0"/> <xs:element name="placement" type="kbl:transformation" minoccurs="0"/> <xs:documentation>ref to Connector_housing</xs:documentation> <xs:element name="reference_element" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to Connector_occurrence</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:element name="slots" type="kbl:slot_occurrence" minoccurs="0" <xs:complextype name="contact_point"> <xs:element name="position_on_wire" type="xs:double"/> <xs:element name="associated_parts" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to Cavity_seal_occurrence, Special_terminal_occurrence, Terminal_occurrence</xs:documentation> <xs:element name="contacted_cavity" type="xs:idrefs"> <xs:documentation>ref to Cavity_occurrence</xs:documentation> <xs:complextype name="core"> <xs:element name="cable_designator" type="xs:string" minoccurs="0"/> <xs:element name="wire_type" type="xs:string" minoccurs="0"/> <xs:element name="cross_section_area" type="kbl:numerical_value"/> <xs:element name="outside_diameter" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="bend_radius" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="core_colour" type="kbl:wire_colour" <xs:complextype name="core_occurrence"> <xs:element name="wire_number" type="xs:string"/> <xs:documentation>ref to Core</xs:documentation> <xs:element name="length_information" type="kbl:wire_length" <xs:complextype name="creation"> <xs:element name="name" type="xs:string"/> <xs:element name="department" type="xs:string"/>
9 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 9 of 20 <xs:element name="date" type="xs:string"/> <xs:element name="is_applied_to" type="xs:idrefs"> <xs:documentation>ref to Part_with_title_block</xs:documentation> <xs:complextype name="cross_section_area"> <xs:element name="value_determination" type="kbl:value_determination"/> <xs:element name="area" type="kbl:numerical_value"/> <xs:complextype name="dimension_specification"> <xs:element name="origin" type="xs:idref"> <xs:documentation>ref to Dimension_specification,, Accessory_occurrence, Assembly_part_occurrence, Connector_occurrence, Fixing_occurrence, Special_terminal_occurrence, Wire_protection_occurrenceNode</xs:documentation> <xs:element name="target" type="xs:idref"> <xs:documentation>ref to Dimension_specification,, Accessory_occurrence, Assembly_part_occurrence, Connector_occurrence, Fixing_occurrence, Special_terminal_occurrence, Wire_protection_occurrenceNode</xs:documentation> <xs:element name="tolerance_indication" type="kbl:tolerance" minoccurs="0"/> <xs:complextype name="external_reference"> <xs:element name="document_type" type="xs:string"/> <xs:element name="document_number" type="xs:string"/> <xs:element name="change_level" type="xs:string"/> <xs:element name="file_name" type="xs:string" minoccurs="0"/> <xs:element name="location" type="xs:string" minoccurs="0"/> <xs:element name="data_format" type="xs:string"/> <xs:element name="creating_system" type="xs:string" minoccurs="0"/> <xs:complextype name="fixing"> <xs:element name="fixing_type" type="xs:string" minoccurs="0"/> <xs:complextype name="fixing_assignment"> <xs:element name="location" type="xs:double"/> <xs:element name="orientation" type="xs:double" minoccurs="2" maxoccurs="3"/> <xs:element name="fixing" type="xs:idref"> <xs:documentation>ref to Accessory_occurrence, Fixing_occurrence</xs:documentation> <xs:complextype name="fixing_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0"
10 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 10 of 20 <xs:element name="placement" type="kbl:transformation" minoccurs="0"/> <xs:documentation>ref to Fixing</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:complextype name="general_terminal"> <xs:element name="terminal_type" type="xs:string" minoccurs="0"/> <xs:element name="plating_material" type="xs:string" minoccurs="0"/> <xs:element name="cross_section_area" type="kbl:value_range" minoccurs="0"/> <xs:element name="outside_diameter" type="kbl:value_range" minoccurs="0"/> <xs:complextype name="general_wire"> <xs:element name="cable_designator" type="xs:string" minoccurs="0"/> <xs:element name="wire_type" type="xs:string" minoccurs="0"/> <xs:element name="bend_radius" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="cross_section_area" type="kbl:numerical_value"/> <xs:element name="outside_diameter" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="core" type="kbl:core" minoccurs="0" <xs:element name="cover_colour" type="kbl:wire_colour" <xs:complextype name="general_wire_occurrence" abstract="true"> <xs:documentation>ref to General_wire</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:element name="length_information" type="kbl:wire_length" <xs:complextype name="harness"> <xs:extension base="kbl:part_with_title_block"> <xs:element name="content" type="kbl:harness_content"/> <xs:element name="accessory_occurrence" type="kbl:accessory_occurrence" minoccurs="0" <xs:element name="assembly_part_occurrence" type="kbl:assembly_part_occurrence" minoccurs="0" <xs:element name="cavity_plug_occurrence" type="kbl:cavity_plug_occurrence" minoccurs="0" <xs:element name="cavity_seal_occurrence" type="kbl:cavity_seal_occurrence" minoccurs="0" <xs:element name="co_pack_occurrence" type="kbl:co_pack_occurrence" minoccurs="0" <xs:element name="component_occurrence" type="kbl:component_occurrence" minoccurs="0" <xs:element name="connection" type="kbl:connection" minoccurs="0" <xs:element name="connector_occurrence" type="kbl:connector_occurrence" minoccurs="0"
11 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 11 of 20 <xs:element name="fixing_occurrence" type="kbl:fixing_occurrence" minoccurs="0" <xs:element name="general_wire_occurrence" type="kbl:general_wire_occurrence" minoccurs="0" <xs:element name="special_terminal_occurrence" type="kbl:special_terminal_occurrence" minoccurs="0" <xs:element name="terminal_occurrence" type="kbl:terminal_occurrence" minoccurs="0" <xs:element name="wire_protection_occurrence" type="kbl:wire_protection_occurrence" minoccurs="0" <xs:element name="wiring_group" type="kbl:wiring_group" minoccurs="0" <xs:element name="harness_configuration" type="kbl:harness_configuration" minoccurs="0" <xs:element name="module" type="kbl:module" minoccurs="0" <xs:element name="module_configuration" type="kbl:module_configuration" minoccurs="0" <xs:element name="module_families" type="kbl:module_family" minoccurs="0" <xs:complextype name="harness_configuration"> <xs:extension base="kbl:part_with_title_block"> <xs:element name="logistic_control_information" type="xs:string" minoccurs="0"/> <xs:element name="modules" type="xs:idrefs"> <xs:documentation>ref to Module</xs:documentation> <xs:complextype name="installation_instruction"> <xs:element name="instruction_type" type="xs:string"/> <xs:element name="instruction_value" type="xs:string"/> <xs:element name="kbl_container" type="kbl:kbl_container"/> <xs:complextype name="kbl_container"> <xs:element name="accessory" type="kbl:accessory" minoccurs="0" <xs:element name="approval" type="kbl:approval" minoccurs="0" <xs:element name="assembly_part" type="kbl:assembly_part" minoccurs="0" <xs:element name="cartesian_point" type="kbl:cartesian_point" minoccurs="0" <xs:element name="cavity_plug" type="kbl:cavity_plug" minoccurs="0" <xs:element name="cavity_seal" type="kbl:cavity_seal" minoccurs="0" <xs:element name="co_pack_part" type="kbl:co_pack_part" minoccurs="0" <xs:element name="component" type="kbl:component" minoccurs="0" <xs:element name="connector_housing" type="kbl:connector_housing" minoccurs="0" <xs:element name="creation" type="kbl:creation" minoccurs="0" <xs:element name="dimension_specification" type="kbl:dimension_specification" minoccurs="0" <xs:element name="external_reference" type="kbl:external_reference" minoccurs="0" <xs:element name="fixing" type="kbl:fixing" minoccurs="0" <xs:element name="general_terminal" type="kbl:general_terminal" minoccurs="0" <xs:element name="general_wire" type="kbl:general_wire" minoccurs="0" <xs:element name="harness" type="kbl:harness" minoccurs="0"/> <xs:element name="node" type="kbl:node" minoccurs="0" <xs:element name="routing" type="kbl:routing" minoccurs="0" <xs:element name="segment" type="kbl:segment" minoccurs="0" <xs:element name="unit" type="kbl:unit" minoccurs="0" <xs:element name="wire_protection" type="kbl:wire_protection" minoccurs="0" <xs:complextype name="material"> <xs:element name="material_key" type="xs:string"/>
12 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 12 of 20 <xs:element name="material_reference_system" type="xs:string" minoccurs="0"/> <xs:complextype name="module"> <xs:extension base="kbl:part_with_title_block"> <xs:element name="content" type="kbl:module_content"/> <xs:element name="of_family" type="xs:idref" minoccurs="0"> <xs:documentation>ref to Module_family</xs:documentation> <xs:element name="module_configuration" type="kbl:module_configuration"/> <xs:complextype name="module_configuration"> <xs:element name="logistic_control_information" type="xs:string"/> <xs:element name="configuration_type" type="kbl:module_configuration_type" minoccurs="0"/> <xs:element name="controlled_components" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to Accessory_occurrence, Assembly_part_occurrence, Cavity_plug_occurrence, Cavity_seal_occurrence, Co_pack_occurrence, Component_occurrence, Connection, Connector_occurrence, Fixing_occurrence, General_wire_occurrence, Special_terminal_occurrence, Terminal_occurrence, Wire_protection_occurrence, Wiring_group</xs:documentation> <xs:complextype name="module_family"> <xs:complextype name="node"> <xs:element name="alias_id" type="xs:string" minoccurs="0"/> <xs:element name="cartesian_point" type="kbl:cartesian_point"/> <xs:element name="bend_radius" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="referenced_components" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to Accessory_occurrence, Assembly_part_occurrence, Connector_occurrence, Fixing_occurrence, Special_terminal_occurrence, Wire_protection_occurrence</xs:documentation> <xs:element name="processing_information" type="kbl:processing_instruction" minoccurs="0" <xs:complextype name="numerical_value"> <xs:extension base="kbl:value_with_unit"> <xs:element name="value_component" type="xs:double"/> <xs:complextype name="part" abstract="true"> <xs:element name="part_number" type="xs:string"/> <xs:element name="company_name" type="xs:string"/> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="version" type="xs:string"/>
13 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 13 of 20 <xs:element name="abbreviation" type="xs:string"/> <xs:element name="description" type="xs:string"/> <xs:element name="predecessor_part_number" type="xs:string" minoccurs="0"/> <xs:element name="degree_of_maturity" type="xs:string" minoccurs="0"/> <xs:element name="copyright_note" type="xs:string" minoccurs="0"/> <xs:element name="mass_information" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="external_references" type="xs:idrefs" minoccurs="0"> <xs:documentation>ref to External_reference</xs:documentation> <xs:element name="change" type="kbl:change" minoccurs="0" <xs:element name="material_information" type="kbl:material" minoccurs="0"/> <xs:element name="processing_information" type="kbl:processing_instruction" minoccurs="0" <xs:complextype name="part_substitution"> <xs:element name="replaced" type="xs:idref"> <xs:documentation>ref to Cavity_plug_occurrence</xs:documentation> <xs:complextype name="part_with_title_block" abstract="true"> <xs:element name="project_number" type="xs:string" minoccurs="0"/> <xs:element name="car_classification_level_2" type="xs:string"/> <xs:element name="car_classification_level_3" type="xs:string" minoccurs="0"/> <xs:element name="car_classification_level_4" type="xs:string" minoccurs="0"/> <xs:element name="model_year" type="xs:string"/> <xs:complextype name="processing_instruction"> <xs:element name="instruction_type" type="xs:string"/> <xs:element name="instruction_value" type="xs:string"/> <xs:complextype name="protection_area"> <xs:element name="start_location" type="xs:double"/> <xs:element name="end_location" type="xs:double"/> <xs:element name="taping_direction" type="xs:string" minoccurs="0"/> <xs:element name="gradient" type="kbl:value_with_unit" minoccurs="0"/> <xs:element name="associated_protection" type="xs:idref"> <xs:documentation>ref to Wire_protection_occurrence</xs:documentation> <xs:element name="processing_information" type="kbl:processing_instruction" minoccurs="0" <xs:complextype name="routing"> <xs:element name="routed_wire" type="xs:idref"> <xs:documentation>ref to Connection</xs:documentation> <xs:element name="segments" type="xs:idrefs" minoccurs="0">
14 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 14 of 20 <xs:documentation>ref to Segment</xs:documentation> <xs:complextype name="segment"> <xs:element name="alias_id" type="xs:string" minoccurs="0"/> <xs:element name="start_vector" type="xs:double" minoccurs="0" maxoccurs="3"/> <xs:element name="end_vector" type="xs:double" minoccurs="0" maxoccurs="3"/> <xs:element name="virtual_length" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="physical_length" type="kbl:numerical_value" minoccurs="0"/> <xs:element name="form" type="kbl:segment_form" minoccurs="0"/> <xs:element name="end_node" type="xs:idref"> <xs:documentation>ref to Node</xs:documentation> <xs:element name="start_node" type="xs:idref"> <xs:documentation>ref to Node</xs:documentation> <xs:element name="center_curve" type="kbl:b_spline_curve" minoccurs="0" <xs:element name="cross_section_area_information" type="kbl:cross_section_area" minoccurs="0" <xs:element name="fixing_assignment" type="kbl:fixing_assignment" minoccurs="0" <xs:element name="protection_area" type="kbl:protection_area" minoccurs="0" <xs:complextype name="slot"> <xs:element name="id" type="xs:string" minoccurs="0"/> <xs:element name="number_of_cavities" type="xs:integer"/> <xs:element name="cavities" type="kbl:cavity" <xs:complextype name="slot_occurrence"> <xs:documentation>ref to Slot</xs:documentation> <xs:element name="cavities" type="kbl:cavity_occurrence" <xs:complextype name="special_terminal_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="placement" type="kbl:transformation" minoccurs="0"/> <xs:documentation>ref to General_terminal</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:element name="replacing" type="kbl:part_substitution" minoccurs="0" <xs:complextype name="special_wire_occurrence"> <xs:extension base="kbl:general_wire_occurrence">
15 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 15 of 20 <xs:element name="special_wire_id" type="xs:string"/> <xs:element name="core_occurrence" type="kbl:core_occurrence" minoccurs="0" <xs:complextype name="specified_accessory_occurrence"> <xs:extension base="kbl:accessory_occurrence"> <xs:documentation>ref to Accessory_occurrence</xs:documentation> <xs:complextype name="specified_cavity_plug_occurrence"> <xs:extension base="kbl:cavity_plug_occurrence"> <xs:documentation>ref to Cavity_plug_occurrence</xs:documentation> <xs:complextype name="specified_cavity_seal_occurrence"> <xs:extension base="kbl:cavity_seal_occurrence"> <xs:documentation>ref to Cavity_seal_occurrence</xs:documentation> <xs:complextype name="specified_co_pack_occurrence"> <xs:extension base="kbl:co_pack_occurrence"> <xs:documentation>ref to Co_pack_occurrence</xs:documentation>
16 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 16 of 20 <xs:complextype name="specified_connector_occurrence"> <xs:extension base="kbl:connector_occurrence"> <xs:documentation>ref to Connector_occurrence</xs:documentation> <xs:complextype name="specified_fixing_occurrence"> <xs:extension base="kbl:fixing_occurrence"> <xs:documentation>ref to Fixing_occurrence</xs:documentation> <xs:complextype name="specified_special_terminal_occurrence"> <xs:extension base="kbl:special_terminal_occurrence"> <xs:documentation>ref to Special_terminal_occurrence</xs:documentation> <xs:complextype name="specified_special_wire_occurrence"> <xs:extension base="kbl:special_wire_occurrence"> <xs:documentation>ref to Special_wire_occurrence</xs:documentation>
17 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 17 of 20 <xs:complextype name="specified_terminal_occurrence"> <xs:extension base="kbl:terminal_occurrence"> <xs:documentation>ref to Terminal_occurrence</xs:documentation> <xs:complextype name="specified_wire_occurrence"> <xs:extension base="kbl:wire_occurrence"> <xs:documentation>ref to Wire_occurrence</xs:documentation> <xs:complextype name="specified_wire_protection_occurrence"> <xs:extension base="kbl:wire_protection_occurrence"> <xs:documentation>ref to Wire_protection_occurrence</xs:documentation> <xs:complextype name="terminal_occurrence"> <xs:documentation>ref to General_terminal</xs:documentation> <xs:element name="replacing" type="kbl:part_substitution" minoccurs="0" <xs:complextype name="tolerance"> <xs:element name="lower_limit" type="kbl:numerical_value" minoccurs="0"/>
18 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 18 of 20 <xs:element name="upper_limit" type="kbl:numerical_value" minoccurs="0"/> <xs:complextype name="transformation"> <xs:element name="u" type="xs:double" minoccurs="0" maxoccurs="3"/> <xs:element name="v" type="xs:double" minoccurs="0" maxoccurs="3"/> <xs:element name="cartesian_point" type="xs:idref"> <xs:documentation>ref to Cartesian_point</xs:documentation> <xs:complextype name="unit"> <xs:element name="unit_name" type="xs:string" minoccurs="0"/> <xs:element name="si_unit_name" type="kbl:si_unit_name" minoccurs="0"/> <xs:element name="si_prefix" type="kbl:si_prefix" minoccurs="0"/> <xs:complextype name="value_range"> <xs:extension base="kbl:value_with_unit"> <xs:element name="minimum" type="xs:double"/> <xs:element name="maximum" type="xs:double"/> <xs:complextype name="value_with_unit" abstract="true"> <xs:element name="unit_component" type="xs:idref"> <xs:documentation>ref to Unit</xs:documentation> <xs:complextype name="wire_colour"> <xs:element name="colour_type" type="xs:string"/> <xs:element name="colour_value" type="xs:string"/> <xs:complextype name="wire_length"> <xs:element name="length_type" type="xs:string"/> <xs:element name="length_value" type="kbl:numerical_value"/> <xs:complextype name="wire_occurrence"> <xs:extension base="kbl:general_wire_occurrence"> <xs:element name="wire_number" type="xs:string"/> <xs:complextype name="wire_protection"> <xs:element name="protection_type" type="xs:string" minoccurs="0"/> <xs:element name="type_dependent_parameter" type="xs:string" minoccurs="0"/>
19 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 19 of 20 <xs:complextype name="wire_protection_occurrence"> <xs:element name="alias_id" type="kbl:alias_identification" minoccurs="0" <xs:element name="protection_length" type="kbl:numerical_value" minoccurs="0"/> <xs:documentation>ref to Wire_protection</xs:documentation> <xs:element name="installation_information" type="kbl:installation_instruction" minoccurs="0" <xs:complextype name="wiring_group"> <xs:element name="type" type="xs:string" minoccurs="0"/> <xs:element name="assigned_wire" type="xs:idrefs"> <xs:documentation>ref to Core_occurrence, Wire_occurrence</xs:documentation> <xs:appinfo>there shall be at least 2 elements referenced.</xs:appinfo> <xs:element name="processing_information" type="kbl:processing_instruction" minoccurs="0" <xs:simpletype name="module_content"> <xs:restriction base="xs:string"> <xs:enumeration value="module"/> <xs:enumeration value="variant"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="module_configuration_type"> <xs:restriction base="xs:string"> <xs:enumeration value="option code"/> <xs:enumeration value="module list"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="harness_content"> <xs:restriction base="xs:string"> <xs:enumeration value="harness complete set"/> <xs:enumeration value="harness subset"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="connector_usage"> <xs:restriction base="xs:string"> <xs:enumeration value="no end"/> <xs:enumeration value="ring terminal"/> <xs:enumeration value="splice"/> <xs:enumeration value="dangler"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="segment_form"> <xs:restriction base="xs:string"/> </xs:simpletype> <xs:simpletype name="si_unit_name"> <xs:restriction base="xs:string"> <xs:enumeration value="metre"/> <xs:enumeration value="square metre"/> <xs:enumeration value="gram"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="si_prefix"> <xs:restriction base="xs:string">
20 VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 20 of 20 <xs:enumeration value="milli"/> <xs:enumeration value="centi"/> <xs:enumeration value="micro"/> <xs:enumeration value="kilo"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="value_determination"> <xs:restriction base="xs:string"> <xs:enumeration value="calculated"/> <xs:enumeration value="reserved"/> <xs:enumeration value="measured"/> </xs:restriction> </xs:simpletype> </xs:schema>
QosPolicyHolder:1 Erratum
Erratum Number: Document and Version: Cross References: Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to the service document QosPolicyHolder:1 This Erratum has
More informationX3D Unit Specification Updates Myeong Won Lee The University of Suwon
X3D Unit Specification Updates Myeong Won Lee The University of Suwon 1 Units Specification ISO_IEC_19775_1_2008_WD3_Am1_2011_04_14 PDAM in ISO progress UNIT statement Defined in Core component UNIT statements
More informationOracle Enterprise Data Quality
Oracle Enterprise Data Quality Automated Loading and Running of Projects Version 9.0 January 2012 Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Enterprise Data Quality,
More informationOracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents
Oracle B2B 11g Technical Note Technical Note: 11g_005 Attachments This technical note lists the attachment capabilities available in Oracle B2B Table of Contents Overview... 2 Setup for Fabric... 2 Setup
More informationDocument erratum applies to QosDevice:1. List other Erratum s or Documents that this change may apply to or have associated changes with
Erratum Number: Document and Version: Cross References: QosDevice:1 Erratum Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to QosDevice:1 List other Erratum s or
More informationRestricting complextypes that have mixed content
Restricting complextypes that have mixed content Roger L. Costello October 2012 complextype with mixed content (no attributes) Here is a complextype with mixed content:
More information/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC)
/// Rapport / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC) / Maart 2017 www.vlaanderen.be/informatievlaanderen Informatie Vlaanderen /// Aanpassingen aan de webservices Dit
More informationThe following is a sample XML code from the HCSProductCatalog.wsdl file.
APPENDIXA This appendix contains sample WSDL and XSD files. It includes the following sections: HCSProductCatalog.wsdl File, page A-1 HCSProvision.xsd File, page A-27 HCSProvisionAsyncResponse.wsdl File,
More informationBrief guide for XML, XML Schema, XQuery for YAWL data perspective
Brief guide for XML, XML Schema, XQuery for YAWL data perspective Carmen Bratosin March 16, 2009 1 Data perspective in YAWL YAWL engine files are XML based. Therefore, YAWL uses XML for data perspective
More informationApache UIMA Regular Expression Annotator Documentation
Apache UIMA Regular Expression Annotator Documentation Written and maintained by the Apache UIMA Development Community Version 2.3.1 Copyright 2006, 2011 The Apache Software Foundation License and Disclaimer.
More informationPattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description
Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description Jason McC. Smith Apr 7, 2004 Abstract Pattern/Object Markup Language (or POML) is a simple XML Schema for
More informationOracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related
More informationMWTM 6.1 NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-5 ProvisionAPI.wsdl, page
More information2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1)
Data-centric XML XML Schema (Part 1) Schema and DTD Disadvantages of DTD: separate, non-xml syntax very limited constraints on data types (just ID, IDREF, ) no support for sets (i.e. each element type
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXSHRMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationGeneral Service Subscription Management Technical Specification
General Service Subscription Management Technical Specification Approved Version 1.0 20 Dec 2011 Open Mobile Alliance OMA-TS-GSSM-V1_0-20111220-A OMA-TS-GSSM-V1_0-20111220-A Page 2 (32) Use of this document
More informationQosPolicyHolder 1.0. For UPnP Version Date: March 10th, 2005
QosPolicyHolder 1.0 For UPnP Version 1.0 2 Date: March 10th, 2005 This Standardized DCP has been adopted as a Standardized DCP by the Steering Committee of the UPnP Forum, pursuant to Section 2.1(c)(ii)
More informationMWTM NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1.4 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page
More informationXML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28
1 / 28 XML Schema Mario Alviano University of Calabria, Italy A.Y. 2017/2018 Outline 2 / 28 1 Introduction 2 Elements 3 Simple and complex types 4 Attributes 5 Groups and built-in 6 Import of other schemes
More informationKeio Virtual Sensor System based on Sensor- Over- XMPP
Keio Virtual Sensor System based on Sensor- Over- XMPP 1. Basic information Keio virtual sensor system is based on XMPP PubSub mechanism. Thus, we basically follow XMPP PubSub protocol (XEP- 0060: Publish-
More informationLevel of Assurance Authentication Context Profiles for SAML 2.0
2 3 4 5 Level of Assurance Authentication Context Profiles for SAML 2.0 Draft 01 01 April 2008 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Specification URIs: This
More informationPhysician Data Center API API Specification. 7/3/2014 Federation of State Medical Boards Kevin Hagen
7/3/2014 Federation of State Medical Boards Kevin Hagen Revision Description Date 1 Original Document 2/14/2014 2 Update with Degree search field 7/3/2014 Overview The Physician Data Center (PDC) offers
More informationIntroducing our First Schema
1 di 11 21/05/2006 10.24 Published on XML.com http://www.xml.com/pub/a/2000/11/29/schemas/part1.html See this if you're having trouble printing code examples Using W3C XML By Eric van der Vlist October
More informationTS SIGNATURE VALIDATION REPORT
TS 119 102 2 SIGNATURE VALIDATION REPORT An introduction Presented by Peter Lipp for the esignature and eseal validation workshop, Jan 10 2018 Agenda Scope Relation to EN 319 102 1 Approach Report structure
More informationFall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions
Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery
More informationSYNDICATING HIERARCHIES EFFECTIVELY
SDN Contribution SYNDICATING HIERARCHIES EFFECTIVELY Applies to: SAP MDM 5.5 Summary This document introduces hierarchy tables and a method of effectively sending out data stored in hierarchy tables. Created
More information<xs:include schemalocation="rdmessage,ver14 for NatParas.xsd"/> <xs:include schemalocation="natparas3.xsd"/>
More information
SMKI Repository Interface Design Specification TPMAG baseline submission draft version 8 September 2015
SMKI Repository Interface Design Specification DCC Public Page 1 of 21 Contents 1 Introduction 3 1.1 Purpose and Scope 3 1.2 Target Response Times 3 2 Interface Definition 4 2.1 SMKI Repository Portal
More informationTED schemas. Governance and latest updates
TED schemas Governance and latest updates Enric Staromiejski Torregrosa Carmelo Greco 9 October 2018 Agenda 1. Objectives 2. Scope 3. TED XSD 3.0.0 Technical harmonisation of all TED artefacts Code lists
More information[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification
[MS-OXWSSYNC]: Mailbox Contents Synchronization Web Service Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More informationReleased to: TSCP Architecture Committee
Business Authorization Identification and Labeling Scheme Version 1 (BAILS v.1.0) Prepared by: TSCP ILH Team Lead Author: Jean-Paul Buu-Sao, TSCP Released to: TSCP Architecture Committee Edition: 1.4 Published:
More informationColumbia University R. Mahy, Ed. SIP Edge LLC November An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
Network Working Group Request for Comments: 4235 Category: Standards Track J. Rosenberg Cisco Systems H. Schulzrinne Columbia University R. Mahy, Ed. SIP Edge LLC November 2005 Status of this Memo An INVITE-Initiated
More informationFIPA JXTA Discovery Middleware Specification
1 2 3 4 5 6 FOUNDATION FOR INTELLIGENT PHYSICAL AGENTS FIPA JXTA Discovery Middleware Specification 7 8 9 Document title FIPA JXTA Discovery Middleware Specification Document number Version 1.2 Document
More informationCustom Data Access with MapObjects Java Edition
Custom Data Access with MapObjects Java Edition Next Generation Command and Control System (NGCCS) Tactical Operations Center (TOC) 3-D Concurrent Technologies Corporation Derek Sedlmyer James Taylor 05/24/2005
More informationFIPA JXTA Discovery Middleware Specification
1 2 3 4 5 6 FOUNDATION FOR INTELLIGENT PHYSICAL AGENTS FIPA JXTA Discovery Middleware Specification 7 8 9 Document title FIPA JXTA Discovery Middleware Specification Document number PC00096A Document source
More informationVDS Service Broker APIs
CHAPTER 2 This chapter describes the HTTPS RESTful APIs for VDS-SB and the XML schema. CDN Management API, page 2-1 BFQDN Management API BFQDN Policy API CDN Adaptation Policy API CDN Selection Policy
More informationTest Assertions Part 2 - Test Assertion Markup Language Version 1.0
Test Assertions Part 2 - Test Assertion Markup Language Version 1.0 Draft 1.0.2 6 January 2010 Specification URIs: This Version: Previous Version: [NA] Latest Version: http://docs.oasis-open.org/tag/taml/v1.0/testassertionmarkuplanguage-1.0.html
More informationPTS XML STANDARD GUIDELINE
PTS XML STANDARD GUIDELINE September 2012 Turkish Medicines & Medical Devices Agency, Department of Pharmaceutical Track & Trace System Söğütözü Mahallesi 2176 Sok. No: 5 P.K.06520 Çankaya, Ankara Phone:
More informationValidation Language. GeoConnections Victoria, BC, Canada
Validation Language Submitted To: Program Manager GeoConnections Victoria, BC, Canada Submitted By: Jody Garnett Brent Owens Refractions Research Inc. Suite 400, 1207 Douglas Street Victoria, BC, V8W-2E7
More informationWhite Paper. Fabasoft Integration for Novell GroupWise. Fabasoft Folio 2017 R1 Update Rollup 1
White Paper Fabasoft Integration for Novell GroupWise Fabasoft Folio 2017 R1 Update Rollup 1 Copyright Fabasoft R&D GmbH, Linz, Austria, 2018. All rights reserved. All hardware and software names used
More informationCustomer Market Results Interface (CMRI) For RC Interface Specification. Version: 1.0.0
Customer Market Results Interface (CMRI) For RC Interface Specification Version: 1.0.0 November 1, 2018 Revision History Date Version Description 11/01/2018 1.0.0 Initial document release Page 2 of 10
More informationService Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation
Service Modeling Language (SML) Pratul Dublish Principal Program Manager Microsoft Corporation 1 Outline Introduction to SML SML Model Inter-Document References URI scheme deref() extension function Schema-based
More informationAlwaysUp Web Service API Version 11.0
AlwaysUp Web Service API Version 11.0 0. Version History... 2 1. Overview... 3 2. Operations... 4 2.1. Common Topics... 4 2.1.1. Authentication... 4 2.1.2. Error Handling... 4 2.2. Get Application Status...
More informationONVIF. XML Schema Version and Extension Handling White Paper
ONVIF 1 XML Schema Extension Handling ONVIF XML Schema Version and Extension Handling White Paper Version 1.2 December, 2015 1 Background 1.1 Purpose Version and extensions handling for XML schemas are
More informationIntellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights tice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,
More informationIODEF Data Model Status (progress from 03) <draft-ietf-inch-iodef-03>
IODEF Data Model Status (progress from 03) tracked @ https://rt.psg.com : inch-dm queue Roman Danyliw Wednesday, March 9. 2005 IETF 62, Minneapolis, USA Progress
More informationSchema XACML v0.11c.xsd
Schema XACML v0.11c.xsd schema location: targetnamespace: C:\temp\XACML v0.11c.xsd Elements Complex s Simple s and ActionsType EffectType attributefunction AndType divide equal greaterorequal lessorequal
More informationMarkup Languages. Lecture 4. XML Schema
Markup Languages Lecture 4. XML Schema Introduction to XML Schema XML Schema is an XML-based alternative to DTD. An XML schema describes the structure of an XML document. The XML Schema language is also
More informationCisco Prime Central 1.0 API Guide
Cisco Prime Central 1.0 API Guide Cisco Prime Central API Cisco Prime Central Information Model and API's to support the following features. Managed Elements and Equipment Inventory Object Create, Delete
More informationPTC Integrity 10.7 Web Services Reference
PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation
More informationXML. Document Type Definitions XML Schema. Database Systems and Concepts, CSCI 3030U, UOIT, Course Instructor: Jarek Szlichta
XML Document Type Definitions XML Schema 1 XML XML stands for extensible Markup Language. XML was designed to describe data. XML has come into common use for the interchange of data over the Internet.
More informationfile:///c:/users/tomh/appdata/local/microsoft/windows/temporary%20internet%20fil...
Page 1 of 9
More informationUser Manual. HIPAA Transactions System Integration for Channel Partner Vendor. Version 15.2 May 2015
User Manual HIPAA Transactions System Integration for Channel Partner Vendor Version 15.2 May 2015 Trademarks and Copyrights Optum HIPAA Transactions System Integration Document Channel Partner Vendor
More informationG16-02SE-A02.1-NUE112_SchedaContatto-Rev5 <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema"
More information
Messages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
More informationAON Schemas. Archive Schema APPENDIXA
APPENDIXA This appendix contains schemas used by AMC. It includes the following: Archive Schema, page A-1 Programmatic Management Interface APIs, page A-15 Message Log Schemas, page A-26 Note This information
More informationIntroduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML
Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying
More informationAutomated Load Forecast System (ALFS) For RC Interface Specification
Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load
More informationConfiguring a WMS Feature Source
Configuring a WMS Feature Source Overview This document describes how to specify additional configuration options for a MapGuide WMS feature source (i.e., configuring the GetMap request that is generated
More informationTrustmark Framework Technical Specification
Trustmark Framework Technical Specification Version 1.2 November 6, 2017 Published by the Georgia Tech Research Institute under the Trustmark Initiative https://trustmarkinitiative.org/ Table of Contents
More informationProject Members: Aniket Prabhune Reenal Mahajan Mudita Singhal
CS-5604 Information Storage and Retrieval Project Report Scenario/Class Diagram Synthesis (American South 2) Project Members: Aniket Prabhune (aprabhun@vt.edu) Reenal Mahajan (remahaja@vt.edu) Mudita Singhal
More informationQSAR DataBank - an approach for the digital organization and archiving of QSAR model information
QSAR DataBank - an approach for the digital organization and archiving of QSAR model information V. Ruusmann, S. Sild, U. Maran Institute of Chemistry, University of Tartu, Ravila 14a, 50411, Estonia *corresponding
More informationAntenna Data Exchange File Format (ADX)
Antenna Data Exchange File Format (ADX) Technical Reference Version 1.2 Implementation Approval: : Tony Paul Position: RF Safety Compliance Coordinator Process Owner: : Mike Wood Position: Chairman - MCF
More information[MS-MSL]: Mapping Specification Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationBig Data Exercises. Fall 2018 Week 8 ETH Zurich. XML validation
Big Data Exercises Fall 2018 Week 8 ETH Zurich XML validation Reading: (optional, but useful) XML in a Nutshell, Elliotte Rusty Harold, W. Scott Means, 3rd edition, 2005: Online via ETH Library 1. XML
More informationApproaches to using NEMSIS V3 Custom Elements
NEMSIS TAC Whitepaper Approaches to using NEMSIS V3 Custom Elements Date August 17, 2011 July 31, 2013 (added section Restrictions, page 11) March 13, 2014 ( CorrelationID now reads CustomElementID as
More informationCONVERTING CONCEPTUAL MODEL XUML TO XML SCHEMA
CONVERTING CONCEPTUAL MODEL XUML TO XML SCHEMA XUEMIN ZHANG School of Computer and Information Science, Hubei Engineering University, Xiaogan 432000, Hubei, China ABSTRACT As XML has become the standard
More informationAutomated Load Forecast System (ALFS) Interface Specification. Fall 2017 Release
Automated Load Forecast System (ALFS) Interface Specification Fall 2017 Release Version: 1.1 March 27, 2017 Revision History Date Version Description 03/01/2017 1.0 Initial document release related to
More information<xs:element name="relationshipdata" type="rr:relationshipdatatype"/> <xs:element name="header" type="rr:rrheadertype"> </xs:element>
More information
Relationship Record Common Data File (RR-CDF) Format V1.0
Relationship Record Common Data File (RR-CDF) Format V1.0 DRAFT, 0.9 2016-09-27 Contents 1. Introduction... 6 2. Abstract Data Content... 8 2.1. Relationship Registration State Transitions (Informative)...
More informationData Bus Client Interface Manager Interface Control Document
SunGuide SM : Data Bus Client Interface Manager Interface Control Document SunGuide-DB-CIM-ICD-1.0.0 Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee
More informationOpenTravel Alliance Best Practices
OpenTravel Alliance Best Practices OpenTravel Alliance, Inc. 333 John Carlyle Street, Suite 600 Alexandria, Va. 22314 USA +1 703-548-7005 Fax +1 703-548-1264 opentravel@disa.org http://www.opentravel.org/
More informationXML extensible Markup Language
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationSoftware Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationQVX File Format and QlikView Custom Connector
QVX File Format and QlikView Custom Connector Contents 1 QVX File Format... 2 1.1 QvxTableHeader XML Schema... 2 1.1.1 QvxTableHeader Element... 4 1.1.2 QvxFieldHeader Element... 5 1.1.3 QvxFieldType Type...
More informationOracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On Configuration Guide E84772-01 Last Update: Monday, October 09, 2017 Oracle Utilities Opower Energy Efficiency Web Portal -
More informationQualys Cloud Suite API Release Notes
Qualys Cloud Suite API Release Notes Version 2.28 Qualys Cloud Suite API gives you ways to integrate your programs and API calls with Qualys capabilities. You ll find all the details in our documentation,
More information[MS-TSWP]: Terminal Services Workspace Provisioning Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-TSWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationXSD Reference For EXPRESS XML language
VTT-TEC-ADA-08 Page 1 SECOM Co., Ltd. / VTT Building and Transport Yoshinobu Adachi E-Mail: yoshinobu.adachi@vtt.fi VTT-TEC-ADA-08 XSD Reference For EXPRESS XML language 2002/02/11 1. INTRODUCTION... 2
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-DPDQS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationQosManager:1. For UPnP Version 1.0 Date: March 10th, 2005
QosManager:1 For UPnP Version 1.0 Date: March 10th, 2005 This Standardized DCP has been adopted as a Standardized DCP by the Steering Committee of the UPnP Forum, pursuant to Section 2.1(c)(ii) of the
More information[MS-SSISPARAMS-Diff]: Integration Services Project Parameter File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for
More informationPISOA Interface Specification. Fall 2017 Release
PISOA Interface Specification Fall 2017 Release Version: 1.0 July 21, 2017 Revision History Date Version Description 07/21/2017 1.0 Initial document release related to the PISO Interfaces. RequestVERMeasurements
More informationOn why C# s type system needs an extension
On why C# s type system needs an extension Wolfgang Gehring University of Ulm, Faculty of Computer Science, D-89069 Ulm, Germany wgehring@informatik.uni-ulm.de Abstract. XML Schemas (XSD) are the type
More informationCSC503 Exam 2. Assume that the following functional dependencies beyond that of the primary key are valid:
CSC503 Exam 2 Name: Question 1 Assume that you have the following table: (OrderID, OrderDate, DeliveryDate, CustomerID, CustomerName, CustomerEmail, CustomerCity, CustomerState, CustomerZip, (ProductID,
More informationTesting of Service Oriented Architectures A practical approach / APPENDIX V1.0
Testing of Service Oriented Architectures A practical approach / APPENDIX V1.0 Schahram Dustdar, Stephan Haslinger 1 Distributed Systems Group, Vienna University of Technology dustdar@infosys.tuwien.ac.at
More informationWork/Studies History. Programming XML / XSD. Database
Work/Studies History 1. What was your emphasis in your bachelor s work at XXX? 2. What was the most interesting project you worked on there? 3. What is your emphasis in your master s work here at UF? 4.
More informationRelationship Record Common Data File format V1.1
Relationship Record Common Data File format V1.1 Final V1.1 2017-03-16 Contents 1. Introduction... 5 1.1. Status of this document... 5 1.2. Terminology and Typographical Conventions... 5 1.3. Cardinalities...
More informationCMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION
CMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION CONTENTS 1. Introduction 1.1. Purpose 1.2. Scope Of Project 1.3. Glossary 1.4. References 1.5. Overview Of Document 2. Overall Description 2.1. System
More informationExtensible Markup Language Processing
CHAPTER 2 Revised: June 24, 2009, This chapter describes the Extensible Markup Language (XML) process in the Common Object Request Broker Architecture (CORBA) adapter. XML and Components Along with XML,
More informationOverview of the EU ETS Reporting Language (XETL)
Overview of the EU ETS Reporting Language (XETL) General The EU ETS Reporting Language is an electronic ing language supporting EU ETS Monitoring, Reporting and Validation (MRV) activities such as submitting
More informationDigital Signage Network Playlog Standards
Digital Signage Network Playlog Standards Version 1.1, August 23, 2006 Editor-In-Chief William Wu (DS-IQ) william.wu@ds-iq.com Editors Jeff Porter (Scala) jeff.porter@scala.com Steve Saxe (3M) sgsaxe@mmm.com
More information3GPP TS V8.2.0 ( )
TS 24.623 V8.2.0 (2009-12) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Extensible Markup Language (XML) Configuration Access Protocol
More informationAdministering Oracle Enterprise Data Quality 12c (12.2.1)
[1]Oracle Fusion Middleware Administering Oracle Enterprise Data Quality 12c (12.2.1) E56642-01 October 2015 Describes how to administer Oracle Enterprise Data Quality. Oracle Fusion Middleware Administering
More informationCisco Unity Connection Notification Interface (CUNI) API
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 2018 Cisco Systems, Inc. All rights
More information