<br><br><div class="gmail_quote">2009/1/9 Evgeny Egorochkin <span dir="ltr"><<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c"><br>
<br>
</div></div>I should have written this a bit earlier.<br>
<br>
<a href="http://xesam.org/main/Hackfest2008/Ontology" target="_blank">http://xesam.org/main/Hackfest2008/Ontology</a> mentions link-by-id refinement. It<br>
wasn't voted on or discussed widely though, so let's do it now...<br>
<br>
The idea is to treat content authorship as a special case and<br>
refine "dangling" link representation:<br>
</blockquote><div><br>I must admit that I am having some problems parsing your message, so I'll riposte with some questions :-)<br><br>First: Are we talking xesam:creator only here or are we discussing a more general idea? <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1) xesam:creator chilren are allowed to only link to xesam:ContactMedium of<br>
xesam:Contact, which is consistent with the way it's usually done in RDF<br>
world.<br>
<br>
2) Links by ID between documents are resolved directly to URI of the<br>
document(s) if it exists, or a dummy Document of appropriate type is created<br>
with ID assigned to it and xesam:Source set to xesam:Unavailable.<br>
<br>
Examples:<br>
1) BookA references ISBN:xxx and there's a BookB with ISBN:xxx ==><br>
user:BookA xesam:links user:BookB<br>
2) BookA references ISBN:xxx and there's no document with ISBN:xxx ==><br>
user:BookA xesam:links user:DummyBookB.<br>
user:DummyBookB rdf:type xesam:Document;<br>
rdf:type xesam:Unavailable; # or maybe don't specify Source<br>
xesam:isbn "xxx".<br>
if BookB with ISBN:xxx appears, (2) is replaced with (1)<br>
<br>
pros:<br>
* no need to turn all IDs into URIs</blockquote><div><br>We still want globally unique IDs, no? I can't see how that is possible without URI schemes <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* direct links work much faster</blockquote><div><br>What do you mean direct link? You link to BookB via its URI user:BookB just like one would use any other id... <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* better handing of dangling links:<br>
- links to available and unavailable objects "look" the same to applications<br>
- dummy objects can have an appropriate type like Document or Media and be<br>
properly displayed</blockquote><div><br>As far as I can see the model described in the wiki can handle what you describe just fine..? <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* documents can't be authored by audio files</blockquote><div><br>This is a bit academic, but true. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
cons:<br>
* reason for linking isn't specified when both objects are available. This<br>
doesn't seem to matter to users for links by ISBN and such.<br>
* if there are 2 documents with the same ISBN(eg PDF and ODF versions), a link<br>
by ISBN would target both of them. However, to properly link the second<br>
document, the reason for linking(ISBN reference) must still somehow be<br>
available<br>
* xesam:creator sort of feels like a createdBy relation<br>
</blockquote><div><br>I must admit that I am pretty lost here... I this all about making xesam:creator a relation-but-not-quite? <br></div></div><br>-- <br>Cheers,<br>Mikkel<br>