Paul Connelly

> How can I help to move this project forward? Detail the specific non-technical requirements. Ideally specify what's needed for MVP so we can prioritize. There are some questions in...

Thanks. We do need to think a little beyond MVP when deciding how to implement this. Should we assume fields should behave like they do in MicroStation unless otherwise specified?...

> Has there been any progress on this? If not, is there a plan to begin work on this? If not, how do I escalate this? @aruniverse @calebmshafer

@hl662 here is [some context](https://docs.bentley.com/LiveContent/web/MicroStation%20Help-v21/en/TextFieldsEditor.html) on MicroStation's formatting options for fields.

That is correct, the formatting is a property of the field.

Here are my preliminary thoughts on how to put this together. BisCore ECSchema changes: - Add ITextAnnotation, a mixin class that identifies an element that can host text annotations (e.g.,...

> @pmconne can you point to the current WIP format for your property paths? There isn't one. I need to be able to encode things like: - `topLevelProperty` - `struct.property`...

We should avoid storing element Ids in the JSON representation of the fields if feasible, because element Ids may change during transformations and the transformer may not know how to...

> I assume that we should avoid storing element IDs in the JSON representation for text styles as well? I don't think a relationship per text style used in annotation...

[MstnPropertyFormatter.01.00.ecschema.xml.txt](https://github.com/user-attachments/files/21350509/MstnPropertyFormatter.01.00.ecschema.xml.txt) is the schema MicroStation uses for specifying field formatting options. The appropriate formatter is selected based on the property's primitive+extended types and custom attributes like `StandardValues` which define enums...