EN 61970-501-2006 en Energy management system application program interface (EMS-API) Part 501 Common Information Model Resource Description Framework (CIM RDF) schema《能量消耗监控系统应用程序.pdf

《EN 61970-501-2006 en Energy management system application program interface (EMS-API) Part 501 Common Information Model Resource Description Framework (CIM RDF) schema《能量消耗监控系统应用程序.pdf》由会员分享，可在线阅读，更多相关《EN 61970-501-2006 en Energy management system application program interface (EMS-API) Part 501 Common Information Model Resource Description Framework (CIM RDF) schema《能量消耗监控系统应用程序.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARDBS EN 61970-501:2006Energy management system application program interface (EMS-API) Part 501: Common Information Model Resource Description Framework(CIM RDF) schema The European Standard EN 61970-501:2006 has the status of a British StandardICS 33.200g49g50g3g38g50g51g60g44g49g42g3

2、g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61970-501:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 Ju

3、ne 2006 BSI 2006ISBN 0 580 48876 4National forewordThis British Standard is the official English language version of EN 61970-501:2006. It is identical with IEC 61970-501:2006.The UK participation in its preparation was entrusted to Technical Committee PEL/57, Power systems management and associated

4、 information exchange, which has the responsibility to: A list of organizations represented on this committee can be obtained on request to its secretary.Cross-referencesThe British Standards which implement international or European publications referred to in this document may be found in the BSI

5、Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its

6、 correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep UK interests in

7、formed; monitor related international and European developments and promulgate them in the UK.Summary of pagesThis document comprises a front cover, an inside front cover, the EN title page, pages 2 to 19 and a back cover.The BSI copyright notice displayed in this document indicates when the documen

8、t was last issued.Amendments issued since publicationAmd. No. Date CommentsEUROPEAN STANDARD EN 61970-501 NORME EUROPENNE EUROPISCHE NORM June 2006 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische

9、 Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2006 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61970-501:2006 E ICS 33.200 English version Energy management system application program interface (EMS-API)

10、Part 501: Common Information Model Resource Description Framework (CIM RDF) schema (IEC 61970-501:2006) Systme de gestion dnergie Interface de programmation dapplication (EMS-API) Partie 501: Schma de cadre gnral pour la description des ressources du modle dinformation commun (CIM RDF) (CEI 61970-50

11、1:2006) Anwendungsprogramm-Schnittstelle fr Netzfhrungssysteme (EMS-API) Teil 501: Allgemeines Informationsmodell (CIM) Resource Description Framework (CIM RDF) Schema (IEC 61970-501:2006) This European Standard was approved by CENELEC on 2006-04-01. CENELEC members are bound to comply with the CEN/

12、CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to a

13、ny CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official ve

14、rsions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovak

15、ia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 57/801/FDIS, future edition 1 of IEC 61970-501, prepared by IEC TC 57, Power systems management and associated information exchange, was submitted to the IEC-CENELEC parallel vote and was approved by CENEL

16、EC as EN 61970-501 on 2006-04-01. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2007-01-01 latest date by which the national standards conflicting with the EN have to be wit

17、hdrawn (dow) 2009-04-01 Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61970-501:2006 was approved by CENELEC as a European Standard without any modification. _ EN 61970-501:2006 2 CONTENTS INTRODUCTION.4 1 Scope.5 2 Normative references .5 3 Term

18、s and definitions .6 4 Structure of an XML document .6 4.1 General .6 4.2 Elements .7 4.3 Attributes.7 5 Metadata and RDF Schema7 5.1 General .7 5.2 Resource.7 5.3 Property 8 5.4 Namespaces .8 5.5 CIM RDF Schema extensions8 6 CIM metadata.11 6.1 General .11 6.2 Schema.11 6.3 Mapping from UML 12 6.4

19、Example CIM RDF Schema elements 13 Annex A (informative) CIM RDF Schema generation Mechanism for schema generation.17 EN 61970-501:2006 3 Annex ZA (normative) Normative references to international publications with their.19corresponding European publications INTRODUCTION This standard is part of the

20、 IEC 61970 series that define an Application Program Interface (API) for an Energy Management System (EMS). This standard is based upon the work of the EPRI Control Center API (CCAPI) research project (RP-3654-1). This part specifies the mapping between the conceptual model specified as Unified Mode

21、ling Language (UML) defined in IEC 61970-3XX series: Common Information Model and the machine readable Extensible Markup Language (XML) representation of that schema using the Resource Description Framework (RDF) Schema specification language. EN 61970-501:2006 4 ENERGY MANAGEMENT SYSTEM APPLICATION

22、 PROGRAM INTERFACE (EMS-API) Part 501: Common Information Model Resource Description Framework (CIM RDF) schema 1 Scope This International Standard specifies a Component Interface Specification (CIS) for energy management systems application program interfaces. This part of IEC 61970 specifies the f

23、ormat and rules for producing a machine readable form of the Common Information Model (CIM) as specified in the IEC 61970-301 standard. It describes a CIM vocabulary to support the data access facility and associated CIM semantics. This part of IEC 61970 supports a mechanism for applications from in

24、dependent suppliers to access CIM metadata in a common format and with standard services for the purpose of subsequent CIM data access. Secondary objectives are to provide CIM versioning capabilities and a mechanism that is easily extensible to support site-specific needs. The proposed solution: is

25、both machine readable and human readable, although primarily intended for programmatic access; can be accessed using any tool that supports the Document Object Model (DOM) application program interface; is self-describing; takes advantage of current web standards. This document is the Level 2 Compon

26、ent Interface Specification document that describes in narrative terms (with text and examples based on the CIM), the detailed definition of the CIM metadata interface to be standardized. 2 Normative references The following referenced documents are indispensable for the application of this document

