XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Make implicit structures explicit

> 
> 	Make implicit structures explicit.
> 

Could you define what you mean by "implicit" and "explicit"?

I think your two representations have the same information content.

I think (and it seems most respondents think) that representing a sequence of maintenance tasks as a sequence of task elements is more explicit than representing it as an unordered set of (number, task) pairs. Several reasons:

(a) extracting the ordered sequence of tasks from a set of (number, task) pairs requires more processing (mental or computer processing)

(b) the set of (number, task) pairs is an inaccurate model because it can represent things that are not valid, e.g. two tasks with the same number.

(c) it's not in any sense "explicit" that the numbers in the second representation are intended to be interpreted as sequence numbers; they could for example represent the expected duration of the task.

Michael Kay
Saxonica



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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS