OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xdi] RE: [External] [xdi] Bill: RE your other topics in your response to Minutes: XDI TC Telecon Friday 2013-03-15

Just a quick note that I just read your whole post about ADDI, and through your links I actually ended up (re-)reading some sections of Fielding's dissertation on REST.

I think ADDI is a very promising initiative, and I believe it makes a lot of sense to look beyond the classic synchronous HTTP request/response pattern that is so commonplace everywhere.

Since it goes without saying that we'll all keep working closely with each other, I'm looking forward to the ADDI / XDI exchange process where we can mutually learn from the areas where the two technologies respectively excel :)

all the best,

On Mon, Mar 18, 2013 at 10:03 AM, Barnhill, William [USA] <barnhill_william@bah.com> wrote:

+1 on all.

LATEX is good, and used by everyone for papers, but not natively supported by Github as far as I know.

Yes on ADDIE (or rather ADDI, see further on) being that protocol, though I have been playing with two names.  ADDIE is a more memorable and pronounceable acronym, but is also more in use on the web and verbose when expanded (Async Data Discovery and Interchange Ecosystem). ADDI is less memorable, but also not used much and less wordier when expanded.  I was leaning toward ADDIE but am now leaning back toward ADDI.  For more on the effort see http://www.nodal.info/2013/02/announcing-addi.html.


Kind regards,


Bill Barnhill

Booz Allen Hamilton - Belcamp,MD


Cell: 1-443-924-0824

Desk: 1-443-861-9102


From: xdi@lists.oasis-open.org [mailto:xdi@lists.oasis-open.org] On Behalf Of Drummond Reed
Sent: Monday, March 18, 2013 4:20 AM
To: Barnhill, William [USA]
Subject: [External] [xdi] Bill: RE your other topics in your response to Minutes: XDI TC Telecon Friday 2013-03-15


On Sat, Mar 16, 2013 at 6:23 AM, Barnhill, William [USA] <barnhill_william@bah.com> wrote:

Thanks for discussing the feedback at the meeting.  Unfortunately (well, from an XDI point of view) I'll be on a cruise ship during the next call, without internet or phone.  As a result I thought I'd send out some more thoughts in email.  


I think IIW is a great target for a release date.  I'd recommend earlier for a releasable product though, which will allow socializing the spec docs with key people, and revising if needed, prior to IIW.  In other words I think IIW is a great target for a beta release, but not for an alpha one.


Agreed. We'll basically start getting them out as soon as we can.



On the spec format, DITA is in my opinion the technical winner...but didn't get adopted in the TC so we need something people are more familiar with.  XHTML is a possibility, but I'd caution against using XHTML as HTML (in other words writing XHTML but publishing as a non-XHTML mime type).  That was a big trend when XHTML was on the rise, as a way of getting around the strictness of XHTML syntax, but it means the browser is basically just treating it as a flavor of HTML. I'd actually recommend MarkDown instead, for the following reasons: (1) Github supports MarkDown rendering out of the box if the file has the suffix MD; (2) Github supports MarkDown editing on the site now; (3) MarkDown, while inferior to DITA from a full-kit publishing perspective, still is an intermediate format that can be rendered to HTML5 or PDF, and probably does cover 80% or so of markup needs.  I do think using Github is a clear win.  


Thanks, that's a great perspective. Peter Davis has put in a good word for Latex. We'll figure out the best option as quickly as we can.



On "Drummond explained that XDI forms a bridge between two fields..."  I think Drummond is right, but I also think it is broader than that.  Let me digress a little about Semiotics.  From wikipedia, semiotics is "is the study of signs and sign processes (semiosis), indication, designation, likeness, analogymetaphorsymbolism, signification, and communication.".  Semiotics in digital systems and communities is my specialty.  The wikipedia article says further on, paraphrased, that... semiotics is often divided into three branches: (1) Semantics: Relation between signs and the things to which they refer; their denotata, or meaning; (2) Syntactics: Relations among signs in formal structure; (3) Pragmatics: Relation between signs and the effects they have on the entities who interact with them.  Up until now each Web technology has focused on one of those three.  URLs focus on syntactics. RDF focuses on semantics.  XACML focuses on pragmatics.  Granted, these are broad interpretations of the focus of these technologies, but I think it fits.  The revolutionary leap enabled by XRI addressing that both XDI and ADDIE take is the combined focus on all three branches of semiotics as they apply to the data web.  XDI will address synchronous use cases, ADDIE asynchronous.


Cool. The analogy certainly makes sense to me. I take it ADDIE is the name for the async protocol you mentioned on an earlier call?




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]