BS 8581-2-2012 Exchanging course related information Part 2 Course advertising profile Code of practice《交换课程相关信息 第2部分 课程广告资料 实用规程》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationExchanging course related information Part 2: Course advertising profile Code of practiceBS 8581-2:2012BS 8581-2:2012 BRITISH STANDARDPublishing and copyright informationThe BSI

2、copyright notice displayed in this document indicates when the document was last issued. The British Standards Institution 2012 Published by BSI Standards Limited 2012ISBN 978 0 580 78083 7ICS 35.240.99The following BSI references relate to the work on this standard: Committee reference IST/43 Draft

3、 for comment 12/30259243 DCPublication historyFirst (present) edition October 2012Amendments issued since publicationDate Text affected The British Standards Institution 2012 iBS 8581-2:2012BRITISH STANDARDContentsForeword ii1 Scope 12 Normative references 13 Terms and definitions 14 Conformance 15

4、XCRI-CAP documents 26 Namespace 27 Core elements 28 Common elements 49 Common descriptive elements 810 Elements used in the element 911 Elements used in the course element 912 Elements used in the element 1013 Elements used in the presentation element 1014 Processing XCRI-CAP XML documents 13Annexes

5、Annex A (informative) XML schema 15Bibliography 19List of tablesTable 1 element 11Table 2 element 12Table 3 element 12Table A.1 Mapping BS EN 15982 classes to XCRI elements 15Table A.2 Mapping BS EN 15982 properties to XCRI elements 16Summary of pagesThis document comprises a front cover, an inside

6、front cover, pages i to ii, pages 1 to 20, an inside back cover and a back cover.BS 8581-2:2012ii The British Standards Institution 2012BRITISH STANDARDForewordPublishing informationThis British Standard is published by BSI Standards Limited, under licence from The British Standards Institution, and

7、 came into effect on 31 October 2012. It was prepared by Panel IST/43/-/8, UK adoption of EN 15981 (EuroLMAI), EN 15943 (CEF) and EN 15982 (MLO), under the authority of Technical Committee IST/43, Information technology for learning, education and training. A list of organizations represented on thi

8、s committee can be obtained on request to its secretary.Relationship with other publicationsBS 8581-1 describes the structure of an XCRI-CAP1.2 XML document that conforms to BS EN 15982.BS 8581-2 provides guidance and recommendations on how and when the elements and attributes described in BS 8581-1

9、 are to be used.Use of this documentAs a code of practice, this part of BS 8581 takes the form of guidance and recommendations. It should not be quoted as if it were a specification and particular care should be taken to ensure that claims of compliance are not misleading.Any user claiming complianc

10、e with this part of BS 8581 is expected to be able to justify any course of action that deviates from its recommendations.Presentational conventionsThe provisions in this standard are presented in roman (i.e. upright) type. Its recommendations are expressed in sentences in which the principal auxili

11、ary verb is “should”.Commentary, explanation and general informative material is presented in smaller italic type, and does not constitute a normative element.Contractual and legal considerationsThis publication does not purport to include all the necessary provisions of a contract. Users are respon

12、sible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations. The British Standards Institution 2012 1BS 8581-2:2012BRITISH STANDARD1 ScopeThis British Standard gives recommendations for applications that produce and aggregate XCRI-CAP documents.

13、This British Standard gives recommendations for: policy-makers prescribing a consistent approach for product advertisement to learning opportunity providers that conforms to BS EN 15982; decision-makers specifying or procuring software for advertising or aggregating information about learning opport

14、unities in a format that conforms to BS EN 15982; and software developers writing code for advertising or aggregating information about learning opportunities in a format that conforms to BS EN 15982.NOTE It is intended for use by producers and aggregators alike, in the dissemination of course infor

15、mation to prospective students. 2 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the reference

16、d document (including any amendments) applies.Standards publicationsBS 8581-1:2012, Exchanging course-related information Part 1: Course advertising profile Specification BS EN 15982, Metadata for learning opportunities (MLO) AdvertisingBS ISO 8601, Data elements and interchange formats Information

17、interchange Representation of dates and times 3 Terms and definitionsFor the purposes of this part of BS 8581, the terms and definitions from BS 8581-1:2012 and BS EN 15982 apply.4 ConformanceCOMMENTARY ON CLAUSE 4 There are two classes of application that can conform to this British Standard: a pro

