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: [1] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [2] 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: [Name] src [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] none [Valid Values] a valid Dialog URL [Description]

Output: An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter must load and begin execution upon startup.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] prepareddialogid [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the src, type or namelist attributes. [Type] ECMAScript Expression [Default Value] none [Valid Values] a valid dialogid [Description]

Output: An ECMAScript expression which returns a dialog identifier of a dialog previously prepared by the execution of a dialogprepare element. If the specified dialog identifier refers to an unknown dialog or a dialog that has already been executed, by way of another dialogstart element, an error.dialogwrongstate event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description]

Output: An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of one or more whitespace separated CCXML variable names. These variables must be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


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

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of dialogterminate.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Attribute Constraints] Must not be used with conferenceid. [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a connection. The specified connection must be associated with the dialog being prepared. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter must use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter must use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] conferenceid [Required] false [Attribute Constraints] Must not be used with connectionid. [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a conference bridge. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter must use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter must use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Attribute Constraints] If used in conjunction with prepareddialogid , the bridge type must match that used on the previous dialogprepare element. [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. If both the mediadirection and the prepareddialogid are specified and the bridge type specified by the mediadirection attribute does not match that used on the previous dialogprepare element, an error.dialog.notstarted event must be raised. If no value for the mediadirection attribute was specified on the previous dialogprepare element, any mediadirection type option may be specified.

Voice Browser Call Control: CCXML Version 1.0


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

Output: The character string returned must be interpreted as a time interval. This 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 Browser Call Control: CCXML Version 1.0


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

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' 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 Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager.

Voice Browser Call Control: CCXML Version 1.0


Input: [id] i1 [title] HTTP Version should be case sensitive [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i3 [title] Chunk Size Definition [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i5 [title] Via is a MUST [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i6 [title] Fragments allowed in Location [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i10 [title] Safe Methods vs Redirection [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i11 [title] URI includes query [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i12 [title] Invalidation after Update or Delete [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i14 [title] Clarification regarding quoting of charset values [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i15 [title] No close on 1xx responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i17 [title] Revise description of the POST method [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i18 [title] Cache validators in 206 responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i25 [title] Accept-Encoding BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i31 [title] qdtext BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i62 [title] Whitespace in quoted-pair [target] RFC2616 [type]

Output: design


Input: [id] i2 [title] 'unsafe' characters [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i4 [title] Message Length [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i7 [title] Editors Notes [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i8 [title] Media type registrations [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i9 [title] Trailer [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i16 [title] Remove 'identity' token references [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i26 [title] Import query BNF [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i42 [title] RFC2606 compliance [target] RFC2616 [draft] 02 [type]

Output: editorial


Input: [id] i44 [title] Unneeded references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i45 [title] RFC977 reference [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i46 [title] references to RFC1700 [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i47 [title] inconsistency in date format explanation [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i48 [title] Date reference typo [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i49 [title] Connection header text [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i65 [title] Informative references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i66 [title] ISO-8859-1 Reference [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i68 [title] Encoding References Normative [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i84 [title] Redundant cross-references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i86 [title] Normative up-to-date references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i87 [title] typo in 13.2.2 [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [Event Name] dragstart [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] drag [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] dragenter [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Target]

Output: Immediate user selection or the body element


Input: [Event Name] dragleave [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] None [Target]

Output: Previous target element


Input: [Event Name] dragover [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Target]

Output: Current target element


Input: [Event Name] drop [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event; files returns any files included in the drag operation [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Current target element


Input: [Event Name] dragend [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Source node


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation [effectAllowed] uninitialized [Default Action] Initiate the drag-and-drop operation [dropEffect]


Input: [Event Name] drag [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Continue the drag-and-drop operation [dropEffect]


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] None [dropEffect]


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event; files returns any files included in the drag operation [effectAllowed] Same as last event [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Varies [dropEffect]

Output: Current drag operation


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

Output: Citation Promotion

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


Input: [Status] Proposal [Summary] 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] Proposal [Summary] Extension for describing accessibility properties of a CreativeWork. [Comments] Draft published to elicit feedback. [Topic]

Output: Accessibility

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


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. 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] Property to indicate that a single identity is being described. [Vocab] Essentially same meaning as owl:sameAs, but suggesting a distinct name to make it easier to talk about; also schema.org data is typically scruffier than OWL re http-range-14. [Comments] Draft published to elicit feedback. [Topic]

Output: sameAs

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


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

Output: Actions in Schema.org

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


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

Output: Orders in Schema.org

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


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

Output: Reservations in Schema.org

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


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

Output: EmailMessage type

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


Input: [Status] 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: [Topic]


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: [XKMS element] Message/Service [Required]

Output: Required but not dependent


Input: [XKMS element] Request/Signature [Required]

Output: Optional, may be used to support non-repudiation


Input: [XKMS element] Response/Signature [Required]

Output: Optional, may be used to support non-repudiation


Input: [XKMS element] Message/RequestID [Required]

Output: Required but not dependent


Input: [XKMS element] Message/ResponseID [Required]

Output: Required but not dependent


Input: [XKMS element] Message/Nonce [Required]

Output: Unnecessary


Input: [XKMS element] Request/RespondWith=Represent [Required]

Output: Unnecessary


Input: [XKMS element] Request/MessageHash [Required]

Output: Unnecessary


Input: [Security Issue] Confidentiality [Requirement] Some [Comments]

Output: The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however.


Input: [Security Issue] Request Authentication [Requirement] Some [Comments]

Output: A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service.


Input: [Security Issue] Response Authentication [Requirement] Most [Comments]

Output: An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication.


Input: [Security Issue] Persistent Authentication [Requirement] Some [Comments]

Output: Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications.


Input: [Security Issue] Message Correspondence [Requirement] All [Comments]

Output: The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used.


Input: [Security Issue] Request Replay [Requirement] Some [Comments]

Output: Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack.


Input: [Security Issue] Denial of Service [Requirement] Most [Comments]

Output: Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks.


Input: [Attribute Name] name [Required] true [Details] connection.failed [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] true [Details] The ID of the Connection associated with this event. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] protocol [Required] false [Details] The platform protocol ID of the Connection protocol. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] reason [Required] false [Details] A failure reason code. Content of this field is platform-specific. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] info [Required] false [Details] An object which provides additional platform or protocol dependent information. [Type]

Output: ECMAScript Object

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connection [Required] true [Details] An ECMAScript object reference to the Connection object identified by the connectionid property of this event. [Type]

Output: ECMAScript Object

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Required] true [Details] The unique identifier of the event source. This identifies the Platform Event I/O Processor that sent this event. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [Details] The name of the Event I/O Processor that sent this event. The value is platform dependent as this is an event generated by the Platform Event I/O processor. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] name [Required] true [Type] string [Details]

Output: error.conference.unjoin

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] id1 [Required] true [Type] string [Details]

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] id2 [Required] true [Type] string [Details]

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] reason [Required] true [Type] string [Details]

Output: A description of the reason the operation failed. Content of this field is platform-specific.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Required] true [Type] string [Details]

Output: The unique identifier of the event source. This identifies the Platform Event I/O Processor that sent this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [Type] string [Details]

Output: The name of the Event I/O Processor that sent this event. The value is platform dependent as this is an event generated by the Platform Event I/O processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [0] doctype [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] implementation [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] documentElement [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElement [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createDocumentFragment [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createTextNode [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createComment [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createCDATASection [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createProcessingInstruction [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttribute [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createEntityReference [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagName [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] importNode [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElementNS [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttributeNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagNameNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementById [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


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

Output: No conflict

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict

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


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

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

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


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

Output: No conflict

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


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

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

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


Input: [Attribute Name] name [Type] string [Details] connection.alerting [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Type] string [Details] The ID of the Connection associated with this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] protocol [Type] string [Details] The platform protocol ID of the Connection protocol. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] info [Type] ECMAScript Object [Details] An object which provides additional platform or protocol dependent information. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connection [Type] ECMAScript Object [Details] An ECMAScript object reference to the Connection object identified by the connectionid property of this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Type] string [Details] The unique identifier of the event source. This identifies the Platform Event I/O Processor that sent this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Type] string [Details] The name of the Event I/O Processor that sent this event. The value is platform dependent as this is an event generated by the Platform Event I/O processor. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation [effectAllowed] uninitialized [dropEffect] none [Default Action]

Output: Initiate the drag-and-drop operation


Input: [Event Name] drag [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action]

Output: Continue the drag-and-drop operation


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action]

Output: Reject immediate user selection as potential target element


Input: [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action]


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action]

Output: Reset the current drag operation to "none"


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event; files returns any files included in the drag operation [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action]

Output: Varies


Input: [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action]

Output: Varies


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


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

Output: Date and Time


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

Output: Date


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

Output: Month


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

Output: Week


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

Output: Time


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

Output: Local Date and Time


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

Output: Number


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

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


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

Output: File Upload


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

Output: Submit Button


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

Output: Image Button


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

Output: Reset Button


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

Output: Button


Input: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a valid URL [Description] An ECMAScript expression which returns the URI of the resource to be fetched. [Name]

Output: next

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it must be submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used to fetch the URL. post This indicates that the "POST" method must be used while submitting the URL to the server. [Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier which identifies the newly created session. [Name]

Output: sessionid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description] The character string returned must be interpreted as a time interval. This time interval must be interpreted by the new CCXML session as the maximum time it may wait for the completion of the fetch for the initial document specified by the next attribute. If the new CCXML session is unable to fetch the initial document within the timeout interval, an error.fetch event must be thrown. [Name]

Output: timeout

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age must be 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. [Name]

Output: maxage

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' 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. [Name]

Output: maxstale

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] name [Required] true [Type] string [Details]

Output: dialog.terminatetransfer

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Required] true [Type] string [Details]

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] false [Type] string [Details]

Output: The identifier of the connection to which the dialog connection is bridged (usually the connectionid that was specified in the dialogstart). If the dialog is bridged to a conference the value must be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Required] false [Type] string [Details]

Output: The identifier of the conference to which the dialog connection is bridged (usually the conferenceid that was specified in the dialogstart). If the dialog is bridged to a connection the value must be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] reason [Required] true [Type] string [Details]

Output: A string value specifying the reason the transfer needs to be returned.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Required] true [Type] string [Details]

Output: The unique identifier of the event source. This identifies the DIALOG Event I/O Processor that sent this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [Type] string [Details]

Output: The name of the Event I/O Processor that sent this event. This must be set to dialog as this is an event generated by the Dialog Session Event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] name [Type] string [Details] dialog.disconnect [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Type] string [Details] The ID of the dialog. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Type] string [Details] The identifier of the connection to which the dialog connection is bridged (usually the connectionid that was specified in the dialogstart). If the dialog is bridged to a conference the value must be undefined. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Type] string [Details] The identifier of the conference to which the dialog connection is bridged (usually the conferenceid that was specified in the dialogstart). If the dialog is bridged to a connection the value must be undefined. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Type] string valued array [Details] If the namelist attribute was specified in the Dialog's disconnect element, this property must be a string valued array of the names in the list. The length of the property must be equal to the number of names in the list. The actual values are stored in the "values" sub-object. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] values.* [Type] ECMAScript Object [Details] Each name in the namelist is a property whose value must be the value of the name at the time the Dialog's disconnect element was executed. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Type] string [Details] The unique identifier of the event source. This identifies the DIALOG Event I/O Processor that sent this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Type] string [Details] The name of the Event I/O Processor that sent this event. This must be set to dialog as this is an event generated by the Dialog Session Event processor. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [0] Name [1] Value [2]

Output: Description


Input: [0] charWidth [1] integer [2]

Output: the display width of a the text display device


Input: [0] charHeight [1] integer [2]

Output: the display height of a text display device


Input: [0] pix-x [1] integer [2]

Output: the display width of an image display device


Input: [0] pix-y [1] integer [2]

Output: the display height of an image display device


Input: [0] color [1] binary | grey | limited | mapped | full [2]

Output: an indication of the color capabilities of the device


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

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


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

Output: An ECMAScript expression which returns a string that is the identifier of a Connection, Dialog or Conference. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


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

Output: An ECMAScript expression which returns a string that is the identifier of a Connection, Dialog or Conference. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] duplex [Required] false [Type] ECMAScript Expression [Default Value] full [Valid Values] full half [Description]

Output: An ECMAScript expression that returns a character string equal to "half" or "full", which defines the direction of the media flow between id1 resource and id2 resource. Refer to the discussion of bridging in Section 10.4 . The duplex attribute determines whether the join must establish a half-duplex (unidirectional) or full-duplex (bi-directional) bridge. The following values can be used: full Specifies a full duplex bridge where the media flows in both directions. half Species a half duplex bridge where the media flows towards id1 resource, but no media flows from id1 resource to id2 resource.

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ECMAScript object returned contains information which may be used by the implementing platform or passed to the network when the two specified Connections, Dialogs or Conferences (id1 and id2) are joined. This information may consist of protocol-specific parameters. Note: The meaning of these hints is specific to the implementing platform and the underlying protocol.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] entertone [Required] false [Type] ECMAScript Expression [Default Value] 'true' [Valid Values] 'true' 'false' A Valid URL [Description]

Output: An ECMAScript expression that returns a character string that must be used to play a tone or a custom wav file to the conference participants when another caller joins. The following values can be used: 'true' Setting this to 'true' must play the default system beep. 'false' Setting this to 'false' must result in no alerting sound being played at all. A Valid URL The developer may also specify a URL value which points to a user-defined wav file to be played instead of the default system beep.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] exittone [Required] false [Type] ECMAScript Expression [Default Value] 'true' [Valid Values] 'true' 'false' A Valid URL [Description]

Output: An ECMAScript expression that returns a character string that must be used to play a tone or a custom wav file to the conference participants when another caller exits. The following values can be used: 'true' Setting this to 'true' will play the default system beep. 'false' Setting this to 'false' will result in no alerting sound being played at all. A Valid URL The developer may also specify a URL value which points to a user-defined wav file to be played instead of the default system beep.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] autoinputgain [Required] false [Type] ECMAScript Boolean Expression [Default Value] true [Valid Values] true false [Description]

Output: An ECMAScript Boolean expression that tells the conference mixer if it must use AGC to determine the input gain for a leg. If a platform does not support AGC, it must ignore this attribute. The following values can be used: true AGC must be used to determine input gain for a leg. false AGC must not be used.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] autooutputgain [Required] false [Type] ECMAScript Boolean Expression [Default Value] true [Valid Values] true false [Description]

Output: An ECMAScript boolean expression that tells the conference mixer if it must use AGC to determine the output gain for a leg. If a platform does not support AGC, it must ignore this attribute. The following values can be used: true AGC must be used to determine output gain for a leg. false AGC must not be used.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dtmfclamp [Required] false [Type] ECMAScript Boolean Expression [Default Value] true [Valid Values] true false [Description]

Output: An ECMAScript Boolean expression that tells the conference mixer if it must attempt to remove detected DTMF tones. If a platform does not support removal of DTMF tones, it must ignore this attribute. The following values can be used: true Conference mixer must attempt to remove detected DTMF tones. false Conference mixer must not attempt to remove any detected DTMF tones.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] toneclamp [Required] false [Type] ECMAScript Boolean Expression [Default Value] true [Valid Values] true false [Description]

Output: An ECMAScript Boolean expression that tells the conference mixer if it must attempt to remove loud single-frequency tones from the audio stream. If a platform does not support removal of tones, it must ignore this attribute. The following values can be used: true Conference mixer must attempt to remove loud single-frequency tones. false Conference mixer must not attempt to remove any loud single-frequency tones.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] name [Required] true [Type] string [Details]

Output: dialog.disconnect

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Required] true [Type] string [Details]

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] false [Type] string [Details]

Output: The identifier of the connection to which the dialog connection is bridged (usually the connectionid that was specified in the dialogstart). If the dialog is bridged to a conference the value must be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Required] false [Type] string [Details]

Output: The identifier of the conference to which the dialog connection is bridged (usually the conferenceid that was specified in the dialogstart). If the dialog is bridged to a connection the value must be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Required] false [Type] string valued array [Details]

Output: If the namelist attribute was specified in the Dialog's disconnect element, this property must be a string valued array of the names in the list. The length of the property must be equal to the number of names in the list. The actual values are stored in the "values" sub-object.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] values.* [Required] false [Type] ECMAScript Object [Details]

Output: Each name in the namelist is a property whose value must be the value of the name at the time the Dialog's disconnect element was executed.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Required] true [Type] string [Details]

Output: The unique identifier of the event source. This identifies the DIALOG Event I/O Processor that sent this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [Type] string [Details]

Output: The name of the Event I/O Processor that sent this event. This must be set to dialog as this is an event generated by the Dialog Session Event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] src [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter must load and begin execution upon startup. [Valid Values]

Output: a valid Dialog URL

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] prepareddialogid [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the src, type or namelist attributes. [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression which returns a dialog identifier of a dialog previously prepared by the execution of a dialogprepare element. If the specified dialog identifier refers to an unknown dialog or a dialog that has already been executed, by way of another dialogstart element, an error.dialogwrongstate event must be thrown. [Valid Values]

Output: a valid dialogid

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Description] An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files. [Valid Values]

Output: a Valid MIME Type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with the prepareddialogid attribute. [Type] Var List [Default Value] none [Description] A list of one or more whitespace separated CCXML variable names. These variables must be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of dialogterminate. [Valid Values]

Output: ECMAScript Variable

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Attribute Constraints] Must not be used with conferenceid. [Type] ECMAScript Expression [Default Value] none [Description] An Optional ECMAScript expression which returns the identifier of a connection. The specified connection must be associated with the dialog being prepared. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter must use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter must use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event must be thrown. [Valid Values]

