RESOURCE SCHEDULE CONFIRMATION DOCUMENT UML MODEL AND SCHEMA
|
|
- Cornelia Strickland
- 5 years ago
- Views:
Transcription
1 1 RESOURCE SCHEDULE CONFIRMATION DOCUMENT UML MODEL AND SCHEMA APPROVED DOCUMENT
2 Table of Contents 1 Objective ResourceScheduleConfirmation_MarketDocument... 7 model... 7 Overview of the model... 7 IsBasedOn relationships from the European style market profile... 8 Resource schedule confirmation assembly model... 9 Overview of the model... 9 IsBasedOn relationships from the European style market profile Detailed Resource schedule confirmation assembly model ResourceScheduleConfirmation_MarketDocument root class Original_MarketDocument PlannedResource_TimeSeries Point Reason Series_Period UnavailableReserve_TimeSeries Datatypes ResourceScheduleConfirmation_MarketDocument XML schema structure ResourceScheduleConfirmation_MarketDocument XML schema List of figures Figure 1 - model... 7 Figure 2 - Resource schedule confirmation assembly model... 9 Figure 3 - ResourceScheduleConfirmation_MarketDocument schema structure List of tables Table 1 - IsBasedOn dependency... 8 Table 2 - IsBasedOn dependency Table 3 - Attributes of Resource schedule confirmation assembly model::resourcescheduleconfirmation_marketdocument Table 4 - Association ends of Resource schedule confirmation assembly model::resourcescheduleconfirmation_marketdocument with other classes Table 5 - Attributes of Resource schedule confirmation assembly model::original_marketdocument Table 6 - Association ends of Resource schedule confirmation assembly model::original_marketdocument with other classes Table 7 - Attributes of Resource schedule confirmation assembly model::plannedresource_timeseries Table 8 - Association ends of Resource schedule confirmation assembly model::plannedresource_timeseries with other classes Table 9 - Attributes of Resource schedule confirmation assembly model::point Table 10 - Association ends of Resource schedule confirmation assembly model::point with other classes Page 2 of 22
3 Table 11 - Attributes of Resource schedule confirmation assembly model::reason Table 12 - Attributes of Resource schedule confirmation assembly model::series_period Table 13 - Association ends of Resource schedule confirmation assembly model::series_period with other classes Table 14 - Attributes of Resource schedule confirmation assembly model::unavailablereserve_timeseries Table 15 - Association ends of Resource schedule confirmation assembly model::unavailablereserve_timeseries with other classes Page 3 of 22
4 Copyright notice: Copyright ENTSO-E. All Rights Reserved. This document and its whole translations may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, except for literal and whole translation into languages other than English and under all circumstances, the copyright notice or references to ENTSO-E may not be removed. This document and the information contained herein is provided on an "as is" basis. ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Maintenance notice: This document is maintained by the ENTSO-E CIM EG. Comments or remarks are to be provided at cim@entsoe.eu Page 4 of 22
5 76 Revision History Version Release Date Comments First draft of the document Approved by MC. Page 5 of 22
6 Objective The purpose of this document is to provide the contextual and assembly UML models and the schema of the ResourceScheduleConfirmation_MarketDocument. The schema of the ResourceScheduleConfirmation_MarketDocument could be used in various business processes. It is not the purpose of this document to describe all the use cases, sequence diagrams, business processes, etc. for which this schema is to be used. This document shall only be referenced in an implementation guide of a specific business process. The content of the business process implementation guide shall be as follows: Description of the business process; Use case of the business process; Sequence diagrams of the business process; List of the schema (XSD) to be used in the business process and versions of the schema; For each schema, dependency tables providing the necessary information for the generation of the XML instances, i.e. when the optional attributes are to be used, which codes from which ENTSO-E codelist are to be used. 95 Page 6 of 22
7 ResourceScheduleConfirmation_MarketDocument model Overview of the model Figure 1 shows the model Figure 1 - model 102 Page 7 of 22
8 IsBasedOn relationships from the European style market profile Table 1 shows the traceability dependency of the classes used in this package towards the upper level. Table 1 - IsBasedOn dependency Name Complete IsBasedOn Path Domain FlowDirection MarketAgreement MarketParticipant MarketRole Measure_Unit Original_MarketDocument PlannedResource_TimeSeries Point Process Reason RegisteredResource ResourceProvider_MarketParticipant TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::FlowDirection TC57CIM::IEC62325::MarketManagement::MarketAgreement TC57CIM::IEC62325::MarketCommon::MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketRole TC57CIM::IEC62325::MarketManagement::Unit TC57CIM::IEC62325::MarketManagement::MarketDocument TC57CIM::IEC62325::MarketManagement::TimeSeries TC57CIM::IEC62325::MarketManagement::Point TC57CIM::IEC62325::MarketManagement::Process TC57CIM::IEC62325::MarketManagement::Reason TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketCommon::MarketParticipant ResourceScheduleConfirmation_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument Series_Period Time_Period UnavailableReserve_TimeSeries TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::TimeSeries Page 8 of 22
9 Resource schedule confirmation assembly model Overview of the model Figure 2 shows the model Figure 2 - Resource schedule confirmation assembly model 115 Page 9 of 22
10 IsBasedOn relationships from the European style market profile Table 2 shows the traceability dependency of the classes used in this package towards the upper level. Table 2 - IsBasedOn dependency Name Original_MarketDocument PlannedResource_TimeSeries Point Reason Complete IsBasedOn Path TC57CIM::IEC62325::MarketManagement::MarketDocument TC57CIM::IEC62325::MarketManagement::TimeSeries TC57CIM::IEC62325::MarketManagement::Point TC57CIM::IEC62325::MarketManagement::Reason ResourceScheduleConfirmation_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument Series_Period UnavailableReserve_TimeSeries TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::TimeSeries Detailed Resource schedule confirmation assembly model ResourceScheduleConfirmation_MarketDocument root class An electronic document containing the information necessary to satisfy the requirements of a given business process. Table 3 shows all attributes of ResourceScheduleConfirmation_MarketDocument. Table 3 - Attributes of Resource schedule confirmation assembly model::resourcescheduleconfirmation_marketdocument Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String 1 [1..1] type MessageKind_String 2 [1..1] sender_marketparticipant.mrid PartyID_String 3 [1..1] sender_marketparticipant.marketrole.type MarketRoleKind_String 4 [1..1] receiver_marketparticipant.mrid PartyID_String The unique identification of the document being exchanged within a business process flow. The coded type of a document. The document type describes the principal characteristic of the document. The identification of a party in the energy market. --- The document owner. The identification of the role played by a market player. --- The document owner. --- The role associated with a MarketParticipant. The identification of a party in the energy market. --- The document recipient. 5 [1..1] receiver_marketparticipant.marketrole.type The identification of the role played by a market player. MarketRoleKind_String --- The document recipient. --- The role associated with a MarketParticipant. 6 [1..1] createddatetime ESMP_DateTime 7 [1..1] schedule_period.timeinterval ESMP_DateTimeInterval The date and time of the creation of the document. The start and end date and time for a given interval Table 4 shows all association ends of ResourceScheduleConfirmation_MarketDocument with other classes. Page 10 of 22
11 Table 4 - Association ends of Resource schedule confirmation assembly model::resourcescheduleconfirmation_marketdocument with other classes Order mult. Class name / Role Description 8 [1..1] Original_MarketDocument Original_MarketDocument Association Based On: model::original_marketdocument.original_marketdocument[1..1] model::resourcescheduleconfirmation_marketdocument.[] 9 [1..*] Reason Reason Association Based On: model::reason.reason[1..*] model::resourcescheduleconfirmation_marketdocument.[] Original_MarketDocument An electronic document containing the information necessary to satisfy the requirements of a given business process. Table 5 shows all attributes of Original_MarketDocument. Table 5 - Attributes of Resource schedule confirmation assembly model::original_marketdocument Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String 1 [1..1] revisionnumber ESMPVersion_String 2 [0..1] domain.mrid AreaID_String 3 [0..1] subject_marketparticipant.mrid PartyID_String The unique identification of the document being exchanged within a business process flow. The identification of the version that distinguishes one evolution of a document from another. The unique identification of the domain. The identification of a party in the energy market. --- The party that is the subject of the documents time series. 4 [0..1] subject_marketparticipant.marketrole.type The identification of the role played by a market player. MarketRoleKind_String --- The party that is the subject of the documents time series. --- The role associated with a MarketParticipant. 5 [0..1] process.processtype ProcessKind_String The identification of the nature of process that the document addresses Table 6 shows all association ends of Original_MarketDocument with other classes. Page 11 of 22
12 Table 6 - Association ends of Resource schedule confirmation assembly model::original_marketdocument with other classes Orde r mult. Class name / Role Description 6 [0..*] PlannedResource_TimeSeries PlannedResource_TimeSeries 7 [0..*] UnavailableReserve_TimeSeri es UnavailableReserve_TimeSeri es Association Based On: model::plannedresource_timeseries.plannedresource_timeseries[0.. *] model::original_marketdocument.[] Association Based On: model::unavailablereserve_timeseries.unavailablereserve_timeserie s[0..*] model::original_marketdocument.[] PlannedResource_TimeSeries A set of time-ordered quantities being exchanged in relation to a product. Table 7 shows all attributes of PlannedResource_TimeSeries. Table 7 - Attributes of Resource schedule confirmation assembly model::plannedresource_timeseries Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String 1 [1..1] businesstype BusinessKind_String 2 [0..1] flowdirection.direction DirectionKind_String 3 [1..1] product EnergyProductKind_String 4 [1..1] connecting_domain.mrid AreaID_String 5 [0..1] registeredresource.mrid ResourceID_String A unique identification of the time series. The identification of the nature of the time series. The coded identification of the direction of energy flow. --- The flow direction associated with a TimeSeries. The identification of the nature of an energy product such as power, energy, reactive power, etc. The unique identification of the domain. --- The domain associated with a TimeSeries. The unique identification of a resource. 6 [1..1] resourceprovider_marketparticipant.mrid The identification of a party in the energy market. PartyID_String --- The identification of a market participant associated with a TimeSeries. 7 [0..1] acquiring_domain.mrid AreaID_String 8 [0..1] marketagreement.type CapacityContractKind_String 9 [0..1] marketagreement.mrid ID_String The unique identification of the domain. --- The domain associated with a TimeSeries. The specification of the kind of the agreement, e.g. long term, daily contract. --- The identification of an agreement associated with a TimeSeries. The unique identification of the agreement. --- The identification of an agreement associated with a TimeSeries. Page 12 of 22
13 Order mult. Attribute name / Attribute type Description 10 [1..1] measurement_unit.name MeasurementUnitKind_String 11 [0..1] objectaggregation ObjectAggregationKind_String The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of measure associated with the quantities in a TimeSeries. The identification of the domain that is the common denominator used to aggregate a time series Table 8 shows all association ends of PlannedResource_TimeSeries with other classes. Table 8 - Association ends of Resource schedule confirmation assembly model::plannedresource_timeseries with other classes Order mult. Class name / Role 12 [1..*] Series_Period Series_Period 13 [0..*] Reason Reason Description The time interval and resolution for a period associated with a TimeSeries. Association Based On: model::unavailablereserve_timeseries.[] model::series_period.series_period[1..*] Association Based On: model::reason.reason[0..*] model::unavailablereserve_timeseries.[] Point The identification of the values being addressed within a specific interval of time. Table 9 shows all attributes of Point. Table 9 - Attributes of Resource schedule confirmation assembly model::point Order mult. Attribute name / Attribute type 0 [1..1] position 1 [1..1] quantity Position_Integer Decimal Description A sequential value representing the relative position within a given time interval. The principal quantity identified for a point Table 10 shows all association ends of Point with other classes. Table 10 - Association ends of Resource schedule confirmation assembly model::point with other classes Order mult. Class name / Role 2 [0..*] Reason Reason Description The Reason information associated with a Point providing motivation information. Association Based On: model::point.[] model::reason.reason[0..*] 164 Page 13 of 22
14 Reason The motivation of an act. Table 11 shows all attributes of Reason. Table 11 - Attributes of Resource schedule confirmation assembly model::reason Order mult. Attribute name / Attribute type 0 [1..1] code ReasonCode_String 1 [0..1] text ReasonText_String Description The motivation of an act in coded form. The textual explanation corresponding to the reason code Series_Period The identification of the period of time corresponding to a given time interval and resolution. Table 12 shows all attributes of Series_Period. Table 12 - Attributes of Resource schedule confirmation assembly model::series_period Order mult. Attribute name / Attribute type 0 [1..1] timeinterval 1 [1..1] resolution ESMP_DateTimeInterval Duration Description The start and end time of the period. The definition of the number of units of time that compose an individual step within a period Table 13 shows all association ends of Series_Period with other classes. Table 13 - Association ends of Resource schedule confirmation assembly model::series_period with other classes Order mult. Class name / Role 2 [1..*] Point Point Description The Point information associated with a given Series_Period.within a TimeSeries. Association Based On: model::series_period.[] model::point.point[1..*] UnavailableReserve_TimeSeries A set of time-ordered quantities being exchanged in relation to a product. Table 14 shows all attributes of UnavailableReserve_TimeSeries. Table 14 - Attributes of Resource schedule confirmation assembly model::unavailablereserve_timeseries Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String A unique identification of the time series. Page 14 of 22
15 Order mult. Attribute name / Attribute type Description 1 [1..1] businesstype BusinessKind_String 2 [0..1] flowdirection.direction DirectionKind_String 3 [1..1] product EnergyProductKind_String 4 [1..1] connecting_domain.mrid AreaID_String 5 [1..1] resourceprovider_marketparticipant.mrid PartyID_String The identification of the nature of the time series. The coded identification of the direction of energy flow. --- The flow direction associated with a TimeSeries. The identification of the nature of an energy product such as power, energy, reactive power, etc. The unique identification of the domain. --- The domain associated with a TimeSeries. The identification of a party in the energy market. --- The identification of a market participant associated with a TimeSeries. 6 [0..1] substituteresourceprovider_marketparticipant.mrid The identification of a party in the energy market. PartyID_String --- The identification of a market participant associated with a TimeSeries. 7 [1..1] acquiring_domain.mrid AreaID_String 8 [0..1] marketagreement.type CapacityContractKind_String 9 [0..1] marketagreement.mrid ID_String 10 [1..1] measurement_unit.name MeasurementUnitKind_String 11 [0..1] objectaggregation ObjectAggregationKind_String The unique identification of the domain. --- The domain associated with a TimeSeries. The specification of the kind of the agreement, e.g. long term, daily contract. --- The identification of an agreement associated with a TimeSeries. The unique identification of the agreement. --- The identification of an agreement associated with a TimeSeries. The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of measure associated with the quantities in a TimeSeries. The identification of the domain that is the common denominator used to aggregate a time series Table 15 shows all association ends of UnavailableReserve_TimeSeries with other classes. Table 15 - Association ends of Resource schedule confirmation assembly model::unavailablereserve_timeseries with other classes Order mult. Class name / Role 12 [1..*] Series_Period Series_Period 13 [0..*] Reason Reason Description The time interval and resolution for a period associated with a TimeSeries. Association Based On: model::unavailablereserve_timeseries.[] model::series_period.series_period[1..*] Association Based On: model::reason.reason[0..*] model::unavailablereserve_timeseries.[] 189 Page 15 of 22
16 Datatypes The list of datatypes used for the Resource schedule confirmation assembly model is as follows: ESMP_DateTimeInterval compound AreaID_String datatype, codelist CodingSchemeTypeList BusinessKind_String datatype, codelist BusinessTypeList CapacityContractKind_String datatype, codelist ContractTypeList DirectionKind_String datatype, codelist DirectionTypeList EnergyProductKind_String datatype, codelist EnergyProductTypeList ESMP_DateTime datatype ESMPVersion_String datatype ID_String datatype MarketRoleKind_String datatype, codelist RoleTypeList MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList MessageKind_String datatype, codelist MessageTypeList ObjectAggregationKind_String datatype, codelist ObjectAggregationTypeList PartyID_String datatype, codelist CodingSchemeTypeList Position_Integer datatype ProcessKind_String datatype, codelist ProcessTypeList ReasonCode_String datatype, codelist ReasonCodeTypeList ReasonText_String datatype ResourceID_String datatype, codelist CodingSchemeTypeList YMDHM_DateTime datatype Page 16 of 22
17 213 ResourceScheduleConfirmation_MarketDocument XML schema structure Figure 3 - ResourceScheduleConfirmation_MarketDocument schema structure Page 17 of 22
18 ResourceScheduleConfirmation_MarketDocument XML schema The schema to be used to validate XML instances is to be identified by: urn:iec :tc57wg16:451-7:resourcescheduleconfirmationdocument:6:0 <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:cl="urn:entsoe.eu:wgedi:codelists" xmlns:sawsdl=" xmlns="urn:iec :tc57wg16:451-7:resourcescheduleconfirmationdocument:6:0" xmlns:cimp=" xmlns:xs=" targetnamespace="urn:iec :tc57wg16:451-7:resourcescheduleconfirmationdocument:6:0" elementformdefault="qualified" attributeformdefault="unqualified"> <xs:import namespace="urn:entsoe.eu:wgedi:codelists" schemalocation="urn-entsoe-eu-wgedicodelists.xsd"/> <xs:element name="resourcescheduleconfirmation_marketdocument" type="resourcescheduleconfirmation_marketdocument"/> <xs:simpletype name="id_string" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:maxlength value="35"/> </xs:restriction> <xs:simpletype name="esmpversion_string" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:pattern value="[1-9]([0-9]){0,2}"/> </xs:restriction> <xs:simpletype name="areaid_string-base" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:maxlength value="18"/> </xs:restriction> <xs:complextype name="areaid_string" sawsdl:modelreference=" <xs:simplecontent> <xs:extension base="areaid_string-base"> <xs:attribute name="codingscheme" type="cl:codingschemetypelist" use="required"/> </xs:extension> </xs:simplecontent> </xs:complextype> <xs:simpletype name="partyid_string-base" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:maxlength value="16"/> </xs:restriction> <xs:complextype name="partyid_string" sawsdl:modelreference=" <xs:simplecontent> <xs:extension base="partyid_string-base"> <xs:attribute name="codingscheme" type="cl:codingschemetypelist" use="required"/> </xs:extension> </xs:simplecontent> </xs:complextype> <xs:simpletype name="marketrolekind_string" sawsdl:modelreference=" <xs:restriction base="cl:roletypelist"/> <xs:simpletype name="processkind_string" sawsdl:modelreference=" <xs:restriction base="cl:processtypelist"/> <xs:complextype name="original_marketdocument" sawsdl:modelreference=" <xs:sequence> <xs:element name="mrid" type="id_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" Page 18 of 22
19 <xs:element name="revisionnumber" type="esmpversion_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="domain.mrid" type="areaid_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="subject_marketparticipant.mrid" type="partyid_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="subject_marketparticipant.marketrole.type" type="marketrolekind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="process.processtype" type="processkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="plannedresource_timeseries" type="plannedresource_timeseries" minoccurs="0" maxoccurs="unbounded" sawsdl:modelreference=" <xs:element name="unavailablereserve_timeseries" type="unavailablereserve_timeseries" minoccurs="0" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:simpletype name="businesskind_string" sawsdl:modelreference=" <xs:restriction base="cl:businesstypelist"/> <xs:simpletype name="directionkind_string" sawsdl:modelreference=" <xs:restriction base="cl:directiontypelist"/> <xs:simpletype name="energyproductkind_string" sawsdl:modelreference=" <xs:restriction base="cl:energyproducttypelist"/> <xs:simpletype name="resourceid_string-base" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:maxlength value="18"/> </xs:restriction> <xs:complextype name="resourceid_string" sawsdl:modelreference=" <xs:simplecontent> <xs:extension base="resourceid_string-base"> <xs:attribute name="codingscheme" type="cl:codingschemetypelist" use="required"/> </xs:extension> </xs:simplecontent> </xs:complextype> <xs:simpletype name="capacitycontractkind_string" sawsdl:modelreference=" <xs:restriction base="cl:contracttypelist"/> <xs:simpletype name="measurementunitkind_string" sawsdl:modelreference=" <xs:restriction base="cl:unitofmeasuretypelist"/> <xs:simpletype name="objectaggregationkind_string" sawsdl:modelreference=" <xs:restriction base="cl:objectaggregationtypelist"/> <xs:complextype name="plannedresource_timeseries" sawsdl:modelreference=" <xs:sequence> <xs:element name="mrid" type="id_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="businesstype" type="businesskind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="flowdirection.direction" type="directionkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="product" type="energyproductkind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" Page 19 of 22
20 <xs:element name="connecting_domain.mrid" type="areaid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="registeredresource.mrid" type="resourceid_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="resourceprovider_marketparticipant.mrid" type="partyid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="acquiring_domain.mrid" type="areaid_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="marketagreement.type" type="capacitycontractkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="marketagreement.mrid" type="id_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="measurement_unit.name" type="measurementunitkind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="objectaggregation" type="objectaggregationkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="series_period" type="series_period" minoccurs="1" maxoccurs="unbounded" sawsdl:modelreference=" <xs:element name="reason" type="reason" minoccurs="0" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:simpletype name="position_integer" sawsdl:modelreference=" <xs:restriction base="xs:integer"> <xs:maxinclusive value="999999"/> <xs:mininclusive value="1"/> </xs:restriction> <xs:complextype name="point" sawsdl:modelreference=" <xs:sequence> <xs:element name="position" type="position_integer" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="quantity" type="xs:decimal" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="reason" type="reason" minoccurs="0" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:simpletype name="reasoncode_string" sawsdl:modelreference=" <xs:restriction base="cl:reasoncodetypelist"/> <xs:simpletype name="reasontext_string" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:maxlength value="512"/> </xs:restriction> <xs:complextype name="reason" sawsdl:modelreference=" <xs:sequence> <xs:element name="code" type="reasoncode_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="text" type="reasontext_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:simpletype name="messagekind_string" sawsdl:modelreference=" <xs:restriction base="cl:messagetypelist"/> <xs:simpletype name="esmp_datetime" sawsdl:modelreference=" <xs:restriction base="xs:datetime"> <xs:pattern value="((([0-9]{4})[\-](0[13578] 1[02])[\-](0[1-9] [12][0-9] 3[01]) ([0-9]{4})[\-]((0[469]) (11))[\-](0[1-9] [12][0-9] 30))T(([01][0-9] 2[0-3]):[0-5][0-9]:[0-5][0- Page 20 of 22
21 ])Z) (([13579][26][02468][048] [13579][ ](0)[48] [13579][ ][2468][048] [02468][048][0246 8][048] [02468][ ](0)[48] [02468][ ][2468][048] [0-9][0-9][13579][26])[\-](02)[\-](0[1-9] 1[0-9] 2[0-9])T(([01][0-9] 2[0-3]):[0-5][0-9]:[0-5][0-9])Z) (([13579][26][02468][ ] [13579][ ](0)[ ] [13579][ ][2468][ ] [02 468][048][02468][ ] [02468][ ](0)[ ] [02468][ ][2468][ ] [0-9][0-9][13579][ ])[\-](02)[\-](0[1-9] 1[0-9] 2[0-8])T(([01][0-9] 2[0-3]):[0-5][0-9]:[0-5][0-9])Z)"/> </xs:restriction> <xs:simpletype name="ymdhm_datetime" sawsdl:modelreference=" <xs:restriction base="xs:string"> <xs:pattern value="((([0-9]{4})[\-](0[13578] 1[02])[\-](0[1-9] [12][0-9] 3[01]) ([0-9]{4})[\-]((0[469]) (11))[\-](0[1-9] [12][0-9] 30))T(([01][0-9] 2[0-3]):[0-5][0-9])Z) (([13579][26][02468][048] [13579][ ](0)[48] [13579][ ][2468][048] [02468][048][0246 8][048] [02468][ ](0)[48] [02468][ ][2468][048] [0-9][0-9][13579][26])[\-](02)[\-](0[1-9] 1[0-9] 2[0-9])T(([01][0-9] 2[0-3]):[0-5][0-9])Z) (([13579][26][02468][ ] [13579][ ](0)[ ] [13579][ ][2468][ ] [02 468][048][02468][ ] [02468][ ](0)[ ] [02468][ ][2468][ ] [0-9][0-9][13579][ ])[\-](02)[\-](0[1-9] 1[0-9] 2[0-8])T(([01][0-9] 2[0-3]):[0-5][0-9])Z)"/> </xs:restriction> <xs:complextype name="esmp_datetimeinterval" sawsdl:modelreference=" <xs:sequence> <xs:element name="start" type="ymdhm_datetime" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="end" type="ymdhm_datetime" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:complextype name="resourcescheduleconfirmation_marketdocument" sawsdl:modelreference=" <xs:sequence> <xs:element name="mrid" type="id_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="type" type="messagekind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="sender_marketparticipant.mrid" type="partyid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="sender_marketparticipant.marketrole.type" type="marketrolekind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="receiver_marketparticipant.mrid" type="partyid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="receiver_marketparticipant.marketrole.type" type="marketrolekind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="createddatetime" type="esmp_datetime" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="schedule_period.timeinterval" type="esmp_datetimeinterval" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="original_marketdocument" type="original_marketdocument" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="reason" type="reason" minoccurs="1" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:complextype name="series_period" sawsdl:modelreference=" <xs:sequence> <xs:element name="timeinterval" type="esmp_datetimeinterval" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="resolution" type="xs:duration" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="point" type="point" minoccurs="1" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> <xs:complextype name="unavailablereserve_timeseries" sawsdl:modelreference=" Page 21 of 22
22 <xs:sequence> <xs:element name="mrid" type="id_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="businesstype" type="businesskind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="flowdirection.direction" type="directionkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="product" type="energyproductkind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="connecting_domain.mrid" type="areaid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="resourceprovider_marketparticipant.mrid" type="partyid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="substituteresourceprovider_marketparticipant.mrid" type="partyid_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="acquiring_domain.mrid" type="areaid_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="marketagreement.type" type="capacitycontractkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="marketagreement.mrid" type="id_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="measurement_unit.name" type="measurementunitkind_string" minoccurs="1" maxoccurs="1" sawsdl:modelreference=" <xs:element name="objectaggregation" type="objectaggregationkind_string" minoccurs="0" maxoccurs="1" sawsdl:modelreference=" <xs:element name="series_period" type="series_period" minoccurs="1" maxoccurs="unbounded" sawsdl:modelreference=" <xs:element name="reason" type="reason" minoccurs="0" maxoccurs="unbounded" sawsdl:modelreference=" </xs:sequence> </xs:complextype> </xs:schema> Page 22 of 22
PLANNED RESOURCE SCHEDULE DOCUMENT UML MODEL AND SCHEMA
1 PLANNED RESOURCE SCHEDULE DOCUMENT UML MODEL AND SCHEMA 2019-02-12 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 41 42
More informationHISTORICAL ACTIVATION DOCUMENT UML MODEL AND SCHEMA
1 HISTORICAL ACTIVATION DOCUMENT UML MODEL AND SCHEMA 2019-02-12 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 41 42 43
More informationRESERVE ALLOCATION RESULT DOCUMENT UML MODEL AND SCHEMA
1 RESERVE ALLOCATION RESULT DOCUMENT UML MODEL AND SCHEMA 2019-02-12 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 41 42
More informationREDISPATCH DOCUMENT UML MODEL AND SCHEMA
1 REDISPATCH DOCUMENT UML MODEL AND SCHEMA 2019-02-12 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 Table of Contents 1
More informationSCHEDULE DOCUMENT UML MODEL AND SCHEMA
1 SCHEDULE DOCUMENT UML MODEL AND SCHEMA 2017-01-19 DRAFT DOCUMENT FOR APPROVAL VERSION 1.0 2 3 4 5 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 35 36 37 38 39 40
More informationSCHEDULE DOCUMENT UML MODEL AND SCHEMA
1 SCHEDULE DOCUMENT UML MODEL AND SCHEMA 2017-01-19 DOCUMENT APPROVED 2 3 4 5 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 35 36 37 38 39 40 41 Table of Contents 1
More informationHVDC LINK DOCUMENT UML MODEL AND SCHEMA
1 HVDC LINK DOCUMENT UML MODEL AND SCHEMA 2017-01-19 2 3 4 5 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 35 36 37 38 39 40 41 42 Table of Contents 1 Objective...
More informationIMPLICIT AUCTION RESULT DOCUMENT UML MODEL AND SCHEMA
1 IMPLICIT AUCTION RESULT DOCUMENT UML MODEL AND SCHEMA 2018-05-08 DOCUMENT APPROVED 2 3 4 5 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 35 36 37 38 39 40 41 Table
More informationREPORTING INFORMATION DOCUMENT UML MODEL AND SCHEMA
1 REPORTING INFORMATION DOCUMENT UML MODEL AND SCHEMA 2018-11-08 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 41 42 43
More informationRESERVE BID DOCUMENT UML MODEL AND SCHEMA
1 RESERVE BID DOCUMENT UML MODEL AND SCHEMA 2018-03-08 APPROVED DOCUMENT 2 3 4 5 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 35 36 37 38 39 40 41 Table of Contents
More informationRESERVE BID DOCUMENT UML MODEL AND SCHEMA
1 RESERVE BID DOCUMENT UML MODEL AND SCHEMA 2017-01-10 2 3 4 5 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 35 36 37 38 39 40 41 42 43 44 Table of Contents 1 Objective...
More informationCAPACITY AUCTION SPECIFICATION DOCUMENT UML MODEL AND SCHEMA
1 CAPACITY AUCTION SPECIFICATION DOCUMENT UML MODEL AND SCHEMA 2018-05-08 DOCUMENT APPROVED 2 3 4 5 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 35 36 37 38 39 40
More informationCAPACITY DOCUMENT UML MODEL AND SCHEMA
1 CAPACITY DOCUMENT UML MODEL AND SCHEMA 2017-01-03 2 3 4 5 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 35 36 37 38 39 40 41 42 43 Table of Contents 1 Objective...
More informationTRANSMISSION NETWORK DOCUMENT UML MODEL AND SCHEMA
1 TRANSMISSION NETWORK DOCUMENT UML MODEL AND SCHEMA 2017-01-27 2 3 4 5 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 35 36 37 38 39 40 41 42 43 44 45 46 47 Table of
More informationUNAVAILABILITY DOCUMENT UML MODEL AND SCHEMA
1 UNAVAILABILITY DOCUMENT UML MODEL AND SCHEMA 2017-01-27 2 3 4 5 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 35 36 37 38 39 40 41 42 43 Table of Contents 1 Objective...
More informationMERIT ORDER LIST DOCUMENT UML MODEL AND SCHEMA
1 MERIT ORDER LIST DOCUMENT UML MODEL AND SCHEMA 2017-02-24 2 3 4 5 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 35 36 37 38 39 40 41 42 43 44 Table of Contents 1
More informationENTSO-E GENERATION AND LOAD SHIFT KEY IMPLEMENTATION GUIDE
1 2 ENTSO-E GENERATION AND LOAD SHIFT KEY IMPLEMENTATION GUIDE 2016-22-09 DRAFT DOCUMENT FOR APPROVAL VERSION 2.0 3 4 5 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
More informationENTSO-E CODING SCHEMES MAPPING IMPLEMENTATION GUIDE
1 2 ENTSO-E CODING SCHEMES MAPPING IMPLEMENTATION GUIDE 2016-01-21 DOCUMENT APPROVED 3 4 5 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 35 36 37 38 39 40 Table of
More informationIMPLEMENTATION GUIDE
ENTSO-E CONTINGENCY LIST, REMEDIAL ACTIONS AND ADDITIONAL CONSTRAINTS (CRAC) 2016-05-11 1 Copyright notice: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Copyright ENTSO-E. All Rights Reserved. This document
More informationIMPLEMENTATION GUIDE
ENTSO-E CONTINGENCY LIST, REMEDIAL ACTIONS AND ADDITIONAL CONSTRAINTS (CRAC) 2017-01-12 1 Copyright notice: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Copyright ENTSO-E. All Rights Reserved. This document
More informationIMPLEMENTATION GUIDE
ENTSO-E CONTINGENCY LIST, REMEDIAL ACTIONS AND ADDITIONAL CONSTRAINTS (CRAC) 2017-11-09 1 Copyright notice: 2 3 4 5 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 35
More informationENTSO-E European Style Market Standards IEC IEC IEC IEC n IEC CIM Users Group Oslo (NO)
ENTSO-E European Style Market Standards IEC 62325-301 IEC 62325-450 IEC 62325-351 IEC 62325-451-n IEC 62325-503 CIM Users Group Oslo (NO) 2013-06-17 Electricity Market CIM for the Market Why? 525 millions
More informationIMPLEMENTATION GUIDE
1 PAN EUROPEAN VERIFICATION FUNCTION 2018-04-11 VERSION 01 RELEASE 00 2 Copyright notice: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Copyright ENTSO-E. All Rights Reserved. This document and its whole translations
More informationIMPLEMENTATION GUIDE
ENTSO-E CRITICAL NETWORK ELEMENT 2015-11-10 DRAFT DOCUMENT VERSION 1.1 2 Copyright notice: 3 4 5 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 35 36 37 38 39 Copyright
More informationQosPolicyHolder: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 informationENTSO-E ACKNOWLEDGEMENT DOCUMENT (EAD) IMPLEMENTATION GUIDE
1 ENTSO-E ACKNOWLEDGEMENT DOCUMENT (EAD) 2014-01-16 2 3 4 5 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 35 36 37 38 Table of Contents 1 OBJECTIVE... 5 2 THE ACKNOWLEDGEMENT
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 informationImplementation Guide. afrr capacity market. Version: 0.8
Implementation Guide afrr capacity market Business process: afrr capacity market Version: 0.8 Status: Draft Date: 28.06.2018 1 Revision History Version Release Date Changed by Comments 0.8 Draft A 28.06.2018
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 informationINTERNATIONAL STANDARD
INTERNATIONAL STANDARD IEC 62325-451-4 Edition 2.0 2017-04 colour inside Framework for energy market communications Part 451-4: Settlement and reconciliation business process, contextual and assembly models
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
UPDATES TO THE LRIT SYSTEM. Report of the Drafting Group
E SUB-COMMITTEE ON NAVIGATION, COMMUNICATIONS AND SEARCH AND RESCUE 5th session Agenda item 4 21 ebruary 2018 Original: ENGLISH DISCLAIMER As at its date of issue, this document, in whole or in part, is
More information<?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:types="http://www.slc.co.uk/course/types/1.0" xmlns:xs="http://www.w3.org/2001/xmlschema"
More information
Intellectual 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 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 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 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 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 informationThis document is a preview generated by EVS
INTERNATIONAL STANDARD IEC 62325-451-4 Edition 2.0 2017-04 colour inside Framework for energy market communications Part 451-4: Settlement and reconciliation business process, contextual and assembly models
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 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 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 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 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 informationMessages 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 informationInfor Enterprise Server User Guide for Triggering
Infor Enterprise Server User Guide for Triggering Copyright 2015 Infor Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential
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 information[MS-TMPLDISC]: Template Discovery Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-TMPLDISC]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information<xs:element name="record" type="recordtype" maxoccurs="unbounded" /> </xs:sequence> </xs:complextype>
- -
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 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 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 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 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 informationWeb Service Provider Example - Enabling Visible Business
Web Services Example Web Service Provider Example - Enabling Visible Business Company A makes earrings. One of their suppliers, Company B, provides the glass beads that are used in the earrings. Company
More informationTC57 Use of XML Schema. Scott Neumann. October 3, 2005
TC57 Use of XML Schema Scott Neumann October 3, 2005 Introduction The purpose of this presentation is to respond to an action item from the last WG14 meeting regarding the use of XML Schema by WG14 and
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 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 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 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 informationGemini API Specification
Gemini API Specification Copyright National Grid, all rights reserved. No part of this publication may by reproduced in any material form (including photocopying and restoring in any medium or electronic
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 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 information7.1. Redovna datoteka sa slogovima koji se odnose na kupnje i prodaje valuta na tržištu stranih sredstava plaćanja
7. XSD datoteke za dostavu podataka 7.1. Redovna datoteka sa slogovima koji se odnose na kupnje i prodaje valuta na tržištu stranih sredstava plaćanja
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 informationIII General Acknowledgement message. Acknow. Workgroup Document version: A. Version 5.0 SECTION
1 2 3 4 5 SECTION III General Acknowledgement Message Acknow 6 Version 5.0 Edig@s 7 8 9 10 EASEE-gas/Edig@s Workgroup Document version: A ACKNOW Version 5.0 / 2010-02-17 III - 1 11 COPYRIGHT & LIABILITY
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 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 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 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 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 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 informationSECTION. 0 General Message Guidelines. Version Workgroup Document version: 3. Version 5.
1 2 3 SECTION 0 General Message Guidelines 4 Version 5.1 Edig@s 5 6 7 8 EASEE-gas/Edig@s Workgroup Document version: 3 Version 5.1 / 2015-09-02 0-1 9 COPYRIGHT & LIABILITY 10 11 12 13 14 15 16 17 18 19
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 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 informationDocument Metadata: document technical metadata for digital preservation
Document Metadata: document technical metadata for digital preservation By Carol Chou - Florida Digital Archive (FDA) Andrea Goethals - Harvard Library (HL) March 18, 2009 Rev. November 30, 2012 1 Table
More informationExample set of DFDL 1.0 properties
Example set of DFDL 1.0 properties Status of This Document This working draft document provides an example to the OGF community of the Data Format Description Language (DFDL) standard. Distribution is
More informationPESC Compliant JSON Version /19/2018. A publication of the Technical Advisory Board Postsecondary Electronic Standards Council
Version 0.5.0 10/19/2018 A publication of the Technical Advisory Board Postsecondary Electronic Standards Council 2018. All Rights Reserved. This document may be copied and furnished to others, and derivative
More informationGistiskýrslur - Schema
Statistics Iceland Borgartúni 21a IS-105 Reykjavík Iceland Gistiskýrslur - Schema Last updated: 13.2.2017 Owner Statistics Iceland Version 2.00 Author Sigurður Marísson sigurdur.marisson@statice.is Table
More informationSpecifications for the Preliminary Official Statement Submission Service
Specifications for the Preliminary Official Statement Submission Service Version 1.2 August 2015 1 EVISION HISTOY Version Date Major Changes 1.0 May 2011 Initial version. 1.1 July 2011 emove security types
More informationBig Data 9. Data Models
Ghislain Fourny Big Data 9. Data Models pinkyone / 123RF Stock Photo 1 Syntax vs. Data Models Physical view Syntax this is text. 2 Syntax vs. Data Models a Logical view
More informationTechnical requirements
ANNEX 1: TECHNICAL REQUIREMENTS Technical requirements 1. Introduction... 2 2. Overview of the import formalities section of the market access database... 2 2.1. Architecture... 2 2.2. The dataset... 2
More informationInformation Document Wind and Solar Power Forecasting ID # R
Information Documents are not authoritative. Information Documents are for information purposes only and are intended to provide guidance. In the event of any discrepancy between an Information Document
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 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 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 informationSo far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it?
XML Page 1 XML and web services Monday, March 14, 2011 2:50 PM So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it? XML Page 2 Where
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 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 informationPrivacy and Personal Data Collection Disclosure. Legal Notice
Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this
More informationsaml requesting attributes v1.1 wd01 Working Draft January 2016 Standards Track Draft Copyright OASIS Open All Rights Reserved.
Standards Track Draft Copyright OASIS Open 2015. All Rights Reserved. Page 1 of 10 SAML v2.0 Protocol Extension for Requesting Attributes in AuthnRequest Version 1.1 Working Draft 02 19 January 2016 Technical
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 informationNotes. Any feedback/suggestions? IS 651: Distributed Systems
Notes Grading statistics Midterm1: average 10.60 out of 15 with stdev 2.22 Total: average 15.46 out of 21 with stdev 2.80 A range: [18.26, 23] B range: [12.66, 18.26) C or worse range: [0, 12.66) The curve
More informationCapability Advertisement Messages
Capability Advertisement Messages These sections describe schema definitions for the Capability Advertisement messages. Capability Advertisement Schema, page 1 Components of CCDL, page 2 Schema Definition,
More informationSpecifications for SHORT System Document Submission Service
Specifications for SHOT System Document Submission Service Version 1.3 August 2015 Version 1.3 August 2015 1 evision History Version Date Major Changes 1.0 December 2010 Initial version. 1.1 February 2011
More information[MS-OXSHRMSG]: Sharing Message Attachment Schema. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-OXSHRMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information