Input: [Action] End of Life [From State] UP [Sub-State] -o- [Comment] Destroyed [To State]

Output: Exit

WS Management Architecture blueprint: concepts


Input: [Action] End of Life [From State] DOWN [Sub-State] -o- [Comment] Destroyed [To State]

Output: Exit

WS Management Architecture blueprint: concepts


Input: [Action] Activate [From State] DOWN [Sub-State] -any- [Comment] Becomes available. [To State]

Output: UP

WS Management Architecture blueprint: concepts


Input: [Action] Passivate [From State] UP [Sub-State] -any- [Comment] Becomes not available. [To State]

Output: DOWN

WS Management Architecture blueprint: concepts


Input: [Prefix] rdf: [Description] The RDF Vocabulary [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] rdfs: [Description] The RDF Schema vocabulary [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] xsd: [Description] XML Schema [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] foaf: [Description] Friend Of A Friend [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] skos: [Description] Simple Knowledge Organization System [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] dc: [Description] Dublin Core Metadata Element Set, Version 1.1 [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] dcterms: [Description] Dublin Core Metadata Terms [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [AtomPub] any atompub server exposes a "service document" that describes what the server is exposing. each service document lists a set of "workspaces", which are just a grouping construct for "collections". workspaces have no interaction semantics in atompub, there is no protocol for creating or deleting them; they just exist. each workspace lists a set of "collections", which is by far the most central construct in atompub. a collection can be listed in more than one workspace. [Model Aspect]

Output: service basics

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


Input: [AtomPub] a collection has a URI where you can start interacting with the collection, at the most basic level you can GET a list of members, and very likely this is somehow paginated. through its listing in a service document, the collection exposes some interaction information, such as which kind of mediatypes it will accept, and how members of the collection might use categories to be classified. [Model Aspect]

Output: collection basics

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


Input: [AtomPub] any kind of resource can be listed in a collection, and everything that is in a collection is represented by an entry. entries follow the standardized metadata model defined by atom, but atompub distinguishes two kinds of entries. if a client POSTs an "entry resource" (an atom entry following atom's metadata model), the server pretty much takes this entry resource and starts listing it in the collection as a member. if a client has POSTed a "media resource" (pretty much anything that's not an entry by itself, often something like an image media type), which has to be in one of the accepted media types of the collection, the server accepts this media resource and creates a "media link entry", which will then represent this media resource when you list the collection contents. servers might try to be smart about populating metadata fields in the entry and for example look at exif data to populate certain fields. the interesting aspect of this setup is that you POST one thing, and create two resources, and big media files might for example get added to a CDN and get a CDN URI, whereas the entry gets some URI under the control of the atompub server. [Model Aspect]

Output: creating collection members

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


Input: [AtomPub] a collection is a representation of members, and thus contains a list of entries representing each individual member. according to the atom model, each entry MUST have an , which is a URI but has no interaction semantics (specifically, best practice suggests that minting URIs that are not actionable might be a good idea). entries may have embedded content, or may link to the content they are representing. identity is established by the entry , and this is particularly important in scenarios where collections may be aggregated and filtered and repurposed: entry identity must always be visible in the , and thus identity can be tracked across paths where entries may get repurposed in various collections. [Model Aspect]

Output: member identity

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


Input: [AtomPub] members are listed when GETting a collection, and their identity and metadata about them is exposed through regular atom mechanisms. if members are editable, an "edit" link in the entry will allow clients to update the member entry, by using this link to PUT or DELETE the entry resource. if the entry is a media link entry, then there might be a "edit-media" link in the entry, which will allow clients to update the media resource, by using this link to PUT or DELETE the media resource. this model allows clients to both interact with a media resource's metadata (the "media link entry"), and the media resource itself. [Model Aspect]

Output: interacting with members

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


Input: [AtomPub] like workspaces, collections just exist, and atompub does not define how to create or delete them (i am currently working on a small addition to the spec that addresses that). also, collections have no structure, they have a URI and accept entries. this means there is no hierarchy to collections, it's a flat space. [Model Aspect]

Output: interacting with collections

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


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] onreadsuccess [event type] ReadReportEvent [short description] handles successful read reports [event name]

