. "Rules for deriving profiles"@en . . . . "Extensibility"@en . "consideration"@en . "Client"@en . "A profile is a subset of the technology that supports a particular functional objective or a subset of a set of technologies defining how they are required to operate together (e.g., XHTML plus MathML plus SVG)."@en . "Module"@en . "Producer of content (may be divided into initiators and modifiers)."@en . . . . "MAY"@en . . . "statement"@en . . "Describes an abstraction around which several other specs will synchronize, but which is not implemented in code. Example: XML InfoSet is a foundation for various specs that have a \"data model\" of the usable content of an XML document. However, there is no \"InfoSet API\" or \"InfoSet Parser\" specified."@en . . "operative process"@en . "2021-06-04"^^ . "NOT RECOMMENDED"@en . . . . "Consumer in a one-way pipeline."@en . . . . . . . . "Describes a markup language whose downstream usage is to express meaning to an end user or to applications specific to a discipline other than the Web itself. Example: MathML is a markup language for the math discipline, and may be used to express mathematical ideas to a person or to math software. SVG is a language for expressing graphical ideas."@en . "defines"@en . . "composed of"@en . . "could not"@en . . . "SHALL"@en . . . . . . . . "Self-Review Questionnaire: Security and Privacy"@en . . "Specification Categories"@en . . . . . . "http://www.w3.org/ns/spec#"^^ . "terminology"@en . . . . . . . "Profile"@en . "Specification (guidelines)."@en . "Content/data"@en . . . . "build upon"@en . . "note"@en . . . "conventions"@en . . . . . . "Modules are discrete divisions or functional groupings of the technology and do not necessarily fit in a simple hierarchical structure."@en . . . . "requirement level"@en . . . "conformance"@en . . . _:riog00000001 "2022-11-17"^^ . . "Consideration"@en . . . "Requirement"@en . "test suite"@en . . "intellectual property rights"@en . . . . . . . . . . "Specification"@en . . "Processor"@en . . "extensibility"@en . . "Set of events"@en . . . . "testing"@en . . . . . . "MUST"@en . . "Responding agent"@en . . "Security Consideration"@en . . "might"@en . "success criteria"@en . . "Content (of type, meaning, and format as defined in the specification)."@en . . . . . . . "Conformance"@en . . "Producer of instructions/commands to processor."@en . "module"@en . . "discouraged"@en . . . "publication rules"@en . "cannot"@en . . . . . . . . . . . "Processor (consumer of its vocabulary/instructions)."@en . . "could"@en . "requirement"@en . . . "strongly discouraged"@en . . . "error handling"@en . . . . . . "REQUIRED"@en . . "implementation reports"@en . "issue"@en . . . "Registration considerations for collection of values or data at standards organisations, e.g., IANA, W3C."@en . "Describes a coherent set of events that software may need to raise or listen for. Example: one part of XForms is a set of form-related events."@en . . "Describes the behaviour of a piece of software that takes well-defined inputs and operates on them to produce specified output. Example: the XSL Transformations language specifies the behaviour of an XSLT processor. The specification describes an XML-based style sheet language that directs the operations of a processor, but it clearly states that conformance determinations apply to the processor, not the style sheets. Example: XML Query specifies the behaviour of a processor that takes the query language and fetches data, typically arranging that data in a convenient form for XML/Web use. It allows flexibility of the storage system from which data is fetched."@en . . . "Spec Terms"@en . "Module"@en . . . . . "Describes desirable attributes of content intended for human consumption. Examples: QA Specification Guidelines, Web Content Accessibility Guidelines."@en . . . . . "exit criteria"@en . "Responding agent (e.g., server) of API (consumer and producer)."@en . . "Profile derived from the specification's Rules for Profiles."@en . "Spec Terms provides classes and properties that can be used to describe any significant unit of information in technical reports."@en . . . . "Describes the interaction between two parties. Example: SOAP."@en . . . "requirement reference"@en . . . . "functional level"@en . "RECOMMENDED"@en . . . . . . . . "APIs - describes a programmatic interface, allowing independent implementation of software that occupies the roles on either side of the interface. Example: DOM specifies an interface that can be implemented by a parser or other processor that intends to offer an XML document in navigable form. Other software that wishes to navigate an XML document (e.g., an XSLT processor) can be written to use the DOM interface."@en . . . "spec"@en . "encouraged"@en . "Protocol"@en . "profile"@en . . "scope"@en . "example"@en . . . . . "advisement"@en . . . . . . . "SHOULD"@en . "Internationalization Consideration"@en . "Self-Review Questionnaire"@en . "Module that hosts the processor."@en . . "can"@en . "Set of guidelines"@en . . "API"@en . . . . . . "suited for"@en . . . "Work in Progress!"@en . "Functional level"@en . . . . . . . . "OPTIONAL"@en . "might not"@en . . . "Registration Consideration"@en . . . "review process"@en . . . "acknowledgements"@en . "requirement subject"@en . . "Consumer"@en . . "strongly encouraged"@en . . "MUST NOT"@en . . . "Foundation or abstract"@en . . . . . . . . . . "Notation/syntax"@en . . "SHOULD NOT"@en . . . . . "compliance with other specifications"@en . . . "document status"@en . . . "Requirement Level"@en . "Player (read-only consumer, conveys content in non- XML way)."@en . . . "Functional levels — or in common usage simply levels — are used to group functionality into nested subsets, ranging from minimal or core functionality to full or complete functionally. Level 1 is the minimum or core of the technology. Level 2 includes all of level 1 plus additional functionality. This nesting continues until level n, which consists of the entire technology."@en . . . "test case"@en . "Producer of instructions"@en . "Describes how implementers, or any parties other than the WG itself, may produce a profile for a particular situation that cannot be anticipated in complete detail at the time the WG is writing its specification. Example: part of SMIL."@en . . . . . . . . . "Processor behaviour"@en . "Accessibility Consideration"@en . . . . "Player"@en . . . . . "violates advice"@en . . "Classes of Products"@en . . . . . . . "Describes a language that will be expressed as an actual character stream in XML or Web content and whose semantics will be understood by other W3C-specified technologies. Example: XPath is a non-XML-based notation for expressions that is used as the W3C-standard expression language for XSLT, XPointer, and XForms. The specifications of those other technologies do not treat XPath as a black box, but rather impose limits, add extensions, and/or recognize the range of potential values of an XPath expression. By doing so, the other technologies require a certain level of precision in the XPath specification, including precision about its variability, to use the hooks and impose their limits."@en . "Content"@en . . . . . . "Producer of content"@en . "based on consensus"@en . "SHALL NOT"@en . "Privacy Consideration"@en . . . . _:riog00000001 . . . . . "Server"@en . "Profile"@en . . . "test script"@en . "Advisement Level"@en . . . . . . . . . . "Specification guidelines"@en . . .