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
|
|---|---|---|---|---|---|---|---|
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running). [Event name] | emptied | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. [Event name] | stalled | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin. [Event name] | play | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Playback has been paused. Fired after the pause() method has returned. [Event name] | pause | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The user agent has just determined the duration and dimensions of the media resource [Event name] | loadedmetadata | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The user agent can render the media data at the current playback position for the first time. [Event name] | loadeddata | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. [Event name] | waiting | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Playback has started. [Event name] | playing | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content. [Event name] | canplay | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering. [Event name] | canplaythrough | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event. [Event name] | seeking | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The seeking IDL attribute changed to false. [Event name] | seeked | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously. [Event name] | timeupdate | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Playback has stopped because the end of the media resource was reached. [Event name] | ended | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Either the defaultPlaybackRate or the playbackRate attribute has just been updated. [Event name] | ratechange | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] The duration attribute has just been updated. [Event name] | durationchange | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
fae89202_TML_Elements_audio____W3C_Wiki__Event_name | [Dispatched when...] Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. [Event name] | volumechange | [] | Difference between revisions of "HTML/Elements/audio" - W3C Wiki | Event name | http://www.w3.org/wiki/index.php?title=HTML/Elements/audio&curid=5060&diff=65718&oldid=52834 | 39/1438042989126.22_20150728002309-00185-ip-10-236-191-2_814262483_1.json |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2834 Tim Berners-Lee (archived comment) [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. [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2835 Tim Berners-Lee (archived comment) [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. [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2812 Mark Baker (archived comment) [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. [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2833 Tim Berners-Lee (archived comment) [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 [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2836 Tim Berners-Lee (archived comment) [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. [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2837 Tim Berners-Lee (archived comment) [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.) [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2813 Ashok Malhotra (archived comment) [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”? [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2814 Ashok Malhotra (archived comment) [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. [Working Group decision] Same as LC-2813. [Commentor reply] | yes | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2815 Ashok Malhotra (archived comment) [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? [Working Group decision] Added some informative content to 5.1.2 Ordering section. [Commentor reply] | tocheck | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2816 Ashok Malhotra (archived comment) [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 [Working Group decision] Erroneous comment. See http://lists.w3.org/Archives/Public/public-ldp-comments/2013Aug/0005.html [Commentor reply] | yes | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2838 Tim Berners-Lee (archived comment) [Comment] How does a client find the non-member-property version of a resource R? [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2839 Tim Berners-Lee (archived comment) [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. [Working Group decision] Changed the offending text to clarify intent and use inspect rather than introspect per Tim's recommendation. [Commentor reply] | tocheck | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
76597aa9_rking_Group___Comments_Tracker__Commentor_reply | [Commentor] LC-2840 Tim Berners-Lee (archived comment) [Comment] 4.1 "burden of constraints for resource creation" - I feel that phrase needs more explanation [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 | [
[
"t",
"o",
"c",
"h",
"e",
"c",
"k"
],
[
"y",
"e",
"s"
]
] | Disposition of comments for the Linked Data Platform (LDP) Working Group - Comments Tracker | Commentor reply | 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 |
fc62a93b_Web_Cryptography_API__Result | [Operation] encrypt [Parameters] AesCbcParams [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_9.json |
fc62a93b_Web_Cryptography_API__Result | [Operation] decrypt [Parameters] AesCbcParams [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_9.json |
fc62a93b_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_9.json |
fc62a93b_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_9.json |
fc62a93b_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_9.json |
fc62a93b_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_9.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] loadstart [Interface] ProgressEvent [PROGRESS] [Preconditions] networkState equals LOADING [Dispatched when...] | The user agent begins fetching the media data, synchronously during the load() method call. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] progress [Interface] ProgressEvent [PROGRESS] [Preconditions] networkState is more than EMPTY and less than LOADED [Dispatched when...] | The user agent is fetching media data. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] loadedmetadata [Interface] Event [Preconditions] networkState equals LOADED_METADATA [Dispatched when...] | The user agent is fetching media data, and the media resource's metadata has just been received. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] loadedfirstframe [Interface] Event [Preconditions] networkState equals LOADED_FIRST_FRAME [Dispatched when...] | The user agent is fetching media data, and the media resource's first frame has just been received. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] load [Interface] ProgressEvent [PROGRESS] [Preconditions] networkState equals LOADED [Dispatched when...] | The user agent finishes downloading the entire media resource. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] abort [Interface] ProgressEvent [PROGRESS] [Preconditions] error is an object with the code MEDIA_ERR_ABORTED. networkState equals either EMPTY or LOADED, depending on when the download was aborted. [Dispatched when...] | The user agent stops fetching the media data before it is completely downloaded. This can be fired synchronously during the load() method call. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] error [Interface] ProgressEvent [PROGRESS] [Preconditions] error is an object with the code MEDIA_ERR_NETWORK_ERROR or higher. networkState equals either EMPTY or LOADED, depending on when the download was aborted. [Dispatched when...] | An error occurs while fetching the media data. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] emptied [Interface] Event [Preconditions] networkState is EMPTY; all the DOM attributes are in their initial states. [Dispatched when...] | A media element whose networkState was previously not in the EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was reinvoked, in which case it is fired synchronously during the load() method call). | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] stalled [Interface] ProgressEvent [Dispatched when...] | The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] play [Interface] Event [Preconditions] paused is newly false. [Dispatched when...] | Playback has begun. Fired after the play method has returned. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] pause [Interface] Event [Preconditions] paused is newly true. [Dispatched when...] | Playback has been paused. Fired after the pause method has returned. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] waiting [Interface] Event [Preconditions] readyState is either DATA_UNAVAILABLE or CAN_SHOW_CURRENT_FRAME, and paused is false. Either seeking is true, or the current playback position is not contained in any of the ranges in buffered. It is possible for playback to stop for two other reasons without paused being false, but those two reasons do not fire this event: maybe playback ended, or playback stopped due to errors. [Dispatched when...] | Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] seeking [Interface] Event [Dispatched when...] | The seeking DOM attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] seeked [Interface] Event [Dispatched when...] | The seeking DOM attribute changed to false. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] timeupdate [Interface] Event [Dispatched when...] | The current playback position changed in an interesting way, for example discontinuously. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] ended [Interface] Event [Preconditions] currentTime equals the effective end; ended is true. [Dispatched when...] | Playback has stopped because the end of the media resource was reached. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] dataunavailable [Interface] Event [Preconditions] The readyState attribute is newly equal to DATA_UNAVAILABLE. [Dispatched when...] | The user agent cannot render the data at the current playback position because data for the current frame is not immediately available. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] canshowcurrentframe [Interface] Event [Preconditions] The readyState attribute is newly equal to CAN_SHOW_CURRENT_FRAME. [Dispatched when...] | The user agent cannot render the data after the current playback position because data for the next frame is not immediately available. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] canplay [Interface] Event [Preconditions] The readyState attribute is newly equal to CAN_PLAY. [Dispatched when...] | The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] canplaythrough [Interface] Event [Preconditions] The readyState attribute is newly equal to CAN_PLAY_THROUGH. [Dispatched when...] | The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] ratechange [Interface] Event [Dispatched when...] | Either the defaultPlaybackRate or the playbackRate attribute has just been updated. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] durationchange [Interface] Event [Dispatched when...] | The duration attribute has just been updated. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
d549031f_HTML_5__Dispatched_when___ | [Event name] volumechange [Interface] Event [Dispatched when...] | Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. | [] | HTML 5 | Dispatched when... | http://www.w3.org/TR/2008/WD-html5-20080610/video.html | 39/1438042989126.22_20150728002309-00059-ip-10-236-191-2_816582832_0.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] additionalType (added) [Expected Type] URL [Description] | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] description [Expected Type] Text [Description] | A short description of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] image [Expected Type] URL [Description] | URL of an image of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] name [Expected Type] Text [Description] | The name of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] url [Expected Type] URL [Description] | URL of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] alternativeHeadline [Expected Type] Text [Description] | A secondary title of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] inLanguage [Expected Type] Language [Description] | The language of the content. Please use one of the language codes from the IETF BCP 47 standard. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] dateCreated [Expected Type] Date [Description] | The date on which the content was created (in ISO 8601 date format). | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] dateModified [Expected Type] Date [Description] | The date on which the content was most recently modified (in ISO 8601 date format). | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] keywords [Expected Type] Text [Description] | The keywords/tags used to describe this content. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] provider [Expected Type] Person or Organization [Description] | Specifies the person or organization that distributed the content. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] breadcrumb [Expected Type] Text [Description] | A set of links that can help a user understand and navigate a website hierarchy. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] relatedLink (or “seeAlso”) [Expected Type] URL [Description] | A link related to this web page, for example to other related web pages. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] entryID [Expected Type] Text [Description] | The identifier of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] isEntryOf [Expected Type] BiologicalDatabase [Description] | Indicates the database to which the entry belongs. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] taxonID (or “taxon”) [Expected Type] Text [Description] | The taxonomy identifier of the entry. Please use the NCBI Taxonomy ID. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] taxon (or “taxonID”) [Expected Type] BiologicalDatabaseEntry (or Text) [Description] | The taxonomy information of the entry. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
05357abc_hemas_BioDatabases____W3C_Wiki__Description | [Property] seeAlso (or “relatedLink”) [Expected Type] BiologicalDatabaseEntry (or URL) [Description] | Reference to another resource. | [] | Difference between revisions of "WebSchemas/BioDatabases" - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/BioDatabases&curid=6353&diff=62920&oldid=62919 | 39/1438042989126.22_20150728002309-00272-ip-10-236-191-2_817814216_1.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] encrypt [Result] ArrayBuffer [Parameters] | AesCbcParams | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] decrypt [Result] ArrayBuffer [Parameters] | AesCbcParams | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] generateKey [Result] CryptoKey [Parameters] | AesKeyGenParams | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] importKey [Result] CryptoKey [Parameters] | None | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] exportKey [Result] object [Parameters] | None | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
fd139b32_Web_Cryptography_API__Parameters | [Operation] get key length [Result] Integer [Parameters] | AesDerivedKeyParams | [
[
"A",
"e",
"s",
"C",
"b",
"c",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_9.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] encrypt [Result] ArrayBuffer [Parameters] | AesGcmParams | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] decrypt [Result] ArrayBuffer [Parameters] | AesGcmParams | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] generateKey [Result] CryptoKey [Parameters] | AesKeyGenParams | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] importKey [Result] CryptoKey [Parameters] | None | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] exportKey [Result] object [Parameters] | None | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
bb82f5da_Web_Cryptography_API__Parameters | [Operation] get key length [Result] Integer [Parameters] | AesDerivedKeyParams | [
[
"A",
"e",
"s",
"G",
"c",
"m",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"A",
"e",
"s",
"K",
"e",
"y",
"G",
"e",
"n",
"P",
"a",
"r",
"a",
"m",
"s"
],
[
"N",
"o",
"n",
"e"
],
[
"A",
"e",
"s",
"D",
"e",
"r",
"i",
"v",
"e",
"d",
"K",
"e",
"y",
"P",
"a",
"r",
"a",
"m",
"s"
]
] | Web Cryptography API | Parameters | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_11.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] NotSupportedError [Message (optional)] | The algorithm is not supported | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] SyntaxError [Message (optional)] | A required parameter was missing or out-of-range | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] InvalidStateError [Message (optional)] | The requested operation is not valid for the current state of the provided key. | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] InvalidAccessError [Message (optional)] | The requested operation is not valid for the provided key | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] UnknownError [Message (optional)] | The operation failed for an unknown transient reason (e.g. out of memory) | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] DataError [Message (optional)] | Data provided to an operation does not meet requirements | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
dff863ca_Web_Cryptography_API__Message__optional_ | [Type] OperationError [Message (optional)] | The operation failed for an operation-specific reason | [] | Web Cryptography API | Message (optional) | http://www.w3.org/TR/WebCryptoAPI/ | 39/1438043062723.96_20150728002422-00216-ip-10-236-191-2_808981146_1.json |
312f937f_PROV_Overview__Audience | [Part] 1 [Type] Note [Document] PROV-PRIMER is the entry point to PROV offering an introduction to the provenance model. This is where you should start and for many may be the only document needed. [Audience] | Users | [
[
"U",
"s",
"e",
"r",
"s"
],
[
"D",
"e",
"v",
"e",
"l",
"o",
"p",
"e",
"r",
"s"
],
[
"A",
"d",
"v",
"a",
"n",
"c",
"e",
"d"
]
] | PROV-Overview | Audience | http://www.w3.org/TR/2012/WD-prov-overview-20121211/ | 39/1438043062723.96_20150728002422-00063-ip-10-236-191-2_822575680_0.json |
312f937f_PROV_Overview__Audience | [Part] 2 [Type] Rec [Document] PROV-O defines a light-weight OWL2 ontology for the provenance model. This is intended for the Linked Data and Semantic Web community. [Audience] | Developers | [
[
"U",
"s",
"e",
"r",
"s"
],
[
"D",
"e",
"v",
"e",
"l",
"o",
"p",
"e",
"r",
"s"
],
[
"A",
"d",
"v",
"a",
"n",
"c",
"e",
"d"
]
] | PROV-Overview | Audience | http://www.w3.org/TR/2012/WD-prov-overview-20121211/ | 39/1438043062723.96_20150728002422-00063-ip-10-236-191-2_822575680_0.json |
312f937f_PROV_Overview__Audience | [Part] 3 [Type] Note [Document] PROV-XML defines an XML schema for the provenance model. This is intended for developers who need a native XML serialization of PROV [Audience] | Developers | [
[
"U",
"s",
"e",
"r",
"s"
],
[
"D",
"e",
"v",
"e",
"l",
"o",
"p",
"e",
"r",
"s"
],
[
"A",
"d",
"v",
"a",
"n",
"c",
"e",
"d"
]
] | PROV-Overview | Audience | http://www.w3.org/TR/2012/WD-prov-overview-20121211/ | 39/1438043062723.96_20150728002422-00063-ip-10-236-191-2_822575680_0.json |
312f937f_PROV_Overview__Audience | [Part] 4 [Type] Rec [Document] PROV-DM defines a conceptual data model for provenance including UML diagrams. PROV-O and PROV-XML are serializations of this conceptual model. [Audience] | Advanced | [
[
"U",
"s",
"e",
"r",
"s"
],
[
"D",
"e",
"v",
"e",
"l",
"o",
"p",
"e",
"r",
"s"
],
[
"A",
"d",
"v",
"a",
"n",
"c",
"e",
"d"
]
] | PROV-Overview | Audience | http://www.w3.org/TR/2012/WD-prov-overview-20121211/ | 39/1438043062723.96_20150728002422-00063-ip-10-236-191-2_822575680_0.json |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.