[osis-core] Experimental version (note X in name)

[Troy A. Griffitts]

Ok guys.  Our stuff, that confirms to the last osisCore.1.1.1.xsd-- 
before this email-- is up at:

http://www.bibletechnologieswg.org/osis/docs/

Very basic markup for most of this stuff, but it might have a high 
'global interest factor'.

Chris, I updated a few of your modules slightly and added them here, as 
well.

	Goodnight,
		-Troy.


Harry Plantinga wrote:
> OK, hopefully I'm back in business. I've changed milestone
> types "br" to "x-br" and "hr" to "x-hr". I've changed 
> <date type="Created" calendarType="ISO"> to 
> <date subType="Created">.  I noticed too late that it would
> have been possible to say <date type="ISO" subStype="Created">.
> 
> However, the type attribute on date is rather restrictive.
> It's not possible to specify any western date type other than ISO,
> as far as I can tell. What if my document uses 11/22/02?
> 
> Also, it doesn't seem to be possible to give a value for the date,
> e.g. <date value="2001-12-25">last Christmas</date>
> 
> Now I have to go back and edit those XSLT stylesheets to handle the
> language changes. 
> 
> I think I will have done two fulltime weeks of work in the last week
> getting these texts ready!
> 
> -Harry
> 
> On Sun, 17 Nov 2002, Patrick Durusau wrote:
> 
> 
>>Harry,
>>
>>Harry Plantinga wrote:
>>
>>
>>>Well, glad to hear it's not intentional and sorry to have vented
>>>frustration. 
>>>
>>
>>Not a problem. It has been a long year!
>>
>>
>>
>>>But all my documents have zillions of validity
>>>errors now having to do with illegal "type" attribute values.
>>>The ones I've seen so far have been 
>>>
>>><milestone type="pb"> (milestone used to have an unconstrainted type
>>>
>>
>>This should work now with the schema I just posted.
>>
>>
>>>and
>>>
>>><date type="Created"> (date used to have an unconstrainted type.
>>>
>>
>>Actually, <date had the regular type (unconstrained) and a dateType 
>>(that was constrained). If you want to add "Created" to the current type 
>>(which is constrained for date) use "x-" as a prefix and it should 
>>validate. The reason for constraining date was for automated processing 
>>of dates.
>>
>>Patrick
>>
>>
>>>There may be others.
>>>
>>>-Harry
>>>
>>>
>>>On Sun, 17 Nov 2002, Patrick Durusau wrote:
>>>
>>>
>>>>Harry,
>>>>
>>>>No! Not at all!
>>>>
>>>>What we did was allow almost all element to have globalWithType. That is 
>>>>the xs:string type that you want.
>>>>
>>>>For elements where we wanted to define the range of allowable type 
>>>>values, same ones as before, such as note, div, etc., rather than have 
>>>>noteType, divType, we simply used globalWithoutType, which allows us to 
>>>>define the type for that element alone, without stepping on the type 
>>>>declarations for other elements or elements in general.
>>>>
>>>>Completely unconstrain type altogether? Everywhere? Hmmm, we have 
>>>>discussed that from time to time but I don't know what the current 
>>>>feeling is on it. Certainly unconstraining it would not break anything.
>>>>
>>>>Comments?
>>>>
>>>>If the majority want to unconstrain type, I suggest we do so this 
>>>>evening so I can send Harry the final version with globalAttributes, and 
>>>>everything has type, but unconstrained. Less to explain to new users at 
>>>>any rate.
>>>>
>>>>Patrick
>>>>
>>>>Harry Plantinga wrote:
>>>>
>>>>
>>>>>Patrick,
>>>>>
>>>>>Are you saying that all uses of "type" are now constrained
>>>>>by a list of valid types that is shared among all tags?
>>>>>e.g. I can't say <date type="created"> for example?
>>>>>
>>>>>I object!  
>>>>>
>>>>>type is one of those attributes whose types of use can't
>>>>>be predicted in advance -- see, for example, <date type="Created">
>>>>>
>>>>>I'm going to have to go through all my documents and scripts
>>>>>and change type values to x-[whatever] in order to get them to
>>>>>validate.
>>>>>
>>>>>But I think it would be better if "type" were left unconstrained,
>>>>>especially on <date>, <milestone>, and similar tags. I can see
>>>>>why you might want to constrain it on <div>, but my preference
>>>>>woudl be to leave it unconstrained even there.
>>>>>
>>>>>-Harry
>>>>>
>>>>>On Sun, 17 Nov 2002, Patrick Durusau wrote:
>>>>>
>>>>>
>>>>>>Harry,
>>>>>>
>>>>>>Yes, this is the sort of confusion that was caused by having 
>>>>>>(essentially) two "type" attributes, one with a funny name and the other 
>>>>>>just "type."
>>>>>>
>>>>>>The constrained list (which now governs "type") for milestone has "page" 
>>>>>>and not "pb." What made it possible before was that "type" was xs:string.
>>>>>>
>>>>>>But, I think "pb" is common enough to replace "page" naking your 
>>>>>>instance valid.
>>>>>>
>>>>>>Note while we are in the changing mood, the other "type"s for milestone 
>>>>>>are column, footer, header, line, page (soon to be pb), and screen.
>>>>>>
>>>>>>I would be happy with changing milestone to have globalWithType and make 
>>>>>>those who choose to constrain the type attribute on milestone to do so.
>>>>>>
>>>>>>Patrick
>>>>>>
>>>>>>
>>>>>>Harry Plantinga wrote:
>>>>>>
>>>>>>
>>>>>>>Patrick,
>>>>>>>
>>>>>>><milestone type="pb"/> won't validate in the 1.1.1x schema --
>>>>>>>it says the type is invalid. That should be fixed.
>>>>>>>
>>>>>>>-Harry
>>>>>>>
>>>>>>>On Sun, 17 Nov 2002, Patrick Durusau wrote:
>>>>>>>
>>>>>>>
>>>>>>>>Troy,
>>>>>>>>
>>>>>>>>Sorry. I did include it in milestoneStart for cases where you want to 
>>>>>>>>replace <q> with milestones but still have the same attributes 
>>>>>>>>available. Corrected in the non-X version I will be sending out later today.
>>>>>>>>
>>>>>>>>Patrick
>>>>>>>>
>>>>>>>>Troy A. Griffitts wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>Patrick,
>>>>>>>>> I think you _forgot_ to add level to quote :)  I hope it was an 
>>>>>>>>>oversight :)  I still really think it is valuable.  An english quote 
>>>>>>>>>has an implied level.
>>>>>>>>>
>>>>>>>>> -Troy.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Patrick Durusau wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>Guys,
>>>>>>>>>>
>>>>>>>>>>I have entered the edits I proposed and marked this as an 
>>>>>>>>>>experimental version. This conforms to what I posted yesterday as the 
>>>>>>>>>>result of my conversation with Steve. Please check, noting problems 
>>>>>>>>>>with the prose as well, but I can change that without any risk of 
>>>>>>>>>>breakage.
>>>>>>>>>>
>>>>>>>>>>Note that I removed the indirect for the attribute groups (was 
>>>>>>>>>>commonAttributes and then into globalAttributes) in favor of simply 
>>>>>>>>>>having two attributes groups, one is globalWithType and the other is 
>>>>>>>>>>globalWithoutType.
>>>>>>>>>>
>>>>>>>>>>Well, I will be working on documentation (and some demos for Mike, 
>>>>>>>>>>whether they make it to the CD or not) and some other stuff today. 
>>>>>>>>>>Should be online most of the day so post early and often!
>>>>>>>>>>
>>>>>>>>>>Patrick
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>-- 
>>>>>>>>Patrick Durusau
>>>>>>>>Director of Research and Development
>>>>>>>>Society of Biblical Literature
>>>>>>>>pdurusau@emory.edu
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>-- 
>>>>>>Patrick Durusau
>>>>>>Director of Research and Development
>>>>>>Society of Biblical Literature
>>>>>>pdurusau@emory.edu
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>-- 
>>>>Patrick Durusau
>>>>Director of Research and Development
>>>>Society of Biblical Literature
>>>>pdurusau@emory.edu
>>>>
>>>>
>>>>
>>>
>>-- 
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>pdurusau@emory.edu
>>
>>
>>
>