Input: [Topic] Locales, timezones and time functions. [Evaluation Methods] (Modules with exercises are appreciated.) Final exam Final assignment [Competency]

Output: Explain the concept of locales. Demonstrate how to set timezones for PHP scripts. Demonstrate how to set locale for PHP scripts. Explain the concept of collation and demonstrate how to use locale aware string and array comparison and sorting. Demonstrate how locale and timezone information affects date and time functionality in PHP. Use the basic date and time functions.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Strings [Evaluation Methods] Assignment 3. Final exam. Final assignment. [Competency]

Output: Explain the concept of a string. Compare the two types of strings there is in PHP 6. Demonstrate how to set them and convert between them. Demonstrate how to get the length of a string and access its characters by index Demonstrate how to handle single and double quotes in strings with variables. Demonstrate how to concatenate strings. Demonstrate how to use heredoc and nowdoc. Recognize the two syntaxes that exist for heredoc as of PHP 5.3. Demonstrate how to escape characters in strings. Demonstrate correct usage of basic string functions, e.g. strlen, substr, strstr, strpos, trim, strtolower, with variants. Demonstrate how to compare strings, using operators and comparison functions like strcmp or strcoll. Demonstrate how to check the integrity of string contents using the ctype-functions. Explain the concept of regular expressions, exemplify when they can be used and demonstrate simple usage.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Array usage and array functions [Evaluation Methods] Assignment 3. Final exam. Final assignment. [Competency]

Output: Demonstrate how to iterate over an array using the foreach function. Demonstrate how to sort arrays. Demonstrate how to perform a function call on each value in an array. Specifically, demonstrate how to remove magic quotes from GPC-data. Explain what the cursor is in an array and demonstrate how to walk through arrays. Demonstrate how to use assign multiple variables from array values using the list() language construct. Demonstrate how to check for the existence of specific keys or values within an array. Demonstrate how to attach and how to delete values at both the bottom and top of an array.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Objects and classes (simple overview) [Evaluation Methods] (Modules with exercises are appreciated.) Final exam Final assignment [Competency]

Output: Explain some benefits of Object Oriented programming compared to procedural programming. Explain basic OO terminology. Demonstrate how to define and instantiate classes in PHP. Explain constructors and destructors, how to name constructors in PHP 4 and 5+ and how to use constructors. Demonstrate how to use the $this pseudovariable. Explain the concept of inheritance och demonstrate how to use the extends keyword. Explain the concept of polymorfism and demonstrate how to use interfaces and abstract classes in PHP. Briefly explain the differences in the object model between PHP 4 and PHP 5. Explain visibility of properties and methods. Explain class constants, static properties and methods and demonstrate how to use the scope resolution operator (Paamayim Nekudotayim).

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Error handling and exceptions [Evaluation Methods] (Modules with exercises are appreciated.) Final exam. Final assignment. [Competency]

Output: Recognize the types of errors in PHP. Handle interaction errors e.g. GET-data does not match DB-record might produce a 404. Use good error handling strategies. E.g: Differentiate between development servers (show on page) vs. production servers (log errors). Make usable error pages and understandable error messages. Send the correct HTTP status code for error pages. Recognize exceptions and handle them using try and catch.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Server side architecture [Evaluation Methods] Exercise 4. Final exam. Final assignment. [Competency]

Output: Recognize what separation of concerns mean for PHP development. Recognize the following concepts: Presentation logic and templates, business logic and data storage logic. Demonstrate a secure and logical directory structure for PHP applictions. Explain include paths. Demonstrate how to write an application that does not depend on being in a specific root directory. Demonstrate a good strategy for filtering all untrusted data. Demonstrate consistent and appropriate escaping of output data. Implement usable, SEO-friendly and hackable URL:s. Recognize rewrite rules. Recognize the abbreviation MVC and briefly explain the rationale behind it.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Handling posted data [Evaluation Methods] Exercise 5. Final exam. Final assignment. [Competency]

Output: Explain why client side checks only can be used to offload a server and provide better usability, never for security. Explain why GPC-data might be quoted in PHP 4.x and 5.x. Explain what problems magic quotes were intended to solve, why they did not work properly and are being removed in PHP 6 and how they can be removed in a script. Explain how the superglobal array $_POST relates to name attributes in HTML forms. Demonstrate handling posted data. Recognize the usage of register globals and explain why it is a security hazard. Recognize the bad habit of manually making EGPCS-data into regular variables ($foo = $_POST[‘foo’] or extract($_POST)). Recognize the usage of $_REQUEST and explain why it is considered bad practice to use it. Recognize how sensitive data can be transmitted securily, using encryption. Recognize the abbreviations SSL and TLS.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Sending email [Evaluation Methods] Exercise 5. Final exam. Final assignment. [Competency]

Output: Demonstrate simple usage of the mail() function in PHP. Recognize the concept SMTP injection and demonstrate how to avoid it.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Sessions and authentication [Evaluation Methods] Final exam. Final assignment. [Competency]

