XDI TC Minutes

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

Date: Friday, 28 February 2014 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)

THE LINK TO THIS AGENDA AND LIVE MEETING MINUTES IS:

https://docs.google.com/document/d/1t5Mx0ITqJdLwo8wM5GD9lcqehgbgnrhk-k2sERwc7J0/edit

THE WEBEX INSTRUCTIONS FOR THIS MEETING ARE:

1. Go to https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&RT=MiMxMQ%3D%3D

2. If requested, enter your name and email address.

3. If a password is required, enter the meeting password: 5474

4. Click "Join".

5. Follow the instructions that appear on your screen.

To view in other time zones or languages, please click the link:

https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&ORT=MiMxMQ%3D%3D

PRESENTATIONS/DISCUSSIONS

Reassigning XDI Context Symbols

See these two messages on the mailing list:

Drummond asked if there was any disagreement about the proposal to reassign the + symbol for the legal authority space (i.e., companies, organizations, NGOs, trademarks, any other legal authority besides a natural person).

There was consensus that this reassignment makes sense due to the market confustion caused by Twitter’s defacto standardization of the @ symbol as the prefix for Twitter names.

The key question is, then, what symbol should be used for the dictionary space. Andy suggested using the # sign for that space. Peter felt that the # sign has been overloaded by Twitter (a problem similar to the @ sign), and thus should be avoided. He suggested $ would be better.

Peter also pointed out that # is that it is an anchor symbol in URLs, but we all agreed that multiple symbols in XDI addresses will need to be percent-encoded anyway, so this is not really a concern.

Drummond felt the opposite—that $ does not have any natural connotation of semantic tagging, whereas # has become widely used as a tagging prefix, including on other sites besides Twitter.

Joseph noted that he had suggested several years ago moving away from the Twitter due to the collision with @names, and he supports the change now.

Phil said that he’s not convinced that there is enough of a reason to have a separate legal/business namespace, but he wants to have more time to think about it. He agreed to have a direct conversation with Drummond about it early next week.

We then discussed the code base impact. Animesh said that the impact is primarily in the SDK and XDI messages. Markus was not able to attend the call, however he has made a list of the impact on the XDI2 code base. We want to be sensitive to the overall impact.

Drummond acknowledged that this is a very important decision, but also one we need to make very quickly. He suggested we continue the discussion on the list over the following week and make a decision on next Friday’s call.

Link Contract Addressing

Drummond and Markus have further discussed Link Contract patterns:

https://wiki.oasis-open.org/xdi/LinkContractPattern

https://wiki.oasis-open.org/xdi/LinkContractPattern/Discussion

Drummond asked what had been discussed earlier. Animesh explained what was covered.

We then ran through several examples of link contracts using the inner graph format. Animesh had a specific question about how governor contracts would be formatted. Drummond agreed to write up more specifics on the Discussion page, including multiple examples, so it was explicit how everything on the current main wiki page would map to the inner graph pattern on the Discussion page.

DECISION POINTS FOR THIS CALL

None scheduled.

DECISION POINT QUEUE REVIEW

The decision queue stack is shown on the following three auto-generated Category pages:

https://wiki.oasis-open.org/xdi/CategoryLastCall

https://wiki.oasis-open.org/xdi/CategoryCurrent

https://wiki.oasis-open.org/xdi/CategoryHighPriority

See also this list of proposals that need to be developed:

https://wiki.oasis-open.org/xdi/XdiPendingIssues

NEXT CALL

The next call is next week at the regular time.