Private URI Schemes - Revision history

Mholmes at 15:45, 11 October 2012

2012-10-11T15:45:01Z

Kshawkin: added Category:Council

2012-09-19T10:45:47Z

added Category:Council

Kshawkin: /* Remaining questions */ wiki markup fix

2012-09-19T10:00:54Z

‎Remaining questions: wiki markup fix

Mholmes: /* Remaining questions */

2012-07-16T03:23:34Z

‎Remaining questions

Mholmes: /* Elements, attributes and datatypes */

2012-07-05T15:24:58Z

‎Elements, attributes and datatypes

Mholmes: /* A Possible Solution */

2012-07-05T15:18:26Z

‎A Possible Solution

Mholmes: /* A Possible Solution */

2012-06-29T22:09:52Z

‎A Possible Solution

Mholmes: /* A Possible Solution */

2012-06-29T22:09:36Z

‎A Possible Solution

Mholmes: /* Remaining questions */

2012-06-29T15:56:56Z

‎Remaining questions

Mholmes: /* A Possible Solution */

2012-06-29T15:56:32Z

‎A Possible Solution

← Older revision		Revision as of 15:45, 11 October 2012
Line 1:		Line 1:
		+	'''NOTE: THIS PAGE HAS BEEN SUPERCEDED BY THE [http://wiki.tei-c.org/index.php/Prefix_Definition_Proposal Prefix Definition Proposal] following the TEI Council meeting in Oxford in September 2012.'''
		+
	This page contains a draft proposal for a framework whereby private URI schemes 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 used in TEI attributes with datatypes of data.pointer can be documented and dereferenced.

← Older revision		Revision as of 10:45, 19 September 2012
Line 111:		Line 111:

	<references/>		<references/>
		+
		+	[[Category:Council]]

← Older revision		Revision as of 10:00, 19 September 2012
Line 105:		Line 105:

	# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.		# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.
−
	# JC is uncomfortable with naming elements based on the actual name of a protocol (if that's what it is) such as Private URI Scheme. However, we already have attributes such as @url.		# JC is uncomfortable with naming elements based on the actual name of a protocol (if that's what it is) such as Private URI Scheme. However, we already have attributes such as @url.

← Older revision		Revision as of 03:23, 16 July 2012
Line 106:		Line 106:
	# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.		# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.

		+	# JC is uncomfortable with naming elements based on the actual name of a protocol (if that's what it is) such as Private URI Scheme. However, we already have attributes such as @url.

	== Notes ==		== Notes ==

@@ Line 92: / Line 92: @@
 == Elements, attributes and datatypes ==
-The following elements and attributes are proposed:
+The following elements, attributes and classes are proposed:
 == Remaining questions ==

@@ Line 26: / Line 26: @@
 Where the key value corresponds to a unique @xml:id within the project, and the project data is stored in an XML database, dereferencing the key to look up the <person> element to which it corresponds is simple. But if the XML data is removed from the context of the XML database and associated XQuery which enables the simple lookup, the relationship between the key and the target element becomes opaque, and any researcher working with the data will have to read the encoding description and reconstruct it.
-The proposed solution is to create a method of documenting this relationship which can be mechanically dereferenced as well as being described in human readable text. This would enable a processor to reconstruct the actual path of a link without human intervention. This can be done with a search-and-replace operation, encoded for example as the second and third arguments to XPath 2.0's replace() function. Imagine this in the &lt;encodingDesc&gt; of a document:
+The proposed solution is to create a method of documenting this relationship which can be mechanically dereferenced as well as being described in human readable text. This would enable a processor to reconstruct the actual path of a link without human intervention. This can be done with a search-and-replace operation, encoded for example as the second and third arguments to XPath 2.0's replace() function. The attributes @matchPattern and @replacementPattern are adopted from the existing TEI element <cRefPattern>. Imagine this in the &lt;encodingDesc&gt; of a document:
 <code>
    &lt;listPrivateUri>
-     <privateUri prefix="bios" pattern="([a-z]+)" replacement="../bios/bios.xml#$1">
+     <privateUri prefix="bios" matchPattern="([a-z]+)" replacementPattern="../bios/bios.xml#$1">
        &lt;p&gt;In the context of this project, private URIs with the prefix "bios" point to <person> elements in the project's bios/bios.xml file.&lt;/p&gt;
      </privateUri>
@@ Line 60: / Line 60: @@
 <code>
    &lt;listPrivateUri>
-     <privateUri prefix="moleebo" pattern="([0-9]+)|([0-9]+)" replacement="http://eebo.chadwyck.com/fetchimage?vid=$1&amp;page=$2&amp;width=1200">
+     <privateUri prefix="moleebo" matchPattern="([0-9]+)|([0-9]+)" replacementPattern="http://eebo.chadwyck.com/fetchimage?vid=$1&amp;page=$2&amp;width=1200">
        &lt;p&gt;In the context of this project, private URIs with the prefix "moleebo" point to facsimile pages on the EEBO website.&lt;/p&gt;
      </privateUri>
@@ Line 84: / Line 84: @@
 <code>
    &lt;listPrivateUri>
-     <privateUri prefix="bios" pattern="([a-z]+)" replacement="tag:bcgenesis.uvic.ca.bios.2012-06-29:$1">
+     <privateUri prefix="bios" matchPattern="([a-z]+)" replacementPattern="tag:bcgenesis.uvic.ca.bios.2012-06-29:$1">
        &lt;p&gt;In the context of this project, private URIs with the prefix "bios" represent tag URIs based on the project domain bcgenesis.uvic.ca.&lt;/p&gt;
      </privateUri>

@@ Line 26: / Line 26: @@
 Where the key value corresponds to a unique @xml:id within the project, and the project data is stored in an XML database, dereferencing the key to look up the <person> element to which it corresponds is simple. But if the XML data is removed from the context of the XML database and associated XQuery which enables the simple lookup, the relationship between the key and the target element becomes opaque, and any researcher working with the data will have to read the encoding description and reconstruct it.
-The proposed solution is to create a method of documenting this relationship which can be mechanically dereferenced as well as being described in human readable text. This would enable a processor to reconstruct the actual path of a link without human intervention. This can be done with a search-and-replace operation, encoded in a manner similar to XPath 2.0's replace() function. Imagine this in the encodingDesc of a document:
+The proposed solution is to create a method of documenting this relationship which can be mechanically dereferenced as well as being described in human readable text. This would enable a processor to reconstruct the actual path of a link without human intervention. This can be done with a search-and-replace operation, encoded for example as the second and third arguments to XPath 2.0's replace() function.. Imagine this in the &lt;encodingDesc&gt; of a document:
 <code>
@@ Line 89: / Line 89: @@
    &lt;/listPrivateUri>
 </code>
 == Elements, attributes and datatypes ==

← Older revision		Revision as of 15:56, 29 June 2012
Line 105:		Line 105:

	# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.		# Should it be possible to provide multiple dereferencing privateUri elements for the same prefix? This seems potentially useful; one might provide a relative path through the document collection, for instance, while another might provide a web URL that would retrieve the same information from a web application.
		+
		+
		+	== Notes ==
		+

	<references/>		<references/>