27、. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61970-1, Energy management system application program interface (EMS-API) Part 1: Guidelines and general requirements IEC 61970-2, Ene

28、rgy management system application program interface (EMS-API) Part 2: Glossary IEC 61970-301, Energy management system application program interface (EMS-API) Part 301: Common Information Model (CIM) base IEC 60050 series: International Electrotechnical Vocabulary EN 61970-501:2006 5 3 Terms and def

29、initions For the purposes of this part of IEC 61970, the terms and definitions given in IEC 61970-2, as well as the following, apply. 3.1 Common Information Model CIM abstract model that represents all the major objects in an electric utility enterprise typically contained in an EMS information mode

30、l NOTE By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of EMS applications developed independently by different vendors, between entire EMS systems developed independently, or bet

31、ween an EMS system and other systems concerned with different aspects of power system operations, such as generation or distribution management. 3.2 Document Object Model DOM platform- and language-neutral interface defined by the World Wide Web Consortium (W3C) that allows programs and scripts to d

32、ynamically access and exchange the content, structure and style of documents 3.3 Resource Description Framework RDF language recommended by the W3C for expressing metadata that machines can process simply. It is expressed as a special kind of XML document 3.4 RDF Schema schema specification language

33、 expressed using RDF to describe resources and their properties, including how resources are related to other resources, which is used to specify an application-specific schema 3.5 Unified Modelling Language UML modelling language and methodology for specifying, visualizing, constructing, and docume

34、nting the artefacts of a system-intensive process 3.6 Extensible Markup Language XML subset of Standard Generalized Markup Language (SGML), ISO 8879, for putting structured data in a text file. It is an endorsed recommendation from the W3C NOTE It is license-free, platform-independent and well-suppo

35、rted by many readily available software tools. 4 Structure of an XML document 4.1 General An XML document is a set of containers. The containers can contain other containers as well as content. The two required pieces of a well-formed XML document are the prolog and the root element. The prolog cont

36、ains statements that indicate the version of the XML standard to which the document conforms and the encoding that is used. The prolog for the CIM RDF Schema file is simply: EN 61970-501:2006 6 The root element contains the XML documents actual contents, which are contained within starting and endin

37、g tags. The CIM RDF Schema contains the root element: . : The root element also contains references to namespaces, which define a context for elements that are used within the rest of the document. The element name is preceded by the namespace alias followed by a colon. For example, the RDF Schema n

38、amespace is declared: xmlns:rdfs=“http:/www.w3.org/TR/1999/PR-rdf-schema-19990303#“ References to it within the document use the syntax: Comments can appear anywhere within an XML document; they are delimited with characters. 4.2 Elements An element is a container enclosed between start and stop tag

39、s. The start tag defines the name of the element and contains any attributes of the element. In the following example, Class is the name of the element and ID is its attribute. The stop tag for this element is . 4.3 Attributes The ID attribute is used for the Class elements to be able to reference o

40、ther element nodes within the CIM RDF Schema document. The element with ID=“Bay“ can be referenced by other elements using the # symbol in front of the attributes value, as “#Bay“. Note that the XML concept of attribute is not the same as the UML definition. XML attributes store information about th

41、e element that are not directly or immediately relevant to the reader, such as an ID which is used for linking internal elements. UML attributes are data in this context. They shall hold structure of their own, such as datatype, constraints, and description. Therefore, they are specified as elements

42、 in the CIM RDF Schema. 5 Metadata and RDF Schema 5.1 General RDF Schema allows the definition of application-specific vocabularies. It is a very concise way to represent the CIM classes and their attributes and relationships. It is designed to be extensible, so that local extensions to the CIM can

43、easily be referenced. 5.2 Resource A resource is anything that can be referenced by a Uniform Resource Identifier (URI). For the purposes of the CIM RDF Schema, a resource corresponds to a class. By convention, resources are named with an initial uppercase letter. EN 61970-501:2006 7 5.3 Property A

44、property is a specific aspect, characteristic, attribute, or relation used to describe a resource. Each property has a specific meaning, defines its permitted values, the types of resources it can describe, and its relationship with other properties. Within the context of the CIM RDF Schema, a prope

45、rty can be either a class attribute or a rolename for an association of the class. By convention, properties are named with an initial lowercase letter. 5.4 Namespaces Namespaces are a way to tie a specific use of a word in context to the dictionary (schema) where the intended definition is to be fo

46、und. RDF requires the XML namespace facility to precisely associate each property with the schema that defines the property. 5.5 CIM RDF Schema extensions 5.5.1 General The RDF Schema has been extended to support some of the UML concepts that are important or useful in the CIM. 5.5.2 Multiplicity A

47、constraint property is a special kind of property that can be used to limit the values for the named properties. A multiplicity constraint documents the CIM values for allowed cardinality for a rolename in an association. The multiplicity resource is defined as: multiplicity Indicates how many insta

48、nces of a given property are allowed for a given resource. Allowed values are: M:01 (zero-or-one), M:11 (exactly-one), M:0n (zero-or-more), M:1n (one-or-more). Multiplicity Definition of the enumerated type which will contain the list of valid values. The CIM RDF Schema extensions create resources o

49、f this type which are used to express the values for allowed CIM cardinalities. The resources are named M:01, M:11, M:0n, and M:1n to correspond to the UML values in the model. 5.5.3 Inverse Rolename The inverseRolename property provides the name of the rolename at the opposite class for the association. This property is useful for navigating through the CIM relationships. It is defined as: inverseRoleName Role name at opposite end of this association. EN 61970-501:2006 8 5.5.4 IsAggregate Some of the associati