Output: Connection IDs

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] conferenceid [Required] false [Attribute Constraints] Must not be used with connectionid. [Type] ECMAScript Expression [Default Value] none [Description] An Optional ECMAScript expression which returns the identifier of a conference bridge. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter must use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter must use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event must be thrown. [Valid Values]

Output: Conference IDs

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Attribute Constraints] If used in conjunction with prepareddialogid , the bridge type must match that used on the previous dialogprepare element. [Type] ECMAScript Expression [Default Value] both [Description] An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. If both the mediadirection and the prepareddialogid are specified and the bridge type specified by the mediadirection attribute does not match that used on the previous dialogprepare element, an error.dialog.notstarted event must be raised. If no value for the mediadirection attribute was specified on the previous dialogprepare element, any mediadirection type option may be specified. [Valid Values]

Output: both dialogtransmit dialogreceive

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The character string returned must be interpreted as a time interval. This 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. [Valid Values]

Output: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' 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. [Valid Values]

Output: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Valid Values]

Output: valid media encoding type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager. [Valid Values]

Output: get post

Voice Browser Call Control: CCXML Version 1.0


Input: [Module] Deployment [Term Name] Deployment [Type] class [Definition]

Output: The ongoing Process of Entities (for the purposes of this ontology, mainly sensors) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal.


