Read-Only Properties in the EDG UI

[Branson, GaBriella C]

Hi,

Is it possible to make a property read-only, but only after data has been added? I know in the ontology I can make a property read-only for always, but I want to allow a user to add data to a field once and then lock the field down. Is that possible?

Thanks!

 

GaBriella Branson

Interagency Wildland Fire Data Management - Knowledge Manager

U.S. Department of the Interior, Office of Wildland Fire 

Office Phone: (907)483-0330 | gbra...@ios.doi.gov

Follow us online: Website | Facebook | Flickr | X

Stay connected! Sign up to receive email updates

   

 

[David Price]

Hi GaBriella,

I cannot think of nothing out-of-the-box that fully supports this request. Closest thing I can think of is a “power" user could move the instance with the property to a collection that is read-only for “normal” users once the value is first written in the editable collection.

I’d also ask why … what if the user made a mistake? Who can fix it?

The closest similar customer requirement I’ve heard is, for example, not being able to edit a refernce data code that has status=Active in order to stop accidental changes/deletes.  To support that we wrote a ChangeScript that just puts the old values back into place when  status=Active (and both changes appear in the Change History!). That forces data stewards to change the code so status=In Development and then they can edit property values.

Hope that clarifies things.

Cheers,

David

On 24 Nov 2025, at 17:02, 'Branson, GaBriella C' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Hi,

Is it possible to make a property read-only, but only after data has been added? I know in the ontology I can make a property read-only for always, but I want to allow a user to add data to a field once and then lock the field down. Is that possible?

Thanks!

 

GaBriella Branson

Interagency Wildland Fire Data Management - Knowledge Manager

U.S. Department of the Interior, Office of Wildland Fire 

Office Phone: (907)483-0330 | gbra...@ios.doi.gov

Follow us online: Website | Facebook | Flickr | X

Stay connected! Sign up to receive email updates

<Outlook-Logo for t.png>   

 

-- 
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to topbrai...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/topbraid-users/BN3PR09MB119815A84AA8677801A8641C3DAD0A%40BN3PR09MB11981.namprd09.prod.outlook.com.

David Price, Semantic Solution Architect

UK +44 (0) 7788 561308

TopQuadrant.com

[Branson, GaBriella C]

Hi David,

Thank you for the reply. I had considered the option to move an instance to a read-only collection, but wanted to see if there was a more elegant solution.

For more details: We have a class Channel that is part of a reference dataset. Our Frequency Managers are responsible for ensuring the channels associated with their Dispatch Center are current and accurate. Via an API we are sharing this information with other systems in the enterprise to use. It is imperative that once a channel is created and approved that none of the fields change. If at some point the channel is no longer applicable, it will be made inactive but remain in the dataset to track historical usage. It is necessary to know exactly what the values were when the channel was used in another dataset. Frequency Managers will yearly review their channels and identify any that need to become inactive and add any new ones. We are currently undergoing an effort to get all the correct data in EDG before we start using it as a reference dataset. We are finding corrections and so at this time I would not make anything read-only, but once we have it in the most correct state possible, we want to lock down any edits and only allow additions or inactivations.

Following is an example of a channel (minus the status fields), that we are using.

wfradfreqgraph:d9a50213-ff7d-47c2-ba18-3d4f95a82ec2

  a wfschema:Channel ;

  rdfs:label "IDCDOC 134.5500" ;

  wfschema:bandwidth wfenum:Narrowband ;

  wfschema:channelDispatchCenter wforg:e5b0bd55-81af-4936-8ee3-a4f2c883b245 ;

  wfschema:channelManagingAgency wforg:d3903883-1389-442b-b4cb-803d87b49fe1 ;

  wfschema:channelName "134.5500" ;

  wfschema:channelUseDesignator wfenum:AirToAirAM ;

  wfschema:mode wfenum:analog ;

  wfschema:receiveFrequency wfradfreqgraph:f0dfb70b-0bcf-43d1-b184-ecc890ed32b9 ;

  wfschema:subaudibleCodeType wfenum:ContinuousToneCodedSquelchSystem ;

  wfschema:transmitFrequency wfradfreqgraph:f0dfb70b-0bcf-43d1-b184-ecc890ed32b9 ;

.

Thanks for taking the time to reply. I do appreciate your insight.

GaBriella Branson

Interagency Wildland Fire Data Management - Knowledge Manager

U.S. Department of the Interior, Office of Wildland Fire 

Office Phone: (907)483-0330 | gbra...@ios.doi.gov

Follow us online: Website | Facebook | Flickr | X

Stay connected! Sign up to receive email updates

   

 

---

From: topbrai...@googlegroups.com <topbrai...@googlegroups.com> on behalf of David Price <dpr...@topquadrant.com>
Sent: Monday, November 24, 2025 9:46 AM
To: 'Felix Sasaki' via TopBraid Suite Users <topbrai...@googlegroups.com>
Subject: [EXTERNAL] Re: [topbraid-users] Read-Only Properties in the EDG UI

 

 

This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.

To view this discussion visit https://groups.google.com/d/msgid/topbraid-users/59F1374D-8895-4CAA-B60F-DC6D21300C86%40topquadrant.com.

[David Price]

Hi GaBriella,

Given that use case, I think the script approach I mentioned where you would set a status = read-only when ready to lock could get you pretty close. People would have to go way out of their way to make changes. You could also run a query/report over the Change History of the collection to find cases of that status=read-only being changed to double-check.

Of course, the move-locked-instances to a read-only collection is the safest approach. Could script or SPARQL that too, of course.

Cheers,

David

UK +44 (0) 7788 561308

<Outlook-Logo for t.png>   

 

To view this discussion visit https://groups.google.com/d/msgid/topbraid-users/BN3PR09MB119813C5ECA31E1B79119061CDAD0A%40BN3PR09MB11981.namprd09.prod.outlook.com.