Imported from previous forum
In the FAST 1.2 spec, it states:
So:
translates to:
I’d like to know what translates to. Is it
-
or -
or - either one is acceptable.
Thanks,
Craig
It should be case 1. The auxiliary identifier is a property of the field rather than a property of the type of the field.
/David
In the FAST 1.2 spec, it states: So:
translates to:
I’d like to know what
translates to. Is it
- or
- or
- either one is acceptable.
Thanks, Craig
If you’re using SHOULD (as opposed to saying MUST), then the answer is 3, right?
- Craig
It should be case 1. The auxiliary identifier is a property of the field
rather than a property of the type of the field./David
In the FAST 1.2 spec, it states: So:
translates to:
I’d like to know what
translates to. Is it
or
or- either one is acceptable.
Thanks, Craig
SHOULD as in the 1.2 specification is not written yet and this particular tidbit is not covered by the 1.2 extension proposal. But your case 1 is what the proposal should have said, had it been more specific on this matter.
/David
If you’re using SHOULD (as opposed to saying MUST), then the answer
is 3, right?
- Craig
It should be case 1. The auxiliary identifier is a property of the
field rather than a property of the type of the field./David
In the FAST 1.2 spec, it states: So:
translates to:
I’d like to know what
translates to. Is it
or
or- either one is acceptable.
Thanks, Craig