Re: [ACTION-19] Elaborate support annotation of grouping of CMS documents or CCMS components

It seems that Dave’s response brings up two issues, one indirectly: The first is obviously the question he asks, but the second could be more broadly generalized about overrides and inheritance when two rules seem to conflict. While it would seem obvious to me that a local rule or override takes precedence, that needs to be explicitly stated. Indeed we've seen some cases with the translate attribute in Richard’s testing where there are some issues, like being unable to override an assumption of translate="no" in <code> elements. While this doesn't go into a category, we should have some rules/processing expectations explicitly stated about this in the final document. I suppose this should be put in the tracker as an issue for later on, just to make sure we are explicit about it.

-Arle

Sic scripsit Dr. David Filip in Mar 29, 2012 ad 15:25 :

> Hi all, re-posting Dave's reply to this action item as he is having e-mail authorization issues:
> 
> -----------------
> Hi all,
> I think a CSS-like approach makes sense in most cases. However, I don't 
> think it addresses the use case when some rules are in an external 
> script, but we want to change the rules for some documents currently 
> bound to that script but not for others. Is it a requirement to be able 
> to assign such meta-data to a document or component without actually 
> changing the document, i.e. without editing the external rule script 
> reference. In CMS, such external meta-data associations can be edited 
> external to the document, i.e. using CMS database tables.
> 
> So a question to CMS integrators and user organizations -it this 
> external binding to external meta-data, in this case rule scripts, an 
> important requirement for document management?
> 
> Regards,
> Dave
> ----------------------------
> 
> Dr. David Filip
> =======================
> LRC | CNGL | LT-Web | CSIS
> University of Limerick, Ireland
> telephone: +353-6120-2781
> cellphone: +353-86-0222-158
> facsimile: +353-6120-2734
> mailto: david.filip@ul.ie
> 
> 
> 
> On Wed, Mar 21, 2012 at 18:51, Felix Sasaki <fsasaki@w3.org> wrote:
> Dear all,
> 
> I had an action item to "elaborate support annotation of grouping of CMS documents or CCMS components". This may become an issue to discuss in detail later, but here is my first take.
> 
> I would propose to define for all kinds of content, no matter whether an HTML snippet, a single CMS content item, a group of components etc., using the following mechanisms:
> 
> 1) adding information to a span of text "locally"
> 2) adding information via a global, position independent mechanism.
> 3) describing defaults for a data category, no matter whether metadata is set explicit or not. Example for "Translate" in XML: defaults for attributes is that they are not translatable
>  
> Above is based on ITS 1.0 http://www.w3.org/TR/2007/REC-its-20070403/#selection-precedence
> and a CSS like approach: 1) is like the "style" attribute in HTML, 2) like the "style" element or links to external stylesheets, 3) like default styling rules.
>  
> Our challenge is then to adapt 1-3 to CMS documents and components. I would see 2) as the main means for this.
> 
> Comments are very welcome,
> 
> Felix
> 
> -- 
> Felix Sasaki
> DFKI / W3C Fellow
> 
>