Date: Thursday, 09 February 2012 USA
Time: 1:00PM - 2:30PM Pacific Time (21:00-22:30 UTC)
PLEASE DIAL ONE OF THE FOLLOWING NUMBERS:
1) Skype Number: +9900827047990866
(this will connect you directly to the conference room)
2) US/Canada Toll Number: +1-201-793-9022
3) International Toll Number (follow this with the Conference Room Number:
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)
THE GOTOMEETING FOR TODAY IS:
THE IDEARPAD LINK FOR TODAY IS:
Please preface each of your comments with your name to facilitate
transcription into the minutes.
1) IDTRUST BUDGET PROPOSAL
The previous proposal had some issues, so we'll discuss proposed modifications.
2) OPEN SOURCE PROJECT UPDATES
Mike Schwartz, Markus Sabadello
3) LITERAL CONTEXTS PROPOSAL
Drummond Reed posted updated versions of all 3 core XDI documents: http://lists.oasis-open.org/archives/xdi/201202/msg00007.html
The most significant update is the "literal contexts" proposal, in which all RDF literals are modeled with an XDI literal context. As explained in Drummond's message:
- This gives every literal in the XDI graph its own XDI address without using a cross-reference - simplifying navigation and XRI processing time.
- This makes it much cleaner to express and navigate XDI metadata, such as datestamps and versioning.
- This simplifies parsing and serialization, since all semantics describing a literal will be in the XDI subject identifying it,
and every XDI literal (now called a "terminal") will have an XDI
predicate consisting only of "!". (Note that Victor Grey has suggested
another XRI delimiter character could also be used for this - he
4) NESTED ROOT CONTEXTS PROPOSAL
The revised XDI docs also show nested root contexts. As explained in Drummond's message:
- This provides a clean way to model the relationship of different
local XDI graphs available at different XDI network endpoints for the
purposes of XDI discovery.
- This shows how a single physical XDI server (such as an LDAP server,
SQL database, NOSQL database, etc.) can implement a "multi-tenant" model
where it can host multiple independent local XDI graphs yet still have
them logically appear as part of the global XDI graph.
5) PROPOSALS FOR OPTIMIZING $GET - XDI QUERIES
Continuation of earlier discussion. See:
6) NEXT CALL