ISSUE-75 |
CLOSED |
Role of schema canonicalizaton wrt schema defaults |
2008-11-18 |
|
0 |
| ISSUE-97 |
CLOSED |
Clarify inputs and outputs, see http://lists.w3.org/Archives/Public/public-xmlsec/2009Feb/0029.html |
2009-02-10 |
|
0 |
| ISSUE-46 |
CLOSED |
Acceptability of PI for various environments/segments/use cases |
2008-08-12 |
|
0 |
| ISSUE-102 |
CLOSED |
AES Keywrap |
2009-02-24 |
|
0 |
| ISSUE-74 |
CLOSED |
Hmac-sha256 required in 1.1? |
2008-11-18 |
|
0 |
| ISSUE-105 |
CLOSED |
HMAC output length is defined on bits base64 on octets |
2009-02-24 |
|
1 |
| ISSUE-76 |
CLOSED |
Http://lists.w3.org/Archives/Member/member-xmlsec/2008Nov/0029.html |
2008-11-18 |
|
0 |
| ISSUE-94 |
CLOSED |
In the ECParameterType type definition, note that the <Order>element may also be a large number and hence the use of the\"integer\" type may again be problematic |
2009-01-27 |
|
0 |
| ISSUE-84 |
CLOSED |
What should the best practices say about defenses against collision generation? |
2009-01-13 |
|
0 |
| ISSUE-81 |
CLOSED |
ECDSA requires new elements; what do we do about schema and DTD? |
2009-01-13 |
|
0 |
| ISSUE-85 |
CLOSED |
Add note to dsig 1.1 re 18 digit limit for x509 issuer serial nmber |
2009-01-14 |
|
0 |
| ISSUE-89 |
CLOSED |
Testing |
2009-01-22 |
|
0 |
| ISSUE-93 |
CLOSED |
Missing a <Hash> element in the ds:ECParametersType type definition |
2009-01-27 |
|
0 |
| ISSUE-92 |
CLOSED |
Include the \"implicitCA\" option for ECKeyValueType and separate ECDomainParameterType type |
2009-01-27 |
|
0 |
| ISSUE-80 |
CLOSED |
ECDSA |
2009-01-13 |
|
0 |
| ISSUE-70 |
CLOSED |
Require DER encoding in 1.1 |
2008-11-04 |
|
0 |
| ISSUE-130 |
CLOSED |
How does canonicalization deal with xsi:type |
2009-05-13 |
|
0 |
| ISSUE-129 |
CLOSED |
C14N should notice xml:space |
2009-05-13 |
|
0 |
| ISSUE-138 |
OPEN |
What interoperability and security issues arise out of schema validation behavior? |
2009-09-01 |
|
0 |
| ISSUE-156 |
OPEN |
Threat for signature from use of namespace prefixes with corresponding unsigned namespace declarations leading to wrapping like attacks |
2009-11-17 |
|
0 |
| ISSUE-152 |
OPEN |
Add pratik as author to xpath subset document if produced by ws-ra |
2009-11-06 |
|
0 |
| ISSUE-151 |
OPEN |
Review XML SIgnature 2.0 and Canonical XML 2.0 for testable assertions |
2009-11-05 |
|
0 |
| ISSUE-111 |
CLOSED |
Clarify role of document use case in renamed 2.0 versus 1.1 |
2009-03-31 |
|
0 |
| ISSUE-128 |
CLOSED |
Add clarification in XML Signature regarding serialization impact with issue:: add clarification in XML Signature regarding serialization impact with |
2009-05-13 |
|
0 |
| ISSUE-116 |
CLOSED |
C14N clarification and errata as noted by Konrad wrt ACTION-259 |
2009-04-28 |
|
0 |
| ISSUE-67 |
CLOSED |
Revise XSLT transform; it's currently octet-stream to node-set. |
2008-10-21 |
|
0 |
| ISSUE-118 |
CLOSED |
Http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-AlgID |
2009-05-05 |
|
0 |
| ISSUE-120 |
CLOSED |
Keep AES KeyWrap with padding as optional |
2009-05-05 |
|
0 |
| ISSUE-126 |
CLOSED |
Clarify XMLENC Section 5.8 (Message Authentication) |
2009-05-13 |
|
0 |
| ISSUE-121 |
CLOSED |
Provide recommendation regarding key length for signature a la widget signature, either in signature 1.1 or best practices |
2009-05-12 |
|
0 |
| ISSUE-153 |
OPEN |
Change Canonicalization 2.0 to replace the pseudo code snippets with descriptive text, and move all the pseudo code to another non normative section |
2009-11-07 |
|
0 |
| ISSUE-77 |
CLOSED |
Is there a requirement for algorithm,data, digest/signature value order in 1.1? |
2008-11-18 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-79 |
CLOSED |
Clearly support OCSP response and CRL inclusion in KeyInfo? |
2009-01-05 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-101 |
CLOSED |
Add AES Key Wrap with Padding to Encryption |
2009-02-24 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-109 |
CLOSED |
Some Algorithm URIs have extra spaces |
2009-03-06 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-112 |
CLOSED |
FPWD typo |
2009-04-01 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-108 |
CLOSED |
exclusive C14N is recommended and not required in the XML Signature 1.1 |
2009-03-06 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-100 |
CLOSED |
Ripe URIs |
2009-02-24 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-95 |
CLOSED |
add as recommended algorithms "XPATH 2 Filter" and "Exclusive Canonicalization" to the list in section 6.0 |
2009-01-30 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-96 |
CLOSED |
replace should with SHOULD |
2009-02-02 |
Algs (XML Security Algorithms Note) |
0 |
ISSUE-90
addtluris |
CLOSED |
Define algorithm URIs for ecdsa-ripemd160 and ecdsa-whirlpool? |
2009-01-22 |
Algs (XML Security Algorithms Note) |
0 |
| ISSUE-78 |
CLOSED |
XMl Signature 1.1 missing references and broken links |
2009-01-02 |
Algs (XML Security Algorithms Note) |
0 |
ISSUE-56
Timestamp References |
CLOSED |
Add references related to timestamping |
2008-09-25 |
Best Practices for XML Signature |
0 |
ISSUE-55
Implementation language |
CLOSED |
Language should not focus on implementations but on specification use |
2008-09-24 |
Best Practices for XML Signature |
0 |
ISSUE-53
Practice summaries |
CLOSED |
Add short summary for each best practice |
2008-09-22 |
Best Practices for XML Signature |
0 |
| ISSUE-71 |
OPEN |
Change section titles in best practices to match practices |
2008-11-04 |
Best Practices for XML Signature |
0 |
| ISSUE-69 |
CLOSED |
Update example file to avoid empty XPath result |
2008-11-03 |
Best Practices for XML Signature |
0 |
ISSUE-64
how-to |
CLOSED |
How to use XML Signature for various applications, e.g. Mail, unstructured content etc |
2008-10-08 |
Best Practices for XML Signature |
0 |
ISSUE-62
schema validation |
CLOSED |
Clarify best practice related to order of schema validation and xml security processing for 2nd Edition |
2008-10-08 |
Best Practices for XML Signature |
0 |
ISSUE-52
clarify keyinfo |
CLOSED |
Rules for syntax of KeyInfo child elements should be unambiguous |
2008-09-15 |
Best Practices for XML Signature |
0 |
ISSUE-54
C14N usage |
CLOSED |
Use consistent spelling of C14N11 |
2008-09-22 |
Best Practices for XML Signature |
0 |
| ISSUE-73 |
CLOSED |
XML Schema defaults |
2008-11-13 |
Best Practices for XML Signature |
0 |
| ISSUE-10 |
CLOSED |
Specify c14n with a tree-walk rather than a nodeset |
2008-07-17 |
C14N (Design for Canonicalization V Next) |
0 |
ISSUE-57
c14n end tags |
CLOSED |
eliminate the need of the name of the element in end tag / make it optional |
2008-09-25 |
C14N (Design for Canonicalization V Next) |
0 |
| ISSUE-154 |
OPEN |
Links to references need to be updated |
2009-11-15 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-155 |
OPEN |
Add AES-GCM to XML Encryption 1.1 |
2009-11-16 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-134 |
CLOSED |
Camellia algorithm for section of 5.2 Block Encryption Algorithm and 5.6 Symmetric Key Wrap |
2009-06-08 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-137 |
CLOSED |
Normative reference to DRAFT-HOUSLEY-KW-PAD |
2009-07-13 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-135 |
CLOSED |
Review transforms for XML Encryption 1.1 and alignment with Signature 1.1 |
2009-06-09 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-148 |
CLOSED |
Define PartyUInfo with XML structure, SP80056AConcatKDF in XML Encryption 1.1 |
2009-10-19 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-103 |
CLOSED |
Shouldn't there be a REQUIRED curve in XMLENC as well as there is one in XMLDSIG |
2009-02-24 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-125 |
CLOSED |
Add C14N1.1 to the list of canonicalization algorithms in Section 5.9 of XMLENC |
2009-05-13 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-147 |
OPEN |
XML Encryption 1.1 table of contents incomplete, some headings not numbered correctly in document |
2009-10-06 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-150 |
OPEN |
Use of XML encryption type encoding in EXI |
2009-11-05 |
Enc11 (XML Encryption 1.1) |
0 |
| ISSUE-91 |
OPEN |
ECC can't be REQUIRED |
2009-01-26 |
Enc11 and Sig11 and Security Algorithms Summary |
0 |
ISSUE-59
consistent single location to define c14n URIs |
CLOSED |
xml security algorithm URIs are not defined in consistent location leading to confusion |
2008-10-07 |
Errata-C14N |
0 |
| ISSUE-133 |
CLOSED |
Update Exclusive C14N Schema |
2009-06-08 |
Errata-C14N |
0 |
ISSUE-58
xml-namespace-handling |
CLOSED |
Clarify c14n11 handling of xml: namespace declarations |
2008-10-02 |
Errata-C14N |
0 |
| ISSUE-88 |
CLOSED |
Spelling errors in XML Encryption Recommendation |
2009-01-16 |
Errata-XML Encryption |
0 |
| ISSUE-144 |
OPEN |
XML Schema and DTD inconsistency for SPKISexp element |
2009-10-01 |
Errata-XML Signature |
0 |
| ISSUE-145 |
CLOSED |
Errors in XML Signature Example in section 9, "Schema, DTD, Data Model, and Valid Examples" |
2009-10-01 |
Errata-XML Signature |
0 |
| ISSUE-119 |
CLOSED |
Erratum for Signature 1.0 and use of SHA256 in favor of SHA1 |
2009-05-05 |
Errata-XML Signature |
0 |
ISSUE-50
dsig example typo |
CLOSED |
Missing < in closing DigestValue element tag |
2008-08-28 |
Errata-XML Signature |
0 |
ISSUE-141
c14n11nodeprocessing |
OPEN |
C14N 1.1 processing of non-element, non-PI nodes in a node set |
2009-09-28 |
Maint-C14N11 |
0 |
| ISSUE-117 |
CLOSED |
Key Wrap |
2009-04-29 |
Maint-Enc (XML Encryption Syntax and Processing Maintenance) |
0 |
| ISSUE-99 |
CLOSED |
Key Wrapping intro in XML Encryption needs Example |
2009-02-23 |
Maint-Enc (XML Encryption Syntax and Processing Maintenance) |
0 |
ISSUE-110
visibly utilizes in Exc-C14N |
CLOSED |
Need better definition for "visibly utilizes" in Exc-C14N |
2009-03-12 |
Maint-ExC14N (Exclusive XML Canonicalization Version 1.0 Maintenance) |
0 |
| ISSUE-13 |
CLOSED |
What would it take to use XML Signature for structured non-XML content |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-149 |
OPEN |
Link requirements to features |
2009-10-20 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-40 |
CLOSED |
Appropriate signing/verification position in EXI workflow, expectations and correctness review |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-12 |
CLOSED |
What would it take for XML Signature to be usable for Mail |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-68
algorithms |
CLOSED |
Enable generic use of randomized hashing |
2008-11-03 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-42 |
CLOSED |
Backward and forward compatibility |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-5 |
CLOSED |
Which selections from subtree are required |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-18 |
CLOSED |
Data between algorithm info and digest? |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-4 |
CLOSED |
Need to allow transforms to go between octets and nodeset |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-17 |
CLOSED |
Placement of KeyInfo relative to SIgnedInfo |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-49
DerivedKeyType |
CLOSED |
No support for derived keys in XML Dsig, XML Enc |
2008-08-28 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-15 |
CLOSED |
Minimal caching to support streaming |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-41 |
CLOSED |
Signing compact EXI representation of XML - is that reproducable for verification |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-127 |
CLOSED |
Should XML Security WG consider supporting and/or defining EXI canonicalization |
2009-05-13 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-6 |
CLOSED |
Is there requirement to canonicalize/sign exi representation |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-61
streaming reqmts |
CLOSED |
characterize what is meant by streaming and associated requirements |
2008-10-08 |
Rqmts (XML Security Use Cases and Requirements) |
1 |
| ISSUE-139 |
CLOSED |
Need to collect streaming XPath requirements |
2009-09-08 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-60
EXI Requirements |
CLOSED |
Define requirements for XML Security and EXI usage |
2008-10-08 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-51
schema normalization |
CLOSED |
Effects of schema normalization on signature verification |
2008-09-02 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-136 |
CLOSED |
Is normalization of prefixes a goal for 2.0 c14n |
2009-07-07 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-63
namespace rqmts |
OPEN |
Namespace requirements: undeclarations, QNames, use of partial content in new contexts |
2008-10-08 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-48
DerivedKeyType |
CLOSED |
No support for derived keys in XML Dsig, XML Enc |
2008-08-28 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-9 |
OPEN |
Review WS-I BSP constraints on DSig |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-131 |
CLOSED |
Is semantic equivalence robustness in requirements document |
2009-05-13 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-66
constrain-xml-data-model |
CLOSED |
Which constraints can we impose on xml data model for simplification |
2008-10-08 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-65
transform-rqmts |
CLOSED |
Define requirements on transforms |
2008-10-08 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-3 |
CLOSED |
Can we limit the generality of subsetting to reduce complexity, e.g. XPath 2.0 |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-16 |
CLOSED |
Backward reference for streaming - don't know what is referenced, algs |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-38 |
CLOSED |
Profile for signature processing for non-XML or for constrained XML requirements |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-29 |
CLOSED |
Able to run transforms in parallel (in general parallelism related to pipelining) |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-28 |
CLOSED |
QNames? |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-19 |
CLOSED |
Placement of signature relative to signing or verification, different placement? |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-26 |
CLOSED |
Require well formed XML between transforms |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-30 |
CLOSED |
Limit XPath Filter transform to be first transform or to not use parent axis |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-37 |
CLOSED |
Simplified c14n for signing versus more general c14n, e.g. not produce compliant xml document |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-34
versioning |
CLOSED |
Versioning and compatibility requirements, namespace versioning policy |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-33 |
CLOSED |
Schema not validating when enveloped signature added and not included in original doc schema |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-32
sig metadata rqmts |
CLOSED |
Define metadata that needs to be conveyed with signature, e.g. profile information |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
ISSUE-31
processing instructions |
CLOSED |
Role for XML processing instruction, if any |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-25 |
CLOSED |
Web services profile |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-27 |
CLOSED |
Profile XML Signature spec to disallow removal of used namespace nodes from nodesets |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-24 |
CLOSED |
Requirement for NodeSets |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-45 |
CLOSED |
Multiple or layered signatures |
2008-08-12 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-21 |
CLOSED |
Arbitrary selection from nodeset vs XPath expressions without backward references, traversal and navigation |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-20 |
CLOSED |
Transform model should support streaming, filtering model |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-39 |
CLOSED |
Namespace Undeclarations and canonicalization |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-44 |
CLOSED |
Requirement to enable signatures on documents that do not anticipate signatures in the schema |
2008-07-29 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-22 |
CLOSED |
Requirement to validate xml before application processing, signature processing, thus need to read entire document before processing, thus not true streaming |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-23 |
CLOSED |
Requirement for NodeSets |
2008-07-17 |
Rqmts (XML Security Use Cases and Requirements) |
0 |
| ISSUE-142 |
CLOSED |
Is a single schema needed for XML Signature 1.1 to validate against, given that we have 2nd edition schema plus 1.1 additional schema |
2009-09-29 |
Sig11 (XML Signature 1.1) |
0 |
| ISSUE-115 |
CLOSED |
XPath Filter Transform and Namespace Declarations for Qualified Nodes, see http://lists.w3.org/Archives/Public/public-xmlsec/2009Apr/0025.html |
2009-04-21 |
Sig11 (XML Signature 1.1) |
0 |
| ISSUE-143 |
CLOSED |
Add use="required" to the URI attribute in NamedCurveType and well as review attributes for use-clause |
2009-10-01 |
Sig11 (XML Signature 1.1) |
0 |
| ISSUE-82 |
OPEN |
Should 1.1 spec mandate support for range of RSA key sizes (and DSA)? |
2009-01-13 |
Sig11 (XML Signature 1.1) |
0 |
| ISSUE-140 |
OPEN |
Clarify how XPath is interpreted relative to entire document and ds:Reference |
2009-09-08 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-122 |
OPEN |
Explain why peformance improvements and rationale, relationship to earlier work |
2009-05-12 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-86 |
OPEN |
Document performance criterial and benchmarks |
2009-01-14 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-87 |
CLOSED |
Determine approach to RetrievalMethod in 2.0 with regard to transforms, if any, or if revised transform approach |
2009-01-14 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-104 |
CLOSED |
Carry existing ds:References into new XMLDSIG 2.0 |
2009-02-24 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-146 |
CLOSED |
Determine impact of 2.0 transform model on XML Encryption, and any needed changes to XML Encryption |
2009-10-01 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-123 |
OPEN |
How in 2.0 to disallow SHA-1 when algorithm URI currently defined |
2009-05-12 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-132 |
OPEN |
Keep 2.0 xenc transform feature in sync with signature 2.0 |
2009-06-02 |
Sig20 (XML Signature 2.0) |
0 |
| ISSUE-124 |
CLOSED |
Does w3c support conformance clauses for specification and minimum conformance levels, how to do properly |
2009-05-12 |
WG-Coordination |
0 |
| ISSUE-35 |
CLOSED |
test from vivien (please disregard) |
2008-07-22 |
WG-Tools |
0 |
| ISSUE-1 |
CLOSED |
Tracker Issues not sent to the list |
2008-07-16 |
WG-Tools |
0 |
| ISSUE-2 |
CLOSED |
Tracker doesn't get its e-mails through |
2008-07-16 |
WG-Tools |
0 |
| ISSUE-36 |
CLOSED |
Tracker test #2 |
2008-07-22 |
WG-Tools |
0 |
ISSUE-47
XAdES Signature Reference |
CLOSED |
XAdES references latest XML Signature, depends on ds:Object and ds:KeyInfo |
2008-08-13 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-14 |
CLOSED |
Need to understand plans and impact of namespace undeclarations |
2008-07-17 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-107 |
CLOSED |
deprecate decryption transform?, see what you sign and workflow |
2009-02-24 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-106 |
CLOSED |
see what you sign requirement in transform simplification vs external workflow |
2009-02-24 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-43 |
OPEN |
Improvements to XML Signature schema |
2008-07-29 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-7 |
CLOSED |
Can exi be used by xmlsec wg as part of solution |
2008-07-17 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-113 |
CLOSED |
Requirement to provide extension to Signature 1.1 to enable streaming hints in backward compatible manner |
2009-04-06 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-8 |
CLOSED |
Can spec be written to not rely on XPath data model and achieve same functionality |
2008-07-17 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-114 |
CLOSED |
Are Processing Instructions suitable technology to use |
2009-04-06 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-11 |
CLOSED |
Clarify how to reference Mail element (multipart Mime part) from signature reference |
2008-07-17 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-72 |
CLOSED |
DTD required for v1.1 or v.next of XML Signature? |
2008-11-06 |
v.next (Design for XML Signature V Next) |
0 |
| ISSUE-83 |
CLOSED |
Ecdsa-ripemd160 and ecdsa-whirlpool need identifiers, rfc4051? |
2009-01-13 |
xmlsec-algorithms |
0 |
| ISSUE-98 |
CLOSED |
Reference format needs to be unified |
2009-02-11 |
xmlsec-algorithms |
0 |