Input: [Module] Deployment [Term Name] DeploymentRelatedProcess [Type] class [Definition]

Output: Place to group all the various Processes related to Deployment. For example, as well as Deplyment, installation, maintenance, deployment of further sensors and the like would all be classified under DeploymentRelatedProcess.


Input: [Module] Deployment [Term Name] deployedOnPlatform [Type] property [Definition]

Output: Relation between a deployment and the platform on which the system was deployed.


Input: [Module] Deployment [Term Name] deployedSystem [Type] property [Definition]

Output: Relation between a deployment and the deployed system.


Input: [Module] Deployment [Term Name] deploymentProcessPart [Type] property [Definition]

Output: Has part relation between a deployment process and its constituent processes.


Input: [Module] Deployment [Term Name] hasDeployment [Type] property [Definition]

Output: Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment.


Input: [Module] Deployment [Term Name] inDeployment [Type] property [Definition]

Output: Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment.


Input: [Module] PlatformSite [Term Name] Platform [Type] class [Definition]

Output: An Entity to which other Entities can be attached - particuarly Sensors and other Platforms. For example, a post might act as the Platform, a bouy might act as a Platform, or a fish might act as a Platform for an attached sensor.


Input: [Module] PlatformSite [Term Name] attachedSystem [Type] property [Definition]

