Joe, yes you are correct that the range of dc:format should be MediaTypeOrExtent. We have a bug ticket to update version of Dublin Core we include in TopBraid. In the meantime you can import the file yourself with Import from URL... and use the URL to the standard you want to use (the current version in Composer uses both http://purl.org/dc/elements/1.1/ and http://purl.org/dc/terms/).
Not sure that helps get a URI for MIME types, but using the model you reference, you can define an instance of MediaTypeOrExtent and use the rdfs:label or some other annotation or datatype property to define the actual MIME type ...string. Unless others know of a URI someone has minted for MIME types, the actual string or your own URI is about all one can do. -- Scott On Feb 7, 9:37 pm, Joe <[email protected]> wrote: > I believe you may be mistaken. The specification declares a formal > range for format (see: "http://www.dublincore.org/documents/dcmi-terms/ > #terms-format"). > > On Feb 3, 12:32 pm, Scott Henninger <[email protected]> > wrote: > > > Joe; The range of dc:format is unspecified and it's type is > > rdf:Property, so the value can be either a resource (URI) or a > > literal. Literals don't run counter to linked data. They just > > represent a terminal node of the linked data graph. My recommendation > > would be to use the MIME type as a literal. > > > -- Scott > > > On Feb 3, 10:02 am, Joe <[email protected]> wrote: > > > > I was attempting to use Dublin Core's format property to define the > > > type of file cited as a source. Dubline Core calls for the object of > > > this predicate to be a resource, and even goes as far as to recommend > > > using iana's controlled medai types. Only problem is, these are > > > literals and there doesn't seem to be a recognized way of referencing > > > them in a "semantic-web" way. > > > > Maybe I'm just too much of a purist - yes, using literals will work > > > and that would be a pragmatic way to go, but it seems to run counter > > > to the idea of linked data, since these mime types are defined in > > > pretty serious detail, including RFC's etc... OK, ok, i'll just shut > > > up and use the literal. > > > > Term Name: format > > > URI: http://purl.org/dc/terms/format > > > Label: Format > > > Definition: The file format, physical medium, or dimensions of the > > > resource. > > > Comment: Examples of dimensions include size and duration. > > > Recommended best practice is to use a controlled vocabulary such as > > > the list of Internet Media Types [MIME]. > > > References: [MIME]http://www.iana.org/assignments/media-types/ > > > Type of Term: Property > > > Refines: http://purl.org/dc/elements/1.1/format > > > Has Range: http://purl.org/dc/terms/MediaTypeOrExtent > > > Version: http://dublincore.org/usage/terms/history/#formatT-001 > > > > On Feb 2, 10:07 am, Scott Henninger <[email protected]> > > > wrote: > > > > > Hello Joe; I'm not aware of any efforts to create URIs for MIME > > > > types. I'm not clear on the rationale or need for this, so maybe a > > > > bit more description on the problem you are trying to solve will > > > > help. In my experience a literal for the MIME type suffices and is > > > > usually preferred because the entity needing the MIME type will > > > > recognize the literal. > > > > > -- Scott > > > > > On Feb 1, 8:40 pm, Joe <[email protected]> wrote: > > > > > > Not a Top Braid question so much as one on proper nomenclature. > > > > > > I'm trying to determine whether or not there is any standard out there > > > > > on how to reference MIME Types using fully qualified URI's? In > > > > > particular "text/xml". > > > > > > I know there are several "ad-hoc" ways of doing this, but I'm looking > > > > > for something published by a reputable working group or consortium. > > > > > > Any and all advice welcome! > > > > > Thanks, > > > > > Joe -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
