[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda: XRI TC Telecon 2-3PM PT Thursday 2009-08-20
Following is the agenda for the unofficial telecon of the XRI TC at: Date: Thursday, 20 August 2009 USA Time: 2:00PM - 3:00PM Pacific Time (21:00-22:00 UTC) The telecon bridge supports both standard phone and direct Skype connections: 1) Skype Number: +9900827047990866 (this will connect you directly to the conference room) 2) US/Canada Toll Number: +1-201-793-9022 7990866# 3) US/Canada Toll-free Number: : +1-888-350-0075 7990866# (please use ONLY if you cannot connect via Skype or the toll number above): 4) International Toll Number (follow this with the Conference Room Number 7990866#): Austria (0820 401 15470) Belgium (0703 57 134) France (0826 109 071) Germany (0180 500 9527) Ireland (0818 270 968) Spain (902 885 791) Switzerland (0848 560 397) United Kingdom/Northern Ireland (0870 0990 931) AGENDA 1) PUNCHLIST OF XRD 1.0 ISSUES Will, Eran, and Drummond have prepared a punchlist of remaining issues for XRD 1.0 WD05. http://wiki.oasis-open.org/xri/XrdOne/SpecHome The majority of the call will be spent going over these issues (1A thru 1I below). 1A) SCHEMA ISSUE: RELAX OR XSD? We have a key issue: there is no authoritative RelaxNG schema for XML dSig. Since we inherit a significant portion of it for XRD signatures. 1B) KEYWORDS IN UPPERCASE Will agrees we should do this. Unless anyone disagrees, we will make this change. Ideally this is done as part of either the DocBook template or the CSS display. 1C) ALIAS ELEMENT DEFINITION Need to close on aligning this with Subject. 1D) EXPIRES AND CACHING Should we say that bindings to specific transport protocols MUST define what to do about conflicts? If so, this should be done in LRDD for HTTP/S binding. 1E) URI TEMPLATE VARIABLE NAMES Three issues 1F) NAME FOR REL FOR LINKED XRD (CURRENTLY #SEE-ALSO) Drummond has some misgivings about #see-also (a URI for a non-information resource). Will and Drummond discussed this and see three options: a) #see-also (or something else from the SemWeb) b) #equiv-xrd (or something similar we define that is explicitly ours) c) #application/xrd+xml (the mime type) 1G) SUBJECT MATCHING FOR XRIS 1H) REPLACEMENT FOR TERM "XRD CONSUMING APPLICATION"? This occurs 26 times in the spec. Potential replacements are either "XRD consumer" or "XRD processor". 1I) XRDS SECTION Will and Drummond discussed this. By adding a short section at the end (it would become section 5 and Conformance would become section 6), the XRD spec would also be authoritative for the super-simple XRDS wrapper needed to define a sequence of XRDs. XRI Resolution 3.0 is not the only application that will need this - any potential application (such as grid computing) that wants an XRD processor to navigate a set of linked XRDs based on some discovery criteria and report back the resulting path will need an XRD sequence. 2) LRDD - SUBJECT OF A HOST-META XRD Representation of Subject sets was discussed a bit on the call last week and followed up on the mailing list. Is this matter closed? http://lists.oasis-open.org/archives/xri/200908/msg00007.html 3) OTHER LINK HEADER/HOST META/LRDD STATUS/ISSUES http://tools.ietf.org/html/draft-nottingham-http-link-header http://tools.ietf.org/html/draft-nottingham-site-meta http://tools.ietf.org/html/draft-hammer-discovery Eran. 4) XRI SYNTAX 3.0 WORKING DRAFT 02 STATUS/ISSUES Drummond plans to post Working Draft 02 before today's call. 5) NEW BUSINESS 6) NEXT CALL
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]