Meeting minutes
Next week
dbooth: I'll be out. Erich Bremer offered to chair.
DICOM
erich: Discussion about etting a namespace for mapping DICOM enums to URIs. Grahame enquired from David Clooney.
detlef: There's an ont that defines thes URIs, though a few were not included.
… Can use the official DICOM namespace? Not possible.
… Some are describing units.
… Another list is of clinical terms.
… E.g., "US" means two different things, so they cannot use the same URI.
… Need to stick to what DICOM has defined. If they defined URI we can use them, otherwise we use a string or your own URIs.
… A few people think that David Clooney is right, and they'll have a hard time refactoring what DICOM has provided.
… Clooney thinks the enums cannot just be turned into URIs.
erich: How much do we RDF-ize things?
erich: RDF work that was done on DICOM seems to be that one section, and then they stopped.
ACTION: Erich to email DBooth DICOM ont link, and DBooth to intro Dave Beckett
erich: Also David Clooney thinks if there isn't DICOM community push, nothing will happen.
… Clooney shared his code w me.
… I'm all for pushing this forward.
… There was a group in California doing early DICOM work, and David Clooney was a part of it, but it stopped.
… DICOM ont on bioportal keeps getting downloaded.
Meta issue for DICOM: w3c/
detlef: RDF lists are a problem in SPARQL for retaining the order of polygon segments.
erich: But they could now be represented as well-known text strings.
… But they can't be indexed well.
erich: There's a binary version of well-known text, more array-like.
… And could be sent in RDF.
… But the problem: Unless your triplestore knows how to do spatial indexing, you want get the performance.
… I developed my own way of dealing w things. I sit on an image repo committee. Got invited w NIH person, and David Clooney sits onthese mtgs.
… My point: Although nice to do polygons in DICOM, they didn't think about spatial indexing. I convert them to Hilbert polygons, which allows my SPARQL to go quickly.
… Invited to talk about the spatial indexing problem.
dbooth: DICOM should deal w that.
erich: Would love a simple transfer syntax, but that won't be sufficient for efficient query.
erich: Re polygons, how about using well-known text?
detlef: It's an option.
erich: There is intrest in the geo SPARQL group.
… Jena and virtuoso have spatial indexing. Well-known text might be a better choice than other things.
… There's also well-known binary.
… Open Spatial added curved polygon.
… Seems like there is a well-known rep of each of the polygon types.
… Something like HDT binary RDF, when you store binhex strings, it stores it as a string, not binary.
… Will systems actually take advantage of the binary?
detlef: What if it's bitmaps instead of polygons? Lots are just huge blobs.
… Gray scale values.
erich: Is it in RDF as a string, or as a file reference?
detlef: I prefer external http reference.
… A JSON format offers both.
… That one uses binary data. What's the point of storing it as a string in RDF?
… The point of RDF is to link w other data.
erich: Have you looked at complex datatypes work in RDF? Might be a way to reference it.
detlef: Available yet?
erich: It's a proposal from Amazon group.
… I'd focus on today's tech.
erich: Can the sys take advantaage of the data? Does well-known text help?
… What about raster data?
… But RDF lists will not a useful form for it.
erich: In my processing, want to annotate images and link kthem spatially w other data.
dbooth: image processing is generally very specialized. Most RDF linkage is of the metadata for the image.
eric: Agree.
… Can we come up w concrete use cases we care about? I think we don't want the the binary image data in RDF.
erich: Curious what a DICOM server does when asked for raster data?
detlef: I think there's a header for returning binary.
ADJOURNED