>Steven R. Newcomb wrote:
>>
>> Property sets describe classes of nodes, and the properties of each
>> class of node, as such nodes are output by a parser for a given
>> notation. A property set does not describe any methods, so it can
>> form an excellent all-purpose foundation for methods and applications.
>> Since every property of every syntactic construct is assigned a name
>> in a property set, the names of properties readily form a natural
>> basis for query languages, too.
>>
>> Having a property set for XML would set the stage for XML to become
>> the language of documents that integrate information expressed in all
>> other notations, because they can pretty much all have property sets,
>> too.
>
>Yes. This comes up on the VRML list from time to time as its designers
>puzzle over the best way to work with XML and DOM. If the property
>set approach were taken, IMHO, many of the issues of mapping among
>language standards would be settled and work could go forward in a
>sensible
>and rigorous way. The days of debating pointy brackets and curly
>brackets should be over. Nodes are nodes. Must be. Unfortunately,
>because XML is a syntax specification, that isn't workable except
>by ugly tricks with object tags and VRML protos.
Some simple examples here might add a great deal to this discussion.
I suspect that (a) this is vital, (b) I am not the only one unfamiliar with
property sets, and (c) it is probably worth the bandwith to bring folks
up to speed on this topic rather than simply cite some references.
Thanks!
Bill