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] adding multiple attributes using scheme and content


I guess there are four separate goals in the excerpted message:
 - to define syntax that allows the introduction of multiple names
 - to define syntax that allows specification of relationships among names so that structured values can be represented using multiple names
 - to use a scheme attribute to separate values from names and then bind the values by pattern matching
 - to use a scheme attribute to allow specification of the content of the value that binds to a name

Looking at these goals, it starts to seem that this direction is not talking about allowing new attributes to be added. Instead, it talks about adding a new class of identifiers outside of XML mechanisms that are introduced by placing special values in standard attributes.

Best wishes,

Bruce Esrig

-----Original Message-----
From: Paul Grosso [mailto:pgrosso@arbortext.com]
Sent: Monday, August 22, 2005 12:45 PM
To: dita@lists.oasis-open.org
Subject: RE: [dita] adding multiple attributes using scheme and content


fwiw, you cannot have a > character within an attribute
value in XML. 

paul

> -----Original Message-----
> From: Esrig, Bruce (Bruce) [mailto:esrig@lucent.com] 
> Sent: Thursday, 2005 August 18 6:48
> To: dita@lists.oasis-open.org
> Subject: RE: [dita] adding multiple attributes using scheme 
> and content
> 
> The "otherprops" approach is to allow a syntax in otherprops 
> for nesting attribute names and values in the value of the 
> otherprops attribute.
> 
> From Paul Prescod, 2 August 2005:
> 
> <p otherattrs="last-changed-date(2005-08-02T12:28:57((-07:00)))"
> generalizedprops="otherattrs"/>
> 
> Here is an alternate proposal for the underpinnings of a DITA 
> enhancement that would allow the encoding of multiple 
> metadata attributes using a scheme attribute in parallel with 
> a content attribute.
> 
> The examples show how two existing DITA elements could be 
> represented in the HTML Meta tag using this approach.
> 
> 1. Define a delimiter syntax such as ":>".
> 2. Add a scheme attribute.
> 3. Map to the three-place attribute set name, scheme, value 
> in the following way (specification by example ...).
> 
> The DITA audience element
> <audience type="programmer" job="programming" 
> experiencelevel="expert"/>
> might be represented as
> 
> <meta name="audience" 
> scheme="name:>type:>job:>experencelevel" 
> content="audience:>programmer:>programming:>expert">


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