task
stringlengths
12
101
input
stringlengths
5
5.87k
output
stringlengths
1
5.47k
options
sequence
pageTitle
stringlengths
0
151
outputColName
stringlengths
1
142
url
stringlengths
24
147
wdcFile
stringlengths
71
75
32d780fa_mantic_Sensor_Network_Ontology__Type
[Module] Skeleton [Term Name] FeatureOfInterest [Definition] A feature is an abstraction of real world phenomena (thing, person, event, etc). [Type]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[Module] Skeleton [Term Name] Sensing [Definition] Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon. [Type]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
class
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[Module] Skeleton [Term Name] hasProperty [Definition] A relation between a FeatureOfInterest and a Property of that feature. [Type]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[Module] Skeleton [Term Name] isPropertyOf [Definition] Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature. [Type]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[Module] Skeleton [Term Name] observedBy [Type]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
32d780fa_mantic_Sensor_Network_Ontology__Type
[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]
property
[ [ "c", "l", "a", "s", "s" ], [ "p", "r", "o", "p", "e", "r", "t", "y" ] ]
Semantic Sensor Network Ontology
Type
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_28.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] 2.0 Agreement scenarios [Feature/Operation] propID [Explanation]
propID uniquely identifies any privacy proposal
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] 3.1 Data transport [Feature/Operation] the HTML LINK tag [Explanation]
agents and services must be able to locate a proposal in this location
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Feature/Operation] the HTTP extension mechanism [Explanation]
agents and services must be able to locate a proposal in this location
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Feature/Operation] propURI [Explanation]
a proposal must be able to be located at an external URI
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] 4.1.2 XML/RDF encoding [Feature/Operation] XML parsing [Explanation]
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.
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] 4.4 Data References [Feature/Operation] data reference syntax [Explanation]
agents must be able to understand that syntax of solicited information
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] Base 3.0 Abstract Elements [Feature/Operation] abstract elements [Explanation]
methods of references data exchanged through mechanisms other than P3P
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
53c83d2a_WD_P3P_syntax_19981109__Explanation
[Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary [Explanation]
see the harmonized vocubarly for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure
[]
WD-P3P-syntax-19981109
Explanation
http://www.w3.org/TR/1998/WD-P3P-19981109/syntax
28/1438042990112.92_20150728002310-00259-ip-10-236-191-2_807232087_1.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] doctype [1] ro attribute [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] implementation [1] ro attribute [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] documentElement [1] ro attribute [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createElement [1] method [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createDocumentFragment [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createTextNode [1] method [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createComment [1] method [2] no [3]
no
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createCDATASection [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createProcessingInstruction [1] method [2] no [3]
no
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createAttribute [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createEntityReference [1] method [2] no [3]
no
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] getElementsByTagName [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] importNode [1] method [2] no [3]
no
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createElementNS [1] method [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] createAttributeNS [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] getElementsByTagNameNS [1] method [2] no [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
3b4906f0_ofiles__SVG_Tiny_and_SVG_Basic__3
[0] getElementById [1] method [2] yes [3]
yes
[ [ "y", "e", "s" ], [ "n", "o" ] ]
Mobile SVG Profiles: SVG Tiny and SVG Basic
3
http://www.w3.org/TR/2003/REC-SVGMobile-20030114/
28/1438042990112.92_20150728002310-00143-ip-10-236-191-2_824649584_23.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] W3C [Required?] all [Notes] Branding [Primary Audience]
all
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] WG/TF [Required?] all [Notes] Associated WG or Task Force [Primary Audience]
potential participants
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Title [Required?] all [Primary Audience]
all
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Pub date [Required?] all [Notes] Indication of out-of-date-ness / recency of change [Primary Audience]
all
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Status [Required?] all [Notes] ED/WD/LC/CR/PR/REC/NOTE [Primary Audience]
all
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Status disclaimer [Required?] all [Notes] Warn people the document is unstable, etc. [Primary Audience]
new to reading W3C specs
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Copyright [Required?] all [Primary Audience]
lawyers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Patent Policy / Disclosures [Required?] some [Primary Audience]
laywers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Errata [Required?] REC [Notes] Only if there's errata [Primary Audience]
implementers, reviewers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Issues list [Required?] all? [Primary Audience]
reviewers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] At-risk list [Required?] LC/CR [Primary Audience]
W3C
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Discussion fora / Feedback [Required?] all [Notes] Mailing list, IRC, wiki, bugtracker, etc. [Primary Audience]
reviewers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Editor's draft [Required?] most [Primary Audience]
reviewers, implementers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Previous version(s) [Required?] all [Primary Audience]
reviewers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Test suite Link [Required?] CR/REC [Primary Audience]
implementers, contributors
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Editors [Required?] all [Notes] Tells people who to talk to and who can fix issues [Primary Audience]
participants
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Translations [Required?] some [Primary Audience]
non-English speakers
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
83458046_rod_Restyle_Content___W3C_Wiki__Primary_Audience
[Item] Other formats [Required?] some [Notes] Links to other formats suitable for offline/printing; particularly useful for multipage specs [Primary Audience]
all
[]
SpecProd/Restyle/Content - W3C Wiki
Primary Audience
http://www.w3.org/wiki/index.php?title=SpecProd/Restyle/Content&oldid=55885
28/1438042989301.17_20150728002309-00017-ip-10-236-191-2_826237735_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
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)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
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)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
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)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
recognized as XML, parsing failed due to the omitted namespace declaration
[]
XHTML media type test - results: Netscape Browser 8.0.2 (IE)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
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)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
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)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
showed blank page
[]
XHTML media type test - results: Netscape Browser 8.0.2 (IE)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
b5fcb736_s__Netscape_Browser_8_0_2__IE___application_xml
[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]
failed correctly while parsing the DTD
[]
XHTML media type test - results: Netscape Browser 8.0.2 (IE)
application/xml
http://www.w3.org/People/mimasa/test/xhtml/media-types/Netscape8.0.2-IE
28/1438042990112.92_20150728002310-00210-ip-10-236-191-2_824241343_0.json
ffd5995a_HTML_5__Situation
[Code] 0 [Situation]
The transaction failed for reasons unrelated to the database itself and not covered by any other error code.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 1 [Situation]
The statement failed for database reasons not covered by any other error code.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 2 [Situation]
The statement failed because the expected version of the database didn't match the actual database version.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 3 [Situation]
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.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 4 [Situation]
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.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 5 [Situation]
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.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
ffd5995a_HTML_5__Situation
[Code] 6 [Situation]
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.
[]
HTML 5
Situation
http://www.w3.org/TR/2009/WD-html5-20090212/structured-client-side-storage.html
28/1438042990112.92_20150728002310-00140-ip-10-236-191-2_822061705_0.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[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]
System
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] hasSubSystem [Type] property [Definition] Haspart relation between a system and its parts. [Module]
System
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] Input [Type] class [Definition] Any information that is provided to a process for its use [MMI OntDev] [Module]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] Output [Type] class [Definition] Any information that is reported from a process. [MMI OntDev] [Module]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[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]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] hasInput [Type] property [Module]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] hasOutput [Type] property [Module]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
0abc4a22_mantic_Sensor_Network_Ontology__Module
[Term Name] isProducedBy [Type] property [Definition] Relation between a producer and a produced entity: for example, between a sensor and the produced output. [Module]
Process
[ [ "S", "y", "s", "t", "e", "m" ], [ "P", "r", "o", "c", "e", "s", "s" ] ]
Semantic Sensor Network Ontology
Module
http://www.w3.org/2005/Incubator/ssn/ssnx/ssn.html
28/1438042989301.17_20150728002309-00046-ip-10-236-191-2_806819312_50.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 53 [Status] Closed [Commenter] Kathy Wahlbin [Location] Scope of Applicability [Current text] "Note: Websites using responsive design techniques (i.e. adapting the presentation according to user hardware, software, and preferences) as opposed to redirecting the user to a different location are not considered to be independent website versions". [Rationale] Clarify what is needed for evaluating responsive websites. [Resolution] Resolution: Add a section on "Websites using responsive design" under "Particular Types of Websites" to elaborate on the need to test the different adaptations and breakpoints using a variety of user agents (tablets, phones, etc.). Rationale: More information about responsive design is needed but adding it to this particular note will not be as useful. See also Eval TF minutes of 9 January 2014. [Suggested Change]
"Note: Websites using responsive design techniques (i.e. adapting the presentation according to user hardware, software, and preferences) as opposed to redirecting the user to a different location are not considered to be independent website versions unless the site at the different breakpoints utilizes different code. In that case, the website at the different breakpoints could be considered as individual websites each for evaluation".
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 55 [Status] Closed [Commenter] Kerstin Probiesch [Location] Scope of Applicability [Current text] "When a target website is defined for evaluation, it is essential that all web pages, web page states, and functionality within the scope of this definition are considered for evaluation". [Rationale] - [Resolution] Resolution: Change the note in the definition of "web page" to read "Web pages may include multimedia content, interactive components, and rich and mobile web applications. Web pages are not limited to HTML and can be PDF documents and any other format." Rationale: Explaining this point in the definition of the term "web page" has a more global impact throughout the document. [Suggested Change]
should be made clear that also PDF and other formats have to be considered for evaluation and that not only HTML is meant
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 56 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "Examples of Websites". [Rationale] The case where the responsibility for content publishing of each department is distributed, is typical and relevant enough to be mentioned among the list of examples (even though is later dealt with in detail, in the discussion on websites with separable areas) [Resolution] Resolution: No change. Rationale: The reference to "organizational department" was removed because it was not immediately clear that it only applies to such cases where they are separable areas. [Suggested Change]
Add another example corresponding to the website of an organization department.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 57 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "This includes (...) forms for online payments, and discussion boards, including when such parts originate from third-party sources". [Rationale] Make the information more explicit. [Resolution] Resolution: Move the second paragraph of the example to outside the example. Rationale: That would make the text part of the main section rather than of the example alone. [Suggested Change]
Add this information outside the example as well.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 58 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "Example of Website Enclosure" and "Particular Types of Websites" sections. [Rationale] "Example of Website Enclosure" relies on the definition of "Website with separable areas" (included in "Particular Types of Websites"). [Resolution] Resolution: No change. Rationale: The term "separable areas" is not used anywhere in "Example of Website Enclosure". [Suggested Change]
Exchange the order of these two subsections.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 59 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "Web applications will typically require (...) larger web page samples to reflect the different types of content, functionality, and processes." [Rationale] In my understanding, the amount of "different types of content, functionality and processes" does not depend on being a web application per se. On the contrary, if the same functions are offered through a static site and a dynamic web application, the same complexity should be expected. Besides, even some web applications are more homogeneous than static web sites, in that all the contents are generated from the same templates and scripts, and then a smaller sample is enough. Step 3 talks about "How interactive the content is", which is a much more objective foundation to determine that a sample should be larger, rather than just relying on the fact the functionality is provided through a web application. [Resolution] Resolution: No change. Rationale: This section refers to web applications that "tend to be more complex and interactive" such as "webmail clients, document editors, and online shops". These *typically* tend to require larger samples. [Suggested Change]
Check whether this is substantiated or just assumed.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 60 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "are each independent of one another in usage, where using one version does not require or depend on using another version of the website" [Rationale] clarify the wording. [Resolution] Resolution: Change as suggested. Rationale: Better language. [Suggested Change]
"are independent of one another in use, that is, using one version does not require or..."
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 61 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "In this context evaluators often have easier access to the website developers and maintainers, the development environment and authoring tools, and the materials used for development." [Rationale] Being able to "get into the kitchen" eases accessibility evaluation. Not only is it a matter of snooping around development processes, but it also facilitates access to later stages. E.g. self-assessment may ease accessing restricted areas (which is unrelated to accessing development). [Resolution] Resolution: Change to "In this context evaluators often have easier access to the website developers and maintainers, the development and hosting environments, the authoring tools, and the materials used for development and maintenance." Rationale: Clearer meaning. [Suggested Change]
"... and the hosting platform where the website is deployed".
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 62 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] "Third-party evaluators typically use pure black-box testing and … Therefore it is more difficult, often impossible, to make conformance claims based on such an evaluation alone." [Rationale] First, black-box testing means 'no access to the internals of the software', instead of 'no access to the development environment (and authoring tools)'. Second, in the specific context of website evaluation accessibility, third-party evaluators usually do have access to a large part of the source code (e.g. HTML, CSS, Javascript), which even sometimes represents all the source code (e.g. in static websites, where there is no server-side scripting environment). Thus these tests are rather grey-box (or even white-box). Third, WCAG success criteria are defined from the perspective of the end-user, so black-box testing should not be in principle excluded as a way to test conformance. For instance, the evaluator does not need to know whether device-independent scripting events have been used -i.e. black box-, they just need to check the functionality is available from a keyboard -white box-. [Resolution] Resolution: Change section to read "Third-party evaluators typically have little information about how a website was developed, its internal software, and all its areas and functionality. Therefore it is more difficult, often impossible, to make conformance claims for entire websites based on such an evaluation alone. However, such evaluation can be effective for validating conformance claims and statements about websites." Rationale: Clearer meaning. [Suggested Change]
-
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 63 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] in "Example of Web site enclosure", it is said that the scope of evaluation includes "aggregated and embedded content (...) including when such parts originate from third-party sources". Later on, in "Particular Evaluation Contexts", it is said that "third-party content is not under the control of the website or web service providers (...) non-conforming content needs to be clearly identified in the web pages in which it appears". [Rationale] The same term "third-party" is used for two different concepts that require two different approaches, this may confuse the readers. [Resolution] Resolution: No change. Rationale: Section "Principle of website enclosure" states that all third-party content in scope must be included in the evaluation while section "evaluating third-party content" explains how to go about with this type of content; the sections do not contradict. [Suggested Change]
Distinguish between these two uses of "third-party content". One refers to content integrated from external sources, but which is part of the scope, so as to consider complete processes. The other refers to user-generated contents, which can be either repaired or excluded from the scope through a statement of partial conformance.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 64 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] Bullet list under "Re-Running Website Evaluation". [Rationale] In the previous working draft, the phrases "as per step x.x" appeared at the end of each item. They have been removed to make the structure clearer, but at the same time the whole section has been shifted and now appears before the methodology steps. With the current wording, "exemplar web page instances" are mentioned before they are explained in the methodology. [Resolution] Resolution: Link to particular section 3.c Rationale: In the previous text all links lead to the same section (step 3), which wasn't really useful. That is why we took the links out. [Suggested Change]
Add links from each item to the relevant steps.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 66 [Status] Closed [Commenter] Samuel Martin [Location] Scope of Applicability [Current text] - [Rationale] Security and privacy issues may appear when following this methodology, and evaluators should be aware of that, so as to take whatever measures (out of the scope of WCAG-EM) they consider. Different kinds of standards usually add a section on potential security risks. In any case, not sure if it fits in "Particular Evaluation Contexts", or they should be added directly to Step 2 and Step 5.b respectively. [Resolution] Resolution: Add "Granting evaluators such access may require particular security and privacy precautions" to the corresponding note in Step 2, and a new "Note: Records of the evaluation specifics may include sensitive information such as internal code, passwords, and copies of data. They may need particular security and privacy precautions to secure." to section 5.b. Rationale: Better to address directly in the corresponding sections. further not role of document but of evaluator and evaluation commissioner to point to legal issues besides W3C legal and copyright notices. See also comment 41. [Suggested Change]
Add an explanation of the security and privacy issues that may be involved when following this methodology.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json
6af9bb7a__Editor_Draft_29_November_2013__Suggested_Change
[ID] 67 [Status] Closed [Commenter] Michael Cooper [Location] Scope of Applicability [Current text] - [Rationale] - [Resolution] Resolution: No change. Rationale: Both single pages and aggregated websites are in scope; the intent is to specifically address *any* type of website. [Suggested Change]
Think it would be useful to add examples of what is *not* in scope, e.g., single pages, aggregated sites, etc.
[]
Disposition of Comments - WCAG-EM Editor Draft 29 November 2013
Suggested Change
http://www.w3.org/WAI/ER/conformance/comments-20131129
28/1438042989301.17_20150728002309-00006-ip-10-236-191-2_824175729_4.json