abstract={This document provides recommendations for the implementation of password-based cryptography, covering key derivation functions, encryption schemes, message authentication schemes, and ASN.1 syntax identifying the techniques. This document represents a republication of PKCS \#5 v2.1 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series. By publishing this RFC, change control is transferred to the IETF. This document also obsoletes RFC 2898.},
creationdate={2020-10-05T00:00:00},
howpublished={RFC 8018},
owner={lorenzo},
publisher={RFC Editor},
series={Request for Comments},
timestamp={2020-10-05},
}
@TechReport{Klensin2008,
...
...
@@ -194,11 +194,11 @@
url={https://rfc-editor.org/rfc/rfc5321.txt},
urldate={2020-10-05},
abstract={This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. {[}STANDARDS-TRACK{]}},
creationdate={2020-10-05T00:00:00},
howpublished={RFC 5321},
owner={lorenzo},
publisher={RFC Editor},
series={Request for Comments},
timestamp={2020-10-05},
}
@TechReport{Klensin2004,
...
...
@@ -213,252 +213,252 @@
url={https://rfc-editor.org/rfc/rfc3696.txt},
urldate={2020-10-05},
abstract={Many Internet applications have been designed to deduce top-level domains (or other domain name labels) from partial information. The introduction of new top-level domains, especially non-country-code ones, has exposed flaws in some of the methods used by these applications. These flaws make it more difficult, or impossible, for users of the applications to access the full Internet. This memo discusses some of the techniques that have been used and gives some guidance for minimizing their negative impact as the domain name environment evolves. This document draws summaries of the applicable rules together in one place and supplies references to the actual standards. This memo provides information for the Internet community.},
creationdate={2020-10-05T00:00:00},
howpublished={RFC 3696},
owner={lorenzo},
publisher={RFC Editor},
series={Request for Comments},
timestamp={2020-10-05},
}
@Software{jquery,
author={{The jQuery Team}},
date={2006-01},
title={jQuery},
url={https://jquery.com/},
urldate={2020-10-01},
license={MIT},
owner={lorenzo},
repository={https://github.com/jquery/jquery},
timestamp={2020-10-05},
author={{The jQuery Team}},
date={2006-01},
title={jQuery},
url={https://jquery.com/},
urldate={2020-10-01},
creationdate={2020-10-05T00:00:00},
license={MIT},
owner={lorenzo},
repository={https://github.com/jquery/jquery},
}
@Software{jqueryvalidation,
author={Jörn Zaefferer and Markus Staab and Brahim Arkni},
abstract={JSP technology is focused on simplifying the generation of dynamic web content. The JSP 2.0 specification (JSR-152) substantially extended the technology by integrating a simple yet powerful expression language, simplifying the tag extension API, and enhancing the pure XML syntax, among other important enhancements. These enhancements greatly reduced the learning curve of the technology, warranting a major version number upgrade.},
abstract={JSP technology is focused on simplifying the generation of dynamic web content. The JSP 2.0 specification (JSR-152) substantially extended the technology by integrating a simple yet powerful expression language, simplifying the tag extension API, and enhancing the pure XML syntax, among other important enhancements. These enhancements greatly reduced the learning curve of the technology, warranting a major version number upgrade.},
abstract={The primary goal of this JSR is to expose support for the upcoming IETF standard HTTP/2 to users of the Servlet API. A secondary goal is to refresh the Servlet API with to achieve compliance with new features in HTTP 1.1 as well as responding to community input.},
abstract={The primary goal of this JSR is to expose support for the upcoming IETF standard HTTP/2 to users of the Servlet API. A secondary goal is to refresh the Servlet API with to achieve compliance with new features in HTTP 1.1 as well as responding to community input.},
abstract={The Expression Language (EL), has been part of JSP specification since JSP 2.0. It enables a JSP or JSF application to access and manipulate application objects or managed beans without Java codes. In Java EE 6, EL is an integrated component in CDI (Context and Dependency Injection for Java EE, JSR 299), and it allows direct use of CDI components in JSP or JSF.},
file={:- Expression Language Specification.pdf:PDF},
abstract={The Expression Language (EL), has been part of JSP specification since JSP 2.0. It enables a JSP or JSF application to access and manipulate application objects or managed beans without Java codes. In Java EE 6, EL is an integrated component in CDI (Context and Dependency Injection for Java EE, JSR 299), and it allows direct use of CDI components in JSP or JSF.},
creationdate={2020-10-05T00:00:00},
file={:- Expression Language Specification.pdf:PDF},
abstract={The Java Persistence API is the Java API for the management of persistence and object/relational mapping in Java EE and Java SE environments.},
abstract={The Java Persistence API is the Java API for the management of persistence and object/relational mapping in Java EE and Java SE environments.},
