Re: [dxwg] Introduce mappingFrom and mappingTo properties (#810)

@aisaac great work tracking down examples! 

We have valid examples of both unidirectional and bi-directional mappings ( XSLT and cross-walks) so lets make sure we empower people to describe these. we have mappings in human readable form and machine readable form.  Its obvious this is useful to have in scope and it looks like there is an appetite to provide enough metadata to answer interesting questions such as @kcoyle suggests.

maybe we need  a subclass (narrower concept in this case) of "mapping" which is "specification of a conversion" - allowing "mapping" to be anything that allows you to get information about the relationship between two specifications with different conformance requirements (such as different schemas and/or different terms in values).


OTOH,  maybe dct:conformsTo will tell you the form of the mapping and that tells you if its a specification language.  (yes your system may need to include additional statements about the set of specifications to ask for things that can be converted using _any_ conversion formalism) 

I think property chain axioms could be introduced to make the profile the object of a "from" qualifier if this is not specified - but need to be careful it doesnt stop us being bi-directional.  Another wrinkle would be a conversion script that spits out multiple forms- i.e. does more than one conversion  (I've just written one that does that!)

So i think all the following are valid:
1) mapping from "this" profile X to a different profile Y (noting profile=specification through principles of reflexivity)
2) mapping from another specification  Y to this profile X
3) bi-directional mapping between X and Y
4) mapping from X to Y,Z.. etc

Can we identify a case where the combination of role="mapping", "to", "from" and "conformsTo" doesnt give us enough information to answer a query we think should be supported (and if necessary added to the competency questions for PROF)?




-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/810#issuecomment-533332898 using your GitHub account

Received on Thursday, 19 September 2019 22:30:55 UTC