Re: [opencsa-liaison] Latest/This Version URI for Schema/WSDL files

[Simon Nash <NASH@uk.ibm.com>]

Here's what the Bindings TC agreed:

The TC wishes the liaison sc to give
guidance on the granularity of namespaces across sca.  The TC recommends
that more than one namespace be allowd across the SCA TCs. In addition,
TC suggests investigating different namespaces for each extensibility,
but in parallel, a broad SCA namespace, that duplicates the definitions
in the fine grained definitions, for all the technologies that go into
that.

    Simon

Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156  Fax +44-1962-818999

Anish Karmarkar <Anish.Karmarkar@oracle.com>

25/03/2008 19:12

To	Michael Rowley <mrowley@bea.com>
cc	Mike Edwards/UK/IBM@IBMGB, opencsa-liaison@lists.oasis-open.org
Subject	Re: [opencsa-liaison] Latest/This Version URI for Schema/WSDL files

Michael,

Since we are the liaison reps from binding, were we (or was I) supposed
to do this?

-Anish
--

Michael Rowley wrote:
> +1
> 
> I don't think a meeting is necessary for this one, but I believe that
> the binding TC was looking for input from the Liason committee regarding
> whether or not the bindings should be in the SCA namespace, a binding
> specific namespace, or both.  I thought that someone from Bindings
was
> going to be formally asking the Liason committee to provide a
> recommendation on that.
> 
> Michael
> 
> 
> -----Original Message-----
> From: Anish Karmarkar [mailto:Anish.Karmarkar@Oracle.com] 
> Sent: Tuesday, March 25, 2008 11:31 AM
> To: Mike Edwards
> Cc: opencsa-liaison@lists.oasis-open.org
> Subject: Re: [opencsa-liaison] Latest/This Version URI for Schema/WSDL
> files
> 
> I'm happy to agree on this via email.
> So +1 to accepting the proposal as a recommendation.
> 
> -Anish
> --
> 
> Mike Edwards wrote:
>> Folks,
>>
>> I'm happy for us to accept this proposal as a recommendation to
all 
>> OpenCSA TCs.
>>
>> Do we need a meeting to discuss this further or can we agree this
by
> email?
>>
>> Yours,  Mike.
>>
>> Strategist - Emerging Technologies, SCA & SDO.
>> Co Chair OASIS SCA Assembly TC.
>> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great
Britain.
>> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431
 
>> Email:  mike_edwards@uk.ibm.com
>>
>>
>> *"Patil, Sanjay" <sanjay.patil@sap.com>*
>>
>> 21/03/2008 01:17
>>
>>                
 
>> To
>>                
 <opencsa-liaison@lists.oasis-open.org>
>> cc
>>                
 
>> Subject
>>                
 [opencsa-liaison] Latest/This Version URI for Schema/WSDL
files
>>
>>
>>                
 
>>
>>
>>
>>
>>
>> This is regarding naming of the schema files and the URI for storing
>> the schema files in the OASIS doc repository.
>>
>> The OpenCSA Steering Committee's recommendation for Filename and
URL 
>> Consistency [1] suggests the following format for schema file
name:
>> sca-[productName]-[versionNum]-[docType]-[yyyymm].[ext], an example
of
> 
>> which would look like: sca-assembly-1.1-schema-200712.xsd. Note
that 
>> this recommendation does not include any suggestions for URI for
the 
>> schema files in the OASIS doc repository.
>>
>> The SCA BPEL TC discussed this topic on the 3/19/08 conf-call
[2] and 
>> here are my notes from that discussion:
>>
>> - The contents of schema files typically do not change as frequently
>> as the associated specification files. In particular, the schema
files
> 
>> may remain unchanged while the document level of the associated
>> specification is moved up (CDxx -->CSxx --> OSxx). Therefore,
'This 
>> Version URI' for schema files does not have to include bits related
to
> 
>> the document-level.
>>
>> - 'This Version URI' for schema files needs to be changed whenever
the
> 
>> content of that schema file receives an update in order to ensure
that
> 
>> new versions do not overwrite the previous versions, and all the
>> versions remain accessible. A solution here would be for 'This
Version
> 
>> URI' for schema files to include the month-year of when updates
were 
>> applied to their content of the schema files.
>>
>> - Since the recommended schema file name already includes the
>> month-year info from the corresponding namespace URI, it would
be 
>> awkward to add another month-year info to the schema file name
>> corresponding to when updates were applied to its contents.
>>
>> - 'Latest Version URI' can include only the month-year of the
>> corresponding namespace URI, and need not include the month-year
>> corresponding to when updates were applied to the content of the
>> schema files.
>>
>> - The values for 'This Version URI' and 'Latest Version URI' for
>> schema files are independent of the URI value of the namespace
to 
>> which the definitions in the schema file contribute to.
>>
>> The SCA BPEL TC adopted the following resolutions:
>> This Version URI:
>> Format: 
>> _http://docs.oasis-open.org/opencsa/sca-bpel/[yyyy-of-namespace-URI]/[
>> mm-of-namespace-URI]/sca-bpel-1.1-schema-[yyyymm-of-content-update].xs
>> d_
>>
>>
>> Example: 
>> _http://docs.oasis-open.org/opencsa/sca-bpel/2007/12/sca-bpel-1.1-sche
>> ma-200803.xsd_
>>
>>
>> Latest Version URI:
>> Format: 
>> _http://docs.oasis-open.org/opencsa/sca-bpel/[yyyy-of-namespace-URI]/[
>> mm-of-namespace-URI]/sca-bpel-1.1-schema.xsd_
>>
>>
>> Example: 
>> _http://docs.oasis-open.org/opencsa/sca-bpel/2007/12/sca-bpel-1.1-sche
>> ma.xsd_
>>
>>
>> Note that the above discussion would also be relevant in regards
to 
>> the other artifacts associated with the specifications such as
WSDL
> files, etc.
>> Since this topic is concerning the various OpenCSA TCs, I was
given an
> 
>> action item to bring this issue to the attention of the OpenCSA
>> Liaison Subcommittee and suggest for consideration of the resolution
>> adopted by the SCA BPEL TC as a recommendation for the rest of
the
> OpenCSA TCs.
>> -- Sanjay
>> On Behalf of SCA BPEL TC
>>
>> [1] 
>> _http://lists.oasis-open.org/archives/sca-bpel/200710/msg00063.html_
>> [2] 
>> _http://lists.oasis-open.org/archives/sca-bpel/200803/msg00037.html_
>>
>>
>>
>> ----------------------------------------------------------------------
>> --
>>
>> /
>> /
>>
>> /Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with
>> number 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6
> 
>> 3AU/
>>
>>
>>
>>
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your
TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your
TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU