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

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


Input: [Element] prototype [Section]

Output: Element definitions

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


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

Output: Element definitions

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


Input: [Element] transformer [Attribute] type [Values] content-type [Section]

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


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

Output: Element definitions

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


Input: [Element] refContent [Attribute] select [Values] %XPathSelector; [Section]

Output: Element definitions

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


Input: [Element] refContent [Attribute] transform [Values] %TransformList; [Section]

Output: Element definitions

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


Input: [Element] container elements and graphics elements [Attribute] focusable [Values] true | false | auto [Section]

Output: Element focus and navigation

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


Input: [Element] hint [Section]

Output: Tooltips

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


Input: [Element] handler [Attribute] commonAttrs [Section]

Output: The handler element

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


Input: [Element] handler [Attribute] type [Values] %ContentType; [Section]

Output: The handler element

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


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

Output: The handler element

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


Input: [Element] handler [Attribute] xml:base [Values] %URI; [Section]

Output: The handler element

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


Input: [Element] handler [Attribute] ev:event [Values] CDATA [Section]

Output: The handler element

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


Input: [Element] audio [Attribute] XLinkEmbedAttrs [Section]

Output: The audio element

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


Input: [Element] audio [Attribute] MediaAttrs [Section]

Output: The audio element

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


Input: [Element] video [Attribute] x [Values] %Coordinate; [Section]

Output: The video element

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


Input: [Element] video [Attribute] y [Values] %Coordinate; [Section]

Output: The video element

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


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

Output: The video element

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


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

Output: The video element

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


Input: [Element] video [Attribute] preserveAspectRatio [Values] %PreserveAspectRatioSpec; [Section]

Output: The video element

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


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

Output: The video element

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


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

Output: The video element

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


Input: [Element] video [Attribute] XLinkEmbedAttrs [Section]

Output: The video element

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


Input: [Element] video [Attribute] MediaAttrs [Section]

Output: The video element

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


Input: [Element] transition [Attribute] type [Values] transition-type [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] subtype [Values] transition-type [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] dur [Values] CDATA [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] startProgress [Values] %TransitionValue; [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] endProgress [Values] %TransitionValue; [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] direction [Values] forward | reverse [Section]

Output: Transition effects

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


Input: [Element] transition [Attribute] fadeColor [Values] %Color; [Section]

Output: Transition effects

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


Input: [Element] par [Section]

Output: Timing and Synchronization

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


Input: [Element] seq [Section]

Output: Timing and Synchronization

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


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

Output: The pageSet element

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


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

Output: The pageSet element

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


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

Output: The page element

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


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

Output: The page element

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


Input: [Element] page [Attribute] viewBox [Values] %ViewBoxSpec; [Section]

Output: The page element

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


Input: [Element] page [Attribute] preserveAspectRatio [Values] %PreserveAspectRatioSpec; [Section]

Output: The page element

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


Input: [Element] page [Attribute] page-orientation [Values] 270 | -180 | -90 | 0 | 90 | 180 | 270 [Section]

Output: The page element

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


Input: [Element] svg, page? [Attribute] timelineBegin [Values] onLoad | onStart [Section]

Output: The timelineBegin attribute

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


Input: [Element] page? [Attribute] streamedContent [Values] keep | discard [Section]

Output: The streamedContents attribute

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


Input: [Element] container elements and graphics elements [Attribute] clip-to-self [Values] true | false | inherit [Section]

Output: Enhanced Alpha Compositing

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


Input: [Element] container elements [Attribute] enable-background [Values] accumulate | new [ x y width height ] | inherit [Section]

Output: Enhanced Alpha Compositing

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


Input: [Element] container elements [Attribute] knock-out [Values] true | false | inherit [Section]

Output: Enhanced Alpha Compositing

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


Input: [Element] container elements and graphics elements [Attribute] comp-op [Values] 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 [Section]

Output: Enhanced Alpha Compositing

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


Input: [Element] container elements, use, image, feImage [Attribute] transform-host [Values] true | false [Section]

Output: Constrained Transformations

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


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

Output: The solidColor Element

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


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

Output: The solidColor Element

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


Input: [Element] solidColor [Attribute] solid-color [Values] currentColor | [icc-color( [, ]* ) ] | inherit [Section]

Output: The solidColor Element

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


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

Output: The solidColor Element

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


Input: [Element] viewport-creating elements [Attribute] background-fill [Section]

Output: Background Fill Property

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


Input: [Element] all elements that establish shadow trees [Attribute] shadowInherit [Values] onDefine | onUse | none | inherit [Section]

Output: Inheritance into the shadow tree

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


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

Output: Using device colors

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


Input: [Element] deviceColor [Attribute] name [Section]

Output: Using device colors

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


Input: [Element] container elements and graphical elements [Attribute] rendering-color-space [Values] auto | sRGB | linearRGB | | %URI; |inherit [Section]

Output: Controlling the rendering color space

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


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

