I agree with Sunil's proposal.
> PS: Should the version nos. for reference, fnp, and wsrmfp be 1.1 or 1.0
?
I have no strong opinion with this.
I think 1.1 is better to avoid any confusion of mixing
different version number.
I also can update the spec, if it is better to do so before
next teleconference.
Or I can wait until the decision of Tuesday.
Thanks,
Iwasa
----- Original Message -----
From: "Sunil Kunisetty" <>
To: "Tom Rutt" <>
Cc: "wsrm" <>
Sent: Friday, June 04, 2004 2:48 PM
Subject: Re: [wsrm] Action Item status as of 6/3/04
>
>
> <!--[if !supportLists]-->1.2 <!--[endif]-->Action 060104-1 (Sunil)
pending
>
>
> Action: Sunil will come up with a proposal for the Namespaces and Schema
file locations.
>
> I haven't heard anything from the OASIS Technical Services Manager w.r.t.
mapping URIs to Files inspite of
> couple of reminders. He may be vacation.
>
> So in the spirit of making progress and wrapping up work, here is a
proposal based on some discussions
> this tuesday:
>
> a.. The namespaces have ".xsd" in them to make them easily
referencible without any mappings.
> b.. Namespaces follow both MM/YYYY convention in the URI and also the
version no. of the specification as suffix to the file name.
>
>
> Schema Namespace File name Prefix Description
> http://docs.oasis-open.org/wsrm/2004/06/ws-reliability-1.1.xsd
ws-reliability-1.1.xsd wsrm Schemas for the WSRM Elements
> http://docs.oasis-open.org/wsrm/2004/06/reference-1.1.xsd
reference-1.1.xsd ref Has the schema for ServiceRefType
> http://docs.oasis-open.org/wsrm/2004/06/fnp-1.1.xsd fnp-1.1.xsd
fnp Schema for F,P, and all Compositor constructs
> http://docs.oasis-open.org/wsrm/2004/06/wsrmfp-1.1.xsd
wsrmfp-1.1.xsd wsrmfp Schema for WSRM Features and Properties
>
> PS: Should the version nos. for reference, fnp, and wsrmfp be 1.1 or 1.0
?
>
> If there are no major objections, I'll upload a 'draft' version of these
schemas before the next con. call
> so that we can vote on these on that call.
>
> -Sunil
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.