Output: readsuccess


Input: [event handler] onreaderror [event type] ReadReportEvent [short description] handles failure read reports [event name]

Output: readerror


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: [postal] name [Structure] personname [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data

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


Input: [postal] street [Structure] unstructured [Short display name] Street Address [Category]

Output: Physical Contact Information

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


Input: [postal] city [Structure] unstructured [Short display name] City [Category]

Output: Demographic and Socioeconomic Data

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


Input: [postal] stateprov [Structure] unstructured [Short display name] State or Province [Category]

Output: Demographic and Socioeconomic Data

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


Input: [postal] postalcode [Structure] unstructured [Short display name] Postal Code [Category]

Output: Demographic and Socioeconomic Data

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


Input: [postal] country [Structure] unstructured [Short display name] Country Name [Category]

Output: Demographic and Socioeconomic Data

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


Input: [postal] organization [Structure] unstructured [Short display name] Organization Name [Category]

Output: Demographic and Socioeconomic Data

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


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

Output: onreceived


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

Output: onsent


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

Output: ondeliverysuccess


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

Output: ondeliveryerror


Input: [event name] readsuccess [event type] ReadReportEvent [short description] handles successful read reports [event handler]

Output: onreadsuccess


Input: [event name] readerror [event type] ReadReportEvent [short description] handles failure read reports [event handler]

Output: onreaderror


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

Output: onserviceadded


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

Output: onserviceremoved


Input: [Property] additionalType (added) [Expected Type] URL [Description]

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

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


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

Output: A short description of the entry.

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


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

Output: URL of an image of the entry.

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


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

Output: The name of the entry.

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


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

Output: URL of the entry.

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


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

Output: A secondary title of the entry.

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


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.

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


Input: [Property] relatedLink (or “seeAlso”) [Expected Type] URL [Description]

Output: A link related to this web page, for example to other related web pages.

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


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

Output: The identifier of the entry.

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


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

Output: Indicates the database to which the entry belongs.

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


Input: [Property] taxonID (or “taxon”) [Expected Type] Text [Description]

Output: The taxonomy identifier of the entry. Please use the NCBI Taxonomy ID.

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


Input: [Property] taxon (or “taxonID”) [Expected Type] BiologicalDatabaseEntry (or Text) [Description]

Output: The taxonomy information of the entry.

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


Input: [Property] seeAlso (or “relatedLink”) [Expected Type] BiologicalDatabaseEntry (or URL) [Description]

Output: Reference to another resource.

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


Input: [Action] Start of Life [From State] Enter [To State] UP [Sub-State] IDLE [Comment]

Output: Instantiated and available

WS Management Architecture blueprint: concepts


Input: [Action] Start of Life [From State] Enter [To State] DOWN [Sub-State] STOPPED [Comment]

Output: Instantiated but not available

WS Management Architecture blueprint: concepts


Input: [Action] End of Life [From State] UP [To State] Exit [Sub-State] -o- [Comment]

Output: Destroyed

WS Management Architecture blueprint: concepts


Input: [Action] End of Life [From State] DOWN [To State] Exit [Sub-State] -o- [Comment]

Output: Destroyed

WS Management Architecture blueprint: concepts


Input: [Action] Activate [From State] DOWN [To State] UP [Sub-State] -any- [Comment]

Output: Becomes available.

WS Management Architecture blueprint: concepts


Input: [Action] Passivate [From State] UP [To State] DOWN [Sub-State] -any- [Comment]

Output: Becomes not available.

WS Management Architecture blueprint: concepts


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

Output: HTML to Text converter


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

Output: Link Checker


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

Output: Link Checker


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

Output: HTML Validator


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

Output: W3C Spellchecker


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

Output: CSS Validator


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

Output: CVS Log


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

Output: Headers


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

Output: the pubrules checker


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

Output: the pubrules checker


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

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


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

Output: List of bad links in the page


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

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


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

Output: List of HTML markup errors.


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

Output: List of spelling errors.


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

Output: List of style CSS errors.


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

Output: Log of changes to the document


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

Output: HTTP headers sent by the server


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

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


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

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


Input: [IDL type] boolean [ECMAScript type]

Output: Boolean

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] float [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] long [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] unsigned short [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] unsigned long [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] DOMString [ECMAScript type]

