[osis-core] Change to <work> type and subType

[Patrick Durusau]

Guys,

Just a note to confirm that I agree with Todd that we may be introducing 
more opportunity for error than any possible gain from the original 
proposal that Steve and I put in the schema. That to me seems to be the 
telling argument.

Those who design material to be copied by encoders would probably get it 
right but your average encoder would not. (Not that Todd is the average 
encoder!)

Comments?

Hope everyone is having a great day!

Patrick

Todd Tillinghast wrote:

>Patrick and I talked earlier today about the type and subType attributes
>of <work>.
>
>PROPOSAL: Remove "content" or "declaration" and put the list currently
>on subType on type.  
>
>The reasoning being that you know "content" or "declaration" based on
>the other value.  The reasoning Patrick and Steve had when including the
>"content"/"declaration" attribute was that people would not know which
>the other value was.  The same reasoning would apply to those encoding.
>The difference is that the encoder would introduce error.  
>
>Until I read Patrick's post earlier today I had used "content" and
>"declaration" differently that it was intended.  By removing
>"content"/"declaration", we reduce confusion and eliminate the potential
>for error.
>
>Todd
>
>_______________________________________________
>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!