Output: Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform.


Input: [Module] PlatformSite [Term Name] onPlatform [Type] property [Definition]

Output: Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion).


Input: [Module] OperatingRestriction [Term Name] MaintenanceSchedule [Type] class [Definition]

Output: Schedule of maintenance for a system/sensor in the specified conditions.


Input: [Module] OperatingRestriction [Term Name] OperatingProperty [Type] class [Definition]

Output: An identifiable characteristic of the environmental and other conditions in which the sensor is intended to operate. May include power ranges, power sources, standard configurations, attachments and the like.


Input: [Module] OperatingRestriction [Term Name] OperatingRange [Type] class [Definition]

Output: The environmental conditions and characteristics of a system/sensor's normal operating environment. Can be used to specify for example the standard environmental conditions in which the sensor is expected to operate (a Condition with no OperatingProperty), or how the environmental and other operating properties relate: i.e., that the maintenance schedule or power requirements differ according to the conditions.


Input: [Module] OperatingRestriction [Term Name] SurvivalProperty [Type] class [Definition]

Output: An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted.


Input: [Module] OperatingRestriction [Term Name] SurvivalRange [Type] class [Definition]

Output: The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold.


Input: [Module] OperatingRestriction [Term Name] SystemLifetime [Type] class [Definition]

Output: Total useful life of a sensor/system (expressed as total life since manufacture, time in use, number of operations, etc.).