Output: Recognize the sessionless nature of HTTP. Recognize session fixation and session hijacking. Use session_regenerate_id and set session ID using cookies only. Recognize HTTP-authentication in PHP. Preventing multiple submits of a form. Demonstrate how to prevent cross-posting using a session variable.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Cookies [Evaluation Methods] Final exam. Final assignment. [Competency]

Output: Explain the concept of cookies and how they are passed to the server from the browser. Demonstrate how to set and read cookies. Explain the security benefits of server side only cookies, and demonstrate how to set them.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] File handling and storing data in text files [Evaluation Methods] Final exam. Final assignment. [Competency]

Output: Demonstrate how to read from and write to files. Recognize the different flags used to control the opening of file sockets. Recognize the most common security problems when usiing file functions. Demonstrate how to safely handle files uploaded by the user.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Relational Database concepts and MySQL fundamentals [Evaluation Methods] Final assignment Final exam [Competency]

Output: List some common Database Management Systems (DBMS). List some common alternatives to storing data in a relational database and briefly explain the merits and disadvantages of each option. Explain how SQLite can be used from every modern PHP installation. (Note: SQLite is primarily included to provide a way to explain data access abstraction using PDO.) Give an overview of how a relational database works. Recognize the terminology used about databases (relation/table, tuple/row, attribute/field/column, default values, NULL, keys, etc). Briefly explain the concept of normalization and recognize the related glossary (keys, functional dependency) List the available data types in MySQL and demonstrate proper usage of the most common ones. Explain the concept of indexes. Demonstrate how to use indexes in MySQL. Recognize the concept of a storage engines in MySQL and briefly explain the main differences between MyISAM and InnoDB. Demonstrate how to use PhpMyAdmin or a graphical tool to set up a database. Make a user with privileges suitable for PHP scripts. Demonstrate how to run queries in the tool. Demonstrate how to backup/dump a MySQL database. Question to reviewers: Is it possible to wait with constraints and referential integrity (foreign keys) until Server Side Scripting 2?

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] SQL [Evaluation Methods] Final assignment Final exam [Competency]

Output: Recognize the glossary of SQL (DDL, DML, CRUD) Demonstrate how to access a MySQL DBMS from a CLI tool. Demonstrate how to SELECT individual records and groups of records; SORT-ing and LIMIT-ing of the results. Demonstrate how to use JOIN. Demonstrate simple usage of SQL-functions (count!) Demonstrate how to INSERT data into a table. Demonstrate how to UPDATE a table and explain why one should always use the WHERE clause doing so. Demonstrate how to DELETE data and explain why one should always use the WHERE clause doing so.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] PDO [Evaluation Methods] Final assignment Final exam [Competency]

Output: Recognize all 3 built in API’s to access a MySQL database from PHP (mysql, mysqli, PDO). Discuss their strengths and downsides. Demonstrate how to connect to a DBMS with PDO, prepare and execute statements, fetch single results and iterate over result sets. Recognize how to access reults from a prepared statement as normal arrays, associative arrays, objects and objects belonging to a specific class. Demonstrate safe usage of user submitted data in SQL. Recognize how to manually quote user submitted data. Discuss the benefits of prepared statements. Demonstrate how to handle errors and unexpected results using PDO. Demonstrate safe handling of database credentials.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] The mysql and the mysqli functions [Evaluation Methods] Final exam [Competency]

Output: Recognize how to use the mysql and the mysqli functions. Discuss how to safely handle user submitted data using the mysql and the mysqli functions.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] SPL, PEAR and Frameworks [Evaluation Methods] Final exam [Competency]

Output: Recognize PEAR, PECL, SPL and the most well known PHP Component libraries? Recognize the most common PHP Frameworks. Recognize the most common PHP applications/Content Managament Systems. Recognize the usage of PHP for extended functionality for some big websites (e.g. Facebook)

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Web Services, API’s, RSS, JSON and Ajax [Evaluation Methods] Final exam [Competency]

Output: Recognize the most common formats for data interchange. Summarize the Ajax pattern for updating a web page. Briefly describe the concepts of API’s and Web Services.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Shared hosting [Evaluation Methods] Final assignment Final exam [Competency]

Output: Recognize the most important technical considerations one must know when chosing a web host. List the most important security considerations one must know about shared hosting. Demonstrate usage of a web host control panel.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Class] Addition [Meaning]

Output: New constructs have been added to the schema


Input: [Class] Clarification [Meaning]

Output: The meaning of the schema has been changed to more accurately match the specification


Input: [Class] Deletion [Meaning]

Output: Constructs have been removed from the schema


Input: [Class] Name [Meaning]

Output: The schema has been changed due to a datatype name change in the XML Schema specification


Input: [Class] Namespace [Meaning]

Output: A namespace name has been changed


Input: [Class] Semantic [Meaning]

Output: The meaning of the schema has been changed


Input: [Class] Style [Meaning]

Output: Style changes have been made to the schema


Input: [Class] Syntax [Meaning]

Output: The syntax of the schema has been updated due to changes in the XML Schema specification


Input: [Function] CreateScope [Arguments] name(optional) [Description] Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteScope [Arguments] name(optional) [Description] Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] CreateVariable [Arguments] variableName, value(optional), scopeName(optional) [Description] Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope. [Return Value]