Output: Prefetching resources

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


Input: [Element] prefetch [Attribute] StdAttrs [Section]

Output: Prefetching resources

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


Input: [Element] prefetch [Attribute] mediaSize [Values] | [Section]

Output: Prefetching resources

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


Input: [Element] prefetch [Attribute] mediaTime [Values] | [Section]

Output: Prefetching resources

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


Input: [Element] prefetch [Attribute] bandwidth [Values] | [Section]

Output: Prefetching resources

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


Input: [Element] vectorEffect [Attribute] vectorEffectUnits [Values] userSpaceOnUse | objectBoundingBox [Section]

Output: The vectorEffect element

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


Input: [Element] vectorEffect [Attribute] compositing [Values] normal | knockout [Section]

Output: The vectorEffect element

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


Input: [Element] veStrokePath [Attribute] result [Values] %OutputName; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] transform [Values] %TransformList; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-width [Values] %StrokeWidthValue; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-dasharray [Values] %StrokeDashArrayValue; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-dashoffset [Values] %StrokeDashOffsetValue; [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-linejoin [Values] (miter | round | bevel | inherit) [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-linecap [Values] (butt | round | square | inherit) [Section]

Output: The veStrokePath element

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


Input: [Element] veStrokePath [Attribute] stroke-miterlimit [Values] %StrokeMiterLimitValue; [Section]

Output: The veStrokePath element

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


Input: [Element] veSetback [Attribute] result [Values] %OutputName; [Section]

Output: The veSetback element

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


Input: [Element] veSetback [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veSetback element

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


Input: [Element] veSetback [Attribute] transform [Values] %TransformList; [Section]

Output: The veSetback element

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


Input: [Element] veSetback [Attribute] setback-offset [Values] %Length; [Section]

Output: The veSetback element

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


Input: [Element] veAffine [Attribute] result [Values] %OutputName; [Section]

Output: The veAffine element

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


Input: [Element] veAffine [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veAffine element

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


Input: [Element] veAffine [Attribute] transformPath [Values] %TransformList; [Section]

Output: The veAffine element

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


Input: [Element] veReverse [Attribute] result [Values] %OutputName; [Section]

Output: The veReverse element

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


Input: [Element] veReverse [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veReverse element

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


Input: [Element] veJoin [Attribute] result [Values] %OutputName; [Section]

Output: The veJoin element

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


Input: [Element] veJoin [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veJoin element

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


Input: [Element] veJoin [Attribute] in2 [Values] %SourcePath; | %InputName; [Section]

Output: The veJoin element

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


Input: [Element] veJoin [Attribute] connect [Values] line | none [Section]

Output: The veJoin element

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


Input: [Element] veUnion [Attribute] result [Values] %OutputName; [Section]

Output: The veUnion element

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


Input: [Element] veUnion [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veUnion element

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


Input: [Element] veUnion [Attribute] in2 [Values] %SourcePath; | %InputName; [Section]

Output: The veUnion element

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


Input: [Element] veIntersect [Attribute] result [Values] %OutputName; [Section]

Output: The veIntersect element

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


Input: [Element] veIntersect [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veIntersect element

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


Input: [Element] veIntersect [Attribute] in2 [Values] %SourcePath; | %InputName; [Section]

Output: The veIntersect element

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


Input: [Element] veExclude [Attribute] result [Values] %OutputName; [Section]

Output: The veExclude element

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


Input: [Element] veExclude [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veExclude element

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


Input: [Element] veExclude [Attribute] in2 [Values] %SourcePath; | %InputName; [Section]

Output: The veExclude element

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


Input: [Element] veFill [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veFill element

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


Input: [Element] veFill [Attribute] fill [Values] StrokePaint | FillPaint [Section]

Output: The veFill element

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


Input: [Element] veFill [Attribute] transform [Values] %TransformList; [Section]

Output: The veFill element

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


Input: [Element] veStroke [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veStroke element

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


Input: [Element] veStroke [Attribute] fill [Values] StrokePaint | FillPaint [Section]

Output: The veStroke element

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


Input: [Element] veStroke [Attribute] transform [Values] %TransformList; [Section]

Output: The veStroke element

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


Input: [Element] veMarker [Attribute] in [Values] %SourcePath; | %InputName; [Section]

Output: The veMarker element

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


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

Output: The veMarker element

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


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

Output: The veMarker element

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


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

Output: The veMarker element

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


Input: [Element] veMarker [Attribute] transform [Values] %TransformList; [Section]

Output: The veMarker element

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


Input: [Element] vePath [Attribute] result [Values] %OutputName; [Section]

Output: The vePath element

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


Input: [Element] vePathRef [Attribute] connect [Values] line | none [Section]

Output: The vePathRef element

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


Input: [Element] vePathRef [Attribute] reverse [Values] ? [Section]

Output: The vePathRef element

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


Input: [Element] vePathRef [Attribute] transform [Values] %TransformList; [Section]

Output: The vePathRef element

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


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

Output: The vePathRef element

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


Input: [Category] Contributions [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] Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate. [4]

Output: 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.

Interact/Project Management - Web Education Community Group


Input: [Category] Working with others [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] Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player. [4]

Output: Almost always listens to, shares with, and supports the efforts of others. Tries to keep people working well together.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting agenda [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] Meeting objectives not specific enough, items of discussion are not actionable. [4]

Output: Meeting objectives are clearly defined, items of discussion are listed and written in an actionable manner.

Interact/Project Management - Web Education Community Group


Input: [Category] Meeting management [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] Meeting runs over time, not all points are covered and action points are not explicitly stated. [4]

Output: Meeting is kept on track and on time, all points are covered, and all action points are assigned.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to team [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] Summary is unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [4]

Output: Summary is readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members.

Interact/Project Management - Web Education Community Group


Input: [Category] Summary message to client [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] Summary is unclear (too long or too short), does not reiterate the issue nor clearly states the team’s proposed solution. [4]

Output: Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. Summary indicates clearly what the next steps will be.

Interact/Project Management - Web Education Community Group


Input: [user] name [Category] Physical Contact Information, Demographic and Socioeconomic Data [Structure] personname [Short display name]

Output: User's Name

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


Input: [user] bdate [Category] Demographic and Socioeconomic Data [Structure] date [Short display name]

Output: User's Birth Date

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


Input: [user] cert [Category] Unique Identifiers [Structure] certificate [Short display name]

Output: User's Identity Certificate

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


Input: [user] gender [Category] Demographic and Socioeconomic Data [Structure] unstructured [Short display name]

Output: User's Gender (male or female)

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


Input: [user] employer [Category] Demographic and Socioeconomic Data [Structure] unstructured [Short display name]

Output: User's Employer

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


Input: [user] department [Category] Demographic and Socioeconomic Data [Structure] unstructured [Short display name]

Output: Department or division of organization where user is employed

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


Input: [user] jobtitle [Category] Demographic and Socioeconomic Data [Structure] unstructured [Short display name]

Output: User's Job Title

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


Input: [user] home-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Structure] contact [Short display name]

Output: User's Home Contact Information

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


Input: [user] business-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Structure] contact [Short display name]

Output: User's Business Contact Information

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


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. [1] Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate. [2]

Output: 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.

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. [1] Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player. [2]

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

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. [1] Meeting objectives not specific enough, items of discussion are not actionable. [2]

Output: Meeting objectives are vague, items of discussion are incomplete and somewhat 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. [1] Meeting runs over time, not all points are covered and action points are not explicitly stated. [2]

Output: Meeting runs over time, most points are covered, action items established.

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. [1] Summary is unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [2]

Output: Summary is fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking 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. [3] Summary is readable and concise, clearly reiterating the issue, and 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. [2]

Output: Summary is fairly readable (too long or too short), does not reiterate the issue, but states the team’s proposed solution.

Interact/Project Management - Web Education Community Group


Input: [Event name] loadstart [Dispatched when...]

Output: The user agent begins looking for media data, as part of the resource selection algorithm.

HTML/Elements/video - Web Education Community Group


Input: [Event name] progress [Dispatched when...]

Output: The user agent is fetching media data.

HTML/Elements/video - Web Education Community Group


Input: [Event name] suspend [Dispatched when...]

Output: The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.

HTML/Elements/video - Web Education Community Group


Input: [Event name] abort [Dispatched when...]

Output: The user agent stops fetching the media data before it is completely downloaded, but not due to an error.

HTML/Elements/video - Web Education Community Group


Input: [Event name] error [Dispatched when...]

Output: An error occurs while fetching the media data.

HTML/Elements/video - Web Education Community Group


Input: [Event name] emptied [Dispatched when...]

Output: A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running).

HTML/Elements/video - Web Education Community Group


Input: [Event name] stalled [Dispatched when...]

Output: The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.

HTML/Elements/video - Web Education Community Group


Input: [Event name] play [Dispatched when...]

Output: Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin.

HTML/Elements/video - Web Education Community Group


Input: [Event name] pause [Dispatched when...]

Output: Playback has been paused. Fired after the pause() method has returned.

HTML/Elements/video - Web Education Community Group


Input: [Event name] loadedmetadata [Dispatched when...]

Output: The user agent has just determined the duration and dimensions of the media resource

HTML/Elements/video - Web Education Community Group


Input: [Event name] loadeddata [Dispatched when...]

Output: The user agent can render the media data at the current playback position for the first time.

HTML/Elements/video - Web Education Community Group


Input: [Event name] waiting [Dispatched when...]

Output: Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.

HTML/Elements/video - Web Education Community Group


Input: [Event name] playing [Dispatched when...]

Output: Playback has started.

HTML/Elements/video - Web Education Community Group


Input: [Event name] canplay [Dispatched when...]

Output: The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.

HTML/Elements/video - Web Education Community Group


Input: [Event name] canplaythrough [Dispatched when...]

Output: The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.

HTML/Elements/video - Web Education Community Group


Input: [Event name] seeking [Dispatched when...]

Output: The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.

HTML/Elements/video - Web Education Community Group


Input: [Event name] seeked [Dispatched when...]

Output: The seeking IDL attribute changed to false.

HTML/Elements/video - Web Education Community Group


Input: [Event name] timeupdate [Dispatched when...]

Output: The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.

HTML/Elements/video - Web Education Community Group


Input: [Event name] ended [Dispatched when...]

Output: Playback has stopped because the end of the media resource was reached.

HTML/Elements/video - Web Education Community Group


Input: [Event name] ratechange [Dispatched when...]

Output: Either the defaultPlaybackRate or the playbackRate attribute has just been updated.

HTML/Elements/video - Web Education Community Group


Input: [Event name] durationchange [Dispatched when...]

Output: The duration attribute has just been updated.

HTML/Elements/video - Web Education Community Group


Input: [Event name] volumechange [Dispatched when...]

Output: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.

HTML/Elements/video - Web Education Community Group


Input: [Dispatched when...] The user agent begins looking for media data, as part of the resource selection algorithm. [Event name]

Output: loadstart


Input: [Dispatched when...] The user agent is fetching media data. [Event name]

Output: progress


Input: [Dispatched when...] The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded. [Event name]

Output: suspend


Input: [Dispatched when...] The user agent stops fetching the media data before it is completely downloaded, but not due to an error. [Event name]

Output: abort


Input: [Dispatched when...] An error occurs while fetching the media data. [Event name]

Output: error


Input: [Dispatched when...] A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running). [Event name]

Output: emptied


Input: [Dispatched when...] The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. [Event name]

Output: stalled


Input: [Dispatched when...] Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin. [Event name]

Output: play


Input: [Dispatched when...] Playback has been paused. Fired after the pause() method has returned. [Event name]

Output: pause


Input: [Dispatched when...] The user agent has just determined the duration and dimensions of the media resource [Event name]

Output: loadedmetadata


Input: [Dispatched when...] The user agent can render the media data at the current playback position for the first time. [Event name]

Output: loadeddata


Input: [Dispatched when...] Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. [Event name]

Output: waiting


Input: [Dispatched when...] Playback has started. [Event name]

Output: playing


Input: [Dispatched when...] The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content. [Event name]

Output: canplay


Input: [Dispatched when...] The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering. [Event name]

Output: canplaythrough


Input: [Dispatched when...] The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event. [Event name]

Output: seeking


Input: [Dispatched when...] The seeking IDL attribute changed to false. [Event name]

Output: seeked


Input: [Dispatched when...] The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously. [Event name]

Output: timeupdate


Input: [Dispatched when...] Playback has stopped because the end of the media resource was reached. [Event name]

Output: ended


Input: [Dispatched when...] Either the defaultPlaybackRate or the playbackRate attribute has just been updated. [Event name]

Output: ratechange


Input: [Dispatched when...] The duration attribute has just been updated. [Event name]

Output: durationchange


Input: [Dispatched when...] Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. [Event name]

Output: volumechange


Input: [Notation] {$ rule text $} [Interpretation]

Output: Emit the rule text substituting any occurrence of variables from the binding map. The outer {$ $} can be omitted in cases where there is no ambiguity.


Input: [Notation] for(?elt in ?list) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.


Input: [Notation] for(?elt in ?list, != ?other) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn, skipping any element identical to ?other, replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.


Input: [Notation] $length(?list)$ [Interpretation]

Output: Used within a template this will be replaced by the length the RDFList bound to ?list.


Input: [Notation] $i$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt.


Input: [Notation] $i+1$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt, plus 1.


Input: [Data category] Translate [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Localization Note [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Terminology [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Directionality [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Ruby [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Language Information [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Elements Within Text [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Status] Proposal [Summary] To promote the 'citation' property currently on MedicalScholarlyArticle up to CreativeWork. [Vocab] Moves citation up to CreativeWork [Topic]

Output: Citation Promotion

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


Input: [Status] Proposal [Summary] Extension for describing accessibility properties of a CreativeWork. [Comments] Draft published to elicit feedback. [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. [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] Property to indicate that a single identity is being described. [Vocab] Essentially same meaning as owl:sameAs, but suggesting a distinct name to make it easier to talk about; also schema.org data is typically scruffier than OWL re http-range-14. [Comments] Draft published to elicit feedback. [Topic]

Output: sameThingAs

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


Input: [Status] Proposal [Summary] A proposal for a new Action type. [Vocab] See full entry and proposal for details. May2013 version builds on two previously published designs. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org

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] 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: [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: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Data category]

Output: Translate

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Data category]

Output: Localization Note

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable [Data category]

Output: Terminology

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Data category]

Output: Directionality

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] None [Overriding] Not applicable [Data category]

Output: Ruby

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Data category]

Output: Language Information

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable [Data category]

Output: Elements Within Text

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [0] scheme [case] insensitive [match]

Output: exact


Input: [0] userInfo [case] sensitive [match]

Output: exact


Input: [0] host [case] insensitive [match]

Output: endswith


Input: [0] port [case] sensitive [match]

Output: exact


Input: [0] path [case] sensitive [match]

Output: startswith


Input: [0] query [case] sensitive [match]

Output: startswith


Input: [0] fragment [case] sensitive [match]

Output: startswith


Input: [0] uri [case] sensitive [match]

Output: regex


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, linked style sheet was not recognized and document tree was rendered [text/xml]

Output: recognized as XML, linked style sheet was not recognized and document tree was rendered

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] not supported [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed due to the omitted xmlns declaration [text/xml]

Output: recognized as XML, parsing failed due to the omitted xmlns declaration

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not detected [application/xhtml+xml] not supported [application/xml] showed blank page [text/xml]

Output: showed blank page

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] failed correctly while parsing the DTD [text/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [QName Local Name] Success [Description] The operation succeeded. [Final]

Output: Final


Input: [QName Local Name] VersionMismatch [Description] The service does not support the protocol version specified in the request. [Final]

Output: Final


Input: [QName Local Name] Sender [Description] An error occurred that was due to the message sent by the sender. [Final]

Output: Final


Input: [QName Local Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final


Input: [QName Local Name] Represent [Description] 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 [Final]

Output: Not Final


Input: [QName Local Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously [Final]

Output: Not Final


Input: [For this page] A plain text version of the page, handy for pasting into email. [,shortcut] ,text [Access control] Same as the document [General tool]

Output: HTML to Text converter


Input: [For this page] List of bad links in the page [,shortcut] ,checklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] Bad links in a page and in pages linked from it [,shortcut] ,rchecklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] List of HTML markup errors. [,shortcut] ,validate [Access control] Same as the document [General tool]

Output: HTML Validator


Input: [For this page] List of spelling errors. [,shortcut] ,spell [Access control] Same as the document [General tool]

Output: W3C Spellchecker


Input: [For this page] List of style CSS errors. [,shortcut] ,cssvalidate [Access control] Works only on public pages. [General tool]

Output: CSS Validator


Input: [For this page] Log of changes to the document [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [General tool]

Output: CVS Log


Input: [For this page] HTTP headers sent by the server [,shortcut] ,headers [Access control] Same as the document [General tool]

Output: Headers


Input: [For this page] Check the compliance of this document to the W3C publication rules [,shortcut] ,pubrules [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [For this page] Check the compliance of this document to the W3C publication rules, only displaying errors [,shortcut] ,pubruleserrors [Access control] Same as the document [General tool]

Output: the pubrules checker


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


Input: [Keyword] datetime [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 [State]

Output: Date and Time


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

Output: Date


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

Output: Month


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

Output: Week


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

Output: Time


Input: [Keyword] datetime-local [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 [State]

Output: Local Date and Time


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

Output: Number


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

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


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

Output: File Upload


Input: [Keyword] submit [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 [State]

Output: Submit Button


Input: [Keyword] image [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 [State]

Output: Image Button


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

Output: Reset Button


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

Output: Button


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

Output: Definition


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

Output: Children


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

Output: Attributes


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

Output: Occurrence


Input: [1] Appraisal elements [Annotation]

Output: Annotation


Input: [1] Annotation of a single emotion appraisal. 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 appraisal MAY have a child element. [Annotation]

Output: Children


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

Output: Attributes


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

Output: Occurrence


Input: [Keyword] hidden [State] Hidden [Data type] An arbitrary string [Control type]


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

Output: Text field


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

Output: Search field


Input: [Keyword] tel [State] Telephone [Data type] Text with no line breaks [Control type]

Output: A text field


Input: [Keyword] url [State] URL [Data type] An absolute IRI [Control type]

Output: A text field


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

Output: A text field


Input: [Keyword] password [State] Password [Data type] Text with no line breaks (sensitive information) [Control type]

Output: Text field that obscures data entry


Input: [Keyword] datetime [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]

Output: A date and time control


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

Output: A date control


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

Output: A month control


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

Output: A week control


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

Output: A time control


Input: [Keyword] datetime-local [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]

Output: A date and time control


Input: [Keyword] number [State] Number [Data type] A numerical value [Control type]

Output: A text field or spinner control


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

Output: A slider control or similar


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

Output: A color well


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

Output: A checkbox


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

Output: A radio button


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

Output: A label and a button


Input: [Keyword] submit [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]

Output: A button


Input: [Keyword] image [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]

Output: Either a clickable image, or a button


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

Output: A button


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

Output: A button


Input: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.


Input: [General tool] CSS Validator [,shortcut] ,cssvalidate [Access control] Works only on public pages. [For this page]

Output: List of style CSS errors.


Input: [General tool] CVS Log [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [For this page]

Output: Log of changes to the document


Input: [General tool] Headers [,shortcut] ,headers [Access control] Same as the document [For this page]

Output: HTTP headers sent by the server


Input: [General tool] the pubrules checker [,shortcut] ,pubrules [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules


Input: [General tool] the pubrules checker [,shortcut] ,pubruleserrors [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules, only displaying errors


Input: [Low Level] Application can obtain and display descriptive metadata for playback content [High Level]

Output: section 4.2.1 Service Discovery section 4.2.3 Content Discovery

Requirements for Home Networking Scenarios


Input: [Low Level] Application can obtain and display other descriptive metadata such as Electronic Programming Guides [High Level]

Output: section 4.2.1 Service Discovery section 4.2.3 Content Discovery

Requirements for Home Networking Scenarios


Input: [Low Level] Application can select content binary formats which match the User-Agent’s supported playback formats [High Level]

Output: section 4.3.3 Playback of Content

Requirements for Home Networking Scenarios


Input: [Low Level] Application can play content from Home Network stored content sources [High Level]

Output: section 4.3.3 Playback of Content

Requirements for Home Networking Scenarios


Input: [Low Level] Applications can play live content from Home Network streaming sources [High Level]

Output: section 4.3.4 Playback of Live Content

Requirements for Home Networking Scenarios


Input: [Low Level] Applications can play content from Home Network recording sources [High Level]

Output: section 4.3.3 Playback of Content

Requirements for Home Networking Scenarios


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

Output: No

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Terminology [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: No

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] None [Overriding] Not applicable

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Elements Within Text [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable

Output: No

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] type 3 error occured, browser crashed [text/xml]

Output: type 3 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] type 3 error occured, browser crashed [text/xml]

Output: type 3 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not checked [application/xhtml+xml] not supported [application/xml] failed correctly [text/xml]

Output: failed correctly

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] failed correctly while parsing the DTD [text/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [Model Aspect] End-point basics [Linked Data Platform (LDP)]

Output: A LDP server exposes at least one URI to a container-type resource. A client can learn about the container and its contents (members), by simply fetching the container. If only the non-member information is needed, a client can request only that. If a client needs to know if it can create things in this container, then usual HTTP methods can be used such as HEAD or OPTIONS to learn about which verbs are permitted on the request URI. Need: It might be useful to define a common property for external vocabularies to use to indicate the end-point, take for example: Alternative: LDP provides no new facilities for web clients to acquire URLs to Containers. Web clients might use out of band knowledge, home resources, POWDER, emailing a friend a link, or any other mechanism deemed appropriate by the application's needs. It is possible for a server to expose a single Container as a home resource, which web clients GET and examine to locate other resources (including other Containers). It is also possible for that same home resource to be serialized and provided to a client as a document. LDP assumes that each client is able to obtain whatever URLs it needs through non-LDP means, and restricts itself to an interaction model for Containers and their members.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Container basics [Linked Data Platform (LDP)]

Output: A container has a URI where you can start interacting with the container, at the most basic level you can GET a list of members, and for containers with many members it is likely the response is broken into pages. Through HTTP HEAD/OPTIONS introspection, a client can learn which HTTP verbs are permitted on this. Since LDP containers are described using RDF constructs, a LDP server may allow clients to POST the representation of the container to create it. Need: How are the acceptable content-types communicated via HTTP headers? Alternative: Before asking 'how' acceptable content-types are communicated, we need to agree that doing so is required (should it be in-scope for LDP - part of ISSUE-21 perhaps). In the simplest case, once the client "knows" it is dealing with a conformant LDP Container it does know (at least) that Turtle is supported. If communicating supported content-types is in-scope, then a syntax needs to be defined (either new, or re-used). Potential re-use choices might include (and these are not necessarily mutually exclusive, although to keep clients simple it would help to have at least one required method if it is in-scope): atom:accept predicate(s) on a container Link: <>; rel="self"; type="one acceptable media type value" Linking itself to a POWDER document - I don't see any POWDER syntax covering media types, but it might be possible to re-use atom:accept in this context. Aside: If we do place it in-scope, we have the same question about members, so it might be that we talk about this introspection at the LDPR level and let LDPCs "inherit" it from LDPRs. LDPRs might leave everything optional, and LDPC requires one particular method while allowing others, for example.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Creating container members (resources) [Linked Data Platform (LDP)]

Output: Any kind of resource can be listed in a container, and everything that is in a container is represented by a member. Members follow the standardized metadata model defined by RDF. If a client has POSTed a "media resource" (pretty much anything other than RDF) to a container URI, which has one of the media types that the container accepts, the server accepts this media resource and creates the resource, which will then represent this media resource when you list the container contents. The interesting aspect of this setup is that you POST one thing, its representation gets converted by the server to some appropriate storage and its membership added to the container. email: there is only one container, and what you POST determines whether it's self-contained or not. if the POSTed resource contains all data (... in XML), it's what we now call "composition". if the POSTed resource contains a link to "external content" ( in XML), it's what we now call "aggregation". Servers might try to be smart about populating additional data fields for the resource, for example creation date and who created it. They also might consider come properties to be "server managed", i.e. read-only from any client's point of view. ISSUE-11 questions how much the LDP spec constrains them.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Member (resource) identity [Linked Data Platform (LDP)]

Output: A container is a set of members and (perhaps) non-member properties, and thus contains a list of members (entries) representing each individual member. The model uses a URI to represent the identity of each member resource, which will be used for identification globally. The identification of the member as an entry, will be represented as using a simple RDF statement: rdfs:member . Note: some proposals on the mailing list for ISSUE-34 include the use of different membership predicates like ldp:owns or ldp:contains in place of rdfs:member. If accepted, those predicates might cover some of the ground for ISSUE-21 (affordances).

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with container members [Linked Data Platform (LDP)]

Output: Members are listed when GETting a container, and their data is exposed through regular RDF mechanisms. If members are editable, a client can introspect via HEAD/OPTIONs to see if PUT, PATCH or DELETE verbs are permitted. A server may provide some member data or just a reference to it in the response of a request for container information.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with containers (composition) [Linked Data Platform (LDP)]

Output: Bringing into existence: typically containers just exist, though some servers may allow creation of containers by POSTing a representation of a container to an already-existing container. Removing from existence (DELETEing): containers are like any other HTTP web resource, they have a URI which a server may accept a DELETE request on. The question becomes, what happens to the members when a container is DELETEd? Based on resolution for ISSUE-25, in order for the container to be deleted all its members must also be deleted. There have been proposals for another model of containers, which may or may not have this rule, see ISSUE-34. Removing a member from a container: simply update the container's membership by PATCHing it with a statement to remove the membership triple. The resource still exists, its ownership is unknown (or perhaps a concept of a "default" container?). Adding an existing member to a container: potentially not allowed (ISSUE-25 resolution) Moving a member from one container to another: potentially not allowed (ISSUE-25 resolution) Alternative: PATCH to remove a member is not allowed; the client must DELETE the member to remove it from the container.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control. [Control Type]

Output: Text input (including date/time and password fields)

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the right of the check box. [Control Type]

Output: Checkbox

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.) [Control Type]

Output: Radio button group

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control.. [Control Type]

Output: Combo box

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is above the list box. [Control Type]

Output: List box

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text. [Control Type]

Output: Button

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [PREFIX] CONSTRUCT [2] DESCRIBE [3] ASK [BASE]

Output: SELECT


Input: [PREFIX] LIMIT [2] OFFSET [3] DISTINCT [4] REDUCED [BASE]

Output: ORDER BY


Input: [PREFIX] FROM NAMED [2] WHERE [BASE]

Output: FROM


Input: [PREFIX] OPTIONAL [2] UNION [3] FILTER [4] a [BASE]

Output: GRAPH


Input: [PREFIX] LANG [2] LANGMATCHES [3] DATATYPE [4] BOUND [5] sameTERM [BASE]

Output: STR


Input: [PREFIX] isIRI [2] isLITERAL [3] REGEX [4] true [5] false [6] isBLANK [BASE]

Output: isURI


Input: [Component] XPath 1.0 compatibility mode [Value]

Output: false

Static Context Components for use-when Expressions


Input: [Component] In scope namespaces [Value]

Output: determined by the in-scope namespaces for the containing element in the stylesheet


Input: [Component] Default element/type namespace [Value]

Output: determined by the xpath-default-namespace attribute if present (see 5.2 Unprefixed QNames in Expressions and Patterns); otherwise the null namespace


Input: [Component] Default function namespace [Value]

Output: The standard function namespace


Input: [Component] In scope type definitions [Value]

Output: The type definitions that would be available in the absence of any xsl:import-schema declaration


Input: [Component] In scope element declarations [Value]


Input: [Component] In scope attribute declarations [Value]


Input: [Component] In scope variables [Value]


Input: [Component] In scope functions [Value]

Output: The core functions defined in [Functions and Operators], together with the functions element-available, function-available, type-available, and system-property defined in this specification, plus the set of extension functions that are present in the static context of every XPath expression (other than a use-when expression) within the content of the element that is the parent of the use-when attribute. Note that stylesheet functions are not included in the context, which means that the function function-available will return false in respect of such functions. The effect of this rule is to ensure that function-available returns true in respect of functions that can be called within the scope of the use-when attribute. It also has the effect that these extensions functions will be recognized within the use-when attribute itself; however, the fact that a function is available in this sense gives no guarantee that a call on the function will succeed.


Input: [Component] In scope collations [Value]

Output: Implementation-defined


Input: [Component] Default collation [Value]

Output: The Unicode Codepoint Collation


Input: [Component] Base URI [Value]

Output: The base URI of the containing element in the stylesheet


Input: [Component] Statically known documents [Value]


Input: [Component] Statically known collections [Value]


Input: [QName Local Name] Success [Final] Final [Description]

Output: The operation succeeded.


Input: [QName Local Name] VersionMismatch [Final] Final [Description]

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


Input: [QName Local Name] Sender [Final] Final [Description]

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


Input: [QName Local Name] Receiver [Final] Final [Description]

Output: An error occurred at the receiver.


Input: [QName Local 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


Input: [QName Local Name] Pending [Final] Not Final [Description]

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


Input: [Responder] Doug Wright [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Whilst I believe the approach of annotating/selectively editing the Editor's draft potentially has merit as a platform for discussion within the WG, I believe that actually publishing multiple versions of the same document as official WDs of the WG is just plain confusing. I would not vote against publishing a reformulation of the additional material as separate WG Note.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Larry Masinter [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I think neither "majority" nor "most votes" should be used: if there is not "consensus" and there are votes (rather than straw polls), then one-vote-per-independent organization should be retained (one company has 17 members in "good standing"), and the "good standing" role of "invited experts" who are not actually experts or who do not actually participate should be reevaluated. A vote should not determined by those who are listed as working group members out of courtesy or for the rationale that their IPR disclaimer is needed. As far as IPR is concerned, both drafts contain new, unreviewed material that might trigger a patent review; commit-then-discuss should be evaluated against the patent policy to see if some adjustment is needed.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Joe Williams [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Manu's work can be used but not directly.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Sam Ruby [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: In this case could live with either document and in the case of competing technical drafts I would support publishing both; but publishing two drafts simultaneously that differ only in informative content seems like it would cause confusion.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Julian Reschke [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing both would create confusion, and also raise the question about which is "the right one".

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Edward O'Connor [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I think each "fork" should go through FPWD (which so far has only happened with formal WG decision-by-vote). Once through FPWD, I think we should always publish new WDs whenever the editor(s) would like to. (I think it wouldn't be a good thing for Manu's draft to also go through FPWD, as it only differs in warnings from Ian's, but nevertheless if we're going to embrace the "anyone can author a spec" idea, we should embrace it fully.)

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Kemp [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: As mentioned, I think it might be confusing to publish two drafts where one is a superset of the other.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Foliot [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: If there were technical differences between the 2 documents, my answer would likely have been very different. Since I currently see the "Manu's Draft" version as simply an enhanced copy of the work produced by Ian I see no benefit in making both available as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Bruce Lawson [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: changed my answer, having seen John Foliot's cleverer response: If there were technical differences between the 2 documents, my answer would likely have been very different. Since I currently see the "Manu's Draft" version as simply an enhanced copy of the work produced by Ian I see no benefit in making both available as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Henri Sivonen [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: The purpose of heartbeat WDs is to communicate to the community outside the WG itself, and publishing multiple drafts with only differences in informative statements fails at clear communication.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ian Hickson [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: If "I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts." wins, please count my vote as YES to both drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Lachlan Hunt [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing two separate drafts that are almost identical except for a few editorial comments about the stability of some random "controversial" sections does not solve any real problems, and will only serve to create confusion among the wider community. Even though I do not support the draft with extra warnings, I would rather see that one published by itself than have both needlessly published together.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Gavin Sharp [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I think publishing multiple drafts would be problematic from a PR perspective.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] David Singer [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I fear having two variants of one document would be confusing.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Shelley Powers [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: Two drafts would acknowledge the Editor's work, while providing another document that shows issues of concern. There is no PR problem with this approach--it reflects the current state of the group. On the other hand, I have a difficult time understanding why people who profess support for making information both visible and semantic, would vote for a choice that does neither.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Charles McCathie Nevile [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing two drafts seems likely to lead to confusion. However I agree with Larry that a serious attempt to reach consensus makes more sense than going through with something that receives a large minority of dissent. I recognise that the decision on how to proceed is up to the chairs, rather than a poll of all comers actually being binding. Please note that Opera Software, with many participants in the group, is not expressing a formal opinion at this time, but rather each participant is free to vote as they see fit, in what we understand to be the spirit of this poll. Should a suggestion such as Larry's be accepted, we would of course submit a single formal vote clarifying that it is such.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Cameron McCormack [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: While I am happy for the WG to publish multiple documents, I don't think selecting between drafts to publish as the main HTML 5 spec at a given point in time is the best way to proceed. I wonder if David Hyatt should really be listed as editor on whichever documents end up being published, though, given that he has not edited either.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Leif Halvard Silli [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: Now is the time to, eventually, display disagreement.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Adida [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: I would prefer that we pick a consistent long-term approach: if we are CTR, then everyone gets to CTR.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System