Re: My task from last week: Semantic free identifiers

If you want to work with a more sophisticated API - I might suggest the OWL API. It's more powerful, but also more sophisticated +1!! Mark

RE: My task from last week: Semantic free identifiers

From: Sivaram Arabandi, MD [mailto:sivaram.araba...@gmail.com] Sent: Monday, June 20, 2011 8:42 PM To: Andrea Splendiani Cc: Michel_Dumontier; Chime Ogbuji; andrea splendiani (RRes-Roth); Vagnoni,Matthew M; James Malone; HCLS Subject: Re: My task from last week: Semantic free identifiers On Jun

Re: My task from last week: Semantic free identifiers

I would argue that "shooting oneself in the foot" may not be as much an issue as the one Wikipedia got into when it assigned personal names to topics, only to find there were others with the same name equally worthy of a topic. Jack On Mon, Jun 20, 2011 at 6:18 PM, Pat Hayes wrote: > If I might

Re: My task from last week: Semantic free identifiers

If I might summarize this debate, the arguments for using opaque and meaningless identifiers seem very similar to the argument that since there is a danger of shooting oneself in the foot, that therefore it is best to prevent this by having all feet surgically removed at birth. Still, HCLS is,

Re: My task from last week: Semantic free identifiers

On Jun 20, 2011, at 7:47 PM, Andrea Splendiani wrote: > Let's be precise. > I think everybody here would agree that to have opaque unique identifier is a > sensible policy for individuals more often than not. > To keep the analogy with relational databases, the issue is not whether ID > should b

RE: My task from last week: Semantic free identifiers

> Perhaps I'm getting the feeling that the different points of view reflects > a > different perception of OWL vs RDF ? > Just a thought. I'm much more likely to move triples via scripts than using > a tool. > > ciao, > Andrea You're partly right. I don't look at RDF/XML or turtle when I repres

RE: My task from last week: Semantic free identifiers

Re:dbpedia - Wikipedia's primary scheme involves using the label itself in the URI - of course since a term can have multiple meanings, it redirects you to a disambiguation page and provides links to each page providing a different meaning. The URI scheme works, but only because they control the

Re: My task from last week: Semantic free identifiers

Well... I don't think people is coding an information system by hand. Perhaps having a look at files with just and editor happens more frequently, and I don't think it can be avoided. Perhaps I'm getting the feeling that the different points of view reflects a different perception of OWL vs RDF ? J

Re: My task from last week: Semantic free identifiers

Am I correct in assuming that we are talking about Ontology models that are used to describe a domain and not the instance data? For sure, at the instance data level, using opaque identifiers, preferably generated, would be the way to go. Excellent point about databases, but I am not sure the

Re: My task from last week: Semantic free identifiers

Let's be precise. I think everybody here would agree that to have opaque unique identifier is a sensible policy for individuals more often than not. To keep the analogy with relational databases, the issue is not whether ID should be opaque or not, but whether Table and Column names should be opa

Re: My task from last week: Semantic free identifiers

On Mon, Jun 20, 2011 at 11:44 PM, Michel_Dumontier < michel_dumont...@carleton.ca> wrote: > IMHO, if you're still coding the content of an information system by hand, > then you're going to introduce errors. A database curator should never > assign their own identifier - this is internal to the te

RE: My task from last week: Semantic free identifiers

IMHO, if you're still coding the content of an information system by hand, then you're going to introduce errors. A database curator should never assign their own identifier - this is internal to the technology and the information system. If you're a programmer, you should query the resource (on

Re: My task from last week: Semantic free identifiers

I agree with Chime points. I will add that the great missing feature or tool is versioning and depreciation handling. I had a customer see a GUID URI once and freak out and almost drop a contract. Readability and maintainability is important. Enforcing uniqueness in literals is not part of the

RE: My task from last week: Semantic free identifiers

It's exactly the same reason why we have tables with incremental primary keys or have social security numbers for people and ISBN's for books. The identifier is meant to identify one thing, and should not clash with other things having similar or exact names. What that thing is, is up to you. B

Re: My task from last week: Semantic free identifiers

Consider the following: 1. Readability - the former is far more readable than the later: RO:part_of vs. - this becomes even more apparent in a triple (CO = a 'Cardiology Ontology'): CO:Mitral_valve

Re: My task from last week: Semantic free identifiers

Hello, On Mon, Jun 20, 2011 at 4:15 PM, M. Scott Marshall wrote: > The main reason is that when semantics and natural language are > inserted into identifiers, some identifers are doomed to become stale > as thinking evolves or changes about the semantic representation. Doesn't the defini

Re: My task from last week: Semantic free identifiers

Il giorno 20/giu/2011, alle ore 22.40, Chime Ogbuji ha scritto: > Hey Scott. Thanks for the detailed reply. See my response inline below > On Monday, June 20, 2011 at 4:15 PM, M. Scott Marshall wrote: > >> Hi Chime, >> >> The main reason is that when semantics and natural language are >> insert

Re: My task from last week: Semantic free identifiers

Hey Scott. Thanks for the detailed reply. See my response inline below On Monday, June 20, 2011 at 4:15 PM, M. Scott Marshall wrote: > Hi Chime, > > The main reason is that when semantics and natural language are > inserted into identifiers, some identifers are doomed to become stale > as thinkin

Re: My task from last week: Semantic free identifiers

I couldn't "agree" more with Andrea and Chime on this one. And would like to see some good reason(s) for us to continue to be burdened by them. The standard answer - 'tooling can help in managing the readability aspects' has been heard several times, and yet everyone seems to pass around 'raw RD

Re: My task from last week: Semantic free identifiers

