ISSUE-69: <bind> attributes can have invalid combinations

<bind> attributes can have invalid combinations

State:

CLOSED

Product:

InkML

Raised by:

Muthuselvam Selvaraj

Opened on:

2009-04-30

Description:

Issue raised by Greg on 12/20/2006 in reviewing LCWD
====================================================
source = xsd:string
Specifies source data values and/or channel to be considered in the mapping.
Required: no, Default: none

target = xsd:string Specifies target data values and/or channel to be considered in the mapping.
Required: no, Default: none
column = xsd:string
Specifies the assigned column within a lookup table either for source or target channels.
Required: for lookup table bindings, Default: none

variable = xsd:string
Specifies the variable within a formula that represents the current source data/channel.
Required: for mathml bindings, Default: none

This truly offers pretty much room for invalid combinations (see 6.1.2 <bind> element attributes).
----------------------------------------------------------------------

Comment by Muthu, 04/11/07.
We may consider the following change,

Drop the <mapping> element and create different Mapping element for each possible mapping type with <bind> child element that have only the relevant attribute list.

Example: For mapping type = lookup, We can create a <tableMapping> element as given below,
<tableMapping id=”mapping1”>
<bind target="X" column="1"/>
<table> </table>
</tableMapping>

All the Mapping element can have “href” attribute which play the role of mappingRef attribute in the <mapping>.
--------------------------------------------------------------------------------
Resolution by Stephen:
The valid combinations of <bind> element attributes are already explained in the specification. Yes, they are difficult to be enforced through XML schema, hence we advise the implementers to take care of these validations out of schema definition.
However, we accept to do the following changes,
1. Change 'column' attribute datatype to integer.
2. Specify a matrix or table in spec that shows explicitly the valid combinations of attributes

Related Actions Items:

No related actions

Related emails:

1. [ink] minutes July 30th, 2009 (from Tom.Underhill@microsoft.com on 2009-07-30)
2. [ink] agenda - 30 July 2009 (from ashimura@w3.org on 2009-07-30)
3. [ink] agenda - 23 July 2009 (from ashimura@w3.org on 2009-07-24)
4. Re: [ink] minutes - 16 July 2009 (from ashimura@w3.org on 2009-07-17)
5. [ink] minutes - 16 July 2009 (from ashimura@w3.org on 2009-07-17)
6. [ink] minutes - 11 June 2009 (from ashimura@w3.org on 2009-06-12)
7. [ink] agenda - 11 June 2009 (from ashimura@w3.org on 2009-06-11)
8. [ink] minutes - 4 June 2009 (from ashimura@w3.org on 2009-06-05)
9. [ink] update to ISSUE-69 (from muthuselvam.selvaraj@hp.com on 2009-06-04)
10. Re: [ink] Regret I won't be able to attend tomorrows meeting (May-14-09) (from ashimura@w3.org on 2009-05-14)
11. [ink] ISSUE-69 update (was Re: [ink] Regret I won't be able to attend tomorrows meeting (May-14-09)) (from ashimura@w3.org on 2009-05-14)
12. [ink] status of Kaz's action items (was Re: [ink] minutes - 30 April 2009) (from ashimura@w3.org on 2009-05-03)
13. [ink] minutes - 30 April 2009 (from ashimura@w3.org on 2009-05-01)
14. ISSUE-69 (Muthu): <bind> attributes can have invalid combinations [InkML] (from sysbot+tracker@w3.org on 2009-04-30)

Related notes:

Display change log