Comments (8)
I could see multiple targets any of which may or may not have contiguous geometry. Why prevent it?
from web-annotation.
as long as it can be expressed in SVG, it should be fine. We can't make our own "SVG profiles" that requires shapes to be continuous or something.
from web-annotation.
The discussion during the CG was that multiple non-contiguous shapes should be separate targets in the model, to avoid multiple ways of expressing the same thing (multiple targets) and to ensure that each target region had the opportunity for identity (via the SpecificResource).
If we don't feel those are important distinctions to maintain, then we can drop the single shape requirement.
from web-annotation.
I think it becomes a difficult thing to enforce or check. What might at
first glance in the SVG look like non-contiguous, could be shown to be
contiguous in rendering - for instance a trianglethat is close to a circle
- you will need to do precise calculations to see if it is a contiguous
shape or not - but why should it matter?
Perhaps the best is to simply keep it as "Multiple non-contiguous shapes
SHOULD be separate targets, this ensures that each target region gets an
identity".
On 8 April 2015 at 15:56, Rob Sanderson [email protected] wrote:
The discussion during the CG was that multiple non-contiguous shapes
should be separate targets in the model, to avoid multiple ways of
expressing the same thing (multiple targets) and to ensure that each target
region had the opportunity for identity (via the SpecificResource).If we don't feel those are important distinctions to maintain, then we can
drop the single shape requirement.—
Reply to this email directly or view it on GitHub
#17 (comment).
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
from web-annotation.
+1 for this. I agree that it will be hard to enforce, which makes me think
its within the boundaries of best practice rather than something the data
model can outright forbid.
On Thu, Apr 9, 2015 at 4:26 AM, Stian Soiland-Reyes <
[email protected]> wrote:
I think it becomes a difficult thing to enforce or check. What might at
first glance in the SVG look like non-contiguous, could be shown to be
contiguous in rendering - for instance a trianglethat is close to a circle
- you will need to do precise calculations to see if it is a contiguous
shape or not - but why should it matter?Perhaps the best is to simply keep it as "Multiple non-contiguous shapes
SHOULD be separate targets, this ensures that each target region gets an
identity".On 8 April 2015 at 15:56, Rob Sanderson [email protected] wrote:
The discussion during the CG was that multiple non-contiguous shapes
should be separate targets in the model, to avoid multiple ways of
expressing the same thing (multiple targets) and to ensure that each
target
region had the opportunity for identity (via the SpecificResource).If we don't feel those are important distinctions to maintain, then we
can
drop the single shape requirement.—
Reply to this email directly or view it on GitHub
#17 (comment).Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718—
Reply to this email directly or view it on GitHub
#17 (comment).
from web-annotation.
I am inclined to agree with Stian point as well. It would be nice to have always the same behavior but if we cannot validate it easily we cannot enforce it either. I have not implemented SVG selectors myself so I would rather rely on the opinion of who did or tried to. For instance, I am not sure on what would happen to a client, which expects one shape only, when multiple shapes are defined in the same target.
from web-annotation.
So no change, and leave as a SHOULD/RECOMMEND. Fine by me. Will leave the issue open in case others want to chime in to disagree, but will close (wontfix) next week if there's no further discussion.
from web-annotation.
Resolved in October WD.
from web-annotation.
Related Issues (20)
- ID of specific resources not used in examples ...
- Wrong ORCiD for Robert Sanderson, Web Annotation Data Model spec editor HOT 1
- Representing a selector that indicates a page range of a book HOT 3
- label property should allow internationalized text
- Confusing disparity between names in data model and vocabulary HOT 3
- Include missing classes as super class of Selector HOT 2
- wrong type in collection_frame.jsonld? HOT 4
- Protocol refers to modified on AnnotationCollection, but not mentioned in Model
- Selector JSON to IRI/URI Mapping: supporting compound fragments so that SPAs work HOT 2
- Percent-encoding in fragment identifier syntax
- oa:assessing missing from anno.jsonld context HOT 1
- Viewport for SvgSelector
- How to hint at previous versions of an annotation? HOT 2
- Comparison of inline examples with the example files from web-platform-tests
- Support mixture of Range Selector, node index and text position HOT 2
- "at exactly 0 or more" should be "(exactly) 0 or more"? HOT 2
- Cloudflare is too afraid to grant me read access to w3.org HOT 2
- Are there any scenarios for multi-licensing of annotations?
- Is id always mandatory for bodies and targets? In example 19 seems not.
- Is it allowed to use annotations as bodies and targets?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from web-annotation.