Input: [Module] OperatingRestriction [Term Name] hasOperatingProperty [Type] property [Definition]

Output: Relation from an OperatingRange to a Property. For example, to a battery lifetime.


Input: [Module] OperatingRestriction [Term Name] hasOperatingRange [Type] property [Definition]

Output: Relation from a System to an OperatingRange describing the normal operating environment of the System.


Input: [Module] OperatingRestriction [Term Name] hasSurvivalProperty [Type] property [Definition]

Output: Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged.


Input: [Module] OperatingRestriction [Term Name] hasSurvivalRange [Type] property [Definition]

Output: A Relation from a System to a SurvivalRange.


Input: [Module] Skeleton [Term Name] FeatureOfInterest [Definition] A feature is an abstraction of real world phenomena (thing, person, event, etc). [Type]

Output: class


Input: [Module] Skeleton [Term Name] Observation [Definition] An Observation is a Situation in which a Sensing method has been used to estimate or calculate a value of a Property of a FeatureOfInterest. Links to Sensing and Sensor describe what made the Observation and how; links to Property and Feature detail what was sensed; the result is the output of a Sensor; other metadata details times etc. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Property [Definition] An observable Quality of an Event or Object. That is, not a quality of an abstract entity as is also allowed by DUL's Quality, but rather an aspect of an entity that is intrinsic to and cannot exist without the entity and is observable by a sensor. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Sensing [Definition] Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Sensor [Definition] A sensor can do (implements) sensing: that is, a sensor is any entity that can follow a sensing method and thus observe some Property of a FeatureOfInterest. Sensors may be physical devices, computational methods, a laboratory setup with a person following a method, or any other thing that can follow a Sensing Method to observe a Property. [Type]

