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: [Property] align-content [Values] auto | [ head | foot | flex-start | flex-end | baseline | center | space-between | space-around ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: block containers and flex containers


Input: [Property] align-items [Values] auto | [ head | foot | flex-start | flex-end | center | baseline | stretch ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: flexbox and grid containers


Input: [Property] align-self [Values] auto | [ baseline | head | foot | center | stretch ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: flex items and grid items


Input: [Property] justify-content [Values] auto | [ start | end | left | right | flex-start | flex-end | center | space-between | space-around ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: block containers and flex containers


Input: [Property] justify-items [Values] auto | [ start | center | end ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: grid containers


Input: [Property] justify-self [Values] auto | [ start | end | center ] && true? [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: block-level elements and grid items


Input: [Component] FTCaseOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be case insensitive or case sensitive. [Default initial value]

Output: case insensitive

Static Context Components


Input: [Component] FTDiacriticsOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be diacritics insensitive or diacritics sensitive. [Default initial value]

Output: diacritics insensitive

Static Context Components


Input: [Component] FTStemOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without stemming or with stemming. [Default initial value]

Output: without stemming

Static Context Components


Input: [Component] FTThesaurusOption overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known thesauri. [Default initial value]

Output: without thesaurus

Static Context Components


Input: [Component] Statically known thesauri augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list. [Default initial value]

Static Context Components


Input: [Component] FTStopWordOption overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known stop word lists. [Default initial value]

Output: without stopwords

Static Context Components


Input: [Component] Statically known stop word lists augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list. [Default initial value]

Static Context Components


Input: [Component] FTLanguageOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be castable to "xs:language" or "none". [Default initial value]

Output: no language is selected

Static Context Components


Input: [Component] FTWildCardOption no overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without wildcards or without wildcards. [Default initial value]

Output: without wildcards

Static Context Components


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string


Input: [Keyword] text [State] Text [Control type] Text field [Data type]

Output: Text with no line breaks


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks


Input: [Keyword] tel [State] Telephone [Control type] A text field [Data type]

Output: Text with no line breaks


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

Output: An absolute IRI


Input: [Keyword] email [State] E-mail [Control type] A text field [Data type]

Output: An e-mail address or list of e-mail addresses


Input: [Keyword] password [State] Password [Control type] Text field that obscures data entry [Data type]

Output: Text with no line breaks (sensitive information)


Input: [Keyword] datetime [State] Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC


Input: [Keyword] date [State] Date [Control type] A date control [Data type]

Output: A date (year, month, day) with no time zone


Input: [Keyword] month [State] Month [Control type] A month control [Data type]

Output: A date consisting of a year and a month with no time zone


Input: [Keyword] week [State] Week [Control type] A week control [Data type]

Output: A date consisting of a week-year number and a week number with no time zone


Input: [Keyword] time [State] Time [Control type] A time control [Data type]

Output: A time (hour, minute, seconds, fractional seconds) with no time zone


Input: [Keyword] datetime-local [State] Local Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone


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

Output: A numerical value


Input: [Keyword] range [State] Range [Control type] A slider control or similar [Data type]

Output: A numerical value, with the extra semantic that the exact value is not important


Input: [Keyword] color [State] Color [Control type] A color well [Data type]

Output: An sRGB color with 8-bit red, green, and blue components


Input: [Keyword] checkbox [State] Checkbox [Control type] A checkbox [Data type]

Output: A set of zero or more values from a predefined list


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

Output: An enumerated value


Input: [Keyword] file [State] File Upload [Control type] A label and a button [Data type]

Output: Zero or more files each with a MIME type and optionally a file name


Input: [Keyword] submit [State] Submit Button [Control type] A button [Data type]

Output: An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission


Input: [Keyword] image [State] Image Button [Control type] Either a clickable image, or a button [Data type]

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


Input: [Keyword] reset [State] Reset Button [Control type] A button [Data type]


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


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: [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: [event handler] onreceived [event name] received [event type] MessagingEvent [short description]

Output: handles received messages


Input: [event handler] onsent [event name] sent [event type] MessagingEvent [short description]

Output: handles sent messages


Input: [event handler] ondeliverysuccess [event name] deliverysuccess [event type] DeliveryReportEvent [short description]

Output: handles successful delivery reports


Input: [event handler] ondeliveryerror [event name] deliveryerror [event type] DeliveryReportEvent [short description]

Output: handles failure delivery reports


Input: [event handler] onserviceadded [event name] serviceadded [event type] ServiceChangeEvent [short description]

Output: handle new messaging services


Input: [event handler] onserviceremoved [event name] serviceremoved [event type] ServiceChangeEvent [short description]

Output: handle disabled messaging services


Input: [event handler] onreceived [event type] MessagingEvent [short description] handles received messages [event name]

Output: received


Input: [event handler] onsent [event type] MessagingEvent [short description] handles sent messages [event name]

Output: sent


Input: [event handler] ondeliverysuccess [event type] DeliveryReportEvent [short description] handles successful delivery reports [event name]

Output: deliverysuccess


Input: [event handler] ondeliveryerror [event type] DeliveryReportEvent [short description] handles failure delivery reports [event name]

Output: deliveryerror


Input: [event handler] onserviceadded [event type] ServiceChangeEvent [short description] handle new messaging services [event name]

Output: serviceadded


Input: [event handler] onserviceremoved [event type] ServiceChangeEvent [short description] handle disabled messaging services [event name]

Output: serviceremoved


Input: [Property] address [Description] Physical address of the item. [Expected Type]

Output: PostalAddress


Input: [Property] aggregateRating [Description] The overall rating, based on a collection of reviews or ratings, of the item. [Expected Type]

Output: aggregateRating


Input: [Property] geo [Description] The geo coordinates of the place. [Expected Type]

Output: GeoCoordinates or GeoShape


Input: [Property] map [Description] A URL to a map of the place. [Expected Type]

Output: URL


Input: [Property] photos [Description] Photographs of this place [Expected Type]

Output: ImageObject or Photograph


Input: [Property] reviews [Description] Review of the item [Expected Type]

Output: Review


Input: [Property] telephone [Description] The telephone number. [Expected Type]

Output: Text


Input: [Name] boxdl [Unicode] U+2510 [Unicode Name] BOX DRAWINGS LIGHT DOWN AND LEFT [Description]

Output: lower left quadrant


Input: [Name] boxdL [Unicode] U+2555 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE [Description]

Output: lower left quadrant


Input: [Name] boxDl [Unicode] U+2556 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE [Description]

Output: lower left quadrant


Input: [Name] boxDL [Unicode] U+2557 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND LEFT [Description]

Output: lower left quadrant


Input: [Name] boxdr [Unicode] U+250C [Unicode Name] BOX DRAWINGS LIGHT DOWN AND RIGHT [Description]

Output: lower right quadrant


Input: [Name] boxdR [Unicode] U+2552 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE [Description]

Output: lower right quadrant


Input: [Name] boxDr [Unicode] U+2553 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE [Description]

Output: lower right quadrant


Input: [Name] boxDR [Unicode] U+2554 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND RIGHT [Description]

Output: lower right quadrant


Input: [Name] boxh [Unicode] U+2500 [Unicode Name] BOX DRAWINGS LIGHT HORIZONTAL [Aliases] HorizontalLine [Description]

Output: horizontal line


Input: [Name] boxH [Unicode] U+2550 [Unicode Name] BOX DRAWINGS DOUBLE HORIZONTAL [Description]

Output: horizontal line


Input: [Name] boxhd [Unicode] U+252C [Unicode Name] BOX DRAWINGS LIGHT DOWN AND HORIZONTAL [Description]

Output: lower left and right quadrants


Input: [Name] boxhD [Unicode] U+2565 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE [Description]

Output: lower left and right quadrants


Input: [Name] boxHd [Unicode] U+2564 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE [Description]

Output: lower left and right quadrants


Input: [Name] boxHD [Unicode] U+2566 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL [Description]

Output: lower left and right quadrants


Input: [Name] boxhu [Unicode] U+2534 [Unicode Name] BOX DRAWINGS LIGHT UP AND HORIZONTAL [Description]

Output: upper left and right quadrants


Input: [Name] boxhU [Unicode] U+2568 [Unicode Name] BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE [Description]

Output: upper left and right quadrants


Input: [Name] boxHu [Unicode] U+2567 [Unicode Name] BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE [Description]

Output: upper left and right quadrants


Input: [Name] boxHU [Unicode] U+2569 [Unicode Name] BOX DRAWINGS DOUBLE UP AND HORIZONTAL [Description]

Output: upper left and right quadrants


Input: [Name] boxul [Unicode] U+2518 [Unicode Name] BOX DRAWINGS LIGHT UP AND LEFT [Description]

Output: upper left quadrant


Input: [Name] boxuL [Unicode] U+255B [Unicode Name] BOX DRAWINGS UP SINGLE AND LEFT DOUBLE [Description]

Output: upper left quadrant


Input: [Name] boxUl [Unicode] U+255C [Unicode Name] BOX DRAWINGS UP DOUBLE AND LEFT SINGLE [Description]

Output: upper left quadrant


Input: [Name] boxUL [Unicode] U+255D [Unicode Name] BOX DRAWINGS DOUBLE UP AND LEFT [Description]

Output: upper left quadrant


Input: [Name] boxur [Unicode] U+2514 [Unicode Name] BOX DRAWINGS LIGHT UP AND RIGHT [Description]

Output: upper right quadrant


Input: [Name] boxuR [Unicode] U+2558 [Unicode Name] BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE [Description]

Output: upper right quadrant


Input: [Name] boxUr [Unicode] U+2559 [Unicode Name] BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE [Description]

Output: upper right quadrant


Input: [Name] boxUR [Unicode] U+255A [Unicode Name] BOX DRAWINGS DOUBLE UP AND RIGHT [Description]

Output: upper right quadrant


Input: [Name] boxv [Unicode] U+2502 [Unicode Name] BOX DRAWINGS LIGHT VERTICAL [Description]

Output: vertical line


Input: [Name] boxV [Unicode] U+2551 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL [Description]

Output: vertical line


Input: [Name] boxvh [Unicode] U+253C [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL [Description]

Output: all four quadrants


Input: [Name] boxvH [Unicode] U+256A [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE [Description]

Output: all four quadrants


Input: [Name] boxVh [Unicode] U+256B [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE [Description]

Output: all four quadrants


Input: [Name] boxVH [Unicode] U+256C [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL [Description]

Output: all four quadrants


Input: [Name] boxvl [Unicode] U+2524 [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND LEFT [Description]

Output: upper and lower left quadrants


Input: [Name] boxvL [Unicode] U+2561 [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE [Description]

Output: upper and lower left quadrants


Input: [Name] boxVl [Unicode] U+2562 [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE [Description]

Output: upper and lower left quadrants


Input: [Name] boxVL [Unicode] U+2563 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND LEFT [Description]

Output: upper and lower left quadrants


Input: [Name] boxvr [Unicode] U+251C [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND RIGHT [Description]

Output: upper and lower right quadrants


Input: [Name] boxvR [Unicode] U+255E [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE [Description]

Output: upper and lower right quadrants


Input: [Name] boxVr [Unicode] U+255F [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE [Description]

Output: upper and lower right quadrants


Input: [Name] boxVR [Unicode] U+2560 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND RIGHT [Description]

Output: upper and lower right quadrants


Input: [EXI Option] alignment [Description] Alignment of event codes and content items [Default Value]

Output: bit-packed

EXI Options in Options Document


Input: [EXI Option] compression [Description] EXI compression is used to achieve better compactness [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] strict [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] fragment [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] preserve [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value]

Output: all false

EXI Options in Options Document


Input: [EXI Option] selfContained [Description] Enables self-contained elements [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] schemaId [Description] Identify the schema information, if any, used to encode the body [Default Value]

Output: no default value

EXI Options in Options Document


Input: [EXI Option] datatypeRepresentationMap [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value]

Output: no default value

EXI Options in Options Document


Input: [EXI Option] blockSize [Description] Specifies the block size used for EXI compression [Default Value]

Output: 1,000,000

EXI Options in Options Document


Input: [EXI Option] valueMaxLength [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value]

Output: unbounded

EXI Options in Options Document


Input: [EXI Option] valuePartitionCapacity [Description] Specifies the total capacity of value partitions in a string table [Default Value]

Output: unbounded

EXI Options in Options Document


Input: [EXI Option] [user defined meta-data] [Description] User defined meta-data may be added [Default Value]

Output: no default value

EXI Options in Options Document


Input: [Term] agency [Remarks]

Output: causal attribution -- who caused the event?


Input: [Term] blame [Remarks]

Output: blame and credit -- part of causal attribution


Input: [Term] controllability [Remarks]

Output: part of coping potential


Input: [Term] changeability [Remarks]

Output: part of coping potential


Input: [Term] power [Remarks]

Output: part of coping potential


Input: [Term] adaptability [Remarks]

Output: part of coping potential


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: [State] Hidden [Data type] An arbitrary string [Control type] n/a [Keyword]

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


Input: [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: [Component] FTCaseOption [Default initial value] case insensitive overwriteable [Scope] lexical [Consistency rules] Value must be case insensitive or case sensitive.

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTDiacriticsOption [Default initial value] diacritics insensitive overwriteable [Scope] lexical [Consistency rules] Value must be diacritics insensitive or diacritics sensitive.

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTStemOption [Default initial value] without stemming overwriteable [Scope] lexical [Consistency rules] Value must be without stemming or with stemming.

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTThesaurusOption [Default initial value] without thesaurus overwriteable [Scope] lexical [Consistency rules] Value must be part of the statically known thesauri.

Output: overwriteable by prolog (refer to default to augment)

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] Statically known thesauri [Default initial value] none augmentable [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list.

Output: cannot be augmented or overwritten by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTStopWordOption [Default initial value] without stopwords overwriteable [Scope] lexical [Consistency rules] Value must be part of the statically known stop word lists.

Output: overwriteable by prolog (refer to default to augment)

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] Statically known stop word lists [Default initial value] none augmentable [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list.

Output: cannot be augmented or overwritten by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTLanguageOption [Default initial value] no language is selected overwriteable [Scope] lexical [Consistency rules] Value must be castable to "xs:language" or "none".

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Component] FTWildCardOption [Default initial value] without wildcards no [Scope] lexical [Consistency rules] Value must be without wildcards or without wildcards.

Output: overwriteable by prolog

Static Context Components

Can be overwritten or augmented by a query?


Input: [Value] copy: [Description]

Output: A duplicate of the source object will be dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] move: [Description]

Output: The source object will be removed from its current location and dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] link: [Description]

Output: A reference or shortcut to the dragged object will be created in the target object.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] execute: [Description]

Output: A function supported by the drop target is executed, using the drag source as an input.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] popup: [Description]

Output: There is a popup menu or dialog that allows the user to choose one of the drag operations (copy, move, link, execute) and any other drag functionality, such as cancel.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] none (default): [Description]

Output: No operation can be performed; effectively cancels the drag operation if an attempt is made to drop on this object. Ignored if combined with any other token value. e.g. 'none copy' is equivalent to a 'copy' value.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Property] namespace name [EXI event types]

Output: AT

Mapping of the attribute information item properties to EXI event types


Input: [Property] local name [EXI event types]

Output: AT


Input: [Property] prefix [EXI event types]

Output: AT


Input: [Property] normalized value [EXI event types]

Output: The value of AT


Input: [Property] specified [EXI event types]

Output: True if the item maps to AT, otherwise false


Input: [Property] attribute type [EXI event types]

Output: Computed based on AT and DT


Input: [Property] references [EXI event types]

Output: Computed based on attribute type and value of AT


Input: [Property] owner element [EXI event types]

Output: Computed based on the last SE event encountered that did not get a matching EE event


Input: [Component] FTCaseOption [Default initial value] case insensitive overwriteable by prolog [Scope] lexical [Consistency rules] Value must be case insensitive or case sensitive.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTDiacriticsOption [Default initial value] diacritics insensitive overwriteable by prolog [Scope] lexical [Consistency rules] Value must be diacritics insensitive or diacritics sensitive.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTStemOption [Default initial value] without stemming overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without stemming or with stemming.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTThesaurusOption [Default initial value] without thesaurus overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known thesauri.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known thesauri [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list.

Output: augmentable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTStopWordOption [Default initial value] without stopwords overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known stop word lists.

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known stop word lists [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list.

Output: augmentable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTLanguageOption [Default initial value] no language is selected overwriteable by prolog [Scope] lexical [Consistency rules] Value must be castable to "xs:language" or "none".

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] FTWildCardOption [Default initial value] without wildcards overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without wildcards or without wildcards.

Output: no

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Language feature] a element that creates a hyperlink [Restrictions] Role must be either link, button, checkbox, menuitem, menuitemcheckbox, menuitemradio, tab, or treeitem [Default implied ARIA semantic]

Output: link role


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main [Default implied ARIA semantic]

Output: article role


Input: [Language feature] aside element [Restrictions] Role must be either complementary, note, or search [Default implied ARIA semantic]

Output: complementary role


Input: [Language feature] audio element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] button element [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group role


Input: [Language feature] dialog element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: dialog role


Input: [Language feature] embed element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] h1 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h2 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h3 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h4 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h5 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h6 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] header element [Restrictions] If specified, role must be banner [Default implied ARIA semantic]

Output: No role


Input: [Language feature] iframe element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] img element whose alt attribute's value is present and not empty [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] input element with a type attribute in the Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] Role must be either checkbox or menuitemcheckbox [Default implied ARIA semantic]

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Image Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] Role must be either radio or menuitemradio [Default implied ARIA semantic]

Output: radio role


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] Role must be either listitem, menuitemcheckbox, menuitemradio, option, tab, or treeitem [Default implied ARIA semantic]

Output: listitem role


Input: [Language feature] object element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] ol element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions [Default implied ARIA semantic]

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: region role


Input: [Language feature] ul element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] video element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] The body element [Restrictions] Role must be either document or application [Default implied ARIA semantic]

Output: document role


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string


Input: [Keyword] text [State] Text [Control type] Text field [Data type]

Output: Text with no line breaks


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks


Input: [Keyword] tel [State] Telephone [Control type] A text field [Data type]

Output: Text with no line breaks


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

Output: An absolute IRI


Input: [Keyword] email [State] E-mail [Control type] A text field [Data type]

Output: An e-mail address or list of e-mail addresses


Input: [Keyword] password [State] Password [Control type] Text field that obscures data entry [Data type]

Output: Text with no line breaks (sensitive information)


Input: [Keyword] datetime [State] Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC


Input: [Keyword] date [State] Date [Control type] A date control [Data type]

Output: A date (year, month, day) with no time zone


Input: [Keyword] month [State] Month [Control type] A month control [Data type]

Output: A date consisting of a year and a month with no time zone


Input: [Keyword] week [State] Week [Control type] A week control [Data type]

Output: A date consisting of a week-year number and a week number with no time zone


Input: [Keyword] time [State] Time [Control type] A time control [Data type]

Output: A time (hour, minute, seconds, fractional seconds) with no time zone


Input: [Keyword] datetime-local [State] Local Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone


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

Output: A numerical value


Input: [Keyword] range [State] Range [Control type] A slider control or similar [Data type]

Output: A numerical value, with the extra semantic that the exact value is not important


Input: [Keyword] color [State] Color [Control type] A color well [Data type]

Output: An sRGB color with 8-bit red, green, and blue components


Input: [Keyword] checkbox [State] Checkbox [Control type] A checkbox [Data type]

Output: A set of zero or more values from a predefined list


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

Output: An enumerated value


Input: [Keyword] file [State] File Upload [Control type] A label and a button [Data type]

Output: Zero or more files each with a MIME type and optionally a file name


Input: [Keyword] submit [State] Submit Button [Control type] A button [Data type]

Output: An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission


Input: [Keyword] image [State] Image Button [Control type] Either a clickable image, or a button [Data type]

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


Input: [Keyword] reset [State] Reset Button [Control type] A button [Data type]


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


Input: [Name] clip-path [Value] | [ || ] | none [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] as specified [Media] visual [Animatable] as specified for [CSS-SHAPES], otherwise no [Computed value] as specified, but with values made absolute [Initial]


Input: [Name] clip-rule [Value] nonzero | evenodd [Applies to] Applies to SVG graphics elements [Inh.] yes [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: nonzero


Input: [Name] mask-image [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified, but with URIs made absolute [Initial]


Input: [Name] mask-mode [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: auto


Input: [Name] mask-repeat [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] Consists of: two keywords, one per dimension [Initial]

Output: no-repeat


Input: [Name] mask-position [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of mask painting area minus size of mask layer image; see text background-position [CSS3BG] [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc [Computed value] Consisting of: two keywords representing the origin and two offsets from that origin, each given as an absolute length (if given a ), otherwise as a percentage. [Initial]

Output: center


Input: [Name] mask-clip [Value] [ | no-clip ]# [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: border-box


Input: [Name] mask-origin [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: border-box


Input: [Name] mask-size [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc (This means keyword values are not animatable.) [Computed value] as specified, but with lengths made absolute [Initial]

Output: auto


Input: [Name] mask-composite [Value] # [Applies to] All elements. In SVG, it applies to container elements without the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: add


Input: [Name] mask [Value] # [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] see individual properties [Media] visual [Animatable] see individual properties [Computed value] see individual properties [Initial]

Output: see individual properties


Input: [Name] mask-border-source [Value] none | [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] none or the image with its URI made absolute [Initial]


Input: [Name] mask-border-mode [Value] luminance | alpha [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: alpha


Input: [Name] mask-border-slice [Value] [ | ]{1,4} fill? [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of the mask border image [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: 0


Input: [Name] mask-border-width [Value] [ | | | auto ]{1,4} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] relative to width/height of the mask border image area [Media] visual [Animatable] no [Computed value] all s made absolute, otherwise as specified [Initial]

Output: auto


Input: [Name] mask-border-outset [Value] [ | ]{1,4} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] all s made absolute, otherwise as specified [Initial]

Output: 0


Input: [Name] mask-border-repeat [Value] [ stretch | repeat | round | space ]{1,2} [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: stretch


Input: [Name] mask-border [Value] <‘mask-border-source’> || <‘mask-border-slice’> [ / <‘mask-border-width’>? [ / <‘mask-border-outset’> ]? ]? || <‘mask-border-repeat’> || <‘mask-border-mode’> [Applies to] See individual properties [Inh.] no [%ages] n/a [Media] visual [Animatable] See individual properties [Computed value] See individual properties [Initial]

Output: See individual properties


Input: [Name] mask-type [Value] luminance | alpha [Applies to] mask elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] as specified [Initial]

Output: luminance


Input: [Name] clip [Value] | auto [Applies to] Absolutely positioned elements. In SVG, it applies to elements which establish a new viewport, elements and mask elements. [Inh.] no [%ages] n/a [Media] visual [Animatable] as rectangle [Computed value] as specified [Initial]

Output: auto


Input: [Property]

Output: Properties from Place[2]


Input: [Expected Type] PostalAddress [Description] Physical address of the item. [Property]

Output: address


Input: [Expected Type] aggregateRating [Description] The overall rating, based on a collection of reviews or ratings, of the item. [Property]

Output: aggregateRating


Input: [Expected Type] GeoCoordinates or GeoShape [Description] The geo coordinates of the place. [Property]

Output: geo


Input: [Expected Type] URL [Description] A URL to a map of the place. [Property]

Output: map


Input: [Expected Type] ImageObject or Photograph [Description] Photographs of this place [Property]

Output: photos


Input: [Expected Type] Review [Description] Review of the item [Property]

Output: reviews


Input: [Expected Type] Text [Description] The telephone number. [Property]

Output: telephone


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: [EXI Option] alignment [Description]

Output: Alignment of event codes and content items

Table 2-3. EXI Options


Input: [EXI Option] compression [Description]

Output: Indicates if EXI compression is to be used for better compactness

Table 2-3. EXI Options


Input: [EXI Option] fragment [Description]

Output: Indicates if the body is to be encoded as an EXI fragment instead of an EXI document

Table 2-3. EXI Options


Input: [EXI Option] preserve [Description]

Output: A set of options that controls whether comments, processing instructions, etc. are preserved

Table 2-3. EXI Options


Input: [EXI Option] schemaID [Description]

Output: Identifies the schema used during encoding

Table 2-3. EXI Options


Input: [EXI Option] codecMap [Description]

Output: Identifies any pluggable CODECs used to encode the body

Table 2-3. EXI Options


Input: [EXI Option] blockSize [Description]

Output: Specifies the block size used for EXI compression

Table 2-3. EXI Options


Input: [EXI Option] [user defined] [Description]

Output: User defined headers may be added

Table 2-3. EXI Options


Input: [Feature] The use of the role attribute with the value presentation [Indication]

Output: Probably a layout table


Input: [Feature] The use of the border attribute with the non-conforming value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of the non-conforming cellspacing and cellpadding attributes with the value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of caption, thead, or th elements [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the headers and scope attributes [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the border attribute with a value other than 0 [Indication]

Output: Probably a non-layout table


Input: [Feature] Explicit visible borders set using CSS [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the summary attribute [Indication]

Output: Not a good indicator (both layout and non-layout tables have historically been given this attribute)


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

EXI Options in Options Document


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

EXI Options in Options Document


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

EXI Options in Options Document


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

EXI Options in Options Document


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether the support for the preservation of comments, pis, etc. is each enabled

EXI Options in Options Document


Input: [EXI Option] selfContained [Default Value] false [Description]

Output: Enables self-contained elements

EXI Options in Options Document


Input: [EXI Option] schemaId [Default Value] no default value [Description]

Output: Identify the schema information, if any, used to encode the body

EXI Options in Options Document


Input: [EXI Option] datatypeRepresentationMap [Default Value] no default value [Description]

Output: Specify alternate datatype representations for typed values in the EXI body

EXI Options in Options Document


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

EXI Options in Options Document


Input: [EXI Option] valueMaxLength [Default Value] unbounded [Description]

Output: Specifies the maximum string length of value content items to be considered for addition to the string table.

EXI Options in Options Document


Input: [EXI Option] valuePartitionCapacity [Default Value] unbounded [Description]

Output: Specifies the total capacity of value partitions in a string table

EXI Options in Options Document


Input: [EXI Option] [user defined meta-data] [Default Value] no default value [Description]

Output: User defined meta-data may be added

EXI Options in Options Document


Input: [Requirement] Use valid (X)HTML [Rationale] Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Details]

Output: Using valid HTML means having an HTML code that follows one of the DTDs of the HTML specification. Your best choice is valid XHTML strict markup: XHTML means that the code will benefit from all the XML power, and strict ensures your site won't mix presentation markup with the structure.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use extensively valid CSS [Rationale] Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Details]

Output: Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use HTTP properly [Rationale] HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy! [Test tool] The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected. [Details]

Output: Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [Rationale] PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc. [Test tool] N/A [Details]

Output: Use PNG for raster images, and SVG for all others.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [Rationale] Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries. [Test tool] See Evaluation Tools for Web Content Accessibility. [Details]

Output: Details.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [Rationale] DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled. [Test tool] N/A [Details]

Output: Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!).

Buy standards compliant Web sites — W3C QA


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

Output: An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax.


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

Output: A short description of the entry.


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

Output: URL of an image of the entry.


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

Output: The name of the entry.


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

Output: URL of the entry.


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

Output: A secondary title of the entry.


Input: [Property] inLanguage [Expected Type] Language [Description]

Output: The language of the content. Please use one of the language codes from the IETF BCP 47 standard.


Input: [Property] dateCreated [Expected Type] Date [Description]

Output: The date on which the content was created (in ISO 8601 date format).


Input: [Property] dateModified [Expected Type] Date [Description]

Output: The date on which the content was most recently modified (in ISO 8601 date format).


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

Output: The keywords/tags used to describe this content.


Input: [Property] provider [Expected Type] Person or Organization [Description]

Output: Specifies the person or organization that distributed the content.


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

Output: A set of links that can help a user understand and navigate a website hierarchy.


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

Output: The identifier of the entry.


Input: [Property] isEntryOf [Expected Type] BiologicalDatabase [Description]

Output: Indicates the database to which the entry belongs.


Input: [Property] taxon [Expected Type] BiologicalDatabaseEntry or Text [Description]

Output: The taxonomy information of the entry.


Input: [Property] seeAlso [Expected Type] BiologicalDatabaseEntry or URL [Description]

Output: Reference to another resource.


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

Output: The identifier of the reference, such as PMID, DOI, and PMCID. For example: .


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] 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 [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Search field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text field that obscures data entry

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A date control

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A time control

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field or spinner control

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A color well

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A checkbox

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A radio button

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: No conflict

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict

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


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

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

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


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

Output: No conflict

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


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

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

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


Input: [Name] dest [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A Valid URI [Description]

Output: An ECMAScript expression which returns a string that is the target of the outbound telephone call. A platform MUST support a telephone URI, as described in [RFC3966] and MAY support other URI schemes such as "sip:" or "h323:" or a SIP URI as described in [RFC3261].

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive the identifier of the Connection on which the outgoing call is attempted.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] aai [Required] false [Type] ECMAScript Expression [Default Value] none [Description]

Output: An ECMAScript expression which returns a string of application-to-application information to be passed to the destination endpoint when establishing the connection. Note: Even if an implementation platform accepts the aai data, certain protocols and network elements may prevent the transmission to the target endpoint. If the platform does not support the transmission of aai data it must raise a connection.progressing event and indicate that the use of aai is not supported.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] callerid [Required] false [Type] ECMAScript Expression [Default Value] none [Description]

Output: An ECMAScript expression which returns a string defining the caller identity to be used when making the outbound connection. The format of this information is protocol and platform specific but might consist of a telephone URI, as described in [RFC3966] or a SIP URI as described in [RFC3261]. Note: An implementation platform is not required to use the specified data and certain protocols and network elements may prevent its use. If the platform does not support the specification of callerid it must raise a connection.progressing event and indicate that the use of callerid is not supported.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform when establishing the outbound connection. This information may consist of protocol-specific parameters, protocol selection guidelines, or routing hints. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] timeout [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

Output: The character string returned is interpreted as a time interval. This interval begins when createcall is executed. The createcall must fail if not completed by the end of this interval. A completion is defined as the call getting to a CONNECTED state as signaled by a connection.connected event. A failed createcall must return the connection.failed event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] joinid [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] (valid connection, conference, or dialog ID) [Description]

Output: An ECMAScript expression that identifies a connection, conference, or dialog ID that the new call must be joined to. This is equivalent, from the perspective of the CCXML application, to performing a immediately following the . However, platforms may use knowledge about the connection/conference/dialog to which the new call will be connected to optimize the call creation process. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] joindirection [Required] false [Attribute Constraints] This attribute is only valid in conjunction with the joinid attribute, otherwise ignored. [Type] ECMAScript Expression [Default Value] both [Valid Values] both calltransmit callreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the newly created connection, and the existing connection/conference/dialog referenced by joinid: both Specifes a full duplex connection where the media flows in both directions. calltransmit The new connection transmits media to the referenced connection/conference/dialog but does not receive any media streams. callreceive The new connection receives media from the referenced connection/conference/dialog but does not transmit any media streams.

Voice Browser Call Control: CCXML Version 1.0


Input: [HTML Techniques] Short text alternatives for img elements ("alt-text") [HTML Tests]

Output: All img elements have an alt attribute. Alt text for all IMG elements is not placeholder text or user has confirmed that the Alt text is appropriate.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Short text alternatives for object elements (future) [HTML Tests]

Output: object must have a text equivalent.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Image and text links side by side [HTML Tests]

Output: Alt text for all img elements used as source anchors is different from the link text.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Text links for server side image maps. (deprecated) [HTML Tests]

Output: Server-side image maps are not used except when image map regions cannot be defined using an available geometric shape.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Text alternatives for client-side image maps [HTML Tests]

Output: All area elements have an alt attribute. Alt text for all area elements contains all non decorative text in the image area.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Text and non-text alternatives for object [HTML Tests]

Output: object must have a text equivalent. object user interface must be accessible.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] Text alternatives for submit buttons [HTML Tests]

Output: All input elements with a type attribute value of "image" have an alt attribute. Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image. Alt text for all input elements with a type attribute value of "image" does not use the words "submit" or "button" (English). Alt text for all input elements with a type attribute value of "image" contains all non decorative text in the image.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [HTML Techniques] scripts and applets (out of scope? depends on defn of non-text content) [HTML Tests]

Output: script must have a noscript section. ?? (depends on baseline discussion) applet must have valid alt attribute. Text equivalents for applet must be updated if applet changes. Text equivalents for object should be updated if object changes.?? User interface for script must be accessible. applet user interface must be accessible.

Playing with General Techniques for G1.1 L1 #1 - text alternatives forfunctional non-text content


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] text [State] Text [Control type] Text field [Data type]

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] tel [State] Telephone [Control type] A text field [Data type]

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: An absolute IRI

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] email [State] E-mail [Control type] A text field [Data type]

Output: An e-mail address or list of e-mail addresses

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] password [State] Password [Control type] Text field that obscures data entry [Data type]

Output: Text with no line breaks (sensitive information)

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] datetime [State] Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] date [State] Date [Control type] A date control [Data type]

Output: A date (year, month, day) with no time zone

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] month [State] Month [Control type] A month control [Data type]

Output: A date consisting of a year and a month with no time zone

4.10.7 The input element — HTML5: Edition for Web Authors