Output: Success or Error

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteVariable [Arguments] variableName, scopeName(optional) [Description] Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] UpdateVariable [Arguments] variableName, newValue, scopeName(optional) [Description] Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] ReadVariable [Arguments] variableName, scopeName(optional) [Description] Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found. [Return Value]

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] EvaluateExpression [Arguments] expr, scopeName(optional) [Description] Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found. [Return Value]

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Feature] Level of abstraction [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Intents] Javascript API to allow client web application to find and communicate with service web application [Google Web Introducer] Javascript API to allow client web application to find and communicate with service web application [Webinos proposal]

Output: Javascript API to obtain Javascript-based Service APIs

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Relation to underlying low level discovery/communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Intents] None [Google Web Introducer] None [Webinos proposal]

Output: Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Location of services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Intents] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Introducer] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Webinos proposal]

Output: In device, locally connected, local network and web-based services

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Network infrastructure required [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Intents] None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view [Google Web Introducer] “Web Introducer server” [Webinos proposal]

Output: Underlying infrastructure for registering user’s devices/services (more details)

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Identification of service type [Opera/CableLabs proposal] Service type tokens exposed from the underlying discovery mechanisms [Google Web Intents] A service (intent) is defined by: Action: a URI defining what to do (share, pick, view, etc) Type: the data type to perform the action on (image, url, json etc) [Google Web Introducer] A service (intent) is a string identifying an interaction pattern between a Client and a Service. Examples are bookmark for sharing, link to media file, user's stream of incoming SMSs [Webinos proposal]

Output: URI identifying a JavaScript API to access the service

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Security / access control [Opera/CableLabs proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. Assumes that access control is handled in the UA. [Google Web Intents] Based on user selection of discovered service and security mechanisms implemented for respective services [Google Web Introducer] Based on user selection of discovered service and security mechanisms implemented for respective services [Webinos proposal]

Output: Based on user selection of discovered service and security mechanisms implemented for respective services. A distributed approach where policy decisions are hosted in a Personal Zone.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service registration [Opera/CableLabs proposal] UA silently (i.e. in the background) handles discovery and registration of services from the local device, local network. UA also silently handles service discovery and registration on visited web sites. [Google Web Intents] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The services Action, Type and URL to a web page that implements the service is registered. For example, in-page meta header registration syntax is collected as the user browses their web sites. [Google Web Introducer] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The service's name, supported intent strings, icons, URLs to service pages are registered. [Webinos proposal]

Output: An application can register new services through a statement in the manifest file

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Discovery process [Opera/CableLabs proposal] UA searches for networked services (the timing of which is at the discretion of the UA) in the local network and on user visited web sites and maintains a list of currently available services. [Google Web Intents] A web application wanting to use a service calls a simple API stating the requested Action and Type. An iframe allows the user to select one of the registered services for this Action and Type. [Google Web Introducer] A web application wanting to use a service calls a simple API stating the requested intent. An iframe or a new window allows the user to select one of the registered services for this intent. [Webinos proposal]

Output: UA searches for networked services at API invocation.A successCallback is issued for each service found. Timer for how long search process lasts could be set. Pending search process can be canceled

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Search filter [Opera/CableLabs proposal] No [1]. [Google Web Intents] No. [Google Web Introducer] No. [Webinos proposal]

Output: Yes. Allows web application to search for services belonging to certain user(s), to state remote or local only services and to state location of service. Also allows the page to set a timer for how long search process lasts could be set. Pending search processes can be canceled.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Communication with service [Opera/CableLabs proposal] A URL, extracted directly from the underlying service discovery process, is provided to the web application to access the service. The web page can then use standard XmlHttpRequest, Web Sockets, Server-Sent Events and Web Messaging, etc (all with implicit cross-origin resource sharing) to communcate with the service. Protocol depends on messaging format implemented in device implementing service (e.g. json, protobufs, text-based, xml, etc). [Google Web Intents] Data is sent bi-directionally between client web application page and the service web page through the Web Intents API. The format/protocol of this data exchange is defined for each Action by the Web Intents specification. Underlying communication mechanism is web messaging but this level is hided to the application developer. [Google Web Introducer] Data is sent bi-directionally between client web application page and the service web page through Web Messaging. The format/protocol of this data exchange must be defined for each Intent by specific API/protocol specifications for each intent type. [Webinos proposal]

Output: A standardized / “well-known” JavaScript API is provided to the web application to access the service.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service status monitoring [Opera/CableLabs proposal] readyState changes fire back to web page's network service objects. readystatechange events occur on a network service object when the service becomes available or unavailable. servicesAvailable attribute is used to monitor general number of services of the authorized type currently available in the user's network(s). [Google Web Intents] No service status monitoring in the Web Intents API itself but guess that this could be handled in the specific protocol for the specific Action. [Google Web Introducer] No service status monitoring in the Web Introducer API itself but guess that this could be handled in the specific protocol for the specific intent type. [Webinos proposal]

Output: onLost callback when found but not yet bound service is lost. onServiceUnavaialble and onServiceAvailable callbacks for bound services.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service binding lifecycle [Opera/CableLabs proposal] Opera to elaborate [Google Web Intents] To be completed [Google Web Introducer] To be completed [Webinos proposal]

Output: Service binding valid until unbind() is called or client page is left. Later the binding to the service can be resumed using the saved service id.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] .... [Opera/CableLabs proposal] ... [Google Web Intents] .... [Google Web Introducer] .... [Webinos proposal]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Description] The credits element matches the schema and it contains one credit child element. This should be linked to a testable assertion in the spec. [Title]

