RE: Seperate content from presentation (was storing info in XSL -FO: new issue?)

> -----Original Message-----
> From: Bullard, Claude L (Len)
> Separation of content from presentation or rendering 
> is not a very strong guideline either.   The problem 
> is that you are singling out one semantic and holding 
> it separate (essentially, the late bound one) while 
> encouraging other semantics to be tightly bound without 
> having a way to indicate the semantic itself without 
> resorting to other means (documented namespace URIs, 
> comments, the usual list).  I generally agree with 
> the use of content-centric schemas given a community 
> of understanding, but unless there is also something
> at the end of the namespace URI, it isn't very easy 
> to know when someone is on or off the bus.
> 
> There isn't a one sized fits all rule here.  There 
> is just a practice that says name it for the maximum 
> amount of unambiguous reuse (the greatest number of 
> communities of understanding) and bind late whereever 
> efficient to the local semantic of any given community.

Do you believe that this seperate content from presentation
position to be invalid, or just wrongly worded?
I don't recall it being challenged as a principle in the ac meeting.
I'd be interested in any variant on this you could offer please.

'Name it for maximum amount of unambiguous use' sounds
kinda like semantic markup to me.

I like the 'bind late for a given community use' though.
My plain English would be 'style for local application',
presuming a human end user.




- 

NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 
system.

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk

Received on Tuesday, 20 August 2002 04:56:21 UTC