Re: Annotating HTML: Distinguishing between annotating the source and the rendition

Hi Simone and Paolo,
This case seems very similar to the one we are addressing in Pundit and
that has been discussed some times ago in this ML.
We are currently using XPointers for that and rely on specific HTML markup
to represent "named content", that are pieces of HTML with a resolvable
URLs and that can be included in different web pages (with different URLs).
We shortly describe our solution here:
http://thepund.it/client.php(section: Play nice with Pundit).
We didn't implement the new OA specs yet, but I was planning to use a
specific XPointer selector and a oa:specificResource where the
oa:hasSources points to the "named-content" instead of to the embedding web
page + a specific property pundit:hasPageContext used to remember the URL
of the embedding Page (we need it at application level).

Example:

   as:fragment1 a oa:SpecificResource ;
       # The selector tells the application how to select this resource
(e.g. using xpointer or other mechanisms.)
       oa:hasSelector as:selector1 ;
       oa:hasSource <http://example.org/named-content3>;
       pundit:hasPageContext <http://example.org/page3.html> .

   as:selector1 a oa:FragmentSelector ;
       a pundit:XPointerFragmentSelector ;
       rdf:value "xpointer(....)".


Hope this helps.

best,

Christian

On Fri, Sep 28, 2012 at 5:40 PM, Paolo Ciccarese
<paolo.ciccarese@gmail.com>wrote:

> Hi Simone,
> If you look at the "Text Selector by Quotation" (
> http://www.openannotation.org/spec/extension/)  we wrote:
> The text to be quoted should be normalized to a readable string before
> recording. Thus HTML/XML tags should be removed, character entities should
> be reduced to the character that they encode, redundant whitespace should
> be normalized, and so forth. This allows the Selector to be used with
> different encodings and still have the same semantics and utility.
>
> As I have the same need I was initially thinking to add a flag to that
> selector, keep the markup and still normalize whitespaces. But that is in
> contrast with the above definition.
> An alternative is to use a different kind of selector with XPath to point
> to the desired DOM element. Would that work for you?
>
> Paolo
>
>
> On Fri, Sep 28, 2012 at 10:55 AM, Simone Sacchi <sacchi1@illinois.edu>wrote:
>
>> Hi all,
>>
>> I have a quick question: is it possible to represent explicit whether
>> (for an HTML page) you are annotating the HTML source code or the
>> rendered text in the browser? I couldn't figure it out...
>>
>> My particular case is one in which you can have the same rendered text
>> (or entire page) using different HTML source codes. I would like to
>> explicitly point to the rendered component and the corresponding
>> selection in the source code.
>>
>> Thanks a lot in advance for any reply,
>> Simone
>>
>> -------------------------------------------------------------------------------------------------------------------------------------
>> Simone Sacchi
>> Research Assistant - Center for Informatics Research in Science and
>> Scholarship
>> Ph.D Student - Graduate School of Library and Information Science
>> University of Illinois at Urbana Champaign
>>
>> Email(s): sacchi1@illinois.edu - simo.sacchi@gmail.com
>> Skype: simone.sacchi
>>
>> ------------------------------------------------------------------------------------------------------------------------------------
>>
>>
>>
>
>
> --
> Dr. Paolo Ciccarese
> http://www.paolociccarese.info/
> Biomedical Informatics Research & Development
> Instructor of Neurology at Harvard Medical School
> Assistant in Neuroscience at Mass General Hospital
> +1-857-366-1524 (mobile)   +1-617-768-8744 (office)
>
> CONFIDENTIALITY NOTICE: This message is intended only for the
> addressee(s), may contain information that is considered
> to be sensitive or confidential and may not be forwarded or disclosed to
> any other party without the permission of the sender.
> If you have received this message in error, please notify the sender
> immediately.
>
>