This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0002.html 4) Why the (implicit) requirement that SMLURI targets be XML? Surely the sml:targetRequired check is useful regardless of target media type?
SML model validation is defined for SML documents. An SML document is a well-formed XML document. In other words, an object that is not a well-formed XML document is not SML document. SML constraints are evaluated during SML model validation. If the target of an SML reference is something other than a well-formed XML document, the target would not be recognized as an SML document. Thus, that SML reference would be treated as unresolved.
Resolution in F2F meeting on 3/31: This is a good idea and may be considered for the next version of SML. The charter of the SML WG scopes the SML 1.1. work to cross-document validation of XML documents, and the SML WG believes that this is the right scope for SML 1.1 The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed. Please review the changes adopted and let us know if you agree with this resolution of your issue, by adding a comment to the issue record and changing the Status of the issue to Closed. Or, if you do not agree with this resolution, please add a comment explaining why. If you wish to appeal the WG's decision to the Director, then also change the Status of the record to Reopened. If you wish to record your dissent, but do not wish to appeal the decision to the Director, then change the Status of the record to Closed. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
resolution (conf call on 4/17/2008): Resolve as 'later' and remove the 'decided' keyword because the 2 week response period has elapsed (see comment# 2).
OK, but you're missing a clear opportunity. Requiring XML targets for any constraints which actually require descent into the target is of course sensible, but targetRequired clearly _doesn't_ require descent, and should be testable w/o regard to the media type of the target.
http://lists.w3.org/Archives/Public/public-sml/2008May/0001.html summarizes the discussion at 3/31 F2F that resulted in this bug being resolved as "RESOLVED LATER"