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
|
|---|---|---|---|---|---|---|---|
a54af633_HTML_5__dataTransfer | [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [dataTransfer] | Empty | [] | HTML 5 | dataTransfer | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
a54af633_HTML_5__dataTransfer | [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [effectAllowed] Same as last event [dropEffect] none [Default Action] None [dataTransfer] | Empty | [] | HTML 5 | dataTransfer | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
a54af633_HTML_5__dataTransfer | [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [dataTransfer] | Empty | [] | HTML 5 | dataTransfer | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
a54af633_HTML_5__dataTransfer | [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [dataTransfer] | getData() returns data set in dragstart event | [] | HTML 5 | dataTransfer | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
a54af633_HTML_5__dataTransfer | [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [dataTransfer] | Empty | [] | HTML 5 | dataTransfer | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2834 Tim Berners-Lee (archived comment) [Working Group decision] The LDP specification brings several features such as paging and containers that are useful even in case of a read-only server. As for PATCH, everybody wants it but given the lack of a standard PATCH format and the WG timeframe it is unpractical for LDP to make PATCH mandatory. The WG is however committed to encourage support for PATCH and will do so via the LDP Best Practices and Guidelines document the WG plans to publish as a Note. As soon as a standard PATCH format is available the WG will revise the LDP spec to make use of it. [Commentor reply] tocheck [Comment] | 4.5.6. You allow servers which do not support PUT or PATCH or POST. Why? A client using such a server will have no write ability at all, and so your spec as a protocol delivers zero value on top of HTTP GET. Suggest change all to MUST, or make two levels of server, one which supports PUT and PATCH and no collections, and one which supports everything. ... 4.8 PATCH is optional. Suggest a MUST. PATCH is to first order the only thing LDP provides over WebDav. 4.8.2 MUST Suggest specify a the subset of sparql-update we use at the moment as a mandatory patch format to get basic interop, with possible later extension to other languages. ******* Something I mentioned in a mail a long time ago is the necessity of doing atomic flag (P/V) operations with a PATCH. To recap, you have to be able to do a form of DELETE triple(s) which will FAIL and prevent any corresponding INSERT from happening. This is top be able to allocate shared resources. Eg DELETE { :x :nextID 4 } INSERT DATA { ?x :nexID 5 }. Hmm. Maybe this is covered by the ETag system sufficiently. If so, the case should be given as an worked example and put in as a test case. A collaborative system which allows atomic flag setting is fundamentally more valuable than one which doesn't. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2835 Tim Berners-Lee (archived comment) [Working Group decision] OPTIONS is not required to achieve this. It could be used in cases when a client wants a low-cost means to learn more about the resource identified by the URI if it hasn't already done a GET. If it has done a GET and kept the header information, there is no need to use OPTIONS. [Commentor reply] tocheck [Comment] | 4.9.1 Servers must support the OPTIONS method. Why? Should there be a basic level of functionality which any LDPR allows and which does not require OPTIONS polling? OPTIONS is expensive: another round trip. Always avoid an extra round trip if you can. We need this system to move really fast. Round trips show up as user interface sluggishness, user task inefficiency, and lost/bored users. Note that OPTIONs is resource-specific. (Unless you use some sort of wildcard extension or a POWDER label say). You have to do it for every fresh URI you find. The Linked Data operation is a GET. Is the basic operation for an LDP-capable client always OPTIONS, GET, or GET, OPTIONS? Maybe key headers can be put into the HEAD and GET response. Maybe the class of resource announced with Link: rel=type can have a URI which can be looked up itself and cached. and will give the set of features in a standard way. Suggest define a core LDP protocol which does NOT use OPTIONS, by assuming that the core functionality is enough for clients to do what they need. Clients needing extensions maybe can use OPTIONS. But maybe POWDERR should be preferred. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2812 Mark Baker (archived comment) [Working Group decision] Thank you for your feedback Mark. While we didn't go as far as rewriting section 4 entirely, we've modified it to ensure that the specification doesn't seem to be redefining HTTP which was never the intent. http://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#conformance clarifies the overall relationship between LDP and HTTP; 4.6.1 was removed entirely as a result. http://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#base-specs and http://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpclient were added to clarify consequences of base specs and how LDP clients differ from HTTP clients. 4.11 (at risk) was removed entirely. [Commentor reply] yes [Comment] | Hi. I raised this issue before, but it was never resolved to my satisfaction, so I'm raising it again now at LC. Sec 4.6.1 says "LDPR servers must remove the resource identified by the Request-URI. After a successful HTTP DELETE, a subsequent HTTP GET on the same Request-URI must result in a 404 (Not found) or 410 ". This is bad because it redefines HTTP DELETE, which already has a well defined meaning in RFC 2616. The definition in 4.6.1 is more specific than the one in 2616, and it's why you need the LDP-specific Link response header which basically tells the client that the 200 response doesn't mean what it says in RFC 2616, but instead what it says in LDP 1.0. The correct way to do this is to simply reuse the definition in 2616 so that the client knows nothing about the state of server after a DELETE has completed. I'm not familiar with the use case that requires those post conditions on DELETE, but from experience I can't imagine why a client would need to depend on this specific behaviour. Let me be clear though, my concern is *only* with the interface between client and server, not with server behaviour. If you want to define that LDP servers have to behave in a certain way, go nuts. But as soon as that information leaks into the interface, you've crossed a line, leaking implementation details so that the client is coupled not to the interface, but the implementation. The same problem with DELETE exists elsewhere in section 4 too, including with PUT, though the definition seems close enough to 2616 that I'm not sure why it's being redefined. So in addition to those concerns about section 4, I'm also concerned with the requirements on client implementations and don't understand why they're necessary. Some seem purely superfluous, such as 4.3.5, as it's part and parcel of the RDF model that resources can have multiple types (not to mention the open world assumption). The same goes for 4.3.6. 4.5.2 falls under this category too because that behaviour is just one possible path through HTTP's conflict detection mechanism. 4.5.3 and 4.5.4 seem more like BCPs that anything needing to be conformance criteria. 4.5.5 just seems like a badly phrased constraint on server implementation that has nothing to do with a client. 4.11.3.3 says that a client shouldn't invoke GET, really? Are you concerned about DoS issues like the W3C's DTD problem? http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ There's no reason to make this a criterion of correct client behaviour AFAICT 4.11.3.4 also seems like it's part and parcel with the RDF model In short, I think section 4 needs to be completely rewritten so that it; - contains no client conformance criteria - contains no interface conformance criteria In addition, the mandatory Link header should be removed so that clients won't be tempted to treat server behaviour implementation conformance criteria as interface conformance criteria; all LDP servers would be indistinguishable from Web servers. Thanks. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2833 Tim Berners-Lee (archived comment) [Working Group decision] The specification was changed to prevent silent loss of data. See http://www.w3.org/2013/meeting/ldp/2013-10-21#resolution_2 Many MAYs and SHOULDs have been changed to MUSTs as requested. See http://www.w3.org/2013/meeting/ldp/2013-10-21#resolution_3 However, imposing creation of resources via PUT is deemed unpractical at this time. See http://www.w3.org/2013/meeting/ldp/2013-11-04#resolution_3 [Commentor reply] tocheck [Comment] | I have comments at various levels. Two things concern me mainly, firstly that the LDP platform will support the functionality which the RWW community has been using, including tabulator-based apps, and the second if that the platform in general provide a in interoperable functionality between compliant client and server. This last is threatened mainly by the huge number of SHOULD's for the server where I would have expected MUSTs to get interoperability, and a persistent theme throughout the spec the actual behavior a client or a server can expect of the other party relies completely on out-of-band agreements. To the extent that that is true, the document does not define an interoperable system. I'll go though in document order now. [...] 4.2.9 This is an example of a complete interop gap. The server might or might not mess with your triples in any way defined elsewhere. I suggest defining a clean simple high-interop version of the server in which the server doesn't mess with or constrain the client application at all. This is a really important use case. For the RWW world, LDP storage must be generic storage which be used with any app. Maybe we can make a profile of this spec for this case, with no domain knowledge or behavior in the server. If not, we have a problem. 4.2.10 "Conservative clients"?? you already have MUST and MAY, but now (and elsewhere) you have conservative (and presumably liberal) clients. If you want to create a new conformance class Conservative Client, by all means do so, but declare it in the Conformance section and SAY WHAT YOU GET from each level of conformance. A client is not an animal tiptoeing gingerly or not into the wide world out there, it is a small hard part of a machine which either works or doesn't work. The phase occurs elsewhere too. It is a red flag. (Why would a client want to be conservative? What is risked by not being? What would a liberal client do? Does this mean the server needs to be more specified to eliminate the risk) I would strongly support as an exercise looking at a version of the spec with everything which is not mandatory removed, and see what you end up being able to do with it. 4.3.4. Broken. No guarantee that anything will work. Suggest strongly the following:- LDP Clients MUST either give no accept header or must give a header which includes at least text/turtle and has NO OTHER mime type with a higher q. LDP servers, which a GET is received on a LDPR, if text/turtle is present and there is no other mime type with a higher q, they MUST return turtle. If there is no Accept header, they must return turtle. Protocol value: If a LDP client goes a GET it will get the data in turtle. Interop is achieved. This provides interoperability and also is compatible with HTTP. It allows existing conneg software to be used, and allows LDP to work within a general conneg-based server serving other things too. 4.5.6. You allow servers which do not support PUT or PATCH or POST. Why? A client using such a server will have no write ability at all, and so your spec as a protocol delivers zero value on top of HTTP GET. Suggest change all to MUST, or make two levels of server, one which supports PUT and PATCH and no collections, and one which supports everything. 4.5.2 Same sort of problem. Are you preventing data loss or not? Suggest yes. Clients MUST use If-match and Servers MUST implement it (which may men ignoring it in a case where you know nothing else can change the data). Protocol value: Changes from others are never overwritten. 4.5.4 A server which throws out random triples is hard as a basis for RWW applications. We must have a profile in which the server has no domain knowledge. 4.5.6 MUST allow PUT. Otherwise, what is the point? (Note that for clients which use PUT To make resources in system that looks like a unix file system, servers will have to generate intermediate directories. It is very useful for servers to be able to map a unix-like file system, for many reasons, including the isomorphisms between remote and local storage. So the use case in which the LDP server is a big unix file system but with PATCH as a performance enhancement is important. This doesn't affect the spec in any normative way I can see.) In this case, objects are not made by POST to a collection, but being mentioned in a a new file with PUT and then later PATCH. 4.5.7 MUST not SHOULD. 4.6.2 Another totally grey area. When you DELTE a resource, the server may or may not remove triples with that subject from other resources. (When you delete R, any quad R P O R2) may be deleted. This is ripe for a profile, and in that profile the value of what happens must be explained. E.G. when you delete R then R is removed from any containers, so there is no C member R *on this server* or on some other URI region. This is hairy feature, as of course, as it can't apply to triples stored on another server, so people splitting data across different servers will get unexpected results. This sounds like another protocol which needs a lot more thought. For now, suggest the LDP spec doe snot specify such behaviour, maybe flag magic triple side effects as possible extension spec in future. [...] 4.10.2.1 "Conservative clients" again. Explain the value of doing this or not doing it. 4.10.2.2 Servers MAY do it. That means clients MUST handle it. 4.10.2.3. MUST | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2836 Tim Berners-Lee (archived comment) [Working Group decision] Given the time constraints under which the WG is it is deemed unpractical to depend on defining a new response code as suggested. However, based on input from several HTTP experts the WG decided to return the first page with 200 response code on initial GET which prevents the additional roundtrip you objected to. See http://www.w3.org/2013/meeting/ldp/2013-11-04#resolution_2 Move Paging information out of the RDF content into HTTP headers. See http://www.w3.org/2013/meeting/ldp/2013-09-30#resolution_2 [Commentor reply] tocheck [Comment] | ######################### 4.10.2.3 303 lis a basically very unsatisfactory design because of the round trip. As this is a new spec, suggest defined 20X code meaning like a 303 but containing the representation of the thing 303d to. This has been found to a problem in LD. LDP can avoid it now. Benefit: First page back to user in one less round trip. ######################### 4.10.2.4.3 This design puts the type and next links in the data. I prefer I think using HTTP headers here as elsewhere. Page control stuff is very meta, messy to have it in with actual data. Not a problem for containers, but for normal LDPRs IMHO. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2837 Tim Berners-Lee (archived comment) [Working Group decision] Drop inlining from the spec, put it on the wish list for LDPnext See http://www.w3.org/2013/meeting/ldp/2013-09-12#resolution_2 [Commentor reply] tocheck [Comment] | 4.11.1 "LDP does not provide clients with any way to detect whether or not the server is capable of inlining (all its resources or any specific resource), nor does it provide clients with any way to influence which (if any) resources are inlined in any given response." This implies cleints must all be able to handle inlining and recover from it if they didn't really want it. Need to define a protocol here properly or abandon the feature. (N3 or one of its weak imitations is obviously a clear choice for a inlined data, as it allows you to preserve the provenance, and basically explain which triples are from which resource. I understand this would frighten people at this stage.) | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2813 Ashok Malhotra (archived comment) [Working Group decision] Dispose of LC-2813 by adding a non-normative section on security setting the expectation right, pointing out that this isn't covered in LDP See http://www.w3.org/2013/meeting/ldp/2013-09-12#resolution_5 See new Security Considerations section https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#security [Commentor reply] yes [Comment] | The spec says nothing about access control. Give that we are discussing read-write capabilities should we add some words like “To work with LDPRs clients must be authorized by the server and must have appropriate access control permissions”? | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2814 Ashok Malhotra (archived comment) [Working Group decision] Same as LC-2813. [Commentor reply] yes [Comment] | The spec also says nothing about authentication. Should we specify some minimum level of authentication, for example: LDP servers that require authentication SHOULD consider supporting basic authentication as specified in *[**RFC2617]*** over HTTPS for the highest level of interoperability with generic clients. They MAY also support other authentication methods. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2815 Ashok Malhotra (archived comment) [Working Group decision] Added some informative content to 5.1.2 Ordering section. [Commentor reply] tocheck [Comment] | We discussed that LDPCs are a subclass of LDPRs and so containers can be members of other containers. Do we say that somewhere? I could not find such a statment. Perhaps we need to add it. Also, of a container contains other containers, how would ordering work? | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2816 Ashok Malhotra (archived comment) [Working Group decision] Erroneous comment. See http://lists.w3.org/Archives/Public/public-ldp-comments/2013Aug/0005.html [Commentor reply] yes [Comment] | Some comments on section 5.1.4 Ordering 1. Why is this section non-normative, given that it defines ldp:containerSortCriteria and ldp:containerSortPredicate | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2838 Tim Berners-Lee (archived comment) [Working Group decision] This is defined by the response header of the form: Link: rel="http://www.w3.org/ns/ldp#nonMemberResource" This is detailed in section 5.9.1 http://www.w3.org/TR/2013/WD-ldp-20130730/#ldpc-5_9_1 [Commentor reply] tocheck [Comment] | How does a client find the non-member-property version of a resource R? | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2839 Tim Berners-Lee (archived comment) [Working Group decision] Changed the offending text to clarify intent and use inspect rather than introspect per Tim's recommendation. [Commentor reply] tocheck [Comment] | 4.10.1 "The triples in the representation of the each page are typically a subset of the triples in the resource - same subject, predicate and object." Same triples then? eh? I prefer the word "inspect" for the way "introspect" is used in the document. "Introspection" is normally looking into oneself, not into something else. | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
bf5e53ed_rking_Group___Comments_Tracker__Comment | [Commentor] LC-2840 Tim Berners-Lee (archived comment) [Working Group decision] This was discussed at the F2F5 and the WG agreed to change the confusing sentence to the following: How can the server make it easy for the client to create resources? See http://www.w3.org/2013/meeting/ldp/2014-04-15#LDP_Specification [Commentor reply] tocheck [Comment] | 4.1 "burden of constraints for resource creation" - I feel that phrase needs more explanation | [] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Comment | http://www.w3.org/2006/02/lc-comments-tracker/55082/ldp/doc/ | 39/1438043062723.96_20150728002422-00227-ip-10-236-191-2_826617545_0.json |
8662980d___XHTML_Object_Module__attribute | [function] For example, when defining an applet you could reference a space-separated list of jar files. [attribute] | archive | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed. [attribute] | content-length | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed. [attribute] | data | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed. [attribute] | declare | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] The author can provide a text string that should be displayed while the object data is being downloaded and processed. [attribute] | standby | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data. [attribute] | type | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
8662980d___XHTML_Object_Module__attribute | [function] Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose. [attribute] | xml:base | [
[
"a",
"r",
"c",
"h",
"i",
"v",
"e"
],
[
"c",
"o",
"n",
"t",
"e",
"n",
"t",
"-",
"l",
"e",
"n",
"g",
"t",
"h"
],
[
"d",
"a",
"t",
"a"
],
[
"d",
"e",
"c",
"l",
"a",
"r",
"e"
],
[
"s",
"t",
"a",
"n",
"d",
"b",
"y"
],
[
"t",
"y",
"p",
"e"
],
[
"x",
"m",
"l",
":",
"b",
"a",
"s",
"e"
]
] | - XHTML Object Module | attribute | http://www.w3.org/TR/2003/WD-xhtml2-20030131/mod-object.html | 39/1438043062723.96_20150728002422-00073-ip-10-236-191-2_810961827_1.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [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] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [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] | No conflict; added LDP headers | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [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] | No conflict; added LDP headers | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph] | 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 | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
dfc8a40c___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph] | 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 | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2840&oldid=2839 | 39/1438043062723.96_20150728002422-00182-ip-10-236-191-2_810605552_28.json |
46fa4611_HTML_5__Event_Name | [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [Event Name] | dragstart | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [Event Name] | drag | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [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] Reject immediate user selection as potential target element [Event Name] | dragenter | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] None [Event Name] | dragleave | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [Target] Current target element [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" [Event Name] | dragover | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name] | drop | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
46fa4611_HTML_5__Event_Name | [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name] | dragend | [
[
"d",
"r",
"a",
"g",
"s",
"t",
"a",
"r",
"t"
],
[
"d",
"r",
"a",
"g"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"t",
"e",
"r"
],
[
"d",
"r",
"a",
"g",
"l",
"e",
"a",
"v",
"e"
],
[
"d",
"r",
"a",
"g",
"o",
"v",
"e",
"r"
],
[
"d",
"r",
"o",
"p"
],
[
"d",
"r",
"a",
"g",
"e",
"n",
"d"
]
] | HTML 5 | Event Name | http://www.w3.org/TR/2008/WD-html5-20080610/editing.html | 39/1438043062723.96_20150728002422-00271-ip-10-236-191-2_810830243_0.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] top-left-corner [‘vertical-align’] middle [‘text-align’] | right | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] top-left [‘vertical-align’] middle [‘text-align’] | left | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] top-center [‘vertical-align’] middle [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] top-right [‘vertical-align’] middle [‘text-align’] | right | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] top-right-corner [‘vertical-align’] middle [‘text-align’] | left | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] left-top [‘vertical-align’] top [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] left-middle [‘vertical-align’] middle [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] left-bottom [‘vertical-align’] bottom [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] right-top [‘vertical-align’] top [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] right-middle [‘vertical-align’] middle [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] right-bottom [‘vertical-align’] bottom [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] bottom-left-corner [‘vertical-align’] middle [‘text-align’] | right | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] bottom-left [‘vertical-align’] middle [‘text-align’] | left | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] bottom-center [‘vertical-align’] middle [‘text-align’] | center | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] bottom-right [‘vertical-align’] middle [‘text-align’] | right | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
23b28d58_CSS_Paged_Media_Module_Level_3_t_values_for_Page_Margin_Boxes__text_align_ | [Page-margin box] bottom-right-corner [‘vertical-align’] middle [‘text-align’] | left | [
[
"r",
"i",
"g",
"h",
"t"
],
[
"l",
"e",
"f",
"t"
],
[
"c",
"e",
"n",
"t",
"e",
"r"
]
] | CSS Paged Media Module Level 3 | ‘text-align’ | http://www.w3.org/TR/css3-page/Overview.html | 39/1438043062723.96_20150728002422-00041-ip-10-236-191-2_822972002_1.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Types of Messages [Portable] Identified [Concrete] Identified [Abstract] | Identified | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Message Structure [Portable] Defined [Concrete] Defined [Abstract] | Not Defined | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Conditions [Portable] Identified [Concrete] Identified [Abstract] | Identified | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Condition evaluation rules [Portable] Defined as far as possible [Concrete] Defined as far as possible [Abstract] | Not defined | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Technology used [Portable] Defined [Concrete] Defined [Abstract] | Not defined | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
8d14d6f7_WS_Choreography_Model_Overview__Abstract | [0] Message Endpoint Data [Portable] Not Defined [Concrete] Defined [Abstract] | Not defined | [
[
"I",
"d",
"e",
"n",
"t",
"i",
"f",
"i",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"D",
"e",
"f",
"i",
"n",
"e",
"d"
],
[
"N",
"o",
"t",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d"
]
] | WS Choreography Model Overview | Abstract | http://www.w3.org/TR/ws-chor-model/ | 39/1438042988305.14_20150728002308-00190-ip-10-236-191-2_818769288_0.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] encrypt [Parameters] AesGcmParams [Result] | ArrayBuffer | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] decrypt [Parameters] AesGcmParams [Result] | ArrayBuffer | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] generateKey [Parameters] AesKeyGenParams [Result] | CryptoKey | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] importKey [Parameters] None [Result] | CryptoKey | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] exportKey [Parameters] None [Result] | object | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
3428d3e5_Web_Cryptography_API__Result | [Operation] get key length [Parameters] AesDerivedKeyParams [Result] | Integer | [
[
"A",
"r",
"r",
"a",
"y",
"B",
"u",
"f",
"f",
"e",
"r"
],
[
"C",
"r",
"y",
"p",
"t",
"o",
"K",
"e",
"y"
],
[
"o",
"b",
"j",
"e",
"c",
"t"
],
[
"I",
"n",
"t",
"e",
"g",
"e",
"r"
]
] | Web Cryptography API | Result | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Address [Specification priority] Nice to [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Address, email [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Alpha string, simple [Specification priority] Should [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Alphanumeric string, non-fixed [Specification priority] Nice to [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Alphanumeric string, sectioned [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Alphanumeric string, simple [Specification priority] Should [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Browsable action list [Specification priority] Should [Task vs. Template] Template [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Browsable selection list [Specification priority] Should [Task vs. Template] Template [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Credit card information [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Confirmation & correction dialog [Specification priority] Should [Task vs. Template] Template [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Currency [Specification priority] Must [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Date, context-compensating [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Date, fully-specified [Specification priority] Must [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Date, partially-specified [Specification priority] Should [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Digit string, sectioned [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Digit string, simple [Specification priority] Must [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Duration [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Error-recovery dialog, simple [Specification priority] Should [Task vs. Template] Template [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Menu [Specification priority] Must [Task vs. Template] Template [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Multiple choice selections [Specification priority] Nice to [Task vs. Template] Template [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Name, spelled [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Name, spoken & spelled [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Natural numbers [Specification priority] Must [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Postal code [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Telephone number [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Time [Specification priority] Must [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Time range [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] URL [Specification priority] Should [Task vs. Template] Task [Specification level] | Return only | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
423d1391_Reusable_dialog_requirements__Specification_level | [Component] Yes/No [Specification priority] Must [Task vs. Template] Task [Specification level] | Configure & Return | [
[
"R",
"e",
"t",
"u",
"r",
"n",
" ",
"o",
"n",
"l",
"y"
],
[
"C",
"o",
"n",
"f",
"i",
"g",
"u",
"r",
"e",
" ",
"&",
" ",
"R",
"e",
"t",
"u",
"r",
"n"
]
] | Reusable dialog requirements | Specification level | http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426 | 39/1438043062723.96_20150728002422-00196-ip-10-236-191-2_815592523_0.json |
02ad6b8b_hemas_Accessibility___W3C_Wiki__ess_Mode__before_augmentation_ | [Expected Values] alternativeText [Augmented Access Mode] Textual [Description] alternative text is provided for visual content (e.g., the HTML alt attribute). | Visual | [
[
"V",
"i",
"s",
"u",
"a",
"l"
],
[
"A",
"u",
"d",
"i",
"t",
"o",
"r",
"y"
],
[
"V",
"i",
"s",
"u",
"a",
"l",
" ",
"o",
"r",
" ",
"T",
"e",
"x",
"t",
"u",
"a",
"l"
]
] | WebSchemas/Accessibility - W3C Wiki | Source Access Mode (before augmentation) | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=70881 | 39/1438042989126.22_20150728002309-00063-ip-10-236-191-2_816488500_3.json |
02ad6b8b_hemas_Accessibility___W3C_Wiki__ess_Mode__before_augmentation_ | [Expected Values] longDescription [Augmented Access Mode] Textual [Description] descriptions are provided for image-based visual content and/or complex structures such as tables, mathematics, diagrams or charts. | Visual | [
[
"V",
"i",
"s",
"u",
"a",
"l"
],
[
"A",
"u",
"d",
"i",
"t",
"o",
"r",
"y"
],
[
"V",
"i",
"s",
"u",
"a",
"l",
" ",
"o",
"r",
" ",
"T",
"e",
"x",
"t",
"u",
"a",
"l"
]
] | WebSchemas/Accessibility - W3C Wiki | Source Access Mode (before augmentation) | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=70881 | 39/1438042989126.22_20150728002309-00063-ip-10-236-191-2_816488500_3.json |
02ad6b8b_hemas_Accessibility___W3C_Wiki__ess_Mode__before_augmentation_ | [Expected Values] ChemML laTex MathML [Augmented Access Mode] Textual [Description] The use of one of these specific ASCII/XML encodings for mathematics or chemistry. These can have extensions specified, but are rarely needed. | Visual | [
[
"V",
"i",
"s",
"u",
"a",
"l"
],
[
"A",
"u",
"d",
"i",
"t",
"o",
"r",
"y"
],
[
"V",
"i",
"s",
"u",
"a",
"l",
" ",
"o",
"r",
" ",
"T",
"e",
"x",
"t",
"u",
"a",
"l"
]
] | WebSchemas/Accessibility - W3C Wiki | Source Access Mode (before augmentation) | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=70881 | 39/1438042989126.22_20150728002309-00063-ip-10-236-191-2_816488500_3.json |
02ad6b8b_hemas_Accessibility___W3C_Wiki__ess_Mode__before_augmentation_ | [Expected Values] transcript [Augmented Access Mode] Textual [Description] The addition of a separate transcript to convey the meaning of the audio. | Auditory | [
[
"V",
"i",
"s",
"u",
"a",
"l"
],
[
"A",
"u",
"d",
"i",
"t",
"o",
"r",
"y"
],
[
"V",
"i",
"s",
"u",
"a",
"l",
" ",
"o",
"r",
" ",
"T",
"e",
"x",
"t",
"u",
"a",
"l"
]
] | WebSchemas/Accessibility - W3C Wiki | Source Access Mode (before augmentation) | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=70881 | 39/1438042989126.22_20150728002309-00063-ip-10-236-191-2_816488500_3.json |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.