Output: String

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [WRL keyword] wrl#variant [RDF usage]

Output: Used as predicate to indicate the WRL variant applied.

Table 5.1: WRL vocabulary extending RDFS for WRL triple syntax


Input: [WRL keyword] wrl#ontology [RDF usage]

Output: Used to define a WRL ontology.


Input: [WRL keyword] wrl#hasConcept [RDF usage]

Output: Used to type a WRL concept and to bind it to an ontology.


Input: [WRL keyword] wrl#attribute [RDF usage]

Output: Used to define a WRL attribute


Input: [WRL keyword] wrl#ofType [RDF usage]

Output: Used as predicate to define constraining attributes and parameters.


Input: [WRL keyword] wrl#hasAttribute [RDF usage]

Output: Used as predicate to bind an attribute to a concept.


Input: [WRL keyword] wrl#transitiveAttribute [RDF usage]

Output: Used to indicate the transitivity of an attribute.


Input: [WRL keyword] wrl#symmetricAttribute [RDF usage]

Output: Used to indicate the symmetry of an attribute.


Input: [WRL keyword] wrl#reflexiveAttribute [RDF usage]

Output: Used to indicate the reflexivity of an attribute.


Input: [WRL keyword] wrl#inverseOf [RDF usage]

Output: Used to indicate the inverse relationship of two attributes.


Input: [WRL keyword] wrl#minCardinality [RDF usage]

Output: Used as predicate to defined the minimal cardinality of an attribute.


Input: [WRL keyword] wrl#maxCardinality [RDF usage]

Output: Used as predicate to defined the maximal cardinality of an attribute.


Input: [WRL keyword] wrl#hasInstance [RDF usage]

Output: Used to type an instance and to bind it to a concept.


Input: [WRL keyword] wrl#hasRelation [RDF usage]

Output: Used to type a relation and to bind it to an ontology.


Input: [WRL keyword] wrl#arity [RDF usage]

Output: Used to define the arity of a WRL relation.


Input: [WRL keyword] wrl#param [RDF usage]

Output: Used to type parameters of WRL relations.


Input: [WRL keyword] wrl#subRelationOf [RDF usage]

Output: Used as predicate to define sub-relations.


Input: [WRL keyword] wrl#hasRelationInstance [RDF usage]

Output: Used to type a relation instance and to bind it to an ontology.


Input: [WRL keyword] wrl#hasAxiom [RDF usage]

Output: Used to type an axiom and to bind it to an ontology.


Input: [WRL keyword] wrl#importsOntology [RDF usage]

Output: Used to define the import of an external ontology.


Input: [WRL keyword] wrl#nfp [RDF usage]

Output: Used to type non-functional properties.


Input: [From State] Enter [To State] UP [Sub-State] IDLE [Comment] Instantiated and available [Action]

Output: Start of Life

WS Management Architecture blueprint: concepts


Input: [From State] Enter [To State] DOWN [Sub-State] STOPPED [Comment] Instantiated but not available [Action]

Output: Start of Life

WS Management Architecture blueprint: concepts


Input: [From State] UP [To State] Exit [Sub-State] -o- [Comment] Destroyed [Action]

Output: End of Life

WS Management Architecture blueprint: concepts


Input: [From State] DOWN [To State] Exit [Sub-State] -o- [Comment] Destroyed [Action]

Output: End of Life

WS Management Architecture blueprint: concepts


Input: [From State] DOWN [To State] UP [Sub-State] -any- [Comment] Becomes available. [Action]

Output: Activate

WS Management Architecture blueprint: concepts


Input: [From State] UP [To State] DOWN [Sub-State] -any- [Comment] Becomes not available. [Action]

