Incorporating BP into P5 - Revision history

Kshawkin: updated to refer to GitHub

2015-10-25T17:01:45Z

updated to refer to GitHub

Kshawkin: clarified template line

2014-11-19T02:22:50Z

clarified template line

Kshawkin: removing sentence about only including those things applicable outside libraries, per recent discussion on tei-board-council

2013-05-12T17:43:01Z

removing sentence about only including those things applicable outside libraries, per recent discussion on tei-board-council

Kshawkin: SF link is now an Allura link

2013-04-06T18:23:44Z

SF link is now an Allura link

Kshawkin: removed "https" from SF link for viewing without logging in

2012-08-12T21:30:27Z

removed "https" from SF link for viewing without logging in

Kshawkin: new row: etaining punctuation marks in the text of a TEI document

2012-08-12T21:29:41Z

new row: etaining punctuation marks in the text of a TEI document

Kshawkin: Created page with "The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization]..."

2012-08-12T20:48:41Z

Created page with "The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization]..."

New page

The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization] on the TEI-C website to make it more discoverable by members of the community. But TEI Technical Council members are interested in incorporating into the TEI Guidelines those parts of our Best Practices that are applicable outside of the library community.

We invite all members of the TEI community to submit practices given in the BP for inclusion in the Guidelines. Requests for changes to the TEI Guidelines are made through the [http://tei.sourceforge.net/ TEI's Sourceforge site] so that all such requests are stored in a single place for Council members to process. You'll need to create an account in order to file a ticket. There are two types of tickets in use: a ''bug report'' and a ''feature request''. The latter is more likely to be appropriate for tickets arising from the BP.

There are some practices in the BP which have already become outdated thanks to more recent clarifications to the Guidelines. Most of these are mentioned in the list of [[Future changes to Best Practices for TEI in Libraries]]. You might consult this list before filing a report.

To claim an item, please add it to the table below. That will allow us to avoid duplication of effort in providing context for an issue. Once you create the ticket, please return to this page and add the ticket number below. That will allow people find other tickets to comment on or "follow" them in order to receive email updates when someone comments on an issue or implements it.

Thank you!

{| class="wikitable"
|-
! Description of aspect of the BP proposed for addition
! Name of volunteer to write up a SF ticket
! SF ticket number (once filed)
|-
|
|
|-
|}

[[Category:SIG:Libraries]]

@@ Line 1: / Line 1: @@
 The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization] on the TEI-C website to make it more discoverable by members of the community.
-We invite all members of the TEI community to submit practices given in the BP for inclusion in the Guidelines.  Requests for changes to the TEI Guidelines are made through the [http://tei.sourceforge.net/ TEI's Sourceforge site] so that all such requests are stored in a single place for Council members to process.  You'll need to create an account in order to file a ticket.  There are two types of tickets in use: a ''bug report'' and a ''feature request''.  The latter is more likely to be appropriate for tickets arising from the BP.
+We invite all members of the TEI community to submit practices given in the BP for inclusion in the Guidelines.  Requests for changes to the TEI Guidelines are made through the [https://github.com/TEIC/TEI/issues TEI's GitHub site] so that all such requests are stored in a single place for Council members to process.  You'll need to create an account in order to create an issue.
-There are some practices in the BP which have already become outdated thanks to more recent clarifications to the Guidelines.  Most of these are mentioned in the list of [[Future changes to Best Practices for TEI in Libraries]].  You might consult this list before filing a report.
+There are some practices in the BP which have already become outdated thanks to more recent clarifications to the Guidelines.  Most of these are mentioned in the [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues list of issues to be implemented in the BP].  You might consult this list before filing a report.
-To claim an item, please add it to the table below.  That will allow us to avoid duplication of effort in providing context for an issue.  Once you create the ticket, please return to this page and add the ticket number below. That will allow people find other tickets to comment on or "follow" them in order to receive email updates when someone comments on an issue or implements it.
+To claim an item, please add it to the table below.  That will allow us to avoid duplication of effort in providing context for an issue.  Once you create the issue, please return to this page and add the issue number below. That will allow people find other issues to comment on or "watch" them in order to receive email updates when someone comments on an issue or implements it.
 Thank you!
@@ Line 12: / Line 12: @@
 |-
 ! Description of aspect of the BP proposed for addition
-! Name of volunteer to write up a SF ticket
+! Name of volunteer to write up a GitHub issue
-! SF link (once ticket is created)
+! GitHub link (once issue is created)
 |-
 | retaining punctuation marks in the text of a TEI document
 | Kevin Hawkins
-| http://sourceforge.net/p/tei/feature-requests/377/
+| https://github.com/TEIC/TEI/issues/379
 |-
 | (your idea here!)

@@ Line 19: / Line 19: @@
 | http://sourceforge.net/p/tei/feature-requests/377/
 |-
+| (your idea here!)
+|
 |-

← Older revision		Revision as of 17:43, 12 May 2013
Line 1:		Line 1:
−	The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization] on the TEI-C website to make it more discoverable by members of the ~~community. But TEI Technical Council members are interested in incorporating into the TEI Guidelines those parts of our Best Practices that are applicable outside of the library~~ community.	+	The [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries] (BP) is now listed as a [http://www.tei-c.org/Guidelines/Customization/ community customization] on the TEI-C website to make it more discoverable by members of the community.

	We invite all members of the TEI community to submit practices given in the BP for inclusion in the Guidelines. Requests for changes to the TEI Guidelines are made through the [http://tei.sourceforge.net/ TEI's Sourceforge site] so that all such requests are stored in a single place for Council members to process. You'll need to create an account in order to file a ticket. There are two types of tickets in use: a ''bug report'' and a ''feature request''. The latter is more likely to be appropriate for tickets arising from the BP.		We invite all members of the TEI community to submit practices given in the BP for inclusion in the Guidelines. Requests for changes to the TEI Guidelines are made through the [http://tei.sourceforge.net/ TEI's Sourceforge site] so that all such requests are stored in a single place for Council members to process. You'll need to create an account in order to file a ticket. There are two types of tickets in use: a ''bug report'' and a ''feature request''. The latter is more likely to be appropriate for tickets arising from the BP.

@@ Line 17: / Line 17: @@
 | retaining punctuation marks in the text of a TEI document
 | Kevin Hawkins
-| http://sourceforge.net/tracker/?func=detail&aid=3556778&group_id=106328&atid=644065
+| http://sourceforge.net/p/tei/feature-requests/377/
 |-
+|

@@ Line 17: / Line 17: @@
 | retaining punctuation marks in the text of a TEI document
 | Kevin Hawkins
-| https://sourceforge.net/tracker/?func=detail&aid=3556778&group_id=106328&atid=644065
+| http://sourceforge.net/tracker/?func=detail&aid=3556778&group_id=106328&atid=644065
 |-
+|