IDS schema location - Githubissues

buildingSMART / IDS

Computer interpretable (XML) standard to define Information Delivery Specifications for BIM (mainly used for IFC)

Other

167 stars 52 forks source link

IDS schema location #250

Closed mschro3der closed 3 weeks ago

mschro3der commented 2 months ago

What

The schema location: 0.9.6 known to me provides the schema via an html body tag (meta data: <meta http-equiv="content-type" content="text/html; charset=windows-1252">).
I would have expected that the schema is provided like: inspire. Here the schema file is directly available - which in my view is necessary for the usual tools to validate an xml file.

Solution

provide the plain schema file (and no html document of type text/html)

Workaround

link the current XSD from the github directory: raw xsd

CBenghi commented 2 months ago

Hey @berlotti,

this has to do with the configuration of buildingSMART's webserver.

The suggested workaround could do, but would you be happy if we kept the official xsd files on github? This would also allow us to work on beta versions of 1.1 more independently, retaining schema in various editors.

IDS files would change from:

xsi:schemaLocation="http://standards.buildingsmart.org/IDS http://standards.buildingsmart.org/IDS/0.9.7/ids.xsd"

xsi:schemaLocation="http://standards.buildingsmart.org/IDS https://raw.githubusercontent.com/buildingSMART/IDS/master/Schema/1.0/ids.xsd"

NickNisbet commented 2 months ago

GitHub is not the place to hold official releases of buildingsmart standards. Stuff on GitHub can be lost amongst official working, rival, deprecated versions.

MatthiasWeise commented 2 months ago

Same issue with the new 0.9.7: https://standards.buildingsmart.org/IDS/0.9.7/ids.xsd Any plans to fix?

CBenghi commented 2 months ago

For context and completeness:

According to documentation, the ideal content-type returned by the server for the xsd files, should be application/xml.

In my tests, the server currently returns an empty content type. @mschro3der, is it possible that the <body> tag you see is added by your browser? I don't see it when I fetch the schema with curl or another similar tool.

andyward commented 2 months ago

Looks like it's an Apache server from the headers. Presumably whoever published the xsd content can finds someone to update the apache.config? I'd guess it just needs this adding to the httpd.config:

AddType application/xml .xsd

See https://httpd.apache.org/docs/2.4/mod/mod_mime.html#addtype

atomczak commented 3 weeks ago

The 'Content-Type' header has just been added, with the type: 'text/xml' (not 'application/xml' to include textual implementers agreements). Please test if it works now.

mschro3der commented 3 weeks ago

@atomczak Now also works via the web interface. Great!

Issue can therefore be closed.