Output: Passivate

WS Management Architecture blueprint: concepts


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

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Represent [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol. [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


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

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [Property] box-decoration-break [Values] slice | clone [Initial] slice [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: all elements


Input: [Property] break-after [Values] auto | avoid | always | any | avoid-page | page | left | right | recto | verso | avoid-column | column | avoid-region | region [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: block-level elements, table row groups, table rows (but see prose)


Input: [Property] break-before [Values] auto | avoid | always | any | avoid-page | page | left | right | recto | verso | avoid-column | column | avoid-region | region [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: block-level elements, table row groups, table rows (but see prose)


Input: [Property] break-inside [Values] auto | avoid | avoid-page | avoid-column | avoid-region [Initial] auto [Inh.] no [Percentages] N/A [Media] visual [Applies to]

Output: elements in the normal flow that that establish formatting contexts, or are block containers, table row groups, or table rows


Input: [Property] orphans [Initial] 2 [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: block containers


Input: [Property] widows [Initial] 2 [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: block containers


Input: [Margin box] top-left-corner ['vertical-align'] middle ['text-align']

Output: right

Table 2. Initial values for Margin Boxes


Input: [Margin box] top-left ['vertical-align'] middle ['text-align']

Output: left


Input: [Margin box] top-center ['vertical-align'] middle ['text-align']

Output: center


Input: [Margin box] top-right ['vertical-align'] middle ['text-align']

Output: right


Input: [Margin box] top-right-corner ['vertical-align'] middle ['text-align']

Output: left


Input: [Margin box] left-top ['vertical-align'] top ['text-align']

Output: center


Input: [Margin box] left-middle ['vertical-align'] middle ['text-align']

Output: center


Input: [Margin box] left-bottom ['vertical-align'] bottom ['text-align']

Output: center


Input: [Margin box] right-top ['vertical-align'] top ['text-align']

Output: center


Input: [Margin box] right-middle ['vertical-align'] middle ['text-align']

Output: center


Input: [Margin box] right-bottom ['vertical-align'] bottom ['text-align']

Output: center


Input: [Margin box] bottom-left-corner ['vertical-align'] middle ['text-align']

Output: right


Input: [Margin box] bottom-left ['vertical-align'] middle ['text-align']

Output: left


Input: [Margin box] bottom-center ['vertical-align'] middle ['text-align']

Output: center


Input: [Margin box] bottom-right ['vertical-align'] middle ['text-align']

Output: right


Input: [Margin box] bottom-right-corner ['vertical-align'] middle ['text-align']

Output: left


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

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

Text input (including date/time and password fields)

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


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

Output: Checkbox

Text input (including date/time and password fields)

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


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

Output: Radio button group

Text input (including date/time and password fields)

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


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

Output: Combo box

Text input (including date/time and password fields)

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


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

Output: List box

Text input (including date/time and password fields)

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


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

Output: Button

Text input (including date/time and password fields)

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


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

Output: User's Name

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


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

Output: User's Birth Date

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


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

Output: User's Identity Certificate

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


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

Output: User's Gender (male or female)

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


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

Output: User's Employer

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


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

Output: Department or division of organization where user is employed

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


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

Output: User's Job Title

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


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

Output: User's Home Contact Information

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


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

Output: User's Business Contact Information

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


Input: [attribute] archive [function]

Output: For example, when defining an applet you could reference a space-separated list of jar files.


Input: [attribute] content-length [function]

Output: This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed.


Input: [attribute] data [function]

Output: This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed.


Input: [attribute] declare [function]

Output: This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed.


Input: [attribute] standby [function]

Output: The author can provide a text string that should be displayed while the object data is being downloaded and processed.


Input: [attribute] type [function]

Output: Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data.


Input: [attribute] xml:base [function]

Output: Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose.


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 [HTML5 examples] tbd [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 [HTML5 examples] tbd [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 [HTML5 examples] tbd [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 [HTML5 examples] tbd [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 [HTML5 examples] tbd [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 [HTML5 examples] tbd [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Elements Within Text [Local Usage] No Yes [Global, rule-based selection] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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 [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Disambiguation [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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" localeFilterList="*" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd [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] None [Overriding] Not applicable [HTML5 examples] tbd [Global adding of information]

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality PrÃ©cis [Local Usage] Yes [Global, rule-based selection] Yes Yes [Default Values] None [Inheritance] Textual content of element, including child elements, but excluding attributes [Overriding] Yes [HTML5 examples] tbd [Global adding of information]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: URI of requested resource

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


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

Output: Request timestamp

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


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

Output: Client's IP address or hostname

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


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

Output: HTTP request method

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


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

Output: Data bytes in response

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


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

Output: Response status code

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


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

Output: User's Name


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

Output: User's Birth Date


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

Output: User's Identity Certificate


Input: [user.] gender [Category] Demographic and Socioeconomic Data [Type] gender [Short display name]

Output: User's Gender


Input: [user.] employer [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Employer


Input: [user.] department [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: Department or division of organization where user is employed


Input: [user.] jobtitle [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Job Title


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

Output: User's Home Contact Information


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

Output: User's Business Contact Information


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 note, complementary, or search [Default implied ARIA semantic]

Output: note role


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

Output: No 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] 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] 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] 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 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 image [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 region, document, application, contentinfo, main, search, alert, dialog, alertdialog, status, or log [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: [Control Type] Text input (including date/time and password fields) [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control.

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


Input: [Control Type] Checkbox [LiveCycle Placement Rules]

Output: Default placement for the label is to the right of the check box.

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


Input: [Control Type] Radio button group [LiveCycle Placement Rules]

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

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


Input: [Control Type] Combo box [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control..

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


Input: [Control Type] List box [LiveCycle Placement Rules]

Output: Default placement for the label is above the list box.

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


Input: [Control Type] Button [LiveCycle Placement Rules]

Output: LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text.

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


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

Output: A space-separated list of references to document-unique identifiers


Input: [Attribute Type] NAME [Definition]

Output: A name with the same character constraints as ID above


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of only name tokens as defined in XML 1.0 [ XML ].


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [WCAG 2.0 checkpoint] 1.2 Synchronize text equivalents with multimedia presentations. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.3 Synchronize a description of the essential visual information in multimedia presentations. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.4 Use markup or a data model to provide the logical structure of content. [Manual checks]

Output: Generate outline and determine if structure is good

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.5 Separate content and structure from presentation. [Auto checks] HTML Validator [Manual checks]

Output: Increase font size in the browser settings. does all the text increase in size?

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.1 Provide more than one path or method to find content. [Auto checks] N/A [Examples and Techniques] Refer to Core techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.2 Provide consistent responses to user actions. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.3 Give users control of mechanisms that cause extreme changes in context. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.4 Give users control over how long they can spend reading or interacting with content. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.5 Use device-independent event handlers. [Auto checks] N/A [Examples and Techniques] Refer to client-side scripting techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.1 Use consistent presentation. [Manual checks]

Output: Check for use of external style sheets. Check that classes are used for function rather than presentation (?)

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.2 Emphasize structure through presentation, positioning, and labels. [Manual checks]

Output: Print on paper using only black and white ink. Is all the info present? i.e., is info presented not in color alone?

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.3 Write clearly and simply. [Auto checks] N/A [Examples and Techniques] Refer to Core techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.5 Summarize complex information. [Auto checks] N/A [Examples and Techniques] Refer to Core techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.6 Define key terms, abbreviations, acronyms, and specialized language. [Auto checks] N/A [Examples and Techniques] Refer to Core techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.7 Divide information into smaller, more manageable units. [Auto checks] N/A [Examples and Techniques] Refer to Core techniques [Manual checks]

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 4.1 Choose languages, API's, and protocols that support the use of these guidelines. [Manual checks]

Output: Use CSS1 or CSS2 with HTML 4.01 or XHTML 1.1

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 4.2 Use languages, API's, and protocols according to specification. [Auto checks] W3C CSS Validator W3C HTML Validator [Manual checks]

Output: check that link element in head of page references an external style sheet. ensure that no style attributes exist on elements, ensure that font element is not used. etc.

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 4.3 Design assistive-technology compatible user interfaces. [Manual checks]

Output: Does your site work with a variety of assistive technologies, such as screen readers, magnifiers, on screen keyboards, etc.?

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 4.4 Design content so that when presentation effects are turned off or not supported the content is still usable. [Manual checks]

Output: Use a browser that does not support or that will turn off CSS to determine if content is still usable.

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.1 Provide a text equivalent for all non-text content. [Examples and Techniques]

Output: Generated content

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.2 Synchronize text equivalents with multimedia presentations. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.3 Synchronize a description of the essential visual information in multimedia presentations. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.1 Provide more than one path or method to find content. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.2 Provide consistent responses to user actions. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.3 Give users control of mechanisms that cause extreme changes in context. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.4 Give users control over how long they can spend reading or interacting with content. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.5 Use device-independent event handlers. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.3 Write clearly and simply. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.5 Summarize complex information. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.6 Define key terms, abbreviations, acronyms, and specialized language. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.7 Divide information into smaller, more manageable units. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


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

Output: Physical Contact Information, Demographic and Socioeconomic Data

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


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

Output: Demographic and Socioeconomic Data

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


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

Output: Unique Identifiers

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


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

Output: Demographic and Socioeconomic Data

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


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

Output: Demographic and Socioeconomic Data

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


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

Output: Demographic and Socioeconomic Data

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


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

Output: Demographic and Socioeconomic Data

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


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

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

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


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

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

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


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

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] implementation-defined overwriteable by prolog [Scope] lexical [Consistency rules] Value must be castable to "xs:language".

Output: overwriteable

Static Context Components

Can be overwritten or augmented by implementation?


Input: [Component] Statically known languages [Default initial value] none cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each string uniquely identifies a language.

Output: augmentable

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: [Code] NoMatch [Possible Major Codes] Success, Receiver [Description]

Output: No match was found for the search prototype provided.


Input: [Code] TooManyResponses [Possible Major Codes] Success, Receiver [Description]

Output: The request resulted in the number of responses exceeding the ResponseLimit value specified in the request


Input: [Code] Incomplete [Possible Major Codes] Success [Description]

Output: Only part of the information requested could be provided.


Input: [Code] Failure [Possible Major Codes] Sender, Receiver [Description]

Output: The operation failed for unspecified reasons.


Input: [Code] Refused [Possible Major Codes] Sender, Receiver [Description]

Output: The operation was refused.


Input: [Code] NoAuthentication [Possible Major Codes] Sender [Description]

Output: The operation was refused because the necessary authentication information was incorrect or missing.


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Preserve Space [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] default [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality PrÃ©cis [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] Textual content of element, including child elements, but excluding attributes [Overriding] Yes [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Component] Context item [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Context position [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Context size [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Variable values [Scope]

Output: dynamic; for-expressions and quantified expressions can bind new variables

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Current date and time [Scope]

Output: global; must be initialized by implementation

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Implicit timezone [Scope]

Output: global; must be initialized by implementation

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Available documents [Scope]

Output: global; must be initialized by implementation

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Available collections [Scope]

Output: global; must be initialized by implementation

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [Component] Default collection [Scope]

Output: global; overwriteable by implementation

XML Path Language (XPath)
 2.0 -- Review Version

Dynamic Context Components


Input: [0] Value [1] Description [2] Example [3] Scope [4]

Output: Notes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [1] The content of the target mistranslates the content of the source. [2] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscÃ¬ a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [3] T [4]

Output: Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4]

Output: This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4]

Output: omission takes precedence over untranslated . Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [1] The localization contains content that does not apply to the locale for which it was prepared. [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4]

Output: Legally inappropriate material should be classified as legal .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4]

Output: Some tools may correct for differences in units of measurement to reduce false positives.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [1] There is an issue related to the internationalization of content. [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4]

Output: There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4]

Output: What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4]

Output: This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized . In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] other [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4]

Output: This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category.

Internationalization Tag Set (ITS) Version 2.0


Input: [Component] FTCaseOption [Default initial value] case insensitive overwriteable overwriteable by prolog [Scope] lexical [Consistency rules]

Output: Value must be case insensitive, case sensitive, lowercase, or uppercase.

Static Context Components


Input: [Component] FTDiacriticsOption [Default initial value] diacritics insensitive overwriteable overwriteable by prolog [Scope] lexical [Consistency rules]

Output: Value must be diacritics insensitive or diacritics sensitive.

Static Context Components


Input: [Component] FTStemOption [Default initial value] without stemming overwriteable overwriteable by prolog [Scope] lexical [Consistency rules]

Output: Value must be without stemming or with stemming.

Static Context Components


Input: [Component] FTThesaurusOption [Default initial value] without thesaurus overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules]

Output: Value must be part of the statically known thesauri.

Static Context Components


Input: [Component] Statically known thesauri [Default initial value] none augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules]

Output: Each URI uniquely identifies a thesaurus list.

Static Context Components


Input: [Component] FTStopWordOption [Default initial value] without stopwords overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules]

Output: Value must be part of the statically known stop word lists.

Static Context Components


Input: [Component] Statically known stop word lists [Default initial value] none augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules]

Output: Each URI uniquely identifies a stop word list.

Static Context Components


Input: [Component] FTLanguageOption [Default initial value] implementation-defined overwriteable overwriteable by prolog [Scope] lexical [Consistency rules]

Output: Value must be castable to "xs:language".

Static Context Components


Input: [Component] Statically known languages [Default initial value] none augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules]

Output: Each string uniquely identifies a language.

Static Context Components


Input: [Component] FTWildCardOption [Default initial value] without wildcards no overwriteable by prolog [Scope] lexical [Consistency rules]

Output: Value must be without wildcards or without wildcards.

Static Context Components


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] localeFilterType="all" localeFilterList="*" [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Preserve Space [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] default [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality Issue [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality PrÃ©cis [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


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] clip-path [Value] | [ || ] | none [Initial] 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]

Output: as specified, but with values made absolute


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

Output: as specified


Input: [Name] mask-image [Value] # [Initial] 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]

Output: as specified, but with URIs made absolute


Input: [Name] mask-mode [Value] # [Initial] auto [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]

Output: as specified


Input: [Name] mask-repeat [Value] # [Initial] no-repeat [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]

Output: Consists of: two keywords, one per dimension


Input: [Name] mask-position [Value] # [Initial] center [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]

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


Input: [Name] mask-clip [Value] [ | no-clip ]# [Initial] border-box [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]

Output: as specified


Input: [Name] mask-origin [Value] # [Initial] border-box [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]

Output: as specified


Input: [Name] mask-size [Value] # [Initial] auto [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]

Output: as specified, but with lengths made absolute


Input: [Name] mask-composite [Value] # [Initial] add [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]

Output: as specified


Input: [Name] mask [Value] # [Initial] see individual properties [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]

Output: see individual properties


Input: [Name] mask-border-source [Value] none | [Initial] 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]

Output: none or the image with its URI made absolute


Input: [Name] mask-border-mode [Value] luminance | alpha [Initial] 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]

Output: as specified


Input: [Name] mask-border-slice [Value] [ | ]{1,4} fill? [Initial] 0 [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]

Output: as specified


Input: [Name] mask-border-width [Value] [ | | | auto ]{1,4} [Initial] auto [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]

Output: all s made absolute, otherwise as specified


Input: [Name] mask-border-outset [Value] [ | ]{1,4} [Initial] 0 [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]

Output: all s made absolute, otherwise as specified


Input: [Name] mask-border-repeat [Value] [ stretch | repeat | round | space ]{1,2} [Initial] stretch [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]

Output: as specified


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

Output: See individual properties


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

Output: as specified


Input: [Name] clip [Value] | auto [Initial] 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]

Output: as specified


Input: [user] name [Category] Physical Contact Information, Demographic and Socioeconomic Data [Short display name] User's Name [Structure]

Output: personname

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


Input: [user] bdate [Category] Demographic and Socioeconomic Data [Short display name] User's Birth Date [Structure]

Output: date

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


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

Output: certificate

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


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

Output: unstructured

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


Input: [user] employer [Category] Demographic and Socioeconomic Data [Short display name] User's Employer [Structure]

Output: unstructured

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


Input: [user] department [Category] Demographic and Socioeconomic Data [Short display name] Department or division of organization where user is employed [Structure]

Output: unstructured

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


Input: [user] jobtitle [Category] Demographic and Socioeconomic Data [Short display name] User's Job Title [Structure]

Output: unstructured

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


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

Output: contact

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


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

Output: contact

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


Input: [API Feature] Faster than real-time processing [MediaStream] No [Web Audio]

Output: Yes


Input: [API Feature] Native Effects [MediaStream] No [Web Audio]

Output: Yes


Input: [API Feature] Audio primarily manipulated through tags [MediaStream] Yes [Web Audio]

Output: No


Input: [API Feature] Audio primarily manipulated through an Audio-Context [MediaStream] No [Web Audio]

Output: Yes


Input: [API Feature] Can load sounds faster than playback [MediaStream] No [Web Audio]

Output: Yes


Input: [API Feature] Streams/nodes can contain video & audio data [MediaStream] Yes [Web Audio]

Output: No


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


Input: [Definition] Processed character data [Attribute Type]

Output: PCDATA


Input: [Property] bottom [Values] auto | | [Initial] auto [Applies to] positioned elements [Inh.] no [Percentages] , [Media]

Output: refer to height of containing block


Input: [Property] clip [Values] auto | [Initial] auto [Applies to] absolutely positioned elements [Inh.] no [Media]


Input: [Property] left [Values] auto | | [Initial] auto [Applies to] positioned elements [Inh.] no [Percentages] , [Media]

Output: refer to height of containing block


Input: [Property] position [Values] static | relative | absolute | center | page | fixed [Initial] static [Applies to] all elements except table-column-group and table-column [Inh.] no [Percentages] no [Media]


Input: [Property] right [Values] auto | | [Initial] auto [Applies to] positioned elements [Inh.] no [Percentages] , [Media]

Output: refer to height of containing block


Input: [Property] top [Values] auto | | [Initial] auto [Applies to] positioned elements [Inh.] no [Percentages] , [Media]

Output: refer to height of containing block


Input: [Property] z-index [Values] auto | [Initial] auto [Applies to] positioned elements [Inh.] no [Media]


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

Output: implementation-defined

Static Context Components


Input: [Component] Statically known languages augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each string uniquely identifies a language. [Default initial value]

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: [Possible Major Codes] Success, Receiver [Description] No match was found for the search prototype provided. [Code]

Output: NoMatch


Input: [Possible Major Codes] Success, Receiver [Description] The request resulted in the number of responses exceeding the ResponseLimit value specified in the request [Code]

Output: TooManyResponses


Input: [Possible Major Codes] Success [Description] Only part of the information requested could be provided. [Code]

Output: Incomplete


Input: [Possible Major Codes] Sender, Receiver [Description] The operation failed for unspecified reasons. [Code]

Output: Failure


Input: [Possible Major Codes] Sender, Receiver [Description] The operation was refused. [Code]

Output: Refused


Input: [Possible Major Codes] Sender [Description] The operation was refused because the necessary authentication information was incorrect or missing. [Code]

Output: NoAuthentication


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

Output: uri

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


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

Output: timestamp

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


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

Output: clientip

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


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

Output: other.httpmethod

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


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

Output: other.bytes

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


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

Output: other.statuscode

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


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

Output: lexical

Static Context Components


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

Output: lexical

Static Context Components


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

Output: lexical

Static Context Components


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

Output: lexical

Static Context Components


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

Output: module

Static Context Components


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

Output: lexical

Static Context Components