Proposal to delete (or heavily cull) concept Project Library Information

So in case you haven't seen Project Library Information I took a screenshot of it below.

In short, it's 5 sentences and 3 tables that have the ambition to describe a full RESTlike API specification for a model server. Crazy right?

It's a bit last minute but I think it's important - I do not think this is in scope for the IFC schema. Maybe as a "model" module for OpenCDE - but not in the schema.

Using IFC library references is a valid way to link an IFC thing to an external system, so yes in the future when such an IFC model server is more standardised, you may use a library association in this manner. However, I do not think it is the responsibility of the IFC schema itself to specify HTTP headers, HTTP verbs, mime types, and so on. It even makes a proposition to link the IfcPerson to the username of the sever (auth system? what? where? how?). It sounds like an "example of what might happen" with enough content to be thought provoking but not enough content to be useful.

There are too many questions that I'd propose:

1. Delete it all. If it actually is a thing in the future, it can return with proper, fully thought-out documentation.
2. At least just cut it down to a few vague sentences about "association with a model server" and delete the portion of the graph to do with the publisher and IfcPerson.

Edit: originally brought up from buildingSMART/IFC4.3.x-development#403.


Start by reviewing the Project Library Information concept and the originating buildingSMART/IFC4.3.x-development#403 issue. The thread presents deletion or substantial culling as alternatives, so check the discussion for a settled direction. Done means the agreed scope is applied to the concept and its associated tables or graph content.

Written by the indexing model from the issue text.