18、ducer and an aggregator.A producer is a class of application that produces XCRI-CAP documents. An aggregator is a class of application that aggregates XCRI-CAP documents.Either or both classes can conform to this British Standard.A strictly conforming instance is a set of structured information cons

19、tituted only of elements and attributes, and fully qualified refinements of the elements defined in this British Standard.A fully qualified refinement is an element that explicitly refines an element defined by this British Standard. A fully qualified refinement should be capable of being processed

20、according to the semantics of the element it extends.A conforming instance may contain additional elements and attributes not defined by this British Standard.BS 8581-2:20122 The British Standards Institution 2012BRITISH STANDARDA conforming producer should be capable of generating and sharing stric

21、tly conforming instances.A conforming aggregator should be capable of processing strictly conforming instances.NOTE For more information on conformance wrapping see Annex A.5 XCRI-CAP documentsA producer should use the catalog element as the top-level element for general purpose use.NOTE This Britis

22、h Standard allows both provider and course as alternative top-level elements to enable REST-style operations to be supported.6 NamespaceNOTE No guidance given.7 Core elements7.1 element7.1.1 generated attributeThe producer should use both date and time in the generated attribute, e.g. “2010-08-02T06

23、:14:37Z”.Where a element does not contain an generated attribute, the aggregator may process the document as if it was generated at the time the catalog was obtained by the aggregator.Where the value of the generated attribute is not a valid date/time according to BS ISO 8601, it is in error and the

24、 aggregator should ignore this element.7.2 element7.2.1 IdentifierThe producer should create elements with a default unique identifier formatted as a URL (e.g. “http:/www.bolton.ac.uk/”). The producer may include additional identifiers in other formats, but they should be qualified using xsi:type to

25、 a specific identifier namespace, e.g. the UK provider reference number (UKPRN) within the UKRLP:UKPRN namespace. 1)NOTE See BS 8581-1:2012, 8.4, for more details.7.2.2 TitleThe producer should include at least one element for a provider; the title should be the trading name of the organization, see

26、 8.5.1)This is a fictional example. The British Standards Institution 2012 3BS 8581-2:2012BRITISH STANDARD7.2.3 TypeWhere the producer uses the element for a provider, and where it is possible, the producer should refine this element using a vocabulary encoding scheme, see 8.2.1.2.7.2.4 URLThe produ

27、cer should include one element for each provider, which should include its homepage URL, or its applications microsite, in addition to its primary domain identifier (see 7.2.1).7.2.5 CourseThe producer should include at least one course for a provider.NOTE Where this British Standard is used to form

28、at course search results, the capability for supporting zero courses is offered.7.3 element7.3.1 IdentifierThe element should have a unique identifier formatted as a URI (e.g. “http:/www.bolton.ac.uk/courses/1”). Additional identifiers in other formats may be used, but they should be qualified using

29、 xsi:type to a specific identifier namespace, see 8.4 for further guidance.7.3.2 TitleThe producer should include at least one element for each course.7.3.3 SubjectThe producer should include at least one element for each course, see 8.6 for further guidance.7.3.4 LevelThe producer should not use th

30、e element; the aggregator should use the element and element to assist discovery of courses by level.7.3.5 CreditThe producer should use separate elements for describing the credits available under each scheme, e.g. CATS, ECTS.7.3.6 Absence of imageWhere a course does not contain an image, but its c

31、ontaining provider does, the aggregator should use the image of the provider when displaying the course.7.4 element7.4.1 Determining uniquenessWhere a presentation does not contain an identifier, the aggregator may need to construct presentation identifiers. Presentations should use a URL-formatted

32、BS 8581-2:20124 The British Standards Institution 2012BRITISH STANDARDidentifier where possible, following the scheme for the provider and course, e.g. “http:/www.bolton.ac.uk/courses/1/2008-1”.7.4.2 Absence of study mode and attendanceThe aggregators should assume that the default value for studyMo

33、de is “Full time”, the default for attendanceMode is “Campus”, and the default for the element is “Not known”.7.4.3 Start datesThe producer should include a element even if there is no specific start date as this can still be used to describe the start details, see BS 8581-1:2012, 14.2.7.4.4 Duratio

