Prefix Definition Proposal - Revision history

Mholmes at 15:18, 27 March 2014

2014-03-27T15:18:55Z

Piotr Banski: /* Notes */ +1 note (potential security issue)

2012-12-17T17:28:19Z

‎Notes: +1 note (potential security issue)

Mholmes at 01:28, 16 November 2012

2012-11-16T01:28:50Z

Mholmes: /* = New Guidelines Section */

2012-11-16T01:24:26Z

‎= New Guidelines Section

Mholmes: /* Revisions to Guidelines */

2012-11-16T01:23:59Z

‎Revisions to Guidelines

Mholmes: /* Revisions to Guidelines */

2012-11-16T01:18:11Z

‎Revisions to Guidelines

Mholmes: /* Revisions to Guidelines */

2012-11-16T01:11:26Z

‎Revisions to Guidelines

Mholmes: /* Notes */

2012-11-16T01:10:59Z

‎Notes

Kshawkin: /* Notes */ appraisal by Kevin Hawkins

2012-11-14T04:10:18Z

‎Notes: appraisal by Kevin Hawkins

Kshawkin: /* Notes */ split off a new section for footnotes

2012-11-14T04:09:21Z

‎Notes: split off a new section for footnotes

← Older revision		Revision as of 15:18, 27 March 2014
Line 1:		Line 1:
		+	'''NOTE: This proposal has now been accepted and is a part of the TEI Guidelines: [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html#SAPU[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html#SAPU]].'''
		+
	This page contains a draft proposal for a framework whereby private URI schemes and other similar abbreviated pointing systems used in TEI attributes with datatypes of data.pointer can be documented and dereferenced. The feature request ticket relating to this proposal is [http://purl.org/tei/fr/3576367[http://purl.org/tei/fr/3576367]].		This page contains a draft proposal for a framework whereby private URI schemes and other similar abbreviated pointing systems used in TEI attributes with datatypes of data.pointer can be documented and dereferenced. The feature request ticket relating to this proposal is [http://purl.org/tei/fr/3576367[http://purl.org/tei/fr/3576367]].

← Older revision		Revision as of 17:28, 17 December 2012
Line 138:		Line 138:

	This looks fine. It's basically a more powerful version of @xml:base. ([[User:Kshawkin\|Kshawkin]] 23:10, 13 November 2012 (EST))		This looks fine. It's basically a more powerful version of @xml:base. ([[User:Kshawkin\|Kshawkin]] 23:10, 13 November 2012 (EST))
		+
		+	I don't think xml:base is a good analogy, but that is beside the point. What I am somewhat uneasy about here is -- as of this moment purely theoretical -- a potential security risk. Imagine a system where you include a single instance of the header into thousands of individual documents (if you don't want to imagine that, download a sample of the National Corpus of Polish). That obviously provides flexibility (that's why we have used it in this way), but, on the other hand, in contrast to tag URIs, a single attack at the directory where the header is kept results in thousands of changes throughout, and even if (theorizing feebly now...) the result is a kind of DOS attack, whereby you make all those files that use this system try to retrieve something from a single specified URL, it can still be somewhat painful in effect. Don't get me wrong: I think this system is neat. But also extremely powerful (even the fact that it acts on both sides of the '#' is a neat but also very powerful property), and robust systems naturally have the potential to open up serious security holes, when abused or even only misused. The question now is: do we bother. [[User:Piotr Banski\|Piotr]] 12:28, 17 December 2012 (EST)

	== Footnotes ==		== Footnotes ==

← Older revision		Revision as of 01:28, 16 November 2012
Line 1:		Line 1:
−	This page contains a draft proposal for a framework whereby private URI schemes and other similar abbreviated pointing systems used in TEI attributes with datatypes of data.pointer can be documented and dereferenced.	+	This page contains a draft proposal for a framework whereby private URI schemes and other similar abbreviated pointing systems used in TEI attributes with datatypes of data.pointer can be documented and dereferenced. The feature request ticket relating to this proposal is [http://purl.org/tei/fr/3576367[http://purl.org/tei/fr/3576367]].

	'''NOTE: This document is a second draft of the proposal [http://wiki.tei-c.org/index.php/Private_URI_Schemes Private URI Schemes]. A redraft was requested by Council at the meeting in Oxford in September 2012.'''		'''NOTE: This document is a second draft of the proposal [http://wiki.tei-c.org/index.php/Private_URI_Schemes Private URI Schemes]. A redraft was requested by Council at the meeting in Oxford in September 2012.'''

@@ Line 110: / Line 110: @@
 == Revisions to Guidelines ==
-=== New Guidelines Section ==
+=== New Guidelines Section ===
 A proposed new section for the Guidelines is available for comment and editing here:

@@ Line 110: / Line 110: @@
 == Revisions to Guidelines ==
 A proposed new section for the Guidelines is available for comment and editing here:
@@ Line 116: / Line 117: @@
 The section would be located between the current 16.2.2 (Pointing locally) and 16.2.3 (W3C element() Scheme), and is entitled "Using abbreviated pointers".
-Other required changes to the Guidelines:
+=== Change to definition of @matchPattern ===
 The definition of @matchPattern would need to be revised slightly as it's moved into the new attribute class. Currently it says "specifies a regular expression against which the values of cRef attributes can be matched"; this would need to be redrafted, either to extend it:
@@ Line 127: / Line 128: @@
 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-cRefPattern.html [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-cRefPattern.html]]
 == Notes ==

← Older revision		Revision as of 01:18, 16 November 2012
Line 115:		Line 115:

	The section would be located between the current 16.2.2 (Pointing locally) and 16.2.3 (W3C element() Scheme), and is entitled "Using abbreviated pointers".		The section would be located between the current 16.2.2 (Pointing locally) and 16.2.3 (W3C element() Scheme), and is entitled "Using abbreviated pointers".
		+
		+	Other required changes to the Guidelines:
		+
		+	The definition of @matchPattern would need to be revised slightly as it's moved into the new attribute class. Currently it says "specifies a regular expression against which the values of cRef attributes can be matched"; this would need to be redrafted, either to extend it:
		+
		+	"specifies a regular expression against which the values of cRef attributes (in the context of cRefPattern) or data.pointers (in the context of prefixDef) can be matched."
		+
		+	Alternatively, it could be generalized:
		+
		+	"specifies a regular expression against which the values of other attributes can be matched."
		+
		+	[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-cRefPattern.html [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-cRefPattern.html]]

	== Notes ==		== Notes ==

@@ Line 112: / Line 112: @@
 A proposed new section for the Guidelines is available for comment and editing here:
-[[http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/temp-dev/prefix_definition_proposal_draft.xml?view=markup]]
+[http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/temp-dev/prefix_definition_proposal_draft.xml?view=markup[http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/temp-dev/prefix_definition_proposal_draft.xml?view=markup]]
 The section would be located between the current 16.2.2 (Pointing locally) and 16.2.3 (W3C element() Scheme), and is entitled "Using abbreviated pointers".

← Older revision		Revision as of 01:10, 16 November 2012
Line 107:		Line 107:

	Council discussions in Oxford in September 2012 suggested that it will often be useful or necessary to provide multiple expansions for a single prefix. In the example of the EEBO link above, for instance, it might be helpful to provide users who do not have access to EEBO with some alternative link to a public lower-resolution image, or some other helpful information. For this reason, @ident rather than @xml:id is used to specify the prefix, so that multiple dereferencing methods can be described. Processors may choose either to implement the first method for each specific prefix, or generate multiple links. The TEI stylesheets would probably do the former.		Council discussions in Oxford in September 2012 suggested that it will often be useful or necessary to provide multiple expansions for a single prefix. In the example of the EEBO link above, for instance, it might be helpful to provide users who do not have access to EEBO with some alternative link to a public lower-resolution image, or some other helpful information. For this reason, @ident rather than @xml:id is used to specify the prefix, so that multiple dereferencing methods can be described. Processors may choose either to implement the first method for each specific prefix, or generate multiple links. The TEI stylesheets would probably do the former.
		+
		+	== Revisions to Guidelines ==
		+
		+	A proposed new section for the Guidelines is available for comment and editing here:
		+
		+	[[http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/temp-dev/prefix_definition_proposal_draft.xml?view=markup]]
		+
		+	The section would be located between the current 16.2.2 (Pointing locally) and 16.2.3 (W3C element() Scheme), and is entitled "Using abbreviated pointers".

	== Notes ==		== Notes ==

@@ Line 110: / Line 110: @@
 == Notes ==
-Council, please add any comments or suggestions here.
+'''Council, please add any comments or suggestions here.'''
 == Footnotes ==

@@ Line 111: / Line 111: @@
 Council, please add any comments or suggestions here.
 <references/>
 [[Category:Council]]