[humanmarkup] Base Schema-channel

[Rex Brooks <rexb@starbourne.com>]

Hi Everyone.

I didn't want to let a week go by when I didn't have a second or 
third telecon to attend without presenting the start of a new element 
discussion. I realize it is the Memorial Day Weekend Holiday in the 
US, and web traffic and participation is always much slower over a 
weekend regardless of holidays, so I don't expect a lot of responses 
or replies over the weekend, but I thought I would put it out there 
in any event.

Also, please be advised that initiating new element discussions is 
mostly unrelated to on-going discussions of previously introduced 
elements. Starting a new thread does not in any way mean that I think 
any previous discussions are concluded. So don't be surprised when I 
return to bodyLocation next week, which I plan to do at this point, 
since I, at least, am far from finished with it.

So, onward...

channel

This is a Complex Type with the attribute of abstract, which to 
reiterate, as I will continue doing, means an element that cannot be 
used directly but must be used as a complexType derived from this 
complexType. I will keep reiterating this because it is important, 
which in this case involves a suggestion I want to make to broaden 
the definition in this case, which means it will include a larger 
range of derived complexTypes.

It is described as Human Communication Channel as senses or faculties 
byt which a Human communicates a message.

It is further specified that this element is a member of the 
xsd:attributeGroup referenced by "humlIdentifierAtts strength" This 
is a good place to note a difference between and amongst the last two 
elements. The element, bodyLocation, was neither abstract, nor did it 
take any attributes, and therefore no value for the attribute nor an 
attributeGroup association. That was a large part of the reason why I 
suggested a series of related elements. I will return to that next 
week.

My suggestion is that channel be somewhat more explicitly defined so 
that communication is understood such that a channel represents the 
ability to receive as well as to send a message. While the dictionary 
does include notions of sharing information, the definitions are 
preponderantly on the side of transmitting more than receiving, and I 
think that needs to be explicitly made clear.

I actually have much more to say, but this ought to be sufficient to 
get the discussion started.

Last note for now: this is one of those seriously overloaded terms 
which I suspect we will have to append our namespace prefix to: 
huml:channel or else-- humanChannel.

Ciao,
Rex


--