Output: Valid credits Element With Single credit Element


Input: [Description] The credits element matches the schema and it contains two credit child elements. This should be linked to a testable assertion in the spec. [Title]

Output: Valid credits Element With Two credit Elements


Input: [Description] The credits element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One credits Element


Input: [Description] The credits element does not contain a credit child element. This should be linked to a testable assertion in the spec. [Title]

Output: No credit Element in credits Element


Input: [Description] The credits element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in credits Element


Input: [Description] The credits element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in credits Element


Input: [Description] The credits element contains an content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in credits Element


Input: [Description] The description element matches the schema. [Title]

Output: Valid description Element


Input: [Description] The description element does not contain a url attribute but it still matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element Without url Attribute


Input: [Description] The description element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With One No Language Tagged text Element


Input: [Description] The description element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With One Language Tagged text Element


Input: [Description] The description element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With Mixed text Element Language Tags 1


Input: [Description] The description element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With Mixed text Element Language Tags 2


Input: [Description] The description element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One description Element


Input: [Description] The description element does not contain a text child element. This should be linked to a testable assertion in the spec. [Title]

Output: No text Element in description Element


Input: [Description] The description element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in description Element


Input: [Description] The description element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in description Element


Input: [Description] The description element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in description Element


Input: [Description] The description element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in description Element text Element


Input: [Description] The description element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in description Element text Element


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

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

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] 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] taxon [Expected Type] BiologicalDatabaseEntry or Text [Description]

Output: The taxonomy information of the entry.

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


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

Output: Reference to another resource.

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


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

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

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


Input: [Description] Updated to use the http://www.w3.org/2001/XMLSchema namespace [Class]

Output: Namespace


Input: [Description] Value of targetNamespace attribute changed to http://www.w3.org/2001/06/soap-encoding [Class]

Output: Namespace


Input: [Description] Changed type of the root attribute from restriction of boolean that only allowed 0 or 1 as lexical values to the standard boolean in the http://www.w3.org/2001/XMLSchema namespace. The lexical forms 0, 1, false, true are now allowed. [Class]

Output: Semantic


Input: [Description] Added processContents="lax" to all element and attribute wildcards [Class]

Output: Addition


Input: [Description] Changed base64 simple type to be a vacuous restriction of the base64Binary type in the http://www.w3.org/2001/XMLSchema namespace [Class]

Output: Syntax


Input: [Description] Updated all complex type definitions with simple base types to new syntax [Class]

Output: Syntax


Input: [Description] Added to all complex type definitions derived implicitly from the ur-type [Class]

Output: Syntax


Input: [Description] Added to all named model group definitions [Class]

Output: Syntax


Input: [Description] Removed the timeDuration datatype [Class]

Output: Deletion


Input: [Description] Added duration datatype derived by extension from the duration datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Removed the timeInstant datatype [Class]

Output: Deletion


Input: [Description] Added dateTime datatype derived by extension from the dateTime datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added gYearMonth datatype derived by extension from the gYearMonth datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added gYear datatype derived by extension from the gYear datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added gMonthDay datatype derived by extension from the gMonthDay datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added gDay datatype derived by extension from the gDay datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Removed the binary datatype [Class]

Output: Deletion


Input: [Description] Added hexBinary datatype derived by extension from the hexBinary datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added base64Binary datatype derived by extension from the base64Binary datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Removed the uriReference datatype [Class]

Output: Deletion


Input: [Description] Added anyURI datatype derived by extension from the anyURI datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added normalizedString datatype derived by extension from the normalizedString datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added token datatype derived by extension from the token datatype in the http://www.w3.org/2001/XMLSchema namespace. [Class]

Output: Addition


Input: [Description] Added explicit namespace="##any" to all element and attribute wildcards which did not previously have an explicit namespace attribute [Class]

Output: Clarification


Input: [Description] Where possible comments have been changed into annotations [Class]

Output: Style


Input: [Webinos proposal] Javascript API to obtain Javascript-based Service APIs [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Intents] Javascript API to allow client web application to find and communicate with service web application [Google Web Introducer] Javascript API to allow client web application to find and communicate with service web application [Feature]

Output: Level of abstraction

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Intents] None [Google Web Introducer] None [Feature]

Output: Relation to underlying low level discovery/communication mechanisms

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] In device, locally connected, local network and web-based services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Intents] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Introducer] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Feature]

Output: Location of services

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] Underlying infrastructure for registering user’s devices/services (more details) [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Intents] None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view [Google Web Introducer] “Web Introducer server” [Feature]

