Description
From Xcri
Jump to: navigation, search
URI:
Definition: A description element is used within the XCRI Course Advertising Profile to provide descriptions of resources and other structures.
Type: Structured, see below.
v1.1: Namespace: This is defined within the namespace:
+————————————————————————–+ | | | | | Contents | | ——– | | | | | | | | - 1 Attributes | | - 2 Content | | - 3 Example | | - 4 Guidance | | Notes | | - 5 History | | - 6 Usage | +————————————————————————–+
[edit] Attributes
@lang (optional) The language used for the description
@href (optional) A link to supporting information
[edit] Content
The content of the element MUST be one of either:
- Empty (@href MUST NOT be empty or missing)
- Plain unescaped text
- Valid XHTML 1.0 content
[edit] Example
This module shows how to take an existing presentation and modify it and how to create
your own presentations. No knowledge of PowerPoint is assumed.
The topics covered are:
Using and modifying an existing PowerPoint presentation
Creating a simple presentation
Making use of themes and schemes supplied with PowerPoint
The PowerPoint views
Printing and saving your presentation
[edit] Guidance Notes
Encoding schemes: Use of vocabularies is encouraged for descriptions. See XCRI_Terms_1.1.
Use of images: In general images should not be referenced from within the description element by providers as these are unlikely to be presented by Aggregators; potentially an image tag can be used to execute cross-site scripting (XSS) attacks. Instead, any image should be provided separately using the XCRI image element.
Long descriptions: Aggregators may choose to truncate long descriptions.
Safe use of XHTML: XCRI Description elements allow the delivery of XHTML. Many elements in these languages are considered ‘unsafe’ in that they open clients to one or more types of attack. Implementers of software which processes XCRI should carefully consider their handling of every type of element when processing incoming XHTML in XCRI XML documents. See the security sections of IETF RFC2854 and W3C XHTML for guidance. XCRI Aggregators should pay particular attention to the security of the IMG, SCRIPT, EMBED, OBJECT, FRAME, FRAMESET, IFRAME, META, and LINK elements, but other elements might also have negative security properties. XHTML can either directly contain or indirectly reference executable content.
[edit] History
v1.1: Since v1.1 the “type” attribute has been deprecated. Use encoding schemes instead.
[edit] Usage
Description is used in provider, course, and presentation.
Retrieved from “http://localhost/Description”
Views
Personal tools
Navigation
Search
Toolbox
-
This page was last modified 08:28, 19 March 2012.
-
This page has been accessed 8,883 times.
-
Content is available under Attribution 3.0.