If software identifiers are encoded as <iws:segment-metadata sid="IDS_123"><iws:segment-metadata> then Ocelot does not read and display them.
This is categorized as a feature request because the iws namespace is not core XLIFF but rather an approved extension mechanism.
A proposal here would be to read these iws:segment-metadata[sid] attribute values and display them in a new main grid column. Would this be acceptable?
Note: this would only be implemented for XLIFF 1.2 files.
Right, this is WorldServer specific. (This is the older "IdiomXLIFF" variant, not the SDLXLIFF produced when FTS filters are in use.)
I think the iws:segment-metadata/@sid attribute should probably be considered another way of providing the trans-unit/@resname attribute, since they perform the same function. Also, this should arguably be fixed in Okapi's XLIFF filter, not in Ocelot (where we'd have to scrape it with regular expressions or something).
shows a couple of segments with SIDs coming from WorldServer's Java Properties filter. (Search for "key1" and "key2".)
The segment-metadata also contains an iws:status element that gives match status ("fuzzy"), which is relevant for OC-93.