Output: class


Input: [Module] Skeleton [Term Name] SensorInput [Definition] An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor. [Type]

Output: class


Input: [Module] Skeleton [Term Name] SensorOutput [Definition] A sensor outputs a piece of information (an observed value), the value itself being represented by an ObservationValue. [Type]

Output: class


Input: [Module] Skeleton [Term Name] Stimulus [Definition] An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor. [Type]

Output: class


Input: [Module] Skeleton [Term Name] detects [Definition] A relation from a sensor to the Stimulus that the sensor can detect. The Stimulus itself will be serving as a proxy for (see isProxyOf) some observable property. [Type]

Output: property


Input: [Module] Skeleton [Term Name] featureOfInterest [Definition] A relation between an observation and the entity whose quality was observed. For example, in an observation of the weight of a person, the feature of interest is the person and the quality is weight. [Type]

Output: property


Input: [Module] Skeleton [Term Name] forProperty [Definition] A relation between some aspect of a sensing entity and a property. For example, from a sensor to the properties it can observe, or from a deployment to the properties it was installed to observe. Also from a measurement capability to the property the capability is described for. (Used in conjunction with ofFeature). [Type]

Output: property


Input: [Module] Skeleton [Term Name] hasProperty [Definition] A relation between a FeatureOfInterest and a Property of that feature. [Type]

