add revisionId to project

[buildingsmart]

add revisionId to project

[linhard]

The 'project.xsd' is to connect 'extension.xsd' to a BIM-hub.
The place where i would expect a revisionId is in Markup.xsd
Header / File / revisionId
at the moment we have Header / File / Reference (string) to identify IfcFiles belonging to a topic.
Thinking more in Web-Service enviroment than sending bcfzips over email, then the "Reference" is an url which has to be unique.
Within an bcfzip the "Reference" is also unique.
But maybe an revisionId would speed up things ?

[berlotti]

Great!
In that case I have a more detailleed comment.... Most of the time an issue list is based on multiple models. In that case a Reference (or RevisionID, or whatever) should be referenced to multiple sources.
How would you advice to implement such situaties?
Thank you for your answer!

[linhard]

In Markup.xsd .../File/... is a 1:n relation to a topic. (1-Topic - n-Files).

example: response from RESTful service which gets the header of a topic:

GET /apex/ifc/BCF/2.0/topicHeader/{token}/{uuid_topic}

200 (OK)
Content-Type: application/json

{
"next":
{
"$ref": "https://iabi.biz/apex/ifc/BCF/2.0/topicHeader/E709152C7F409DB0A5B3B0C3767F6BE6/ac4d181b-71af-4e1d-8c58-f79f0e7d1206?page=1"
},
"items":
[
{
"ifcproject": "0J$yPqHBD12v72y4qF6XcD",
"isexternal": "true",
"filename": "(1) Architecture_V1.0.ifc",
"date": "2012-01-11T17:26:31+01:00 ",
"reference": "https://iabi.biz:8181/apex/ifc/bimit/getIfcFile/{token}/7285113372583126"
},
{
"ifcproject": "0J$yPqHBD12v72y4qF6XcD",
"isexternal": "true",
"filename": "(2) Heating_V2.0.ifc",
"date": "2012-01-11T17:26:31+01:00 ",
"reference": "https://iabi.biz:8181/apex/ifc/bimit/getIfcFile/{token}/7285404115637259"
},
{
"ifcproject": "0J$yPqHBD12v72y4qF6XcD",
"isexternal": "true",
"filename": "Architecture_V3_0.ifc",
"date": "2012-12-13T14:20:51+01:00",
"reference": "https://iabi.biz:8181/apex/ifc/bimit/getIfcFile/{token}/158666726526927354"
}
]
}

[berlotti]

Ah, your RESTful reply is in JSON... I'm now extra interested in the specification on that (see other issue).

Thanks for the reply!