Re: [xdi-editors] questions about browser-viewable copies on xdi.org

[Markus Sabadello <markus.sabadello@xdi.org>]

Hmm I think the idea of the wiki might have been to only point to "done" working drafts (wd), i.e. the wiki points to xdi-core-1.0-wd02.xml, while somewhere in Github there is currently work being done on xdi-core-1.0-wd03.xml.

So maybe now that I have done some work on messaging and binding, perhaps their wd number can be increased, and the wiki can point to the "done" wd (02), while new work continues on the "next" wd (03).

Markus

On Fri, Nov 21, 2014 at 5:00 PM, Davis, Peter <Peter.Davis@neustar.biz> wrote:

Git is the official document repository. the xdi.org server is merely a convenience joseph set up which allows a browser to properly load the xml document and the associated style sheet(s).

sounds like we need to update the wiki to point to all of the specifications.

=peterd

On Nov 21, 2014, at 4:58 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

I'm again confused how we use the Github repo, XdiOneSpecs wiki page, Kavi, and xdi.org hosted documents in the spec writing process.

In Github we have xdi-core-1.0-wd02.xml, xdi-bindings-1.0-wd02.xml, xdi-messaging-1.0-wd02.xml

On the XdiOneSpecs wiki page, why do we only have a link to xdi-core-1.0-wd02.xml, but not to the others?

On the xdi.org server there is even xdi-core-1.0-wd03.xml, which is neither in Github on the master branch, nor on the XdiOneSpecs wiki page .

On the xdi.org server in /usr/share/nginx/xdi.org/xdi-spec-docbook, I tried to do a "git pull" to get the lastet versions of everything in the master branch, but there are uncommitted local changes, so the "git pull" doesn't work. Why do we manually edit the working drafts on the xdi.org server?

Markus