René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should setting id_ only set the local part of the ID?","articleBody":"Right now, properly setting custom IDs is somewhat counter-intuitive (to me).\n\nThe python-stix documentation has information on setting ID namespaces [1], which at present boils down to `set_id_namespace({\"http://MY-NAMESPACE.com\" : \"myNS\"})` which causes `myNS` to be registered as an alias for `http://MY-NAMESPACE.com`.\n\nAfter setting the namespace, IDs currently need to be set with the namespace alias in mind. For example: `sp = STIXPackage(id_='myNS:SomeID')` is required if you want to use `SomeID` instead of an auto-generated ID. However, I think this might trip some people up. I think some people would expect the `id_` kwarg to just set the local part, and that the API would automatically prepend the alias (e.g., `myNS`). For example, I could see people thinking that `sp = STIXPackage(id_='local_part_only')` would create a valid ID because the APIs would \"know\" to prepend the NS alias.\n\nThis issue is to discuss this point of view and, should there be a consensus, possibly modify the implementation of IDs. One outcome could be that if there is not a namespace alias set in the `id_` property, use the ID namespace. If there is a namespace alias set in the `id_` property, use the specified namespace alias.\n\nThoughts?\n\nNote: https://github.com/STIXProject/python-stix/issues/176 might be related\n\n[1] http://stix.readthedocs.org/en/latest/examples/index.html#id-namespaces\n","author":{"url":"https://github.com/MarkDavidson","@type":"Person","name":"MarkDavidson"},"datePublished":"2014-10-27T16:29:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/222/python-stix/issues/222"}