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

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

On Mon, Nov 24, 2014 at 11:40 PM, Joseph Boyle <boyle.joseph@gmail.com> wrote:

I checked in core spec drafts and git diff is now showing nothing. You’re welcome to try resetting though I don’t see any anomalies now. Please let me know when you’ve reset or decided not to, and I’ll start editing again.

I just did "git status", content on xdi.org seems up-to-date now with Github origin/master, so no reset needed.

 

http://xdi.org/xdi-spec-docbook/xdi/xdi-core-1.0/xdi-core-1.0-wd03.xml is now using the expected ../../htmlruntime path for the stylesheet, so that simply pulling the Git repo to a location on a web server should make it display correctly via HTTP.

Great, I think that's the right solution.

 

I think the ../../../DocBook path was from last year when I was thinking about having a separate repository for the DocBook files, but never followed through on that more than a symlink.

The DTD paths point to OASIS servers. I’m not sure if the browser display uses them at all; the PDF toolchain might. I had tried a couple of different ones to try to pick up the DocBook SVG module.

Joseph

On Nov 24, 2014, at 2:07 PM, Joseph Boyle <boyle.joseph@gmail.com> wrote:

I need to check in files first. I will let you know when I’m done. Actually I can try the reset myself then.

On Nov 24, 2014, at 1:02 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

Another question for you Joseph, do you have any explanation why the files on the xdi.org server differ from what's in Github?

Did you manually edit them on the server, or overwrite them?

I think we should do a "git reset --hard" on the xdi.org server, but I thought I'd ask you first.

You can do a "git diff" to see how they have been modified.

Markus

On Mon, Nov 24, 2014 at 9:07 PM, Joseph Boyle <boyle.joseph@gmail.com> wrote:

The problem is that uploaded drafts are on another server. www.oasis-open.org, not docs. Our final published specs will be on docs.oasis-open.org and should be able to reference the setup on that server.

So far I have just been manually fixing the path in draft copies as needed to display during editing, which is just a few words. I forget why I didn’t use a relative path for Git checkin - there may be a problem I’ve forgotten, so I’ll try it again.

On Nov 24, 2014, at 9:07 AM, Davis, Peter <Peter.Davis@neustar.biz> wrote:

the stylesheet can be found publicly here [1]. we could point to that while we are drafting.

=peterd

[1] http://docs.oasis-open.org/templates/DocBook/spec-0.4/stylesheets/oasis-specification-html.xsl

On Nov 24, 2014, at 12:16 AM, =Drummond Reed <drummond.reed@xdi.org> wrote:

Joseph, it sounds like you and Markus are in violent agreement on this. Who do we need to contact at OASIS to "make it so"?

On Sat, Nov 22, 2014 at 5:15 PM, Joseph Boyle <boyle.joseph@gmail.com> wrote:

We still should ask OASIS to host a copy of (or symlink) the DocBook installation from www.open-oasis.org, the server where uploaded drafts live. That would allow us to always use the HTTP form of the stylesheet reference, preferably from a fixed well-known relative address that might even let us leave out the domain name and make it domain independent.

On Nov 22, 2014, at 9:11 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

I'm just not sure about #3.

The stylesheet references in Github are currently very chaotic, sometimes it's this:

<?xml-stylesheet type="text/xsl"
href="" href="http://docs.oasis-open.org/templates/DocBook/spec-0.6/stylesheets/oasis-specification-html.xsl" target="_blank">http://docs.oasis-open.org/templates/DocBook/spec-0.6/stylesheets/oasis-specification-html.xsl"?>

Sometimes it's this:

<?xml-stylesheet type="text/xsl"
href="" href="http://xdi.org/xdi-spec-docbook/htmlruntime/spec-0.6/stylesheets/oasis-specification-html.xsl" target="_blank">http://xdi.org/xdi-spec-docbook/htmlruntime/spec-0.6/stylesheets/oasis-specification-html.xsl"?>

Sometimes it's this:

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

And sometimes it's this:

<?xml-stylesheet type="text/xsl"
href="">
I understand they all work or don't work under different circumstances, but we should have a rule for which one we use in Github, Kavi, xdi.org etc., and stick to that rule consistently in all specs.

Markus

​