[data-shapes] Should we introduce a property ID property for use cases like GraphQL and APIs? (#559)

HolgerKnublauch has just created a new issue for https://github.com/w3c/data-shapes:

== Should we introduce a property ID property for use cases like GraphQL and APIs? ==
A common use case of shapes is to generate APIs such as GraphQL endpoints or JS or Java classes. The question is how to map from property shapes to valid fields in those languages. Java-style identifiers are a commonly accepted lowest common denominator.

In TopBraid we had to introduce a custom property graphql:name to allow users to specify a Java-style ID for a property shape. This is needed in particular when a property shape uses a path expression. Usually the local name of a property can be used, but it's difficult to construct such names from paths.

Something like sh:propertyID

```
ex:MyShape-myProp
   a sh:PropertyShape ;
   sh:path ( ex:parent ex:income ) ;
   sh:propertyID "parentIncome" ;
   ...
```


```
ex:MyShape-child
   a sh:PropertyShape ;
   sh:name "children" ;
   sh:path [ sh:inversePath ex:parent ] ;
   sh:propertyID "child" ;
   ...
```

Discussed in https://www.linkedin.com/feed/update/urn:li:activity:7367747396455309313?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7367747396455309313%2C7367845601729855488%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287367845601729855488%2Curn%3Ali%3Aactivity%3A7367747396455309313%29

Please view or discuss this issue at https://github.com/w3c/data-shapes/issues/559 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 2 September 2025 12:05:00 UTC