Changes between Version 22 and Version 23 of DASISH/DiscussionPage


Ignore:
Timestamp:
04/25/13 09:02:01 (11 years ago)
Author:
sroth
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DASISH/DiscussionPage

    v22 v23  
    55Answers:
    66 
    7 1. Versioning: There is no real versioning system in Wired-Marker where versioning numbers (or the like) are stored. Instead, - and as long as Auto-caching is enabled in the settings dialogue - pages with markers (i.e. ~ 'annotations') are cached, i.e. saved as html + css files locally (OS X, default path: [/Users/(user name)/Library/Application Support/Firefox/Profiles/(profile name)/WiredMarker/cache/]. When using the 'Cache - Open cache' Wired-Marker function, users can thus get back to a physical 'snapshot' of the original state of the respective web page, which is a local copy though. These snapshots are established according to the URL + date + time range at the time of making an annotation on a specific web page. These data are used for creating a folder structure with a naming convention where among others date and time stamp information is included (example: ../WiredMarker/cache/2013/04/24/11/1a6beade73b701420ce943d404afd8ff/20130424111843). These are in turn checked against the the doc_url (example: [http://dasish.eu/dasishevents/]) and oid_date (example: 04/24/2013 11:18:43) fields of the marked (annotation) object in the local sqlite database, which makes the mapping between an annotated item and its locally cached parent web page version possible.
     71. Versioning: There is no real versioning system in Wired-Marker where versioning numbers (or the like) are stored. Instead, - and as long as Auto-caching is enabled in the settings dialogue - pages with markers (i.e. ~ 'annotations') are cached, i.e. saved as html + css files locally (OS X, default path: {{{/Users/user name/Library/Application Support/Firefox/Profiles/profile name/WiredMarker/cache/}}}. When using the 'Cache - Open cache' Wired-Marker function, users can thus get back to a physical 'snapshot' of the original state of the respective web page, which is a local copy though. These snapshots are established according to the URL + date + time range at the time of making an annotation on a specific web page. These data are used for creating a folder structure with a naming convention where among others date and time stamp information is included (example: {{{../WiredMarker/cache/2013/04/24/11/1a6beade73b701420ce943d404afd8ff/20130424111843}}}). These are in turn checked against the the doc_url (example: [http://dasish.eu/dasishevents/]) and oid_date (example: 04/24/2013 11:18:43) fields of the marked (annotation) object in the local sqlite database, which makes the mapping between an annotated item and its locally cached parent web page version possible.
    88
    992. Fragments: As far as representation of fragments is concerned, Olof has pointed out earlier on that Wired-Marker uses the "hyperanchor" format. This format is a concept of an extended form of URL that includes additional information (position or range in a web page, modification style, etc.). Included is also a version number which refers to the hyperanchor format version (example: #hyperanchor1.3:). For putting together the hyperanchor format path, the XPath syntax is used.
    1010 
    1111'Real example' for 'hyper-anchor code' from Wired-Marker:
    12 http://dasish.eu/dasishevents/#hyperanchor1.3%3A%2F%2Fdiv%5B%40id%3D%26quot%3Bwrapper-crumb-trail%26quot%3B%5D%2Ffollowing-sibling%3A%3Ap%5B1%5D(33)(3)(eve)%26%2F%2Fdiv%5B%40id%3D%26quot%3Bwrapper-crumb-trail%26quot%3B%5D%2Ffollowing-sibling%3A%3Ap%5B1%5D(71)(3)(ect)
     12{{{http://dasish.eu/dasishevents/#hyperanchor1.3%3A%2F%2Fdiv%5B%40id%3D%26quot%3Bwrapper-crumb-trail%26quot%3B%5D%2Ffollowing-sibling%3A%3Ap%5B1%5D(33)(3)(eve)%26%2F%2Fdiv%5B%40id%3D%26quot%3Bwrapper-crumb-trail%26quot%3B%5D%2Ffollowing-sibling%3A%3Ap%5B1%5D(71)(3)(ect)}}}
    1313
    1414[[BR]]
     
    1616 
    1717In URL decoded format:
    18 http://dasish.eu/dasishevents/#hyperanchor1.3://div[@id="wrapper-crumb-trail"]/following-sibling::p[1](33)(3)(eve)&//div[@id="wrapper-crumb-trail"]/following-sibling::p[1](71)(3)(ect)
     18{{{http://dasish.eu/dasishevents/#hyperanchor1.3://div[@id="wrapper-crumb-trail"]/following-sibling::p[1](33)(3)(eve)&//div[@id="wrapper-crumb-trail"]/following-sibling::p[1](71)(3)(ect)}}}
    1919
    2020We have implemented a transformation of this format to an xpointer:
    2121
    22 {{{
    23 http://dasish.eu/dasishevents/#xpointer(start-point(string-range(//div[@id=’wrapper-crumb-trail’/following-sibling::p[1]/text()[1],'',33)) /range-to(string-range(//div[@id=’wrapper-crumb-trail’]/following-sibling::p[1] /text()[1],'',77)))
    24 }}}
     22{{{http://dasish.eu/dasishevents/#xpointer(start-point(string-range(//div[@id=’wrapper-crumb-trail’/following-sibling::p[1]/text()[1],'',33)) /range-to(string-range(//div[@id=’wrapper-crumb-trail’]/following-sibling::p[1] /text()[1],'',77)))}}}
    2523
    2624This format can also be converted back to the hyperanchor format (if it uses a start-point and a range-to).