[tei-council] Private URI Schemes

[Martin Holmes]

On 12-06-27 12:46 PM, Stuart A. Yeates wrote:
> I think the <listPrivateUri/> tag is unnecessary, can't we reuse one
> of the existing TEI header tags for this purpose? <encodingDesc/>?
> Unless of course there are some specific semantics you're trying to
> model.

I was assuming that many projects would use more than one private URI 
scheme -- mine do -- and so there would need to be a list or group 
element to keep them together. I assume they would be in <encodingDesc>.

> You also use the word 'project' in the examples, surely that should be
> 'document' or 'corpus'?

I think of a project as a corpus together with a lot of peripheral 
material (web application, documentation, etc.). If this were coded into 
elementSpecs, though, you're right that "corpus" would make more sense.

Cheers,
Martin

> Other than that it looks really good.
>
> cheers
> stuart
>
> On Thu, Jun 28, 2012 at 5:22 AM, Martin Holmes <mholmes at uvic.ca> wrote:
>> Hi all,
>>
>> We've had a couple of discussions about the magic token vs. private URI
>> scheme issue over the past couple of meetings, and now I've put together
>> a brief description of the way I had imagined putting the use of private
>> URI schemes on a more solid footing than magic tokens:
>>
>> <http://wiki.tei-c.org/index.php/Private_URI_Schemes>
>>
>> Could you take a look and let me know what you think?
>>
>> Cheers,
>> Martin
>> --
>> 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