Re: [xdi] Minutes: XDI TC Telecon Friday 2014-10-31

On Sat, Nov 1, 2014 at 1:14 PM, =Drummond Reed <drummond.reed@xdi.org> wrote:

+1 to starting the Glossary docbook file ASAP but I think we should also maintain the Glossary wiki page, or at least a public version of the Docbook file (as we have been doing for the Docbook spec drafts), so we all can see the definitions easily.

I don't think there is an easy way to automatically create public HTML versions of a Docbook file every time it is changed.

So it would probably be better to only have the wiki page for now, to avoid duplication.

Also, Markus, in the minutes you said:

We had consensus that most likely we would not need to support nested cross references.

As I recall, the consensus was to stick with the current ABNF definition of xref, which includes 3 options:
A URI
An XDI name
A common address (which can include a cross-reference).
My vote would be to keep this ABNF for simplicity even though it does technically allow nested cross-references.

Right, I agree, sorry the way I wrote it was misleading.
So we said we would keep this rule the way it is, even though right now we don't see a need for nested cross-references.

=Drummond

On Fri, Oct 31, 2014 at 7:08 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
Sounds good to me.
And we said we do that for all specs except Core.

How about we create that Glossary docbook file right now and use it instead of the Glossary wiki page..?

Markus

On Fri, Oct 31, 2014 at 3:10 PM, Davis, Peter <Peter.Davis@neustar.biz> wrote:

On Oct 31, 2014, at 5:37 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

We agreed on the following approach:

Each spec will have a glossary in the front-matter of the document that will define the terms used in that document.

Any spec term that has an official definition in a specific spec will reference that spec.

Markus, thanks again for your awesome minutes. One clarification wrt Glossary:

What I described was:

A: one canonical XML (docbook) for all terms

B: each spec includes (via xinclude) all the terms used in that particular spec, placed in the introductory front matter

there is a distinct difference between 1 and A IMV.

=peterd

xdi message