Property order not valid #12

New issue

Closed

opened 2025-04-23 14:14:17 +00:00 by mih · 5 comments

mih commented

2025-04-23 14:14:17 +00:00

Owner

but I have

...
    slot_usage:
      family_name:
        recommended: true
        annotations:
          sh:name: Family name
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 1
      given_name:
        recommended: true
        annotations:
          sh:name: Given name
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 2
      additional_names:
        annotations:
          sh:name: Additional names
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 3
      honorific_name_prefix:
        annotations:
          sh:name: Title or prefix
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 4
      honorific_name_suffix:
        annotations:
          sh:name: Suffix
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 5
      emails:
        recommended: true
        annotations:
          sh:name: Email(s)
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 6
      orcid:
        recommended: true
        annotations:
          sh:name: ORCID
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 7
      offices:
        annotations:
          sh:name: Office room(s)
          sh:group: inm7si:PersonPropertyGroup
          sh:order: 8

Either this is an incomplete annotation (what am I missing?), or it is not honored.

![image](/attachments/1aca520a-94a6-49e6-b820-b00cec241405) but I have ```yaml ... slot_usage: family_name: recommended: true annotations: sh:name: Family name sh:group: inm7si:PersonPropertyGroup sh:order: 1 given_name: recommended: true annotations: sh:name: Given name sh:group: inm7si:PersonPropertyGroup sh:order: 2 additional_names: annotations: sh:name: Additional names sh:group: inm7si:PersonPropertyGroup sh:order: 3 honorific_name_prefix: annotations: sh:name: Title or prefix sh:group: inm7si:PersonPropertyGroup sh:order: 4 honorific_name_suffix: annotations: sh:name: Suffix sh:group: inm7si:PersonPropertyGroup sh:order: 5 emails: recommended: true annotations: sh:name: Email(s) sh:group: inm7si:PersonPropertyGroup sh:order: 6 orcid: recommended: true annotations: sh:name: ORCID sh:group: inm7si:PersonPropertyGroup sh:order: 7 offices: annotations: sh:name: Office room(s) sh:group: inm7si:PersonPropertyGroup sh:order: 8 ``` Either this is an incomplete annotation (what am I missing?), or it is not honored.

image.png

46 KiB

jsheunis commented

2025-04-23 14:24:44 +00:00

Owner

It's not honored. I disabled the sh:propertyGroup functionality, which had the sh:order embedded, when I introduced the reverse inheritance grouping. I'll bring it back to life.

It's not honored. I disabled the `sh:propertyGroup` functionality, which had the `sh:order` embedded, when I introduced the reverse inheritance grouping. I'll bring it back to life.

jsheunis commented

2025-04-23 14:28:40 +00:00

Owner

Side note: SHACL has no equivalent constraint or annotation for recommended: true. This slot annotation in LinkML therefore doesn't propagate through to the SHACL export. After searching a couple of times a while ago I was also not able to find any useful term from a widely used vocabulary. In the absence of a good term, we could also create our own and add it under annotations.

Side note: SHACL has no equivalent constraint or annotation for `recommended: true`. This slot annotation in LinkML therefore doesn't propagate through to the SHACL export. After searching a couple of times a while ago I was also not able to find any useful term from a widely used vocabulary. In the absence of a good term, we could also create our own and add it under annotations.

mih commented

2025-04-23 14:49:45 +00:00

Author

Owner

I think it would be helpful to guide people's attention with something like recommended. But it is not a critical feature.