Issue 7765: Unnecessary requirement to reference the physical schema file                                                                                                                                           (ras-ftf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: P20 of RFC states "The actual filename may vary for the profile file,
but the XML instance documents must reference the schema file." (and
refers to xsi:schemaLocation) This is out of step with common practice
for XML: surely the only thing required is the URI of the Schema via
xmlns.

Resolution: 
Revised Text: Resolution:
Update the RAS 2.0 final document to remove this requirement.

// DONE - updated section 6.4.1, 11 March 2005:
The offending text is below, I've bolded the "must" words below to emphasize:
Every manifest document must reference the XML schema document associated with the profile that can be used to validate the manifest document.  The profile's schema document can be referenced with the xsi:schemaLocation as an attribute of the <asset> element.  For example:
<asset xsi:schemaLocation="RAS_defaultprofile_ver2.1.xsd" 
	name="My Asset" id="369BEA01-B4C2-4d47-99C8-6E44079207F1">
The actual filename may vary for the profile file, but the XML instance documents must reference the schema file.  The schema file is expected to accompany the manifest document, however this is not required.  The profile schema file may be referenced with a URL, and accessed through a network.
The updated text is below, I bold the changed word and show a strike through of what I deleted:
Every manifest document may reference the XML schema document associated with the profile that can be used to validate the manifest document.  The profile's schema document can be referenced with the xsi:schemaLocation as an attribute of the <asset> element.  For example:
<asset xsi:schemaLocation="RAS_defaultprofile_ver2.1.xsd" 
	name="My Asset" id="369BEA01-B4C2-4d47-99C8-6E44079207F1">
The actual filename may vary for the profile file, the only thing required is the URI of the schema via xmlns., but the XML instance documents must reference the schema file.  The schema file is expected to accompany the manifest document, however this is not required.  The profile schema file may be referenced with a URL, and accessed through a network

Actions taken:
September 20, 2004: received issue
August 1, 2005: closed issue
Discussion: 

End of Annotations:=====
ssary requirement to reference the physical schema file
P20 of RFC states "The actual filename may vary for the profile file,
but the XML instance documents must reference the schema file." (and
refers to xsi:schemaLocation) This is out of step with common practice
for XML: surely the only thing required is the URI of the Schema via
xmlns.