34、nThe producer should include a duration, or start and end dates, or both.7.4.5 Absence of imageWhere a presentation does not contain an image, but its containing course does, the aggregator should use the image of the course when displaying the presentation.7.4.6 Absence of titleWhere a presentation

35、 does not contain a title, but its containing course does, the aggregator should use the title of the course when displaying the presentation.7.4.7 Absence of descriptionWhere a presentation does not contain a description, but its containing course does, the aggregator should use the description of

36、the course when displaying the presentation.8 Common elements8.1 General8.1.1 elementThe producer should not use the element, but where possible use the temporal elements defined in BS 8581-1:2012, 14.2: , , , and . 8.1.2 / elementThe producer should not use these elements for general course adverti

37、sing as there is no definition of their use in this British Standard.NOTE 1 These elements are included for compatibility with BS EN 15982 and for use in extended profiles of BS 8581-1, which defines the semantics of these elements for other purposes.NOTE 2 For further guidance on these elements see

38、 BS EN 15982. 8.1.3 elementNOTE No guidance given. The British Standards Institution 2012 5BS 8581-2:2012BRITISH STANDARD8.2 element8.2.1 Refinements8.2.1.1 GeneralThe producer should use refinements of the element, e.g. for the “presenter” or “lecturer” or other contributor type relevant to the typ

39、e of course or presentation.8.2.1.2 Element refinementNOTE 1 This is the process of defining a sub-element of an existing element.Element refinement should be used to enable specialization of elements while retaining strict conformance to the original element specification.The sub-element should be

40、a semantic specialization of its super-element and should be able to be substituted with the super-element by implementations that do not implement the refinement.NOTE 2 For example, the element is defined within BS EN 15982 as describing the logistical means for individuals to engage in a presentat

41、ion, including temporal, modal and spatial patterns of engagement and attendance. In BS EN 1581 this is refined by the specialized elements , and . As each of these elements is described as a refinement of , an implementation of BS EN 15982 can process these elements as if they were elements without

42、 reference to BS 8581-1. Each of the refinements defined in BS 8581-1 also has a recommended vocabulary encoding scheme.Element refinement should be used where defining a subset of the meaning of an element, and also where constraining the set of possible values for the element using an encoding sch

43、eme.NOTE 3 An encoding scheme is a set of rules that apply to the content of the element, either by how the content is structured (a syntax encoding scheme) or by enumerating the valid values (a vocabulary encoding scheme).NOTE 4 For example, the element is defined as an “unambiguous reference to th

44、e resource within a given context” and encompasses all types of identifier that may be used. This element can be refined with a sub-property for a particular type of identifier, e.g. can be defined as a refinement of , which uses the syntax encoding scheme defined in IETF RFC 2396 1.8.2.1.3 Using el

45、ement refinement in XMLNOTE 1 A number of refinements of BS EN 15982 elements are defined within BS 8581-1 using the BS 8581-1 namespace (see Table A.1 and Table A.2, where the relationship is “refined by”).Where required, implementations processing these elements should be capable of transforming t

46、he element into its super-element. For example, implementations should be able to transform elements into elements to output data that strictly conforms to BS EN 15982.Where using element refinements defined outside of the scope of this British Standard, the super-element should be used with an XML

47、Schema Instance type attribute to indicate the refinement, e.g. where a element refinement is used for , it should be represented as follows:999-1234-321NOTE 2 Where the aggregator is not aware of the my:GUID sub-element, it can ignore the xsi:type attribute and treat the element as . This is called

48、 “fallback to declared type”, for further guidance see the W3C Example 24 2. Where an aggregator is aware of the my:GUID definition, it can process the element accordingly.BS 8581-2:20126 The British Standards Institution 2012BRITISH STANDARDNOTE 3 When using xsi:type the XML document needs to decla

49、re both the XSI namespace and the namespace and prefix used by the refinement.8.2.1.4 Element refinements versus extensionsRefinements should only be used where there is a clear super-element/sub-element relationship and, where appropriate, to enable the fallback behaviour to the super-element. Where this is not the case, implementers should define new elements as required.NOTE 1 This allows the aggregator to ignore the element completely where it is unknown to them. NOTE 2 An extension means the instance is no longer stric