[osis-core] Inconsistent use of type on date

[Patrick Durusau]

Todd,

The problem was that in the documentation Steve was using at ABS, he 
used the type attribute on <date> to specify for <work> information such 
as 1st edition, eversion, etc. The sort of stuff you expect to see with 
Dublin Core metadata.

Some bright soul noticed the type in <date> is defined to be the sort of 
calendar that is in use in the <date> element. (ISO, gregorian, chinese, 
etc.)

The problem is that people want to be able to say what the <date> 
element represents and we have no place for that at the moment.

Steve's suggestion is that we use "event" as an attribute.

Hope you are having a great day!

Patrick

Todd Tillinghast wrote:
> Patrick and Steve,
> 
> I went back through the history and am trying to make sense of this
> issue.
> 
> Can you give an example of the problem?
> 
> Todd
> 
> 
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org 
>>[mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of 
>>Steven J. DeRose
>>Sent: Tuesday, September 16, 2003 7:18 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] Inconsistent use of type on date
>>
>>
>>At 12:49 PM -0400 9/16/03, Patrick Durusau wrote:
>>
>>>Steve,
>>>
>>>OK, thus dateCT would have the following attributes:
>>>
>>><xs:attribute name="type" type="calendar" use="optional" 
>>>default="ISO"/> <xs:attribute name="event" type="xs:string" 
>>>use="optinal"/> (added) <xs:attributeGroup ref="globalWithoutType"/> 
>>><xs:attribute name="canonical" type="xs:boolean" use="optional"/> 
>>><xs:attribute name="TEIform" fixed="date"/>
>>>
>>>And the docs suggests values for "event" or explain its usage?
>>
>>I was thinking we should define the basic types -- they're already in 
>>the doc as
>>
>><list type='definition'>
>>	<label>  original</label>
>>
>>		<item>The original publication date of the 
>>first edition</item>
>>
>>	<label>  edition</label>
>>
>>		<item>  The date of publication of the referenced or 
>>source edition</item>
>>
>>	<label>  imprint</label>
>>
>>		<item>  The printing date of the referenced or source 
>>edition</item>
>>
>>	<label>  eversion</label>
>>
>>		<item>  The revision date of the present electronic 
>>edition</item>
>></list>
>>
>>
>>-- 
>>
>>Steve DeRose -- http://www.derose.net
>>Chair, Bible Technologies Group -- http://www.bibletechnologies.net
>>Email: sderose@acm.org  or  steve@derose.net 
>>_______________________________________________
>>osis-core mailing list
>>osis-core@bibletechnologieswg.org 
>>http://www.bibletechnologieswg.org/mailman/lis> tinfo/osis-core
>>
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 


-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!