Re: [xdi] Github repo access

If I put this into xdi-bindings-1.0-wd02.xml, then the error goes away and I can view it, but without the colors and oasis logo.

Also, I think you broke xdi-core-1.0-wd02.xml yesterday, it seems it now has an unresolved merge conflict :)

<<<<<<< HEAD
href=""><!--DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "https://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"-->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook SVG Module V1.1CR1//EN" "http://www.oasis-open.org/docbook/xml/svg/1.1CR1/dbsvg.dtd"
=======
href=""><!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "https://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
>>>>>>> security

Markus

On Wed, Oct 1, 2014 at 9:44 PM, Davis, Peter <> wrote:

i always make the references relative:

<?xml-stylesheet type="text/xsl" href="">

=peterd

On Oct 1, 2014, at 15:34 PM, Markus Sabadello <> wrote:

Do you just open the local file, or are you running a webserver on localhost and view it that way?

I tried both, same result ..

One way or the other, the way we reference the stylesheets should be the same in all specs.

Markus

On Wed, Oct 1, 2014 at 6:16 PM, Le Van Gong, Hubert 
<> wrote:

hmm, bizarre. The document loads correctly in Safari and has the same look as XDI-Core.

I do see the error below in the console but I'm not sure it's a real problem.

[Error] Unsafe attempt to load URL 
http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd from frame with URL 
http://xdi.org/xdi-spec-docbook/xdi/xdi-bindings-1.0/xdi-bindings-1.0-wd02.xml. Domains, protocols and ports must match. (xdi-bindings-1.0-wd02.xml, line 27)

Thanks,

Hubert

On Oct 1, 2014, at 8:20 AM, =Drummond Reed <> wrote:

Joseph has worked on debugging these stylesheets—he had to deal with the same thing with XDI Core. Joseph, any ideas here?

On Wed, Oct 1, 2014 at 1:45 AM, Markus Sabadello 
<> wrote:

Hmm I'm having some problems with the stylesheets..

If I try to view it here:

http://xdi.org/xdi-spec-docbook/xdi/xdi-bindings-1.0/xdi-bindings-1.0-wd02.xml

Then all the OASIS styles seem to be missing.

If I try to view it locally, I get this error in the browser:

Error loading stylesheet: An unknown error has occurred (805303f4)

http://xdi.org/xdi-spec-docbook/htmlruntime/spec-0.6/stylesheets/oasis-specification-html-offline.xsl

Any ideas?

Markus

On Tue, Sep 30, 2014 at 8:46 PM, Le Van Gong, Hubert 
<> wrote:

Thanks Markus,

I have now committed the latest version of the XDI Bindings spec (working draft 02).

This version also includes the titles for the 2 additional bindings we discussed (artifact and browser).

Thanks,

Hubert

On Sep 30, 2014, at 10:00 AM, Le Van Gong, Hubert <> wrote:

Greetings,

I'm trying to add my version of the XDI-binding spec into the Github repo but get an authN failure.

Who can add me as a committer to this project?

My Github account is hubert-levangong

Thanks,

Hubert

--

Hubert A. Le Van Gong

Distinguished Engineer, Technology Foundry

San Jose, CA 95129

USA

--------------------------------------------------

email: 

=hubert

cell: +1.571.449.1433

tel: 
+1.415.659.1492

--

Hubert A. Le Van Gong

Distinguished Engineer, Technology Foundry

San Jose, CA 95129

USA

--------------------------------------------------

email: 

=hubert

cell: +1.571.449.1433

tel: 
+1.415.659.1492

--

Hubert A. Le Van Gong

Distinguished Engineer, Technology Foundry

San Jose, CA 95129

USA

--------------------------------------------------

email: 

=hubert

cell: +1.571.449.1433

tel: 
+1.415.659.1492

Peter Davis: Neustar, Inc.

Distinguished Engineer, Director, Neustar Foundry

45980 Center Oak Plaza Sterling, VA 20166

[T] +1 571 434 5516 [E]
 [W] 
http://www.neustar.biz/ [X] xri://@neustar*pdavis [X]
xri://=peterd

The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received
 this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.