Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357548 - Reengineer ageRange and householdIncome attributes to use fixed ranges
Summary: Reengineer ageRange and householdIncome attributes to use fixed ranges
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Higgins (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Trevithick CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-13 15:40 EDT by Paul Trevithick CLA
Modified: 2016-11-09 16:28 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Trevithick CLA 2011-09-13 15:40:33 EDT

    
Comment 1 Paul Trevithick CLA 2011-09-14 18:30:20 EDT
I have committed changes to mapping.owl and fp.n3 and persona to support attribute whose values are integer intervals (e.g. x-y where x is an integer and y is an integer). E.g. an ageRange attribute whose possible values are "13-18", "19-24", etc. I have added a mapping rule called "roleLiteralRange" to mapping.owl
Comment 2 Paul Trevithick CLA 2011-10-07 16:46:14 EDT
Done. I created a new mapping function: roleDiscreteRange() relies on a new mapping approach that maps individual members of some subclass of p:DiscreteRange to individual members of another subclass of p:DiscreteRange. So now a value like "13-18" would be an instance of DiscreteRange and have a map:sameAs link pointing to (I'll be optimistic here and take an easy case) a member "13-18" in the other p:DiscreteRange.
Comment 3 Paul Trevithick CLA 2011-10-07 16:47:02 EDT
See previous comment. Forgot to click RESOLVED