Output: property


Input: [Module] Skeleton [Term Name] implementedBy [Definition] A relation between the description of an algorithm, procedure or method and an entity that implements that method in some executable way. For example, between a scientific measuring method and a sensor the senses via that method. [Type]

Output: property


Input: [Module] Skeleton [Term Name] implements [Definition] A relation between an entity that implements a method in some executable way and the description of an algorithm, procedure or method. For example, between a Sensor and the scientific measuring method that the Sensor uses to observe a Property. [Type]

Output: property


Input: [Module] Skeleton [Term Name] isPropertyOf [Definition] Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature. [Type]

Output: property


Input: [Module] Skeleton [Term Name] isProxyFor [Definition] A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for. For example, the expansion of the quicksilver is a stimulus that serves as a proxy for temperature, or an increase or decrease in the spinning of cups on a wind sensor is serving as a proxy for wind speed. [Type]

Output: property


Input: [Module] Skeleton [Term Name] observationResult [Definition] Relation linking an Observation (i.e., a description of the context, the Situation, in which the observatioin was made) and a Result, which contains a value representing the value associated with the observed Property. [Type]

Output: property


Input: [Module] Skeleton [Term Name] observedBy [Type]

Output: property


Input: [Module] Skeleton [Term Name] observedProperty [Definition] Relation linking an Observation to the Property that was observed. The observedProperty should be a Property (hasProperty) of the FeatureOfInterest (linked by featureOfInterest) of this observation. [Type]

Output: property


Input: [Module] Skeleton [Term Name] ofFeature [Definition] A relation between some aspect of a sensing entity and a feature. For example, from a sensor to the features it can observe properties of, or from a deployment to the features it was installed to observe. Also from a measurement capability to the feature the capability is described for. (Used in conjunction with forProperty). [Type]

Output: property


Input: [Module] Skeleton [Term Name] sensingMethodUsed [Definition] A (measurement) procedure is a detailed description of a measurement according to one or more measurement principles and to a given measurement method, based on a measurement model and including any calculation to obtain a measurement result [VIM 2.6] [Type]

Output: property


Input: [Section] 2.0 Agreement scenarios [Feature/Operation] propID [Explanation]

Output: propID uniquely identifies any privacy proposal


Input: [Section] 3.1 Data transport [Feature/Operation] the HTML LINK tag [Explanation]

Output: agents and services must be able to locate a proposal in this location


Input: [Feature/Operation] the HTTP extension mechanism [Explanation]

Output: agents and services must be able to locate a proposal in this location


Input: [Feature/Operation] propURI [Explanation]

Output: a proposal must be able to be located at an external URI


Input: [Section] 4.1.2 XML/RDF encoding [Feature/Operation] XML parsing [Explanation]

Output: proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model.


Input: [Section] 4.4 Data References [Feature/Operation] data reference syntax [Explanation]

Output: agents must be able to understand that syntax of solicited information


Input: [Section] Base 3.0 Abstract Elements [Feature/Operation] abstract elements [Explanation]

Output: methods of references data exchanged through mechanisms other than P3P


