OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita] Attribute Generalization


Looking at the proposal, hierarchical values are already covered. In that syntax

props="proglanguage(Java) audience(CompanyA/student CompanyB/teacher))"

means

proglanguage="java" audience="CompanyA/student CompanyB/teacher"

Bruce

-----Original Message-----
From: Paul Prescod [mailto:paul.prescod@blastradius.com]
Sent: Tuesday, April 18, 2006 9:54 AM
To: Esrig, Bruce (Bruce)
Cc: dita@lists.oasis-open.org
Subject: RE: [dita] Attribute Generalization


> From: Esrig, Bruce (Bruce) [mailto:esrig@lucent.com] 
> Sent: Tuesday, April 18, 2006 6:43 AM
> Subject: RE: [dita] Attribute Generalization
> 
> Although it would make it more difficult to support DITA, I 
> have a conflicting urge, which is to allow even more 
> expressive power ...
> 
> props="proglanguage(Java) audience(CompanyA(student) 
> CompanyB(teacher))"

But what does that mean? Just the same as:

proglanguage="java" audience="student teacher"

Or 

proglanguage="java" CompanyA="student" CompanyB="teacher"

Or something else altogether?

> A compromise would be to put declarations of attributes into 
> the props attribute, and then have processors that support 
> extensibility look in those attributes for the values.

I think that according to the proposal, declarations go in the domains
attribute.

 Paul Prescod


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]