Re: [security-services] work product review

[Mary McRae <mary.mcrae@oasis-open.org>]

Hi Scott,

    I don't think most TCs do this, but that's fine - although it  
needs to reference the specific version of the spec it's associated  
with (not the filename, but the reference).

   On the other hand, no schema was previously identified; nor was it  
included in the public review notice; nor does it live at the location  
you've identified. Would the addition of a normative schema not be a  
substantive change?

Mary





On Oct 27, 2009, at 9:48 PM, Scott Cantor wrote:

> Thanks, one last question...historically we have never named schema
> artifacts with the publication status or draft number because people  
> get
> annoyed by schemas changing names (due to location hints for editors  
> and so
> forth).
>
> That makes it impossible to point directly to a versioned artifact  
> in the
> normative reference, but if that's the policy, then I'll upload a  
> renamed
> copy.
>
> -- Scott
>
>