Karen Tung wrote:
> Jack Schwartz wrote:
>>
>> General:
>>
>> In general, the parser places the requirement on the derived profiles
>> project that the format of the tags be in an easily searchable
>> format, for example that they contain a common prefix which can be
>> searched for.
>>
>>
> I don't see why the parser would place requirement on the derived
> profile project on the format
> of the tags or whatever. Since the new parser design doesn't
> automatically do syntactic validation,
> it will be up to the derived manifest client program or AI setup that
> accepts derived manifest
> to perform the derivation whenever it is appropriate,
> and call the parser's function to do syntactic validation whenever it
> feels it is appropriate.
> From the parser's point of view, I don't think it should even need to
> know about whether it is
> a derived manifest or the regular manifest.
It is true that the parser shouldn't care about the data it handles.
This requirement is more of a restriction on the derived profiles
project to structure its data so that the parser can be used to search
it easily.
Thanks,
Jack
>
> Also, whether to have a tag with a common prefix or 2 tags or whatever
> is the implementation detail
> of the derived profile project, I believe. Why would the parser care
> about that?
>
> --Karen