Output: Network infrastructure required

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] URI identifying a JavaScript API to access the service [Opera/CableLabs proposal] Service type tokens exposed from the underlying discovery mechanisms [Google Web Intents] A service (intent) is defined by: Action: a URI defining what to do (share, pick, view, etc) Type: the data type to perform the action on (image, url, json etc) [Google Web Introducer] A service (intent) is a string identifying an interaction pattern between a Client and a Service. Examples are bookmark for sharing, link to media file, user's stream of incoming SMSs [Feature]

Output: Identification of service type

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. A distributed approach where policy decisions are hosted in a Personal Zone. [Opera/CableLabs proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. Assumes that access control is handled in the UA. [Google Web Intents] Based on user selection of discovered service and security mechanisms implemented for respective services [Google Web Introducer] Based on user selection of discovered service and security mechanisms implemented for respective services [Feature]

Output: Security / access control

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] An application can register new services through a statement in the manifest file [Opera/CableLabs proposal] UA silently (i.e. in the background) handles discovery and registration of services from the local device, local network. UA also silently handles service discovery and registration on visited web sites. [Google Web Intents] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The services Action, Type and URL to a web page that implements the service is registered. For example, in-page meta header registration syntax is collected as the user browses their web sites. [Google Web Introducer] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The service's name, supported intent strings, icons, URLs to service pages are registered. [Feature]

Output: Service registration

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] UA searches for networked services at API invocation.A successCallback is issued for each service found. Timer for how long search process lasts could be set. Pending search process can be canceled [Opera/CableLabs proposal] UA searches for networked services (the timing of which is at the discretion of the UA) in the local network and on user visited web sites and maintains a list of currently available services. [Google Web Intents] A web application wanting to use a service calls a simple API stating the requested Action and Type. An iframe allows the user to select one of the registered services for this Action and Type. [Google Web Introducer] A web application wanting to use a service calls a simple API stating the requested intent. An iframe or a new window allows the user to select one of the registered services for this intent. [Feature]

Output: Discovery process

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] Yes. Allows web application to search for services belonging to certain user(s), to state remote or local only services and to state location of service. Also allows the page to set a timer for how long search process lasts could be set. Pending search processes can be canceled. [Opera/CableLabs proposal] No [1]. [Google Web Intents] No. [Google Web Introducer] No. [Feature]

Output: Search filter

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] A standardized / “well-known” JavaScript API is provided to the web application to access the service. [Opera/CableLabs proposal] A URL, extracted directly from the underlying service discovery process, is provided to the web application to access the service. The web page can then use standard XmlHttpRequest, Web Sockets, Server-Sent Events and Web Messaging, etc (all with implicit cross-origin resource sharing) to communcate with the service. Protocol depends on messaging format implemented in device implementing service (e.g. json, protobufs, text-based, xml, etc). [Google Web Intents] Data is sent bi-directionally between client web application page and the service web page through the Web Intents API. The format/protocol of this data exchange is defined for each Action by the Web Intents specification. Underlying communication mechanism is web messaging but this level is hided to the application developer. [Google Web Introducer] Data is sent bi-directionally between client web application page and the service web page through Web Messaging. The format/protocol of this data exchange must be defined for each Intent by specific API/protocol specifications for each intent type. [Feature]

Output: Communication with service

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] onLost callback when found but not yet bound service is lost. onServiceUnavaialble and onServiceAvailable callbacks for bound services. [Opera/CableLabs proposal] readyState changes fire back to web page's network service objects. readystatechange events occur on a network service object when the service becomes available or unavailable. servicesAvailable attribute is used to monitor general number of services of the authorized type currently available in the user's network(s). [Google Web Intents] No service status monitoring in the Web Intents API itself but guess that this could be handled in the specific protocol for the specific Action. [Google Web Introducer] No service status monitoring in the Web Introducer API itself but guess that this could be handled in the specific protocol for the specific intent type. [Feature]

Output: Service status monitoring

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] Service binding valid until unbind() is called or client page is left. Later the binding to the service can be resumed using the saved service id. [Opera/CableLabs proposal] Opera to elaborate [Google Web Intents] To be completed [Google Web Introducer] To be completed [Feature]

Output: Service binding lifecycle

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Webinos proposal] ... [Opera/CableLabs proposal] ... [Google Web Intents] .... [Google Web Introducer] .... [Feature]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Description] response to prepare indicating that activeGrammars or activeVoiceModel have been successfully prepared [Event]

Output: prepared

Voice Extensible Markup Language (VoiceXML) 3.0

Table 8: Recognition: Events from Device


Input: [Description] notification that the onset of input has been detected [Event]

Output: inputStarted

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] notification that the end of input has been detected [Event]

Output: inputFinished

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Payload] results (M) [Description] notification of a partial recognition results [Event]

Output: partialResults

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Payload] results (M) [Description] notification of final recognition results [Event]

Output: recoResults

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Payload] error status (M) [Description] an error occurred [Event]

Output: error

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Function] CreateScope [Arguments] name(optional) [Return Value] Success or Failure [Description]

Output: Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteScope [Arguments] name(optional) [Return Value] Success or Failure [Description]