Input: [Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary [Explanation]

Output: see the harmonized vocubarly for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure


Input: [0] doctype [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] implementation [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] documentElement [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElement [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createDocumentFragment [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createTextNode [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createComment [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createCDATASection [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createProcessingInstruction [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttribute [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createEntityReference [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagName [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] importNode [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElementNS [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttributeNS [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagNameNS [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementById [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [Item] W3C [Required?] all [Notes] Branding [Primary Audience]

Output: all


Input: [Item] WG/TF [Required?] all [Notes] Associated WG or Task Force [Primary Audience]

Output: potential participants


Input: [Item] Title [Required?] all [Primary Audience]

Output: all


Input: [Item] Pub date [Required?] all [Notes] Indication of out-of-date-ness / recency of change [Primary Audience]

Output: all


Input: [Item] Status [Required?] all [Notes] ED/WD/LC/CR/PR/REC/NOTE [Primary Audience]

Output: all


Input: [Item] Status disclaimer [Required?] all [Notes] Warn people the document is unstable, etc. [Primary Audience]

Output: new to reading W3C specs


Input: [Item] Copyright [Required?] all [Primary Audience]

Output: lawyers


Input: [Item] Patent Policy / Disclosures [Required?] some [Primary Audience]

Output: laywers


Input: [Item] Errata [Required?] REC [Notes] Only if there's errata [Primary Audience]

Output: implementers, reviewers


Input: [Item] Issues list [Required?] all? [Primary Audience]

Output: reviewers


Input: [Item] At-risk list [Required?] LC/CR [Primary Audience]

Output: W3C


Input: [Item] Discussion fora / Feedback [Required?] all [Notes] Mailing list, IRC, wiki, bugtracker, etc. [Primary Audience]

Output: reviewers


Input: [Item] Editor's draft [Required?] most [Primary Audience]

Output: reviewers, implementers


Input: [Item] Previous version(s) [Required?] all [Primary Audience]

Output: reviewers


Input: [Item] Test suite Link [Required?] CR/REC [Primary Audience]

Output: implementers, contributors


Input: [Item] Editors [Required?] all [Notes] Tells people who to talk to and who can fix issues [Primary Audience]

Output: participants


Input: [Item] Translations [Required?] some [Primary Audience]

Output: non-English speakers


Input: [Item] Other formats [Required?] some [Notes] Links to other formats suitable for offline/printing; particularly useful for multipage specs [Primary Audience]

Output: all


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

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

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

Output: showed blank page

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


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

Output: failed correctly while parsing the DTD

XHTML media type test - results: Netscape Browser 8.0.2 (IE)


Input: [Code] 0 [Situation]

Output: The transaction failed for reasons unrelated to the database itself and not covered by any other error code.


Input: [Code] 1 [Situation]

Output: The statement failed for database reasons not covered by any other error code.


Input: [Code] 2 [Situation]

Output: The statement failed because the expected version of the database didn't match the actual database version.


Input: [Code] 3 [Situation]

Output: The statement failed because the data returned from the database was too large. The SQL "LIMIT" modifier might be useful to reduce the size of the result set.


Input: [Code] 4 [Situation]

Output: The statement failed because there was not enough remaining storage space, or the storage quota was reached and the user declined to give more space to the database.


Input: [Code] 5 [Situation]

Output: The statement failed because the transaction's first statement was a read-only statement, and a subsequent statement in the same transaction tried to modify the database, but the transaction failed to obtain a write lock before another transaction obtained a write lock and changed a part of the database that the former transaction was depending upon.


Input: [Code] 6 [Situation]

Output: An INSERT, UPDATE, or REPLACE statement failed due to a constraint failure. For example, because a row was being inserted and the value given for the primary key column duplicated the value of an existing row.


Input: [Term Name] System [Type] class [Definition] System is a unit of abstraction for pieces of infrastructure (and we largely care that they are) for sensing. A system has components, its subsystems, which are other systems. [Module]

Output: System


Input: [Term Name] hasSubSystem [Type] property [Definition] Haspart relation between a system and its parts. [Module]

Output: System


Input: [Term Name] Input [Type] class [Definition] Any information that is provided to a process for its use [MMI OntDev] [Module]

Output: Process


Input: [Term Name] Output [Type] class [Definition] Any information that is reported from a process. [MMI OntDev] [Module]

Output: Process


Input: [Term Name] Process [Type] class [Definition] A process has an output and possibly inputs and, for a composite process, describes the temporal and dataflow dependencies and relationships amongst its parts. [SSN XG] [Module]

Output: Process


Input: [Term Name] hasInput [Type] property [Module]

Output: Process


Input: [Term Name] hasOutput [Type] property [Module]

Output: Process


Input: [Term Name] isProducedBy [Type] property [Definition] Relation between a producer and a produced entity: for example, between a sensor and the produced output. [Module]

Output: Process