[tei-council] Duplicate pages on tei-c

Rebecca Welzenbach rwelzenbach at gmail.com
Wed Apr 10 23:18:27 EDT 2013


On the pages that Kevin mentions:
The page at http://www.tei-c.org/Guidelines/P5/get_p5.xml is fairly
short and repeats some of the same information available at
http://www.tei-c.org/Guidelines/P5/index.xml#body.1_div.1

Perhaps all of get_p5.xml could simply be collapsed into this
subsection of http://www.tei-c.org/Guidelines/P5/index.xml. Then
get_p5.xml (and the link to it) could be retired.

On the original redundancy Martin pointed out:
I like Martin's suggestion to add the instructions for contributors to
http://www.tei-c.org/Guidelines/P5/get.xml. As well, it looks like
tei-emacs has already been removed from get.xml, while it lingers in
tcw06.xml, so perhaps the former is more up to date.

But what would it mean to retire a council working paper, as Martin
proposed to do with tcw06.xml? All of these working papers have dates
attached to them. Even if most of the content of tcw06.xml is now
repeated elsewhere on tei-c.org, should it stay where it is as
evidence of documentation produced by the council in 2007?

Becky

On Tue, Mar 19, 2013 at 11:15 AM, Martin Holmes <mholmes at uvic.ca> wrote:
> On 13-03-19 06:50 AM, Kevin Hawkins wrote:
>> Martin, to clarify, when you say that get.xml isn't accessible from the
>> menu system, you mean that you can't find any page on www.tei-c.org from
>> which you can reach this page using either the drop-down navbar at the
>> top or the links on the left of any pages?  If so, I should note that as
>> a general rule, not all pages are in fact accessible this way.  For
>> example, http://www.tei-c.org/Activities/Council/Working/ lists 24
>> documents, but they're not listed to the left.
>>
>> I will, however, note that http://www.tei-c.org/Guidelines/P5/get.xml is
>> linked in the text of http://www.tei-c.org/Guidelines/P5/index.xml .  So
>> is http://www.tei-c.org/Guidelines/P5/get_p5.xml .  There seems to be
>> significant overlap in them.  Every time I sit down to think about how
>> to merge them, I recoil at the prospect and decide to put it off to
>> another day.
>
> I know, my heart is sinking too. But I think it's worth doing. I was
> thinking that we might have a single page with two sections:
>
> Checking out code as a user
>
> Checking out code as a contributor
>
> The page could live at the current get.xml location, and TCW 6 might
> then be retired. We have contributors who are not on Council, and I
> don't really think that the instructions for contributors should be
> different depending on whether they're on Council or not, so one page
> outside the Council area would presumably be sufficient.
>
> We also need to look at the status of the other projects listed on that
> page. Sebastian has already said that we can remove tei-emacs from
> documentation like this. It looks to me as though TEI-OO is now obsolete
> as well; Sebastian has written good working ODT converters (no longer
> specific to Open Office), and has completed the "plans for some filters
> for Microsoft Word". Shall we just remove that one?
>
> Cheers,
> Martin
>
>>
>> --K.
>>
>> On 3/19/2013 8:42 AM, Martin Holmes wrote:
>>> Hi there,
>>>
>>> This page:
>>>
>>> <http://www.tei-c.org/Guidelines/P5/get.xml>
>>>
>>> looks like a variant of this page:
>>>
>>> <http://www.tei-c.org/Activities/Council/Working/tcw06.xml>
>>>
>>> In addition, the first one (get.xml) doesn't seem to be accessible from
>>> the menu system.
>>>
>>> Could we remove the first one, or does anyone know of links to it, or a
>>> need for it?
>>>
>>> Cheers,
>>> Martin
>
> --
> Martin Holmes
> University of Victoria Humanities Computing and Media Centre
> (mholmes at uvic.ca)
> --
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived


More information about the tei-council mailing list