The original W3C Submission specified no particular media-type for HDT ( https://www.w3.org/Submission/HDT/#media ) , making is difficult to identify when one is desiring to specify that something is in HDT format. Has the decision to refer to "The media type of HDT is the media type of their parts." been revisited since the submission and a media-type been defined specifically for HDT?
The specification of a media-type for the HDT container should not prevent the use of multiple different RDF formats internally for the various components.
My usecase is wanting to add a constant to RDF4J ( https://github.com/eclipse/rdf4j/issues/232 ) for HDT to prepare for @barthanssens addition of a parser there, but not wanting to do so without a media-type at this stage. RDF4J currently assumes that the relationship between RDFFormat media-type is "1 or more". I.e., the code has not been written to handle the case of having 0 media-types so far.
hoijui
commented
4 months ago
The original W3C Submission specified no particular media-type for HDT ( https://www.w3.org/Submission/HDT/#media ) , making is difficult to identify when one is desiring to specify that something is in HDT format. Has the decision to refer to "The media type of HDT is the media type of their parts." been revisited since the submission and a media-type been defined specifically for HDT?
The specification of a media-type for the HDT container should not prevent the use of multiple different RDF formats internally for the various components.
My usecase is wanting to add a constant to RDF4J ( https://github.com/eclipse/rdf4j/issues/232 ) for HDT to prepare for @barthanssens addition of a parser there, but not wanting to do so without a media-type at this stage. RDF4J currently assumes that the relationship between RDFFormat media-type is "1 or more". I.e., the code has not been written to handle the case of having 0 media-types so far.