lookin' good!

With 2.0.1 in beta, the problems introduced by 2.0.0 are past us. (I say this with fingers crossed.) And I'm happy with the result, though there has been an increase in complexity. (What, with headers, tags and LEnts having 3 distinct types of name/value pairs!)

So I'm looking at the enhancements remaining in 2.0.1. And looking at tags in particular.

Can a tag value be a reference? I don't want to identify which values are references and which are not. Nor do I want to introduce scope resolution--remember that with the new s command, tags are matched across the entire Ark, not just from within a context.

So I'm suggesting something simple for tag value reference identification--if the value names a Topic anywhere in the Ark, then it is a reference. And tag value citations would be added to the cit display.

So if there is a xx-x Topic, then a tag value set to same should, when displayed, be clickable.

Where I hesitate is that this adds even more complexity, as TextContent and Header value references follow very different rules. but it seems reasonable.

For example, if I have a tag value which is a user name, anywhere in the Ark, these references should be accessible. It seems OK for tags to have different rules--they're classifiers, after all.

Now, what about path names? Well, if references are not resolved from within a context, then path names don't seem to make too much sense.

What are the alternatives?

1. don't consider tag values as references--as implemented now, or
2. use the full context resolution mechanism as we do for header values and TextContent.

Comments?