Output: Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] CreateVariable [Arguments] variableName, value(optional), scopeName(optional) [Return Value] Success or Error [Description]

Output: Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteVariable [Arguments] variableName, scopeName(optional) [Return Value] Success or Failure [Description]

Output: Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] UpdateVariable [Arguments] variableName, newValue, scopeName(optional) [Return Value] Success or Failure [Description]

Output: Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] ReadVariable [Arguments] variableName, scopeName(optional) [Return Value] value [Description]

Output: Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] EvaluateExpression [Arguments] expr, scopeName(optional) [Return Value] value [Description]

Output: Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Event Type] cancel [Audio Provided] no [Action]

Output: don’t reprompt

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] error [Audio Provided] yes [Action]

Output: exit interpreter

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] exit [Audio Provided] no [Action]

Output: exit interpreter

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] help [Audio Provided] yes [Action]

Output: reprompt

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] noinput [Audio Provided] no [Action]

Output: reprompt

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] nomatch [Audio Provided] yes [Action]

Output: reprompt

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] maxspeechtimeout [Audio Provided] yes [Action]

Output: reprompt

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] connection.disconnect [Audio Provided] no [Action]

Output: exit interpreter

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] all others [Audio Provided] yes [Action]

Output: exit interpreter

Voice Extensible Markup Language (VoiceXML) Version 2.0


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

Output: Physical Contact Information, Demographic and Socioeconomic Data


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

Output: Demographic and Socioeconomic Data


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

Output: Unique Identifiers


Input: [user.] gender [Type] gender [Short display name] User's Gender [Category]

Output: Demographic and Socioeconomic Data


Input: [user.] employer [Type] text [Short display name] User's Employer [Category]

Output: Demographic and Socioeconomic Data


Input: [user.] department [Type] text [Short display name] Department or division of organization where user is employed [Category]

Output: Demographic and Socioeconomic Data


Input: [user.] jobtitle [Type] text [Short display name] User's Job Title [Category]

Output: Demographic and Socioeconomic Data


Input: [user.] home. [Type] contact. [Short display name] User's Home Contact Information [Category]

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


Input: [user.] business. [Type] contact. [Short display name] User's Business Contact Information [Category]

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


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name. [Function]

Output: CreateScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists. [Function]

Output: DeleteScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, value(optional), scopeName(optional) [Return Value] Success or Error [Description] Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope. [Function]

Output: CreateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] Success or Failure [Description] Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope. [Function]

Output: DeleteVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, newValue, scopeName(optional) [Return Value] Success or Failure [Description] Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found. [Function]

Output: UpdateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] value [Description] Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found. [Function]

Output: ReadVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] expr, scopeName(optional) [Return Value] value [Description] Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found. [Function]

Output: EvaluateExpression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: alignment

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Document


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

Output: compression

Efficient XML Interchange (EXI) Format 1.0


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

Output: strict

Efficient XML Interchange (EXI) Format 1.0


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

Output: fragment

Efficient XML Interchange (EXI) Format 1.0


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

Output: preserve

Efficient XML Interchange (EXI) Format 1.0


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

Output: selfContained

Efficient XML Interchange (EXI) Format 1.0


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

Output: schemaId

Efficient XML Interchange (EXI) Format 1.0


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

Output: datatypeRepresentationMap

Efficient XML Interchange (EXI) Format 1.0


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

Output: blockSize

Efficient XML Interchange (EXI) Format 1.0


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

Output: valueMaxLength

Efficient XML Interchange (EXI) Format 1.0


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

Output: valuePartitionCapacity

Efficient XML Interchange (EXI) Format 1.0


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

Output: [user defined meta-data]

Efficient XML Interchange (EXI) Format 1.0


Input: [Title] Valid description Element [Description]

Output: The description element matches the schema.


Input: [Title] Valid description Element Without url Attribute [Description]

Output: The description element does not contain a url attribute but it still matches the schema. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With One No Language Tagged text Element [Description]

Output: The description element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With One Language Tagged text Element [Description]

Output: The description element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With Mixed text Element Language Tags 1 [Description]

Output: The description element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With Mixed text Element Language Tags 2 [Description]

Output: The description element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One description Element [Description]

Output: The description element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No text Element in description Element [Description]

Output: The description element does not contain a text child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in description Element [Description]

Output: The description element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in description Element [Description]

Output: The description element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in description Element [Description]

Output: The description element contains content. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in description Element text Element [Description]

Output: The description element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in description Element text Element [Description]

Output: The description element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Field Name] name [Details]

Output: " connection.disconnected "

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connectionid [Details]

Output: The ID of the Connection associated with this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] protocol * [Details]

Output: The platform protocol ID of the Connection protocol

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] reason * [Details]

Output: A disconnection reason code

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] info * [Details]

Output: An object which provides additional platform or protocol dependent information

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connection [Details]

Output: an ECMAScript object reference to the Connection object identified by the connectionid property for this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Event Type] cancel [Action] don’t reprompt [Audio Provided]

Output: no

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] error [Action] exit interpreter [Audio Provided]

Output: yes

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] exit [Action] exit interpreter [Audio Provided]

Output: no

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] help [Action] reprompt [Audio Provided]

Output: yes

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] noinput [Action] reprompt [Audio Provided]

Output: no

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] nomatch [Action] reprompt [Audio Provided]

Output: yes

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] maxspeechtimeout [Action] reprompt [Audio Provided]

Output: yes

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] connection.disconnect [Action] exit interpreter [Audio Provided]

Output: no

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Event Type] all others [Action] exit interpreter [Audio Provided]

Output: yes

Voice Extensible Markup Language (VoiceXML) Version 2.0


Input: [Name] confidencelevel [Default] 0.5 [Description]

Output: The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations ).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: 98: Speech Recognition Properties


Input: [Name] sensitivity [Default] 0.5 [Description]

Output: Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations ).

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Name] speedvsaccuracy [Default] 0.5 [Description]

Output: A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations ).

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Name] completetimeout [Default] platform-dependent [Description]

Output: The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations ). See 8.3 Speech and DTMF Input Timing Properties . Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below.

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Name] incompletetimeout [Default] undefined? [Description]

Output: The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations ).

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Name] maxspeechtimeout [Default] platform-dependent [Description]

Output: The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations ).

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Name] name [Type] The name must conform to the variable naming conventions in (TODO). [Required] Yes [Description]

Output: The form item variable in the dialog scope that will hold the recording. The name must be unique among form items in the form. If the name is not unique, then a badfetch error is thrown when the document is fetched. Note that how this variable is implemented may vary between platforms (although all platforms must support its behaviour behavior in and as described in this specification).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] expr [Type] TBD [Required] No [Default Value] ECMAScript undefined [Description]

Output: The initial value of the form item variable. If initialized to a value, then the form item will not be visited unless the form item variable is cleared.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] cond [Type] data model expression [Required] No [Default Value] true [Description]

Output: A data model expression that must evaluate to true after conversion to boolean in order for the form item to be visited.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] modal [Type] boolean [Required] No [Default Value] true [Description]

Output: If this is true, all non-local speech and DTMF grammars are not active while making the recording. If this is false, non-local speech and DTMF grammars are active.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] beep [Type] boolean [Required] No [Default Value] false [Description]

Output: If true, a tone is emitted just prior to recording.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] maxtime [Type] Time Designation [Required] No [Default Value] Platform-specific value [Description]

Output: The maximum duration to record.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] finalsilence [Type] Time Designation [Required] No [Default Value] Platform-specific value [Description]

Output: The interval of silence that indicates end of speech.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] dtmfterm [Type] boolean [Required] No [Default Value] true [Description]

Output: If true, any DTMF keypress will be treated as a match of an active (anonymous) local DTMF grammar.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] type [Type] Required audio file formats specified in Appendix E of VoiceXML 2 (Other formats may also be supported) [Required] No [Default Value] Platform-specific (one of the required formats) [Description]

Output: The media format of the resulting recording.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] The name must conform to the variable naming conventions in (TODO). [Description] The form item variable in the dialog scope that will hold the recording. The name must be unique among form items in the form. If the name is not unique, then a badfetch error is thrown when the document is fetched. Note that how this variable is implemented may vary between platforms (although all platforms must support its behaviour behavior in and as described in this specification). [Required] Yes [Name]

Output: name

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] TBD [Description] The initial value of the form item variable. If initialized to a value, then the form item will not be visited unless the form item variable is cleared. [Required] No [Default Value] ECMAScript undefined [Name]

Output: expr

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] data model expression [Description] A data model expression that must evaluate to true after conversion to boolean in order for the form item to be visited. [Required] No [Default Value] true [Name]

Output: cond

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] boolean [Description] If this is true, all non-local speech and DTMF grammars are not active while making the recording. If this is false, non-local speech and DTMF grammars are active. [Required] No [Default Value] true [Name]

Output: modal

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] boolean [Description] If true, a tone is emitted just prior to recording. [Required] No [Default Value] false [Name]

Output: beep

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] Time Designation [Description] The maximum duration to record. [Required] No [Default Value] Platform-specific value [Name]

Output: maxtime

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] Time Designation [Description] The interval of silence that indicates end of speech. [Required] No [Default Value] Platform-specific value [Name]

Output: finalsilence

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] boolean [Description] If true, any DTMF keypress will be treated as a match of an active (anonymous) local DTMF grammar. [Required] No [Default Value] true [Name]

Output: dtmfterm

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Type] Required audio file formats specified in Appendix E of VoiceXML 2 (Other formats may also be supported) [Description] The media format of the resulting recording. [Required] No [Default Value] Platform-specific (one of the required formats) [Name]

Output: type

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


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

Output: bit-packed

Efficient XML Interchange (EXI) Format 1.0


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

Output: false

Efficient XML Interchange (EXI) Format 1.0


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

Output: false

Efficient XML Interchange (EXI) Format 1.0


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

Output: false

Efficient XML Interchange (EXI) Format 1.0


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

Output: all false

Efficient XML Interchange (EXI) Format 1.0


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

Output: false

Efficient XML Interchange (EXI) Format 1.0


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

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


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

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


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

Output: 1,000,000

Efficient XML Interchange (EXI) Format 1.0


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

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0


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

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0


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

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


Input: [Title] Valid copyright Element With One No Language Tagged text Element [Description]

Output: The copyright element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With One Language Tagged text Element [Description]

Output: The copyright element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 1 [Description]

Output: The copyright element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 2 [Description]

Output: The copyright element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One copyright Element [Description]

Output: The copyright element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No text Element in copyright Element [Description]

Output: The copyright element does not contain a text child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element [Description]

Output: The copyright element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element [Description]

Output: The copyright element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in copyright Element [Description]

Output: The copyright element contains content. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element text Element [Description]

Output: The copyright element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element text Element [Description]

Output: The copyright element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Description] The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations ). [Default] 0.5 [Name]

Output: confidencelevel

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations ). [Default] 0.5 [Name]

Output: sensitivity

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations ). [Default] 0.5 [Name]

Output: speedvsaccuracy

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations ). See 8.3 Speech and DTMF Input Timing Properties . Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below. [Default] platform-dependent [Name]

Output: completetimeout

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations ). [Default] undefined? [Name]

Output: incompletetimeout

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Description] The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations ). [Default] platform-dependent [Name]

Output: maxspeechtimeout

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Type] The only allowed values are "voice" and "dtmf" [Description] Defines the mode of the grammar following the modes of the W3C Speech Recognition Grammar Specification [SRGS] . [Required] No [Default Value] The value of the document property "grammarmode" [Name]

Output: mode

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Type] Weights are simple positive floating point values without exponentials. Legal formats are "n", "n.", ".n" and "n.n" where "n" is a sequence of one or many digits. [Description] Specifies the weight of the grammar. See vxml2: Section 3.1.1.3 [Required] No [Default Value] 1.0 [Name]

Output: weight

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Type] One of the values "safe" or "prefetch" [Description] Defines when the interpreter context should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed. [Required] No [Default Value] None [Name]

Output: fetchhint

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Type] Time Designation [Description] The interval to wait for the content to be returned before throwing an error.badfetch event. [Required] No [Default Value] None [Name]

Output: fetchtimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Required] No [Default Value] None [Name]

Output: maxage

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Required] No [Default Value] None [Name]

Output: maxstale

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] mode [Type] The only allowed values are "voice" and "dtmf" [Required] No [Default Value] The value of the document property "grammarmode" [Description]

Output: Defines the mode of the grammar following the modes of the W3C Speech Recognition Grammar Specification [SRGS] .

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] weight [Type] Weights are simple positive floating point values without exponentials. Legal formats are "n", "n.", ".n" and "n.n" where "n" is a sequence of one or many digits. [Required] No [Default Value] 1.0 [Description]

Output: Specifies the weight of the grammar. See vxml2: Section 3.1.1.3

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] fetchhint [Type] One of the values "safe" or "prefetch" [Required] No [Default Value] None [Description]

Output: Defines when the interpreter context should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] fetchtimeout [Type] Time Designation [Required] No [Default Value] None [Description]

Output: The interval to wait for the content to be returned before throwing an error.badfetch event.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] maxage [Type] An unsigned integer [Required] No [Default Value] None [Description]

Output: Indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


Input: [Name] maxstale [Type] An unsigned integer [Required] No [Default Value] None [Description]

Output: Indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: 16: Attributes


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

Output: Periodicals, Articles and Multi-volume Works

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


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

Output: Audiobook

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


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

Output: Collection

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


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

Output: Accessibility

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


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

Output: Add Organization department property

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


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

Output: Add Quotation type

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


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

Output: Actions in Schema.org (part 2)

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


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

Output: Orders in Schema.org

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


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

Output: Reservations in Schema.org

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


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

Output: EmailMessage type

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


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

Output: Civic Services

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


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

Output: Workers Union type

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


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

Output: TV and Radio proposal

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


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

Output: Sports

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


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

Output: Comics and Serials

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


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

Output: Event schema update

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


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

Output: Historical Data proposal

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


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

Output: Biological Databases

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


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

Output: Breadcrumbs

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


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

Output: Discussion

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


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

Output: Innovation

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


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

Output: dissolutionDate

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


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

Output: Lodging Extensions

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


Input: [Topic]

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


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

Output: Proposal name

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


Input: [Feature] Level of abstraction [Webinos proposal] Javascript API to obtain Javascript-based Service APIs [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Introducer] Javascript API to allow client web application to find and communicate with service web application [Google Web Intents]

Output: Javascript API to allow client web application to find and communicate with service web application

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Relation to underlying low level discovery/communication mechanisms [Webinos proposal] Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Introducer] None [Google Web Intents]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Location of services [Webinos proposal] In device, locally connected, local network and web-based services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Introducer] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Intents]

Output: Anywhere, service is represented by a web application that hides any underlying low level service access methods

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Network infrastructure required [Webinos proposal] Underlying infrastructure for registering user’s devices/services (more details) [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Introducer] “Web Introducer server” [Google Web Intents]

Output: None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view

ServiceDiscoveryComparison - DAP WG Wiki