|
Andreas Savva: 06/30/2008 10:48 PM EDT
|
|
Comment: |
Assigned category due to minor expected tweaks as a result of the experience document
|
|
Action: |
Update
Category set to Version 1.0
|
|
Andreas Savva: 07/25/2005 7:06 PM EST
|
|
Comment: |
Verified in version 30
|
|
Action: |
Update
|
|
Andreas Savva: 07/25/2005 7:06 PM EST
|
|
Action: |
Update
artifact_status changed from Fixed to Closed
close_date changed from - to 2005-07-26 09:06:23
|
|
Tom Maguire: 07/25/2005 3:57 PM EST
|
|
Comment: |
Use SchemaCentricCanonicalization spec
|
|
Action: |
Update
|
|
Tom Maguire: 07/25/2005 3:57 PM EST
|
|
Action: |
Update
artifact_status changed from Resolved to Fixed
|
|
David Snelling: 05/23/2005 9:20 AM EST
|
|
Comment: |
1) Put in a warning about prefixes on requests.
2) Provide a schema for a nodeset.
3) Provide a data structure for response including a choice for the different response types, e.g. bool, node-set, etc.
|
|
Action: |
Update
|
|
David Snelling: 05/23/2005 9:20 AM EST
|
|
Action: |
Update
artifact_status changed from Pending to Resolved
|
|
Tom Maguire: 04/20/2005 3:14 PM EST
|
|
Comment: |
need more discussion on well formedness of serialization. start email discussion on that topic
|
|
Action: |
Update
|
|
Tom Maguire: 04/20/2005 3:14 PM EST
|
|
Action: |
Update
artifact_status changed from Fixed to Pending
|
|
Tom Maguire: 04/20/2005 2:04 PM EST
|
|
Action: |
Update
artifact_status changed from Resolved to Fixed
|
|
Tom Maguire: 04/13/2005 2:58 PM EST
|
|
Comment: |
XML Dig Sig has two cannonicalization specs. Need to chose the appropriate one. Start a thread in mailing list
|
|
Action: |
Update
|
|
Tom Maguire: 03/02/2005 9:03 PM EST
|
|
Comment: |
editor instruction: add serialization requirment
|
|
Action: |
Update
|
|
Tom Maguire: 03/02/2005 9:03 PM EST
|
|
Action: |
Update
artifact_status changed from Open to Resolved
assigned_to changed from 100 to 191
|
|
Tom Maguire: 02/14/2005 11:14 AM EST
|
|
Action: |
Update
Priority changed from - to 3
|
|
|