Hi Chime, The main reason is that when semantics and natural language are inserted into identifiers, some identifers are doomed to become stale as thinking evolves or changes about the semantic representation. Or when a new 'name brand' is created for that namespace: I think that the best example

Re: My task from last week: Semantic free identifiers

Re: reasons for semantic free identifiers I think it depends on how you are using your data + schema. It may be the case that, for the most part, taking for granted the URI fragment or even just the label for a class and predicate gets you very far. I think it probably does in a lot of cases. Exce

Re: My task from last week: Semantic free identifiers

On Mon, 20 Jun 2011 12:53:51 -0700, Matt Vagnoni wrote: I tend to believe that "Perfect is the Enemy of Good". Then perhaps my hesitance (where I suggested that my own argument was possibly spurious) is a workable "Good" middle-ground? The identifier doesn't HAVE to be opaque, so long

Re: My task from last week: Semantic free identifiers

I think the point is not "having to use names". There are cases where IDs are just the best options (see my tax number). It's that in some case, and again, I had some use case in mind which is more "in the wild" than biomedical ontologies... if we want to define property for something that is more

Re: My task from last week: Semantic free identifiers

On Mon, 20 Jun 2011 12:53:51 -0700, Matt Vagnoni wrote: If instead we put the entire burden on the UI (and make the problem one solvable by a product) we could have some sort of Code Complete/Label Lookup, that you could start typing a label and it would offer suggestions? Nothing exist

Re: My task from last week: Semantic free identifiers

Ok, let me take half a step back and make one provocative statement: the step back: I was actually thinking more about something like GoodRelations, rather than biomedical ontologies. I have to admit the second is a more controlled environment. The provocative statement: If the bit about multilin

Re: My task from last week: Semantic free identifiers

> > When applied to instances (but not to Classes and Predicates) I am less > adverse to having non-semantic identifiers. Still, I haven't seen a really > good reason why that exceeds all the reasons to use semantic identifiers. > > Example number 2: hypothetical protein domains ( http://en.wiki

Re: My task from last week: Semantic free identifiers

Hello, On Mon, Jun 20, 2011 at 3:44 PM, Helena Deus wrote: >> thing"... By "right thing" I mean that I'm sure Hungarian semantic-webbers >> would have quite something to say about a decision to make the URI "partOf" >> rather than "A_0001" + multi-lingual labels.  It's a bit selfish of us >>

Re: My task from last week: Semantic free identifiers

I tend to believe that "Perfect is the Enemy of Good". It seems that everyone agrees at some point you need semantic identifiers. Look at the RDF, RDFS, and OWL standards. They don't use non-semantic identifiers (alphanumeric/guids) for core Classes and Predicates. The English-centric standard

Re: My task from last week: Semantic free identifiers

Hi all, thing"... By "right thing" I mean that I'm sure Hungarian semantic-webbers > would have quite something to say about a decision to make the URI "partOf" > rather than "A_0001" + multi-lingual labels. It's a bit selfish of us > English-speakers to create global infrastructures just for our

Re: My task from last week: Semantic free identifiers

On Monday, June 20, 2011 at 3:08 PM, Andrea Splendiani wrote: Hi, > sorry to jump on this thread like this... > > To be honest, I'm kind of concerned by the insistence on semantic-opaque > identifiers. I am as well and I have been for some time. > I understand the reason for them, > Actually,

Re: My task from last week: Semantic free identifiers

On Mon, 20 Jun 2011 12:08:43 -0700, Andrea Splendiani wrote: - in a continuum between web and semantic web, perhaps IDs are not only intended to be 'understood' by machines. Again, I understand the reason for them. But is it worth the reduced intuitiveness ? Or the added complexity to retai

Re: My task from last week: Semantic free identifiers

Hi, sorry to jump on this thread like this... To be honest, I'm kind of concerned by the insistence on semantic-opaque identifiers. I understand the reason for them, but I think they clash a bit with other considerations: - there is a lot of verbosity paid for having RDF 'readable'. Opaque identi

RE: My task from last week: Semantic free identifiers

Consider this: SELECT ?name WHERE { ?s :contains :MRN; ?s a :Patient; rdfs:label ?name} --VERSE-- SELECT ?name WHERE { ?s ?p ?o; rdfs:label ?name. ?p rdfs:label "contains". ?o rdfs:label "Master Record Number". ?s a ?type.

RE: My task from last week: Semantic free identifiers

We've faced the problem of formulating SPARQL queries using alphanumeric identifiers, and have developed software to make queries using the labels : http://www.slideshare.net/elmccarthy/sparql-assist-language-neutral-query-composer http://sadiframework.org/content/2010/11/29/sparql-assist-langu

Re: My task from last week: Semantic free identifiers

It is a burden to carry this prefix file and maintain it, but its better than not being able to do anything about it. ...from phone On Jun 20, 2011 3:47 AM, "James Malone" wrote: Hi, On last week's call I was tasked with contacting Chris and Alan regarding the form of the Relations Ontology UR

RE: Reminder - Scientific Discourse concall Mon., 20 Jun 2011, 10am EDT - Executable Documents

A link to the Executable paper challenge and my slides can be found here: http://www.w3.org/wiki/HCLSIG/SWANSIOC/Actions/RhetoricalStructure/meetings/20110620 Best, - Anita. Anita de Waard Disruptive Technologies Director, Elsevier Labs http://elsatglabs.com/labs/anita/ a.dewa

My task from last week: Semantic free identifiers

Hi, On last week's call I was tasked with contacting Chris and Alan regarding the form of the Relations Ontology URIs. There was some concern that the current text fragment (e.g. part_of) would be replaced with a semantic free identifier (e.g. RO_001). They confirmed this is the case. The