<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 20: Signed manifest.xml are invalid against schema</title><link href="https://sourceforge.net/p/openscoreformat/bugs/20/" rel="alternate"/><link href="https://sourceforge.net/p/openscoreformat/bugs/20/feed.atom" rel="self"/><id>https://sourceforge.net/p/openscoreformat/bugs/20/</id><updated>2009-07-08T10:29:13Z</updated><subtitle>Recent changes to 20: Signed manifest.xml are invalid against schema</subtitle><entry><title>Signed manifest.xml are invalid against schema</title><link href="https://sourceforge.net/p/openscoreformat/bugs/20/" rel="alternate"/><published>2009-07-08T10:29:13Z</published><updated>2009-07-08T10:29:13Z</updated><author><name>Mark Olleson</name><uri>https://sourceforge.net/u/markolleson/</uri></author><id>https://sourceforge.nete4fd1c164ce7423f38398aebbb39f422a076299d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The OSFPT, when signing packages, creates Manifest.xml documents which subsequently fail to validate against version 0.9.1 of the Manifest.xsd schema. &lt;/p&gt;
&lt;p&gt;This problem is caused a xs:keyref check between the ds:Reference URI (the URI for a signed asset) and the osfm:asset name attribute.   The former is relative to the manifest whilst the latter is an absolute path from the package root. &lt;br /&gt;
Version 1.0 of the manifest.xsd removes this check as the output of the .NET digital signature processor is legal and we will have to accept it. &lt;/p&gt;
&lt;p&gt;This does however suggest that the OSFPT doesn't validate it's own output when modifying XML documents. It is also a mystery how it then validates these instance documents open an unpack or validate operation.  Perhaps it discards the ds:signature section?&lt;/p&gt;
&lt;p&gt;This needs investigation.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>