Input: [Description] Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Different 'levels' apply to SysApps - possibly 'roles' [Requirement]

Output: Pre-installed app permissions

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Ability for a system application to access (read and write) files outside of that application's sandboxed storage area. [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications] Need to provide both sandboxed and non-sandboxed storage [Requirement]

Output: Access to files outside owned by the platform

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Category] Navigation and click-stream data [Structure] uri [Short display name] URI of requested resource [loginfo]

Output: uri

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] date [Short display name] Request timestamp [loginfo]

Output: timestamp

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Computer Information [Structure] ipaddr [Short display name] Client's IP address or hostname [loginfo]

Output: clientip

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] HTTP request method [loginfo]

Output: other.httpmethod

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] Data bytes in response [loginfo]

Output: other.bytes

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] Response status code [loginfo]

Output: other.statuscode

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Status] Proposal [Summary] Proposal to address the basic description of Articles within issues and/or volumes of periodicals of most types. [Vocab] Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork [Topic]

Output: Periodicals, Articles and Multi-volume Works

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Audiobook Type and abridged property for Book. [Vocab] Audiobook subtype of Book and of AudioObject, adds readBy property [Topic]

Output: Audiobook

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Collection Type and part properties for CreativeWork. [Vocab] Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork [Topic]

Output: Collection

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussion [Summary] Extension for describing accessibility properties of a CreativeWork. [Vocab] Add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 [Topic]

Output: Accessibility

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. Final discussion on whether to call it subOrganizationOf instead. [Vocab] department property (range and domain both Organization) [Comments] Proposal very greatly simplified after WebSchemas discussion. [Topic]

Output: Add Organization department property

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties. [Vocab] Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee. [Comments] Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise. [Topic]

Output: Add Quotation type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add handlers and potential actions to Action type. [Vocab] See full entry and proposal for details. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org (part 2)

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] "While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)". [Vocab] Adds classes OrderStatus, Order, DeliveryMethod plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Orders in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal includes new types for describing reservations and tickets [Vocab] Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Reservations in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal adds a single new type, EmailMessage [Vocab] EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages. [Comments] No properties currently defined; proposals welcomed. [Topic]

Output: EmailMessage type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Describing public civic services [Vocab] A proposal extending schema.org to cover various kinds of civic services. [Comments] GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties [Topic]

Output: Civic Services

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] This proposal adds a single new type, WorkersUnion, addressing issue 17 in the WebSchemas tracker. [Vocab] "A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying."" [Comments] One type, see draft schema. [Topic]

Output: Workers Union type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted; published in next version [Summary] Proposes modest changes and additions to support TV and radio (from EBU and BBC). [Vocab] Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc. [Comments] See also background notes and [[1]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see VideoObject, AudioObject; Movie. Event re scheduling. See also UserPlays, a kind of UserInteraction. Comics and TV/Radio also share a concern for describing fictional characters and narratives. [Topic]

Output: TV and Radio proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Some initial discussions. [Summary] Several parties are working towards a Sports Vocabulary proposal. See query from Paul Kelly (SportsML), Microdata + Sports Stats post describing earlier ESPN/Google collaboration, and the Sports Ontology used by BBC, Press Association and others. See also sports-schema-collab mailing list. [Vocab] Several sources including a full draft from the ESPN+Google work. Needs summary here. [Comments] March 2nd - posted writeup of the ESPN/Google Microdata vocabulary; next is discussion on finding common basic sports vocab for schema.org. [Topic]

Output: Sports

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussing Proposals [Summary] Proposal from Marvel (see examples). [Vocab] Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. [Comments] Generally well received and specified, but some detailed discussion re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with Book/numberOfPages, or ScholarlyArticle? Should PeriodicalSeries be intangible? [Topic]

Output: Comics and Serials

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Hopefully Final Proposal - please review [Summary] Proposes some modifications to Event based on deployment experience. [Vocab] Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from Thing. [Comments] Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events. [Topic]

Output: Event schema update

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios. [Vocab] Adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. [Comments] There is an associated implementation, github repository, and blog. [Topic]

Output: Historical Data proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A schema extension for describing biological databases, Sagace. [Vocab] Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. [Comments] Others have also mentioned interest in adding some notion of species. [Topic]

Output: Biological Databases

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal resolving current problems handling breadcrumbs. [Vocab] Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See discussion on using literal values. [Topic]

Output: Breadcrumbs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing online discussion forums and message boards. [Vocab] Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful. [Comments] Addition candidate [Topic]

Output: Discussion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [2] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [3] for complete list of terms. [Comments] Addition candidate [Topic]

Output: Innovation

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add a dissolutionDate property to Organization. [Topic]

Output: dissolutionDate

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/ [Vocab] Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service. [Comments] In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. [Topic]

Output: Lodging Extensions

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Topic]

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments] Comments on status, particularly regarding integration, overlaps and open issues. [Topic]

Output: Proposal name

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Description] A sequence of characters [Note: a discussion of character sets will be included in a future version of this document]. Syntactically strings are case-sensitive and may contain whitespace. [Type]

Output: string


Input: [Description] A sequence of characters acting as a unique identifier. Syntactically symbols are case-insensitive. The particular syntax used for metadata restricts the set of characters allowed in a symbol. Furthermore, symbols may not contain whitespace. [Type]

Output: symbol


Input: [Description] An integer. [Type]

Output: integer


Input: [Description] A floating-point approximation of a real number. [Type]

Output: float


Input: [Description] A tuple of two numbers, representing lower and upper bounds of an interval. [Type]

Output: range


Input: [Description] Either an integer, a float, or a range. [Type]

Output: number


Input: [Description] A boolean value. The names of the two possible values are true and false. [Type]

Output: boolean


Input: [Description] An ordered sequence of values (of any type). [Type]

Output: list


Input: [Description] A PICS-NG metadata label. [Type]

Output: label


Input: [Description] A Uniform Resource Locator. Syntactically this is a string, but only those characters are allowed which are legal as specified in the URL specification [Berners-Lee 94]. [Type]

Output: URL


