[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes: XRI TC Telecon 2-3PM PT Thursday 2009-09-17
Following are the minutes of for the unofficial telecon of the XRI TC at: Date: Thursday, 17 September 2009 USA Time: 2:00PM - 3:00PM Pacific Time (21:00-22:00 UTC) ATTENDING Will Norris Drummond Reed Markus Sabadello Eran Hammer-Lahav Breno de Medeiros AGENDA 1) LINKED XRD PROCESSING ISSUE http://www.oasis-open.org/committees/download.php/34072/xrd-1.0-wd06.html The one outstanding issue holding up a Committee Draft at this point is the one raised on the mailing list by Eran: processing of linked XRDs and "includes/replaces" semantics. It turns out Eran and Drummond and Wil all had different assumptions about how linked XRDs would be processed. Drummond thought that every linked XRD is an "equally valid descriptor" of the described resource, and that all information in the linked XRD (including Alias, Types, etc.) should be considered IF a linked XRD needs to be processed. Eran pointed out this would require that XRD consumers follow every linked XRD to determine if there were any required types. Eran brought up the use case of "full delegation" of an XRD and pointed out that #see-also links do not actually accomplish this because not all elements of the linked XRD are processed - only the <Link> elements in the linked XRD are processed. The problem with #see-also links is that since they are "partial includes", they require complex processing on behalf of an XRD library. You can't, in Eran's words, "just give the XRD to an XML parser" and start inspecting the tree. Instead you have to go through the process of checking and building a composite XML document first. The attendees on the call discussed it at length but could not come up with a compelling use case for why we should not drop #see-also in favor of #replace because the latter produces a significantly simpler processing model. The best case for keeping #see-also is "local override" of a delegated XRD, e.g., the owner of a blog keeping a local XRD that describes local services and then delegates to a linked XRD for everything else. [Note: Drummond's done more thinking about this since the call; see his email to the list about this option.] Eran believes #replace should be a link for the same reason #see-also was, i.e., it enables using all the same semantics and trust mechanisms. #ACTION: ERAN AND WILL to put this into Working Draft 07. 2) SCHEDULE FOR COMMITTEE DRAFT 01 VOTE The consensus was to put together a proposed final Working Draft 07, push it out as soon as it is ready, and make it a Last Call before a vote. 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 sent a link to the list to the new draft -- hopefully final -- of site meta: http://www.ietf.org/id/draft-nottingham-site-meta-03.txt 4) XRI SYNTAX 3.0 WORKING DRAFT 03 STATUS/ISSUES Drummond caught a bad cold prior to last week's trip to DC so no progress on this yet. 5) NEXT CALL Next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]