Minutes: XRI TC Telecon 2-3PM PT Thursday 2010-01-14

[Drummond Reed <drummond.reed@xdi.org>]

Following are the minutes of the unofficial telecon of the XRI TC at:

Date:  Thursday, 14 January 2010 USA
Time:  2:00PM - 3:00PM Pacific Time (21:00-22:00 UTC)

ATTENDING

Scott Cantor

Markus Sabadello

Will Norris

George Fletcher

John Bradley

Drummond Reed

Nat Sakimura


1) XRD NAMESPACE REVISIONING POLICY

See the thread currently ending at:

  http://lists.oasis-open.org/archives/xri/200912/msg00050.html

Scott sent two versions. Following is the second and most current one:

 

**** PROPOSED NAMESPACE VERSIONING POLICY *****

 

It is the intent of the OASIS XRI Technical Committee that the Extensible
Resource Descriptor namespace URI will not change arbitrarily with each
subsequent revision of the corresponding XML Schema document but rather
change only when a subsequent revision, published in conjunction with a
Committee Specification, results in backwardly-incompatible changes from a
previously published Committee Specification.

While it is also the intent that backwardly-incompatible changes will not
occur between Committee Drafts, the Technical Committee reserves the right
to make such changes without changing the namespace URI. In such cases,
consultation with the implementation community will be sought before doing
so, but the final decision rests with the TC's voting members.

Under this policy, the following are examples of backwards-compatible
changes that would not result in assignment of a new namespace URI:

   * addition of new global element, attribute, complexType and simpleType
definitions
   * addition of new elements or attributes in locations covered by a
previously specified wildcard
   * modifications to the pattern facet of a type definition for which the
value-space of the previous definition remains valid or for which the
value-space of the preponderance of instances would remain valid
   * modifications to the cardinality of attributes or elements for which
the value-space of possible instance documents conformant to the previous
revision of the schema would still be valid with regards to the revised
cardinality rule

 

******** END EXCERPT ********

Scott made the point that this text, based on the original version, does not really address forwards compatability, which is as big if not a bigger issue than backwards compatability. Thus he believes the policy should say that any change to a schema that was not forwards- or backwards-compatable should result in a change to the namespace. The TC agreed, and Scott will post another version.

 

# ACTION: Scott will post a V3.

 

UPDATE: Scott has already posted V3:

 

            http://lists.oasis-open.org/archives/xri/201001/msg00036.html


2) PROGRESS AND REMAINING OPEN ISSUES TOWARDS XRD 1.0 CD 02

Will has been working on Working Draft 12, so he led us through any open questions he had based on the provisional draft he sent to the list:

 

            http://lists.oasis-open.org/archives/xri/201001/msg00033.html 

 

We discussed the new wording in section 2.2. No further changes were suggested.

 

We reviewed section 7, in particular 7.1. One question was whether the definition of an "XRD document" includes one rooted on either the XRD or XRDS element. We discussed whether XRI Resolution 3.0 will need separate media types for XRD and XRDS. John pointed out that XRI Resolution 2.0 actually never used the different media types. There was consensus that we would like to avoid two different media types going forward.

 

Scott suggested that one option is to formally define XRD and XRDS documents, and then have the conformance for XRDS documents point to the XRD conformance requirements.

 

Scott also suggested moving the signature requirement into the normative part of the spec, and being more granular about conformance, i.e., defining an XRD Consumer and and XRD Consumer with Signatures (and the same for XRD Provider).

 

After some discussion there was consensus to proceed with this.

 

# ACTION: SCOTT will make the suggested changes in coordination with Will.

 

# ACTION: ALL TC MEMBERS should do a full read-through of Working Draft 12 when it is posted and send any feedback to the list ASAP.

 

 

3) XRD 1.0 CD 02 SCHEDULE

 

There was agreement that we are very close, so the plan is to hold the CD 02 vote either starting after next week's telecon or at worst the week after that.


4) XRI SYNTAX 3.0 AND XRI RESOLUTION 3.0

Drummond is now aiming to have the XRI Syntax 3.0 WD 03 (content complete) by the time the XRD CD 02 vote is ready.


5) NEXT CALL

 

Next week at the regular time.