Input: [Description] Objects of this type represent points in time. Syntactically the type looks like a string (with additional restrictions on their contents as defined in the syntax section below), internally it may be represented in any way the implementation sees fit. Syntactically this type is currently defined as quoted-ISO-date in the PICS version 1.1 specification. [Type]

Output: ISODate


Input: [name] accesskey [values] list of key labels [description]

Output: A key label or list of key labels with which to associate the element; each key label represents a keyboard shortcut which UAs can use to activate the element or give focus to the element. An ordered set of unique space-separated tokens, each of which must be exactly one Unicode code point in length.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] class [values] set of space-separated tokens [description]

Output: A name of a classification, or list of names of classifications, to which the element belongs.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] contenteditable [values] "true" or "false" or "" (empty string) or empty [description]

Output: Specifies whether the contents of the element are editable.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] contextmenu [values] ID reference [description]

Output: The value of the id attribute on the menu with which to associate the element as a context menu.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] dir [values] "ltr" or "rtl" [description]

Output: Specifies the element’s text directionality.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] draggable [values] "true" or "false" [description]

Output: Specifies whether the element is draggable.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] hidden [values] "hidden" or "" (empty string) or empty [description]

Output: Specifies that the element represents an element that is not yet, or is no longer, relevant.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] id [values] ID [description]

Output: A unique identifier for the element. There must not be multiple elements in a document that have the same id value. Any string, with the following restrictions: 1. must be at least one character long 2. must not contain any space characters

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] lang [values] language tag [description]

Output: Specifies the primary language for the contents of the element and for any of the element’s attributes that contain text. A valid language tag, as defined in [BCP47].

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] spellcheck [values] "true" or "false" or "" (empty string) or empty [description]

Output: Specifies whether the element represents an element whose contents are subject to spell checking and grammar checking.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] style [values] string [description]

Output: Specifies zero or more CSS declarations that apply to the element [CSS].

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] tabindex [values] integer [description]

Output: Specifies whether the element represents an element that is is focusable (that is, an element which is part of the sequence of focusable elements in the document), and the relative order of the element in the sequence of focusable elements in the document.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] title [values] normal character data [description]

Output: Advisory information associated with the element.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] translate [values] "yes" or "no" [description]

Output: Specifies whether an element's attribute values and the values of its Text node children are to be translated when the page is localized, or whether to leave them unchanged.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [anyURI Name] Success [Final] Final [Description]

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] VersionMismatch [Final] Final [Description]

Output: The service does not support the protocol version specified in the request.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Sender [Final] Final [Description]

Output: An error occurred that was due to the message sent by the sender.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Receiver [Final] Final [Description]

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Represent [Final] Not Final [Description]

Output: The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Pending [Final] Not Final [Description]

Output: The request has been accepted for processing and the service will return the result asynchronously.

XML Key Management Specification (XKMS 2.0)


Input: [Section] Text Wrapping [Element] flowTref [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Text Wrapping [Element] flowRef [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Text Wrapping [Element] flowImage [Attribute] width [Values]

Output: %Length;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Text Wrapping [Element] flowImage [Attribute] height [Values]

Output: %Length;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Editable Text Fields [Element] flowDiv [Attribute] editable [Values]

Output: true | false

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Editable Text Fields [Element] text [Attribute] editable [Values]

Output: true | false

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] elementDef [Attribute] name [Values]

Output: CDATA

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] transformer [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] transformer [Attribute] type [Values]

Output: content-type

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] param [Attribute] name [Values]

Output: CDATA

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] param [Attribute] value [Values]

Output: CDATA

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] refContent [Attribute] select [Values]

Output: %XPathSelector;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element definitions [Element] refContent [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Element focus and navigation [Element] container elements and graphics elements [Attribute] focusable [Values]

Output: true | false | auto

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The handler element [Element] handler [Attribute] type [Values]

Output: %ContentType;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The handler element [Element] handler [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The handler element [Element] handler [Attribute] xml:base [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The handler element [Element] handler [Attribute] ev:event [Values]

Output: CDATA

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The video element [Element] video [Attribute] x [Values]

Output: %Coordinate;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The video element [Element] video [Attribute] y [Values]

Output: %Coordinate;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The video element [Element] video [Attribute] width [Values]

Output: %Length;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The video element [Element] video [Attribute] height [Values]

Output: %Length;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The video element [Element] video [Attribute] preserveAspectRatio [Values]

Output: %PreserveAspectRatioSpec;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] type [Values]

Output: transition-type

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] subtype [Values]

Output: transition-type

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] dur [Values]

Output: CDATA

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] startProgress [Values]

Output: %TransitionValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] endProgress [Values]

Output: %TransitionValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] direction [Values]

Output: forward | reverse

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Transition effects [Element] transition [Attribute] fadeColor [Values]

Output: %Color;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The page element [Element] page [Attribute] viewBox [Values]

Output: %ViewBoxSpec;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The page element [Element] page [Attribute] preserveAspectRatio [Values]

Output: %PreserveAspectRatioSpec;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The page element [Element] page [Attribute] page-orientation [Values]

Output: 270 | -180 | -90 | 0 | 90 | 180 | 270

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The timelineBegin attribute [Element] svg, page? [Attribute] timelineBegin [Values]

Output: onLoad | onStart

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The streamedContents attribute [Element] page? [Attribute] streamedContent [Values]

Output: keep | discard

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Enhanced Alpha Compositing [Element] container elements and graphics elements [Attribute] clip-to-self [Values]

Output: true | false | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Enhanced Alpha Compositing [Element] container elements [Attribute] enable-background [Values]

Output: accumulate | new [ x y width height ] | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Enhanced Alpha Compositing [Element] container elements [Attribute] knock-out [Values]

Output: true | false | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Enhanced Alpha Compositing [Element] container elements and graphics elements [Attribute] comp-op [Values]

Output: clear | src | dst | src_over | dst_over | src_in | dst_in | src_out | dst_out | src_atop | dst_atop | xor | plus | multiply | screen | overlay | darken | lighten | color_dodge | color_burn | hard_light | soft_light | difference | exclusion | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Constrained Transformations [Element] container elements, use, image, feImage [Attribute] transform-host [Values]

Output: true | false

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The solidColor Element [Element] solidColor [Attribute] solid-color [Values]

Output: currentColor | [icc-color( [, ]* ) ] | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The solidColor Element [Element] solidColor [Attribute] solid-opacity [Values]

Output: | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Inheritance into the shadow tree [Element] all elements that establish shadow trees [Attribute] shadowInherit [Values]

Output: onDefine | onUse | none | inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Using device colors [Element] deviceColor [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Controlling the rendering color space [Element] container elements and graphical elements [Attribute] rendering-color-space [Values]

Output: auto | sRGB | linearRGB | | %URI; |inherit

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Prefetching resources [Element] prefetch [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Prefetching resources [Element] prefetch [Attribute] mediaSize [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Prefetching resources [Element] prefetch [Attribute] mediaTime [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] Prefetching resources [Element] prefetch [Attribute] bandwidth [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vectorEffect element [Element] vectorEffect [Attribute] vectorEffectUnits [Values]

Output: userSpaceOnUse | objectBoundingBox

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vectorEffect element [Element] vectorEffect [Attribute] compositing [Values]

Output: normal | knockout

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-width [Values]

Output: %StrokeWidthValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-dasharray [Values]

Output: %StrokeDashArrayValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-dashoffset [Values]

Output: %StrokeDashOffsetValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-linejoin [Values]

Output: (miter | round | bevel | inherit)

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-linecap [Values]

Output: (butt | round | square | inherit)

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStrokePath element [Element] veStrokePath [Attribute] stroke-miterlimit [Values]

Output: %StrokeMiterLimitValue;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veSetback element [Element] veSetback [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veSetback element [Element] veSetback [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veSetback element [Element] veSetback [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veSetback element [Element] veSetback [Attribute] setback-offset [Values]

Output: %Length;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veAffine element [Element] veAffine [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veAffine element [Element] veAffine [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veAffine element [Element] veAffine [Attribute] transformPath [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veReverse element [Element] veReverse [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veReverse element [Element] veReverse [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veJoin element [Element] veJoin [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veJoin element [Element] veJoin [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veJoin element [Element] veJoin [Attribute] in2 [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veJoin element [Element] veJoin [Attribute] connect [Values]

Output: line | none

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veUnion element [Element] veUnion [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veUnion element [Element] veUnion [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veUnion element [Element] veUnion [Attribute] in2 [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veIntersect element [Element] veIntersect [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veIntersect element [Element] veIntersect [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veIntersect element [Element] veIntersect [Attribute] in2 [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veExclude element [Element] veExclude [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veExclude element [Element] veExclude [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veExclude element [Element] veExclude [Attribute] in2 [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veFill element [Element] veFill [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veFill element [Element] veFill [Attribute] fill [Values]

Output: StrokePaint | FillPaint

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veFill element [Element] veFill [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStroke element [Element] veStroke [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStroke element [Element] veStroke [Attribute] fill [Values]

Output: StrokePaint | FillPaint

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veStroke element [Element] veStroke [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veMarker element [Element] veMarker [Attribute] in [Values]

Output: %SourcePath; | %InputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veMarker element [Element] veMarker [Attribute] marker-start [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veMarker element [Element] veMarker [Attribute] marker-mid [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veMarker element [Element] veMarker [Attribute] marker-end [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The veMarker element [Element] veMarker [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vePath element [Element] vePath [Attribute] result [Values]

Output: %OutputName;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vePathRef element [Element] vePathRef [Attribute] connect [Values]

Output: line | none

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vePathRef element [Element] vePathRef [Attribute] reverse [Values]

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vePathRef element [Element] vePathRef [Attribute] transform [Values]

Output: %TransformList;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Section] The vePathRef element [Element] vePathRef [Attribute] xlink:href [Values]

Output: %URI;

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Property] address [Expected Type] PostalAddress [Description]

Output: Physical address of the item.

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] aggregateRating [Expected Type] aggregateRating [Description]

Output: The overall rating, based on a collection of reviews or ratings, of the item.

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] geo [Expected Type] GeoCoordinates or GeoShape [Description]

Output: The geo coordinates of the place.

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] map [Expected Type] URL [Description]

Output: A URL to a map of the place.

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] photos [Expected Type] ImageObject or Photograph [Description]

Output: Photographs of this place

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] reviews [Expected Type] Review [Description]

Output: Review of the item

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [Property] telephone [Expected Type] Text [Description]

Output: The telephone number.

Difference between revisions of "WebSchemas/VacationRentals" - W3C Wiki


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict? Different functionality is to be expected, but do not influence each other

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: Conflict; changes through GSP can break consistency in LDPC

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [Event handler] onabort [Event handler event type]

Output: abort


Input: [Event handler] oncanplay [Event handler event type]

Output: canplay


Input: [Event handler] oncanplaythrough [Event handler event type]

Output: canplaythrough


Input: [Event handler] onchange [Event handler event type]

Output: change


Input: [Event handler] onclick [Event handler event type]

Output: click


Input: [Event handler] oncontextmenu [Event handler event type]

Output: contextmenu


Input: [Event handler] oncuechange [Event handler event type]

Output: cuechange


Input: [Event handler] ondblclick [Event handler event type]

Output: dblclick


Input: [Event handler] ondrag [Event handler event type]

Output: drag


Input: [Event handler] ondragend [Event handler event type]

Output: dragend


Input: [Event handler] ondragenter [Event handler event type]

Output: dragenter


Input: [Event handler] ondragleave [Event handler event type]

Output: dragleave


Input: [Event handler] ondragover [Event handler event type]

Output: dragover


Input: [Event handler] ondragstart [Event handler event type]

Output: dragstart


Input: [Event handler] ondrop [Event handler event type]

Output: drop


Input: [Event handler] ondurationchange [Event handler event type]

Output: durationchange


Input: [Event handler] onemptied [Event handler event type]

Output: emptied


Input: [Event handler] onended [Event handler event type]

Output: ended


Input: [Event handler] oninput [Event handler event type]

Output: input


Input: [Event handler] oninvalid [Event handler event type]

Output: invalid


Input: [Event handler] onkeydown [Event handler event type]

Output: keydown


Input: [Event handler] onkeypress [Event handler event type]

Output: keypress


Input: [Event handler] onkeyup [Event handler event type]

Output: keyup


Input: [Event handler] onloadeddata [Event handler event type]

Output: loadeddata


Input: [Event handler] onloadedmetadata [Event handler event type]

Output: loadedmetadata


Input: [Event handler] onloadstart [Event handler event type]

Output: loadstart


Input: [Event handler] onmousedown [Event handler event type]

Output: mousedown


Input: [Event handler] onmousemove [Event handler event type]

Output: mousemove


Input: [Event handler] onmouseout [Event handler event type]

Output: mouseout


Input: [Event handler] onmouseover [Event handler event type]

Output: mouseover


Input: [Event handler] onmouseup [Event handler event type]

Output: mouseup


Input: [Event handler] onmousewheel [Event handler event type]

Output: mousewheel


Input: [Event handler] onpause [Event handler event type]

Output: pause


Input: [Event handler] onplay [Event handler event type]

Output: play


Input: [Event handler] onplaying [Event handler event type]

Output: playing


Input: [Event handler] onprogress [Event handler event type]

Output: progress


Input: [Event handler] onratechange [Event handler event type]

Output: ratechange


Input: [Event handler] onreadystatechange [Event handler event type]

Output: readystatechange


Input: [Event handler] onreset [Event handler event type]

Output: reset


Input: [Event handler] onseeked [Event handler event type]

Output: seeked


Input: [Event handler] onseeking [Event handler event type]

Output: seeking


Input: [Event handler] onselect [Event handler event type]

Output: select


Input: [Event handler] onshow [Event handler event type]

Output: show


Input: [Event handler] onstalled [Event handler event type]

Output: stalled


Input: [Event handler] onsubmit [Event handler event type]

Output: submit


Input: [Event handler] onsuspend [Event handler event type]

Output: suspend


Input: [Event handler] ontimeupdate [Event handler event type]

Output: timeupdate


Input: [Event handler] onvolumechange [Event handler event type]

Output: volumechange


Input: [Event handler] onwaiting [Event handler event type]

Output: waiting


Input: [Definition] Character data [Attribute Type]

Output: CDATA


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS


Input: [Definition] A name composed of only name tokens as defined in XML 1.0 [ XML ]. [Attribute Type]

Output: NMTOKEN


Input: [Definition] One or more white space separated NMTOKEN values [Attribute Type]

Output: NMTOKENS


Input: [Definition] Sequence of one or more digits ([0-9]) [Attribute Type]

Output: NUMBER


Input: [Requirement] Supports many device form factors [Description] Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices [Source] SysApps Charter [Implications]

Output: The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] DAP API Support [Description] All APIs defined by DAP should be accessible to system applications [Source] SysApps Charter [Implications]

Output: Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Minimal user prompting [Description] Problems such as 'double prompting' should be avoided when integrating other APIs [Source] SysApps Charter [Implications]

Output: Some details of the expected user interactions may need to be specified in the security model or APIs

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with other applications [Description] Applications can communicate with other applications [Implications]

Output: Some kind of messaging will be supported

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Description] Applications can communicate with pre-defined web addresses [Implications]

Output: Access remote domains will be possible

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Trusted application source [Description] When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application. [Source] webinos [Implications]

Output: Apps must have provenance data attached to them

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App stores can revoke applications [Description] "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app" [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: App permissions can be changed remotely

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Description] B2G: "App store must be able to set the default permissions for an app". [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: The user is not the only source of access control decisions. this also suggests a need for conflict resolution.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Owner override [Description] The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example) [Source] B2G (user), webinos (user) [Implications]

Output: Access control settings must be changeable

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App privilege visibility [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: There must be a standard way for applications to identify the permissions they have and lack

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Description] Apps should not be vulnerable to common web vulnerabilities when granted significant privileges [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Non-browser security context: may be additional restrictions on HTML/JavaScript

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Description] Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Different 'levels' apply to SysApps - possibly 'roles'

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Access to files outside owned by the platform [Description] Ability for a system application to access (read and write) files outside of that application's sandboxed storage area. [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications]

Output: Need to provide both sandboxed and non-sandboxed storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Definition] Character data [Attribute Type]

Output: CDATA


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME


Input: [Definition] A name composed of only name tokens as defined in XML 1.0 [XML] [Attribute Type]

Output: NMTOKEN


Input: [Definition] One or more white space separated NMTOKEN values [Attribute Type]

Output: NMTOKENS


Input: [loginfo] uri [Category] Navigation and click-stream data [Structure] uri [Short display name]

Output: URI of requested resource

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] timestamp [Category] Navigation and click-stream data [Structure] date [Short display name]

Output: Request timestamp

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] clientip [Category] Computer Information [Structure] ipaddr [Short display name]

Output: Client's IP address or hostname

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.httpmethod [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: HTTP request method

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.bytes [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: Data bytes in response

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.statuscode [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: Response status code

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] name [Structure] personname [Short display name] User's Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] bdate [Structure] date [Short display name] User's Birth Date [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] cert [Structure] certificate [Short display name] User's Identity Certificate [Category]

Output: Unique Identifiers

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] gender [Structure] unstructured [Short display name] User's Gender (male or female) [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] employer [Structure] unstructured [Short display name] User's Employer [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] department [Structure] unstructured [Short display name] Department or division of organization where user is employed [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] jobtitle [Structure] unstructured [Short display name] User's Job Title [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] home-info [Structure] contact [Short display name] User's Home Contact Information [Category]

Output: Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [user] business-info [Structure] contact [Short display name] User's Business Contact Information [Category]

Output: Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Requirement] Alarm API [Source] SysApps Charter [Description]

Output: Applications can create alarms, notifying users

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Contacts API [Source] SysApps Charter [Description]

Output: Apps can add, remove and edit contacts

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Messaging API [Source] SysApps Charter [Description]

Output: Apps can send, receive and view SMS

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Telephony API [Source] SysApps Charter [Description]

Output: Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Raw Sockets API [Source] SysApps Charter [Description]

Output: Apps can create, manipulate and listen for low-level TCP and UDP connections

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Supports many device form factors [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Description]

Output: Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] DAP API Support [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Description]

Output: All APIs defined by DAP should be accessible to system applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Minimal user prompting [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Description]

Output: Problems such as 'double prompting' should be avoided when integrating other APIs

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] HTML5 [Description]

Output: Applications consist of HTML, CSS and JavaScript

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Location [Description]

Output: Applications have access to geolocation data

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with other applications [Implications] Some kind of messaging will be supported [Description]

Output: Applications can communicate with other applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Implications] Access remote domains will be possible [Description]

Output: Applications can communicate with pre-defined web addresses

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Valid across multiple platforms [Source] Compatibility of application packages [Description]

Output: Applications can run on any conformant platform, potentially including any device form factor

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Access control log [Source] webinos [Description]

Output: Allow access control decisions to be logged.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] API access rationale [Source] webinos [Description]

Output: Applications shall be able to explain why access to data or APIs is being requested.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application capability restriction [Source] webinos [Description]

Output: Applications shall access only its specified device features, extensions and content.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application intent [Source] webinos [Description]

Output: Applications shall specify its required functionality at install time or during updates.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application isolation [Source] webinos [Description]

Output: Applications shall be isolated from each other.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application policy approval [Source] webinos [Description]

Output: Changes to existing application intentions and permissions shall be approved by the end user.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Authenticity check [Source] webinos [Description]

Output: Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Certifier list [Source] webinos [Description]

Output: The list of authorities that certified an application shall be viewable by end-users.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Confidential credentials storage [Source] webinos [Description]

Output: The webinos runtime shall support the confidential storage of user credentials.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Credentials access restriction [Source] webinos [Description]

Output: Access to credentials storage shall be limited to a specific user, a specific device and a set of applications.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Data management rationale [Source] webinos [Description]

Output: applications shall be able to explain how collected sensitive data will be managed.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Default policy [Source] webinos [Description]

Output: A default security and privacy policy shall exist an be enforced on each conformant runtime

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Device-identity binding [Source] webinos [Description]

Output: Personal devices shall be bound to their owner's identities.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Device-identity binding revokation [Source] webinos [Description]

Output: The binding between personal devices and owner's identity shall be revokable.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Hierarchical policy enforcement [Source] webinos [Description]

Output: Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Secure cache [Source] webinos [Description]

Output: Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Secure storage [Source] webinos [Description]

Output: Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Trusted application source [Source] webinos [Implications] Apps must have provenance data attached to them [Description]

Output: When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App stores can revoke applications [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Description]

Output: "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app"

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] The user is not the only source of access control decisions. this also suggests a need for conflict resolution. [Description]

Output: B2G: "App store must be able to set the default permissions for an app".

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Installation [Source] B2G, webinos [Description]

Output: Applications must be installed before executed

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Owner override [Source] B2G (user), webinos (user) [Implications] Access control settings must be changeable [Description]

Output: The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example)

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App privilege visibility [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] There must be a standard way for applications to identify the permissions they have and lack [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Permission usability [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Non-browser security context: may be additional restrictions on HTML/JavaScript [Description]

Output: Apps should not be vulnerable to common web vulnerabilities when granted significant privileges

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Different 'levels' apply to SysApps - possibly 'roles' [Description]

Output: Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Access to files outside owned by the platform [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications] Need to provide both sandboxed and non-sandboxed storage [Description]

Output: Ability for a system application to access (read and write) files outside of that application's sandboxed storage area.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [1] Description of an emotion or a related state using a set of dimensions. [Annotation]

Output: Definition


Input: [1] MUST contain one or more dimension elements. The names of dimension elements which may occur as valid child elements are defined by the set attribute. [Annotation]

Output: Children


Input: [1] Required: set, a name or URI identifying the set of dimension names that can be used. Optional: confidence, the annotator's confidence that the entirety of dimensional annotation given is correct. [Annotation]

Output: Attributes


Input: [1] A single MAY occur as a child of . [Annotation]

Output: Occurrence


Input: [1] Dimension elements [Annotation]

Output: Annotation


Input: [1] Annotation of a single emotion dimension. The tag name must be contained in the list of values identified by the set attribute of the enclosing element. [Annotation]

Output: Definition


Input: [1] Optionally, a dimension MAY have a child element. [Annotation]

Output: Children


Input: [1] Required: (none) Optional: value, the (constant) scale value of this dimension. confidence, the annotator's (constant) confidence that the annotation given for this dimension is correct. [Annotation]

Output: Attributes


Input: [1] Dimension elements occur as children of . Valid tag names are constrained to the set of dimension names identified in the set attribute of the parent element. For any given dimension name in the set, zero or one occurrences are allowed within a element. [Annotation]

Output: Occurrence


Input: [Level] -1 [Preserves]

Output: Preserves only a subset of the XPath data model Level -1 defines the class of candidates that preserve a subset of the XPath 1.0 data model. For example, a candidate might not preserve namespace prefixes.

Efficient XML Interchange Measurements Note

Table 1: The Fidelity Scale for Classification of EXI Candidates


Input: [Level] 0 [Preserves]

Output: Preserves the XPath data model Level 0 defines the class of candidates that preserve the XPath 1.0 data model. Such preservation includes the root node, elements, text nodes, attributes (not including namespace declarations), namespaces, processing instructions and comments. Unexpanded entities, the document type declaration and the internal subset are not preserved. This level corresponds to a common denominator in XML processing, it is equivalent to the SOAP XML subset with the addition of processing instructions and comments.

Efficient XML Interchange Measurements Note


Input: [Level] 1 [Preserves]

Output: Preserves the XML Information Set Level 1 defines the class of candidates that preserve the XML Information Set data model. The XML Information Set preserves more of the information represented in the document type declaration and internal subset than the XPath 1.0 data model but not all information, such as attribute and element declarations, is preserved. The [all declarations processed] property of the Document Information Item is not, strictly speaking, part of the Infoset [XML Infoset] and therefore does not need to be preserved. NOTE: A candidate can fully support level 1, level 2, and the preservation of the complete internal subset by including and encoding the internal subset as a string, thereby leaving it up to the decoder to optionally process it.

Efficient XML Interchange Measurements Note


Input: [Level] 2 [Preserves]

Output: Preserves the the XML Information Set and all declarations Level 2 defines the class of candidates that preserve the XML Information Set data model, as in level 1, in addition to all information that is not purely syntactic. Such additional information will include the attribute, element and entity declarations. This level covers the preservation of all information represented by an XML document but does not accede to supporting purely syntactic constructs. NOTE: A candidate can fully support level 2 by including and encoding the internal subset as a string, and thus leaving it up to the decoder to optionally process it.

Efficient XML Interchange Measurements Note


Input: [Level] 3 [Preserves]

Output: Preservation of syntactic sugar of the XML document Level 3 defines the class of candidates that preserves all information represented by an XML document, as in level 2, in additional to some but not all syntactic information. NOTE: Full syntactic information is supported by level 4. Such preservation includes but is not limited to: CDATA Sections resolved external entity reference boundaries (when an entity is resolved a candidate will flag the part in the produced infoset where the information included from it starts and ends) the use of single or double quotes characters for quoted strings white space in markup the difference between empty element variants the order of attributes.

Efficient XML Interchange Measurements Note


Input: [Level] 4 [Preserves]

Output: Preservation of bytes Level 4 defines the class of candidates that preserve the XML document byte-per-byte. NOTE: This is the simple level supported by generic encodings such as gzip.

Efficient XML Interchange Measurements Note


Input: [Category] Project purpose and scope [3] The project purpose is mostly defined: the client is described moderately, the scope of the project and the project goals are mostly clear and understandable. [2] Some of the project purpose is defined: the client is described only partially, the scope of the project and the project goals are partially clear and understandable. [1] Little if any of the project purpose is defined: the client description is inaccurate, the scope of the project and the project goals are unclear and difficult to understand. [4]

Output: The project purpose is well defined: the client is described well, the scope of the project and the project goals are clear and understandable.

Interact/Project Management - Web Education Community Group


Input: [Category] Stakeholders / sponsors [3] The stakeholders/sponsors have accurate and mostly complete contact information. [2] Some stakeholders/sponsors have accurate and mostly complete contact information. [1] Few if any of the stakeholders/sponsors have accurate and complete contact information. [4]

Output: All of the stakeholders/sponsors have accurate and complete contact information.

Interact/Project Management - Web Education Community Group


Input: [Category] Success criteria and quality definition [3] The success criteria is itemized, mostly accurate and mostly complete. [2] The success criteria is itemized, partially accurate and somewhat complete. [1] The success criteria is poorly itemized, potentially inaccurate and incomplete. [4]

Output: The success criteria is itemized, accurate and complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Project constraints, assumptions and dependencies [3] Project constraints are clearly outlined, complete with assumptions and dependencies. [2] Project constraints are partially outlined, with some assumptions and dependencies. [1] Project constraints not poorly outlined, with some assumptions and dependencies. [4]

Output: Project constraints are clearly and comprehensively outlined, complete with assumptions and dependencies.

Interact/Project Management - Web Education Community Group


Input: [Category] Resources [3] Resources are mostly listed. [2] Resources are partially listed. [1] Resources are incomplete. [4]

Output: Resources are comprehensively listed.

Interact/Project Management - Web Education Community Group


Input: [Category] Budget [3] The project budget is itemized, mostly accurate and mostly complete. [2] The project budget is itemized, partially accurate and somewhat complete. [1] The project budget is poorly itemized, potentially inaccurate and incomplete. [4]

Output: The project budget is itemized, accurate and complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Milestones [3] Most milestones are indicated. [2] Milestones are partially indicated. [1] Some or few milestones are indicated. [4]

Output: Milestones are comprehensively indicated.

Interact/Project Management - Web Education Community Group


Input: [Category] Time/cost estimation [3] The time/cost estimations are mostly clear and accurate. [2] The time/cost estimations are only partially clear and accurate. [1] The time/cost estimations are only unclear and of questionable accuracy. [4]

Output: The time/cost estimations are clear and accurate.

Interact/Project Management - Web Education Community Group


Input: [Category] Process [3] The explanation of the project process is fairly clear, moderately understandable, and mostly follows a natural progression. Roles and participation of parties involved is moderately explained. [2] The explanation of the project process is only partially clear and understandable, and only slightly follows a natural progression. Roles and participation of parties involved are not fully explained. [1] The explanation of the project process is unclear and not understandable, and only does not follow a natural progression. Roles and participation of parties involved are unclear or not explained. [4]

Output: The explanation of the project process is clear, easy to understand, and follows a natural progression. Roles and participation of parties involved is clearly explained.

Interact/Project Management - Web Education Community Group


Input: [Category] Project solution proposal [3] Description is clear, concise, mentioning most activities that will be undertaken, as well as an appropriate technological solution. [2] Description is vague, too long (or too short) mentioning some activities that will be undertaken and a fairly appropriate technological solution. [1] Description is vague, too long (or too short) mentioning some activities that will be undertaken and an inappropriate technological solution. [4]

Output: Description is clear, concise and states what activities that will be undertaken, as well as an appropriate technological solution.

Interact/Project Management - Web Education Community Group


Input: [Category] Presentation [3] The scope document is mostly organized and consistently formatted, and has a moderatly professional presentation/look and feel. [2] The scope document is only somewhat organized and consistently formatted, and has a slight professional presentation/look and feel. [1] The scope document is poorly organized and inconsistently formatted, and completely lacks a professional presentation/look and feel. [4]

Output: The scope document is well-organized, consistently formatted, and has a very professional presentation/look and feel.

Interact/Project Management - Web Education Community Group


Input: [Category] Contributions [4] Routinely provides useful ideas when participating in the group and in classroom discussion. Not afraid to challenge an idea constructively. A definite leader who contributes a lot of effort. [3] Usually provides useful ideas when participating in the group and in classroom discussion. Hesitant to challenge ideas. A strong group member who tries hard. [2] Sometimes provides useful ideas when participating in the group and in classroom discussion. Does not challenge existing ideas. A satisfactory group member who does what is required. [1]

Output: Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate.

Interact/Project Management - Web Education Community Group


Input: [Category] Working with others [4] Almost always listens to, shares with, and supports the efforts of others. Tries to keep people working well together. [3] Usually listens to, shares, with, and supports the efforts of others. Does not cause “waves” in the group. [2] Often listens to, shares with, and supports the efforts of others, but sometimes is not a good team member. [1]

Output: Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting agenda [4] Meeting objectives are clearly defined, items of discussion are listed and written in an actionable manner. [3] Meeting objectives are reasonably clearly stated, items of discussion are listed. [2] Meeting objectives are vague, items of discussion are incomplete and somewhat actionable. [1]

Output: Meeting objectives not specific enough, items of discussion are not actionable.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting management [4] Meeting is kept on track and on time, all points are covered, and all action points are assigned. [3] Meeting runs over time, all points are covered and all action points are assigned. [2] Meeting runs over time, most points are covered, action items established. [1]

Output: Meeting runs over time, not all points are covered and action points are not explicitly stated.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to team [4] Summary is readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members. [3] Summary is readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points. [2] Summary is fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking clear action points. [1]

Output: Summary is unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to client [4] Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. Summary indicates clearly what the next steps will be. [3] Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. [2] Summary is fairly readable (too long or too short), does not reiterate the issue, but states the team’s proposed solution. [1]

Output: Summary is unclear (too long or too short), does not reiterate the issue nor clearly states the team’s proposed solution.

Interact/Project Management - Web Education Community Group


Input: [4] The project purpose is well defined: the client is described well, the scope of the project and the project goals are clear and understandable. [3] The project purpose is mostly defined: the client is described moderately, the scope of the project and the project goals are mostly clear and understandable. [2] Some of the project purpose is defined: the client is described only partially, the scope of the project and the project goals are partially clear and understandable. [1] Little if any of the project purpose is defined: the client description is inaccurate, the scope of the project and the project goals are unclear and difficult to understand. [Category]

Output: Project purpose and scope

Interact/Project Management - Web Education Community Group


Input: [4] All of the stakeholders/sponsors have accurate and complete contact information. [3] The stakeholders/sponsors have accurate and mostly complete contact information. [2] Some stakeholders/sponsors have accurate and mostly complete contact information. [1] Few if any of the stakeholders/sponsors have accurate and complete contact information. [Category]

Output: Stakeholders / sponsors

Interact/Project Management - Web Education Community Group


Input: [4] The success criteria is itemized, accurate and complete. [3] The success criteria is itemized, mostly accurate and mostly complete. [2] The success criteria is itemized, partially accurate and somewhat complete. [1] The success criteria is poorly itemized, potentially inaccurate and incomplete. [Category]

Output: Success criteria and quality definition

Interact/Project Management - Web Education Community Group


Input: [4] Project constraints are clearly and comprehensively outlined, complete with assumptions and dependencies. [3] Project constraints are clearly outlined, complete with assumptions and dependencies. [2] Project constraints are partially outlined, with some assumptions and dependencies. [1] Project constraints not poorly outlined, with some assumptions and dependencies. [Category]

Output: Project constraints, assumptions and dependencies

Interact/Project Management - Web Education Community Group


Input: [4] Resources are comprehensively listed. [3] Resources are mostly listed. [2] Resources are partially listed. [1] Resources are incomplete. [Category]

Output: Resources

Interact/Project Management - Web Education Community Group


Input: [4] The project budget is itemized, accurate and complete. [3] The project budget is itemized, mostly accurate and mostly complete. [2] The project budget is itemized, partially accurate and somewhat complete. [1] The project budget is poorly itemized, potentially inaccurate and incomplete. [Category]

Output: Budget

Interact/Project Management - Web Education Community Group


Input: [4] Milestones are comprehensively indicated. [3] Most milestones are indicated. [2] Milestones are partially indicated. [1] Some or few milestones are indicated. [Category]

Output: Milestones

Interact/Project Management - Web Education Community Group


Input: [4] The time/cost estimations are clear and accurate. [3] The time/cost estimations are mostly clear and accurate. [2] The time/cost estimations are only partially clear and accurate. [1] The time/cost estimations are only unclear and of questionable accuracy. [Category]

Output: Time/cost estimation

Interact/Project Management - Web Education Community Group


Input: [4] The explanation of the project process is clear, easy to understand, and follows a natural progression. Roles and participation of parties involved is clearly explained. [3] The explanation of the project process is fairly clear, moderately understandable, and mostly follows a natural progression. Roles and participation of parties involved is moderately explained. [2] The explanation of the project process is only partially clear and understandable, and only slightly follows a natural progression. Roles and participation of parties involved are not fully explained. [1] The explanation of the project process is unclear and not understandable, and only does not follow a natural progression. Roles and participation of parties involved are unclear or not explained. [Category]

Output: Process

Interact/Project Management - Web Education Community Group


Input: [4] Description is clear, concise and states what activities that will be undertaken, as well as an appropriate technological solution. [3] Description is clear, concise, mentioning most activities that will be undertaken, as well as an appropriate technological solution. [2] Description is vague, too long (or too short) mentioning some activities that will be undertaken and a fairly appropriate technological solution. [1] Description is vague, too long (or too short) mentioning some activities that will be undertaken and an inappropriate technological solution. [Category]

Output: Project solution proposal

Interact/Project Management - Web Education Community Group


Input: [4] The scope document is well-organized, consistently formatted, and has a very professional presentation/look and feel. [3] The scope document is mostly organized and consistently formatted, and has a moderatly professional presentation/look and feel. [2] The scope document is only somewhat organized and consistently formatted, and has a slight professional presentation/look and feel. [1] The scope document is poorly organized and inconsistently formatted, and completely lacks a professional presentation/look and feel. [Category]

Output: Presentation

Interact/Project Management - Web Education Community Group


Input: [Category] Contributions [4] Routinely provides useful ideas when participating in the group and in classroom discussion. Not afraid to challenge an idea constructively. A definite leader who contributes a lot of effort. [2] Sometimes provides useful ideas when participating in the group and in classroom discussion. Does not challenge existing ideas. A satisfactory group member who does what is required. [1] Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate. [3]

Output: Usually provides useful ideas when participating in the group and in classroom discussion. Hesitant to challenge ideas. A strong group member who tries hard.

Interact/Project Management - Web Education Community Group


Input: [Category] Working with others [4] Almost always listens to, shares with, and supports the efforts of others. Tries to keep people working well together. [2] Often listens to, shares with, and supports the efforts of others, but sometimes is not a good team member. [1] Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player. [3]

Output: Usually listens to, shares, with, and supports the efforts of others. Does not cause “waves” in the group.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting agenda [4] Meeting objectives are clearly defined, items of discussion are listed and written in an actionable manner. [2] Meeting objectives are vague, items of discussion are incomplete and somewhat actionable. [1] Meeting objectives not specific enough, items of discussion are not actionable. [3]

Output: Meeting objectives are reasonably clearly stated, items of discussion are listed.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting management [4] Meeting is kept on track and on time, all points are covered, and all action points are assigned. [2] Meeting runs over time, most points are covered, action items established. [1] Meeting runs over time, not all points are covered and action points are not explicitly stated. [3]

Output: Meeting runs over time, all points are covered and all action points are assigned.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to team [4] Summary is readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members. [2] Summary is fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking clear action points. [1] Summary is unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [3]

Output: Summary is readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to client [4] Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. Summary indicates clearly what the next steps will be. [2] Summary is fairly readable (too long or too short), does not reiterate the issue, but states the team’s proposed solution. [1] Summary is unclear (too long or too short), does not reiterate the issue nor clearly states the team’s proposed solution. [3]

Output: Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution.

Interact/Project Management - Web Education Community Group


Input: [Type] string [Description]

Output: A sequence of characters [Note: a discussion of character sets will be included in a future version of this document]. Syntactically strings are case-sensitive and may contain whitespace.


Input: [Type] symbol [Description]

Output: A sequence of characters acting as a unique identifier. Syntactically symbols are case-insensitive. The particular syntax used for metadata restricts the set of characters allowed in a symbol. Furthermore, symbols may not contain whitespace.


Input: [Type] integer [Description]

Output: An integer.


Input: [Type] float [Description]

Output: A floating-point approximation of a real number.


Input: [Type] range [Description]

Output: A tuple of two numbers, representing lower and upper bounds of an interval.


Input: [Type] number [Description]

Output: Either an integer, a float, or a range.


Input: [Type] boolean [Description]

Output: A boolean value. The names of the two possible values are true and false.


Input: [Type] list [Description]

Output: An ordered sequence of values (of any type).


Input: [Type] label [Description]

Output: A PICS-NG metadata label.


Input: [Type] URL [Description]

Output: A Uniform Resource Locator. Syntactically this is a string, but only those characters are allowed which are legal as specified in the URL specification [Berners-Lee 94].


Input: [Type] ISODate [Description]

Output: Objects of this type represent points in time. Syntactically the type looks like a string (with additional restrictions on their contents as defined in the syntax section below), internally it may be represented in any way the implementation sees fit. Syntactically this type is currently defined as quoted-ISO-date in the PICS version 1.1 specification.


Input: [State] Hidden [Data type] An arbitrary string [Control type] n/a [Keyword]

Output: hidden


Input: [State] Text [Data type] Text with no line breaks [Control type] A text field [Keyword]

Output: text


Input: [State] Search [Data type] Text with no line breaks [Control type] Search field [Keyword]

Output: search


Input: [State] Telephone [Data type] Text with no line breaks [Control type] A text field [Keyword]

Output: tel


Input: [State] URL [Data type] An absolute URL [Control type] A text field [Keyword]

Output: url


Input: [State] E-mail [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [Keyword]

Output: email


Input: [State] Password [Data type] Text with no line breaks (sensitive information) [Control type] A text field that obscures data entry [Keyword]

Output: password


Input: [State] Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [Keyword]

Output: datetime


Input: [State] Date [Data type] A date (year, month, day) with no time zone [Control type] A date control [Keyword]

Output: date


Input: [State] Month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [Keyword]

Output: month


Input: [State] Week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type] A week control [Keyword]

Output: week


Input: [State] Time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [Keyword]

Output: time


Input: [State] Local Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [Keyword]

Output: datetime-local


Input: [State] Number [Data type] A numerical value [Control type] A text field or spinner control [Keyword]

Output: number


Input: [State] Range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [Keyword]

Output: range


Input: [State] Color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [Keyword]

Output: color


Input: [State] Checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [Keyword]

Output: checkbox


Input: [State] Radio Button [Data type] An enumerated value [Control type] A radio button [Keyword]

Output: radio


Input: [State] File Upload [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [Keyword]

Output: file


Input: [State] Submit Button [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [Keyword]

Output: submit


Input: [State] Image Button [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [Keyword]

Output: image


Input: [State] Reset Button [Data type] n/a [Control type] A button [Keyword]

Output: reset


Input: [State] Button [Data type] n/a [Control type] A button [Keyword]

Output: button


Input: [Element] flowText [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowText [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRegion [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRegionExclude [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowDiv [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowDiv [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowPara [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowPara [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowSpan [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowSpan [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRegionBreak [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowLine [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowLine [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowTref [Attribute] xlink:href [Values] %URI; [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowTref [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowTref [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRef [Attribute] xlink:href [Values] %URI; [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRef [Attribute] PresentationAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowRef [Attribute] StyleAttrs [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowImage [Attribute] width [Values] %Length; [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowImage [Attribute] height [Values] %Length; [Section]

Output: Text Wrapping

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] flowDiv [Attribute] editable [Values] true | false [Section]

Output: Editable Text Fields

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2


Input: [Element] text [Attribute] editable [Values] true | false [Section]

Output: Editable Text Fields

Mobile SVG Profiles: SVG Tiny and SVG Basic, Version 1.2